What WordPress Theme Is That?
Ever wondered what WordPress theme a site is using? Enter any URL to inspect its live HTML source, active theme, child framework, plugins, and hosting stack.
What WordPress Theme Is That Site Using? Look Under the Hood in Three Seconds
You stumble across a blog, online store, or SaaS marketing site that feels ridiculously fast and clean—and your first instinct is to wonder what theme and plugins are running underneath. Right-clicking View Source and hunting through forty minified stylesheet tags works, sure, until you hit a child theme folder or a site that bundled its CSS with WP Rocket. This WordPress Theme Detector automates the entire detective pass right in your browser: drop in any URL (or paste raw page HTML for strict firewall-protected sites), and it reads the live theme stylesheet header, resolves parent/child theme chains, identifies over forty-five popular SEO, caching, form, and builder plugins, and flags the CDN or hosting stack powering the domain.
How Live Detection Traces a Theme
Enter Any Website URL
Type or paste the domain or specific page URL you want to inspect—whether it is a homepage, blog post, or WooCommerce product page—and click Detect Theme & Plugins.
Inspect Theme & Parent Framework
Review the detected theme name, version, author, pricing tier, and live screenshot. If the site uses a child theme, inspect the resolved parent framework card right beneath it.
Filter Plugins by Category
Browse detected SEO suites, page builders, caching layers, form builders, and e-commerce engines—complete with WordPress.org directory links and exposed version tags.
Use Source Mode for Firewalled Sites
Running into a bot challenge on a locked-down site? Press Ctrl+U in your browser, paste the page HTML into Paste HTML Source mode, and run the exact same audit locally.
How WordPress Theme & Plugin Detection Actually Works (and Why Some Plugins Stay Invisible)
Every standard WordPress theme is required by WordPress core to carry a comment header at the very top of its root style.css file. That single block declares the Theme Name, Author, Version, and—when someone builds a custom child theme on top of a framework like GeneratePress, Astra, or Kadence—a critical line called Template. When you check a domain with our detector, it first parses the rendered HTML for /wp-content/themes/ asset URLs and WordPress 6.4+ body classes (wp-theme-* and wp-child-theme-*), then fetches that style.css file directly to verify the exact human-readable metadata rather than guessing solely from folder names.
Plugin detection works in two layers because modern speed tools complicate things. On a standard site, plugins enqueue public stylesheets and scripts from /wp-content/plugins/<plugin-slug>/, often carrying ?ver= query strings. Our first pass maps those slugs directly to official WordPress.org repository entries. However, once a site activates WP Rocket, LiteSpeed Cache, FlyingPress, or Autoptimize, individual CSS and JS files get merged into combined bundles. That is where our second signature pass steps in—scanning HTML comments left by Yoast SEO or Rank Math, class prefixes like .elementor-section, .gb-container-, .brxe-, or .gform_wrapper, and inline JS configuration globals.
Just as helpful is knowing what no public theme detector can see—and why. Back-end-only plugins such as UpdraftPlus backups, WP Mail SMTP, Redirection, editorial calendar plugins, or server-side security rules rarely inject a single byte into the public front-end HTML. If a site looks like it only runs four plugins, that usually means four plugins load front-end assets while another dozen quietly run on the server inside wp-admin.
You will also run into "bespoke" or obfuscated setups. Agencies building on Roots Bedrock move /wp-content/ to /app/, security plugins like Solid Security or WP Hide rewrite asset paths, and headless WordPress builds serve a Next.js or Astro frontend while keeping WordPress purely as a REST or GraphQL API CMS. When a site exposes no /wp-content/ paths at all, check the Architecture badge and Footprint Notes—our detector still looks for api.w.org REST headers and wp-block markup before telling you WordPress is absent.
Before rushing to buy the exact theme you just discovered on a high-ranking competitor site, take a quick look at the whole stack together. Often a site looks crisp not because of a $99 multipurpose theme, but because the developer started with a lightweight shell (like GeneratePress, Blocksy, or Kadence) and paired it with clean block patterns and solid typography. If a site loads twenty-five heavy plugin scripts and a legacy shortcode builder, you can replicate the layout far faster—and score higher on Core Web Vitals—using a lightweight block theme instead.
What the HTML Source Scan Uncovers
Live style.css Header & Screenshot Extraction
Goes beyond guessing folder names—automatically fetches the theme’s live style.css file to read Theme Name, Author, Version, License, and official homepage links, plus loads the real screenshot.png preview.
Parent & Child Theme Chain Resolution
Many custom sites run a white-labeled child theme (like acme-child). Whenever a Template header or wp-child-theme class appears, the detector resolves the underlying parent framework automatically.
Two-Pass Plugin Discovery (Paths + HTML Signatures)
Extracts exact plugin slugs and version numbers from /wp-content/plugins/ URLs—and catches Yoast, Rank Math, WP Rocket, Elementor, WooCommerce, and Gravity Forms even when asset paths are minified or hidden.
Block Theme (FSE) vs. Page Builder Classification
Quickly tells you whether a site runs modern Full Site Editing Gutenberg blocks, a visual builder like Elementor, Divi, or Bricks, or a classic PHP template.
Cloudflare WAF Fallback (Paste Source Mode)
If a target website blocks automated cross-origin fetches with strict bot protection, switch to Paste HTML Source mode, drop in Ctrl+U source code, and get the full stack audit anyway.
Instant Stack Export (Markdown & JSON)
Copy a formatted Markdown stack summary into client discovery docs or download a clean JSON inspection report in one click.
Most Commonly Detected WordPress Themes & Stacks
| Item / Rule | Standard Reference | Practical Impact |
|---|---|---|
| Astra / Spectra | /wp-content/themes/astra/ | Fast multipurpose shell widely paired with Spectra blocks, Elementor, or WooCommerce. |
| GeneratePress + GenerateBlocks | /wp-content/themes/generatepress/ | Minimalist performance favorite among niche publishers and Core Web Vitals specialists. |
| Kadence + Kadence Blocks | /wp-content/themes/kadence/ | Feature-rich Gutenberg theme with visual header/footer builder and clean markup. |
| Hello Elementor | /wp-content/themes/hello-elementor/ | Zero-style canvas theme specifically made for full Elementor Pro Theme Builder sites. |
| Blocksy | /wp-content/themes/blocksy/ | Modern customizable theme popular for SaaS blogs, agencies, and fast WooCommerce shops. |
| Bricks Builder | /wp-content/themes/bricks/ | Developer-friendly visual site builder theme known for clean semantic HTML output. |
| Divi | /wp-content/themes/Divi/ | All-in-one Elegant Themes visual builder and layout pack ecosystem. |
| Twenty Twenty-Four / Five | /wp-content/themes/twentytwentyfive/ | Official WordPress Full Site Editing (FSE) block themes relying zero percent on legacy PHP templates. |
WordPress Detection Questions
Clear answers and practical edge cases for WordPress Theme Detector.