Free WordPress Theme Detector

Paste a site's address and see which WordPress theme it runs, who made it and which plugins we can spot. Free, no account needed.

What Is a WordPress Theme Detector?

Quick answer: A WordPress theme detector reads the public page of a site and reports which theme it appears to run. Paste an address above, press Get Info, and read the theme name, author and plugins we can spot. Try it on a site you like.

A design catches your eye and you think, what WordPress theme is that? This free WordPress theme detector reads what any visitor can see: the page's stylesheet and script addresses.

Know the limits: it is strongest on directory themes, isn't a security scan, shows no WordPress version or host, and guesses from page clues.

How to Find Out What WordPress Theme a Site Is Using

Four steps answer "what WordPress theme is this site using?"

Copy the address. Add https:// or leave it off. Text that is not a web address gets "The url must be a valid URL." We read only that page, so use the home page.
Paste it and press Get Info. A first check took about half a second to over 15 seconds in our tests, longer on slow sites.
Read the theme card. Under Result you get name, version, author and rating where they exist, plus a Demo button and sometimes Download.
Check the plugin list. The heading reads "Our detection tools have found N plugins", and each card offers Download, Learn More or Search Plugin.

If you get a message instead of a theme: the sections below say why, and checking by hand still works. Or check another site.

What the WordPress Theme Checker Shows You

Ratings and download counts come from the WordPress.org theme directory, so only listed themes have them.

Result field	Where it comes from	How far to trust it
Theme name	The Theme Name line in a stylesheet header, else the directory, else our 19 well-known themes	Good for directory themes and readable headers, weak for custom themes with neither
Version	The style.css theme header if we read one, else the newest directory release	The site's own when the header is read, the newest release when not, a dash when a markup pattern names the theme
Author, rating, downloads	Author from the header or directory, the rest from the directory	Rating and downloads stay blank on custom themes
License	One fixed GPL line, even over an MIT header	Ignore it
Demo and Download	Demo opens the Theme URI, a WordPress.org page, or this page again; Download needs a directory theme or a built-in commercial theme	A theme link, not a demo of that site's setup; Download points at the newest release or the seller's page, not the installed version

How WordPress Theme Detection Works

Our server, not your browser, downloads the page you entered.
Stylesheet links ending in style.css are collected, else any under /themes/, else any CSS file. Only full addresses count.
A stylesheet in the folder the page refers to most often is opened first, then that folder's own style.css, then the others in turn, until one yields a theme stylesheet header: Theme Name, Theme URI, Author URI, Text Domain and Template.
The folder the page refers to most often under /themes/ is the theme folder, which the WordPress.org directory is then asked about.
Last, 19 well-known, mostly commercial themes are checked, plus markup patterns for 8 families, such as Genesis; a markup match names the theme only when no header or directory entry named a different one.

The catch: a header can only be read if the theme's style.css answers and still carries it, so a blocked file, or one with the header stripped or minified away, leaves nothing to read.

By hand, use view source and search for wp-content/themes/, or /themes/ if wp-content was renamed; the folder after it is the theme. See our full guide to finding a WordPress theme by hand.

Real Sites We Ran Through the Detector

In October 2026 we ran 17 live WordPress sites through the detector and checked each against the page source. Six are below, plus a control.

Site	What it really runs	What the detector showed	Verdict
The official Astra preview	Astra 4.14.1	Astra 4.14.1	Correct
wordpress.org/news	A custom theme, 1.0.0	Same name and version	Correct
A theme maker's own site	A child theme on Neve 4.2.3	Neve 4.2.3, no child	Parent shown, child missed
A large news publisher	A custom theme, public style.css	Its name and version, 2 plugins	Correct
A personal blog	A child of Twenty Thirteen	A raw PHP error	Error
A WordPress hosting company	WordPress, no theme files linked	The not-WordPress message	Wrong
example.com	Not WordPress	The same message	Correct

It named the site's theme on 9 of 17 sites, and the version matched the site's own style.css each time. Three showed the parent instead of the child, one showed a framework instead of the site's own theme, two pages that link no theme files went unnamed, and two failed differently. These are single runs, so read them as examples. Test your own site, then confirm in style.css.

Child Themes and Parent Themes

Child themes borrow a parent theme's design and name it in the Template header of their style.css. When the detector reads that header, the card adds a Parent theme line.

The card shows the theme folder the page refers to most often. That is the child when most of the page's theme files come from it, but a page can link its parent's files more, and then the parent shows without its child. On real sites a Neve child and an Astra child came back as their parents, and on one site whose header could not be read, a Genesis Framework markup match took the place of its own theme.

How to check: if a custom-looking site gets a famous theme's name, open the style.css of each other theme folder in the page source and look for a Template line naming it.

Why a WordPress Theme Detector Sometimes Gets It Wrong

A WordPress theme finder sees only what the page exposes.

