Skip to content

WordPress Theme Detector - Identify Any Site's Theme

How the WordPress theme detector works

Our server fetches the page you enter and checks the HTML for wp-content/, wp-includes/ and wp-json/ paths and a generator meta tag mentioning WordPress. If it finds them, it reads the theme slug from the first wp-content/themes/{slug}/ path and collects every distinct wp-content/plugins/{slug}/ path, including ones escaped inside JSON. Plugin slugs are turned into names, so wordpress-seo shows as Yoast SEO and js_composer as WPBakery Page Builder. The same scan also lists analytics, fonts, CDN, hosting and server software.

Example

On techcrunch.com the theme slug is tc-24, a custom theme with no public listing, and the generator tag gives WordPress 6.9.11. Plugins on the home page include sailthru-widget and a premium JW Player plugin. That is typical of a large publisher: the theme is built in-house, so knowing the slug tells you how the site is built rather than what to buy. On smaller sites the slug is more often a theme you can find in the directory, such as astra, kadence or twentytwentyfive.

Limits

Only the page you enter is checked, up to 2 MB. Plugins that load only on certain pages, such as a form plugin on the contact page, appear only when you check that page. Plugins that run entirely on the server never appear. For a Shopify store, use the Shopify theme detector, which reads the theme name, version and Theme Store ID.

Related Tools

Frequently Asked Questions

How do I find out what WordPress theme a site is using?
Paste the URL above and press Analyse. WordPress loads theme files from wp-content/themes/{slug}/, and the tool reads the slug from those paths. To do it by hand, view the page source and search for wp-content/themes/.
Why does it show a slug instead of the theme's full name?
The slug is the theme's folder name, which is all the page source contains. For directory themes it usually matches the name: astra is Astra, generatepress is GeneratePress. For custom themes it is whatever the developer called the folder. The theme's style.css, at wp-content/themes/{slug}/style.css, has the full name, author and version in its header.
What about child themes?
A site on a child theme loads files from both the child and the parent folder. The tool reports the first theme folder it finds in the HTML, which may be either. Search the page source for wp-content/themes/ to see both.
Can it detect WordPress plugins?
Plugins that load a file from wp-content/plugins/ show up with a name and, for free plugins, a link to wordpress.org. Plugins that only run on the server, such as most security and backup plugins, add nothing to the page and can't be detected. Caching plugins that combine assets into one file can hide the others.
Why can't it find the WordPress version?
It reads the version from the generator meta tag, which WordPress adds by default and many security plugins remove. Without the tag, WordPress is still detected from wp-content, wp-includes and wp-json paths, but no version is shown.
Why does it say the site isn't WordPress when I know it is?
The site may be headless, with WordPress serving content to a separate front end built in Next.js, Astro or similar, so the HTML has no wp-content paths. A CDN or optimisation plugin that rewrites asset URLs to another domain has the same effect.