Free · No signup · Reads only the public home page
Recently detected
Most detected across 889 scanned sites
Themes
- 1
Hello Elementor95 sites - 2
Astra68 sites - 3
WoodMart34 sites - 4
Kadence19 sites - 5
GeneratePress17 sites - 6
Divi16 sites
- 7
Inspiro16 sites - 8
Blocksy13 sites - 9
Foodica13 sites - 10
Inspiro PRO12 sites
Plugins
- 1
Elementor329 sites - 2
WooCommerce213 sites
- 3
Contact Form 7196 sites
- 4
Elementor Pro159 sites - 5
Jetpack97 sites
- 6
Site Kit by Google92 sites - 7
LiteSpeed Cache79 sites - 8
ElementsKit Lite70 sites - 9
Social Icons, Share Buttons & Click to Chat by WPZOOM68 sites - 10
Hostinger Reach66 sites
What the detector reveals
Theme, with its history
Name, version, author and whether it’s a child theme. Free themes link to their ranking, active installs and daily download history across 8,582 tracked themes.
Plugins the page loads
Every plugin referenced on the home page, matched against 51,555 WordPress.org plugins and our premium catalog. Ones with a stats page come first.
Hosting and stack
WordPress version, hosting provider, CDN, web server and PHP version, where the site exposes them.
Who else uses it
Every theme and plugin page lists real sites detected running it, from 889 scanned sites so far.
How it works
- Fetch the public home page the way a browser would. No login, nothing installed on either side.
- Read what WordPress leaves in the HTML: theme and plugin directory paths, the theme’s style.css headers, the generator tag and response headers.
- Match against our catalog of tracked free themes and plugins and the premium products we monitor, and link each result to its page here.
Results are cached for 24 hours per site. Scans read only public information.
Frequently asked questions
How accurate is the WordPress theme detector?
Very accurate for the theme: WordPress prints the active theme’s directory in the page source, and the detector reads the theme’s own style.css for its name, version and author. Plugins come from three signals: the assets they load on the home page, the routes they register in the site’s REST API index, and markup they leave behind (comments, generator tags, class names). Plugins that do none of those — many back-end tools — stay invisible, and each result says which signal found each plugin.
Does it detect child themes and their parent?
Yes. When the active theme declares a Template in style.css, the result shows the child theme with its parent underneath, and the ranking, install and rating figures come from the parent’s page in our catalog.
Can it identify premium themes like Divi, Avada or Flatsome?
Yes. Premium themes and plugins aren’t on WordPress.org, so we match their directory names against our premium catalog, which tracks real-world usage across the web. Anything we can’t match is shown by name with a “custom / unlisted” label rather than guessed.
Why does it say no theme was found?
A few sites hide their stack: headless front ends, aggressive optimisation plugins that inline or rename assets, custom wp-content paths, or a firewall that blocks automated requests. In those cases the detector reports what it could and could not see instead of guessing.
Is the tool free, and do I need to install anything?
It’s free, runs in the browser, and needs no extension, account or plugin. Scans only read the site’s public home page, the same way a visitor’s browser does.
Does it show the WordPress version and hosting provider?
When the site exposes them. The WordPress version comes from the generator tag or core asset versions, the hosting provider from response headers and host-specific must-use plugins, and the CDN from headers such as Cloudflare’s.