Situation	What you will see	What to do
Not a WordPress site	"The site https://example.com/ does not seem to be using WordPress."	Search the source for wp-content.
Custom theme with no readable header, or a page that links no theme files	"The theme that this site uses does not exist in our database", but only if a plugin turned up too. With none, the not-WordPress message.	Open its style.css yourself.
Optimized or headless WordPress (a separate front end): combined CSS, hidden asset paths, no theme or plugin files in the page	No theme, no plugins, the not-WordPress message on a WordPress site.	Look in the source for wp-content, or open /wp-json/, the REST API.
Stylesheet header removed or minified away	A message, unless the folder matches a directory theme or the page carries a known theme's markup.	Find the folder in the page source, open its style.css.
Blocked request or failing page	A short message, such as "We could not find that website. Check the address for typos." or "The site answered with HTTP 403."	Open it in your browser. If it loads, a firewall or Cloudflare rule probably blocks us.

We keep a cached page until the end of the day, midnight Pacific time, failures included, so a retry after a site comes back may show the old message.

An empty result is a reason to look by hand, not proof the site isn't WordPress. The reverse happens too: a test page that only linked to a directory theme was reported as running it.

WordPress Plugin Detector: What Shows Up

Plugins show up when a stylesheet or script loads from wp-content/plugins, or the page carries a marker, such as the Yoast SEO comment or Elementor's page builder markup. Each plugin slug, the plugin folder name, is then looked up in the WordPress.org plugin directory.

Plugins that load nothing on public pages never appear, and plugin versions never show. We saw 13 plugins on a publisher's home page and 0 on a plain theme preview.

What We Fetch and Cache

Our server sends a plain GET request for the page you enter and a few of its files, with no login and nothing submitted. It caches the fetched page for the day.

A WordPress theme lookup sends WordPress.org folder names, not your address. For custom themes, your browser may load the preview from a WordPress.com screenshot service, which receives the address you typed.

Related Free Tools

For design inspiration or competitor research, web designers and freelancers can continue here:

Hosting Checker: finds who hosts the site.
Website Screenshot Generator: captures its design.
Website SEO Score Checker: runs an SEO audit, page speed included.
Meta Tag Analyzer: reads its title and description.
WordPress Password Generator: turns a password you type into a WordPress password hash.
All free website management tools: the full category.

Frequently Asked Questions

Frequently Asked Questions (FAQs) is a list of common questions and answers provided to quickly address common concerns or inquiries.

How do I find out what WordPress theme a website is using?

Paste the address, with or without https://, into the tool above and press Get Info. By hand, view the page source and search for wp-content/themes/; the folder name after it is the theme. Open that folder's style.css to read the Theme Name header.

Is this WordPress theme detector free?

Yes, it costs nothing, and there is no account to create and nothing to install. Most of what it shows comes from the public page you enter and the WordPress.org directory, with a built-in list of well-known themes filling some gaps.

Is this WordPress theme detector accurate?

Partly. In our October 2026 tests of 17 live WordPress sites it named the theme on 9, showed a parent or framework instead of the child on 4, named none on 2 whose pages link no theme files and failed on 2. Confirm in style.css.

Can the detector tell me whether a theme is a child theme?

Partly. When the theme's style.css header has a Template line, the card adds a Parent theme line. The card shows the one theme folder the page refers to most often, though, so a child can appear as its parent. To check, open the theme's style.css and find the Template line.

Why does the detector say a WordPress site is not using WordPress?

Because we found no theme we recognize and no plugin, and the message isn't a real WordPress check. Minified or headless sites, pages that link no theme or plugin files and custom themes with a stripped header and no visible plugin can trigger it wrongly. Search the page source for wp-content before concluding.

Why can I not find the theme of a WordPress site?

Usually the theme is custom or the page hides it. Stripped stylesheet headers, minified stylesheets, a blocked style.css and pages that link no theme files all keep the name from us. Try the manual check: several custom themes we checked published a readable style.css with the Theme Name line.

Is the version number the detector shows the one the site runs?

Not always. When the theme's style.css header is read, the card shows the version the site runs, unless one of our markup patterns names the theme, which leaves a dash. When the card falls back on the WordPress.org directory, it shows the newest release instead. The Download button, when it shows, points at the newest release or the seller's page, not the installed version. To confirm, read the Version line in style.css, or the ver= value on the theme's stylesheet link where it is a version number.

Can it detect WordPress plugins too?

Yes, the ones that load a stylesheet or script from /wp-content/plugins/, plus a few that leave a comment or marker. Each card links to a download or search. Anything that loads no front-end file stays hidden, and no plugin versions appear.

Does checking a site affect it or alert the owner?

It doesn't change the site or send an alert, but it isn't invisible. Our server makes a plain GET request for the public page and a few of its files, with no login or form submission. Server logs and firewall dashboards can show the visit.