WordPress Theme Detector

WordPress Theme Detector: Reveal the Theme and Plugins Behind Any Site

Open the source of almost any WordPress page and you will hit a line like <link rel="stylesheet" href="https://example.com/wp-content/themes/astra/style.css?ver=4.6.2">. That one string leaks three facts at once: the site runs WordPress, the active theme is Astra, and the version is 4.6.2. The WordPress Theme Detector hunts down every clue like that — across the whole page, not just one tag — and turns it into a plain-language report: theme name, parent or child relationship, version, author, and the plugins the site loads on the front end.

You paste a URL, press a button, and a couple of seconds later you have an answer that would otherwise mean scrolling through raw HTML by hand. No install, no account, no download. This page walks through what the tool reads, how to read a report that hides a version number or lists fewer plugins than you expected, and how to push a thin first scan toward a complete result.

A Worked Example: Reading a Real Report

Concrete output makes the tool easier to trust, so start with one. Imagine you scan a small business site and the report comes back like this:

• Platform: WordPress 6.5
• Active theme: Acme Pro Child  (version not exposed)
• Parent theme: Astra  (version 4.6.2, author: Brainstorm Force)
• Plugins detected: Elementor, Yoast SEO, Contact Form 7, WP Rocket, WooCommerce

Read that top to bottom and a full picture forms. The site is a current WordPress install. The theme actually running is a child theme named "Acme Pro Child" — a thin custom layer with no public version of its own — built on the popular Astra framework. If you wanted this exact look, you would buy Astra (the parent), not chase the child-theme name, which is almost certainly a one-off the developer made for this client.

The plugin line tells its own story. Elementor means the pages were built with a drag-and-drop builder, so the layout is editable without code. Yoast SEO signals deliberate SEO work. WP Rocket is a premium caching plugin, hinting the owner cares about speed and has a budget. WooCommerce confirms the site sells products. In one scan you learn the design stack, the SEO posture, the performance approach, and the business model — facts that would take a long conversation with the site owner to extract otherwise.

Now contrast that with a thinner report on a different site: Active theme: GeneratePress 3.4.0, Plugins detected: Rank Math. Two lines, no child theme, one plugin. That is not a broken scan — it is a lean, hand-coded build by someone who keeps plugin count low on purpose. The shape of a report is itself information about how the site was made.

How to Detect a WordPress Theme

The scan is faster than reading these steps. Here is the full workflow.

1. Copy the website address. Grab the full URL of the page you want to inspect, for example https://example.com. The home page is a fine start, but it is not always the richest source — more on that below.
2. Paste it into the detector field. Drop the URL into the input box. You do not need to add www or fuss over trailing slashes; the tool normalizes the address.
3. Run the scan. Click Detect Theme. The tool fetches the public HTML and assets of the page and parses them for theme and plugin signatures.
4. Read the theme result. Within a few seconds you see the active theme name plus, where available, its version, author, author URL, theme homepage, and whether a child theme sits on top of a parent.
5. Review the detected plugins. Scroll down to the plugin list, built from script paths, stylesheet handles, and other public markers.
6. Follow the trail. Note the theme name, click the author link to find where to buy or download it, and flag any plugins worth investigating.
7. Scan another site. Clear the field, paste a new URL, repeat. The tool is unlimited and free.

What the Detector Actually Reads

To interpret a report well, it helps to know the footprints the tool relies on. WordPress is a templating system, and every theme and plugin leaves traces in the HTML it sends to your browser. The detector reads those traces; it never logs in or touches anything private.

Theme detection and the style.css header

Every WordPress theme lives in a folder under /wp-content/themes/, and its main stylesheet, style.css, opens with a header block naming the theme, version, author, and description. When a page loads, it links to assets inside its theme folder, so the folder name — and often the full header — becomes visible in the source. The detector parses those references to determine the active theme. A clean, conventional WordPress site therefore returns a confident name almost instantly.

Parent themes versus child themes

A child theme inherits everything from a parent theme and overrides specific styles or templates. Developers use child themes so customizations survive parent updates. A good detector reports both layers: the child that is technically active and the parent it is built on. The distinction matters because, as in the worked example, buying the child-theme name gets you nothing — the engine you want is the parent. When a report shows a custom-sounding child name with a recognizable parent, the parent is what you go shopping for.

Plugin detection from scripts and styles

Plugins live under /wp-content/plugins/, and many enqueue their own JavaScript and CSS on the front end. Those file paths carry the plugin's folder name, which the detector maps to a human-readable label. That is how it identifies page builders, SEO suites, contact-form plugins, caching layers, gallery tools, and e-commerce systems. Detection is strongest for plugins that load visible front-end assets and weakest for back-end-only plugins that never send anything to the browser. A membership plugin that only gates the admin area, for instance, may stay invisible while a page builder lights up immediately.

Version numbers and why they sometimes hide

WordPress often appends a version string to asset URLs for cache-busting — the ?ver=4.6.2 in the example at the top of this page. Security-conscious owners strip or randomize those strings, so a missing version is not a failure; it usually means the site is deliberately hiding that detail. The theme and plugin names themselves typically remain detectable.

Is It WordPress at All?

Before a theme can be named, the site has to run WordPress. The tool checks for the platform's fingerprints, and knowing them helps you read a "not WordPress" result correctly rather than treating it as an error.

• The wp-content directory. The single strongest signal is references to /wp-content/ in the page's assets. Nearly every WordPress front end loads themes and plugins from here.
• The wp-includes directory. Core scripts and styles load from /wp-includes/, another reliable marker.
• The generator meta tag. Many sites include <meta name="generator" content="WordPress 6.5">, naming the platform and sometimes the version — though plenty remove it.
• The REST API and feed links. Links to /wp-json/ or RSS feeds at /feed/ are common WordPress signatures.

If none of these fingerprints appear, the detector reports the site is not WordPress — and that is real information. The site may run on Shopify, Wix, Squarespace, Webflow, a static site generator, or a custom framework. A theme detector is WordPress-specific, so a negative result is itself an answer.

When a First Scan Comes Back Thin

Not every page gives up its secrets on the first try, and the fix is usually to change which page you scan rather than which tool you use. Here is what to do when a result looks incomplete, and why each move works.

Scan a different template, not just the home page

Home pages are often hand-built landing pages that load fewer plugins than the rest of the site. A blog post pulls in comment and typography assets the home page skips. A contact page loads the form plugin. A product page on a shop reveals WooCommerce and its extensions. If a home-page scan lists two plugins, scanning /blog/ or a single article frequently surfaces five or six more, because each template enqueues a different set of front-end files. A concrete pattern: scan shop.example.com and you get the theme but no e-commerce signal; scan shop.example.com/product/blue-mug/ and WooCommerce, a reviews plugin, and a currency switcher all appear.

Watch for caching and optimization side effects

Aggressive performance plugins merge, minify, and rename CSS and JavaScript into combined bundles like cache/min/1/abc123.js. That process erases the folder-name clues the detector depends on, so a heavily optimized site can return a confident theme name but almost no plugins. There is no trick that recovers names a site has deliberately stripped — but knowing why the list is short stops you from mistrusting an otherwise correct theme result.

Custom and renamed themes

A developer who renames the theme folder breaks the marketplace match, so the report shows an unfamiliar name. Check the parent-theme line: the look is frequently based on a popular framework like Astra, GeneratePress, Kadence, or Divi underneath, and the parent is the purchasable theme you actually want.

Headless and full-site-editing setups

A growing number of WordPress sites run "headless" — WordPress powers the admin, but a separate front-end framework like Next.js renders the public pages. Those sites may show no theme folder at all, because the visible HTML was generated outside the theme system. Likewise, a pure block-theme site using full-site editing leans on core block CSS and may surface a sparse plugin list. In both cases the tool is reading the page honestly; the architecture simply leaves fewer classic footprints.

Where the Theme Detector Earns Its Place

A theme detector solves a wider range of problems than its simple interface suggests. These are the scenarios where it saves real time.

• You found a design you love. A site's layout, typography, and spacing feel exactly right for your project. The detector names the theme so you can buy the same one instead of rebuilding it from scratch.
• You are scoping a redesign quote. Spotting a page builder, a membership plugin, or WooCommerce up front changes the estimate. Agencies scan a prospect's current site before sending a number.
• You inherited an undocumented site. A new client cannot remember the theme name or who built it. The detector recovers it in seconds so you can find the right support docs and update path.
• You are researching competitors. Finding that three rivals share the same premium theme and the same caching, SEO, and form plugins tells you their budget, technical maturity, and what "good enough" looks like in your niche.
• You are evaluating a theme to buy. Before spending money on a marketplace theme, scan real sites that already run it to see how it behaves in production, not just in the polished demo.
• You are troubleshooting a conflict. Confirming the exact theme and plugin list helps you reproduce and isolate a bug faster.
• You are learning WordPress. Reverse-engineering how professional sites are assembled turns any admired site into a study reference.

In every case the payoff is the same: you trade assumptions for facts without contacting the site owner or paying for a subscription analytics service.

How the Scan Works Behind the Scenes

The detector only ever reads what any visitor's browser already receives: the public HTML, CSS, and JavaScript of the page you submit. It does not attempt to log in, it does not probe for vulnerabilities, and it never touches the admin area or database. Submitting a URL is comparable to opening that URL in a normal browser tab — non-intrusive by design, and an ethical way to research other people's sites.

For your own privacy, the tool requires no sign-up and no email. You are not building a profile or leaving a history others can read. You paste a URL, get a result, and move on. That makes it well suited to quick competitive checks where registering for a paid service just to learn a single theme name would be overkill. Because everything runs against the public page rather than on your machine, the scan does not depend on your setup at all.

Frequently Asked Questions

Is the WordPress Theme Detector really free?

Yes. The tool is completely free with no sign-up, no email, and no payment. There is no trial that expires and no premium tier you are pushed toward. Paste a URL, read the result, and scan as many sites as you want.

Can it detect plugins as well as the theme?

Yes, it works as a combined WordPress theme and plugin detector. Alongside the active theme, it lists the plugins it can identify from the public front-end assets the page loads, such as page builders, SEO suites, form plugins, and e-commerce systems.

The tool says the site is not WordPress. Is that wrong?

Usually it is correct. If none of the WordPress fingerprints — /wp-content/, /wp-includes/, the generator tag, the REST API — are present, the site is very likely built on another platform such as Shopify, Wix, Squarespace, or a custom stack. Scan a blog or article page to be sure, but a "not WordPress" result is generally trustworthy.

I got a theme name but no version number. Why?

The site owner has probably stripped version strings from asset URLs and removed the generator meta tag, a common hardening step. The theme name is still accurate; only the version is hidden, and for most purposes the name is what you need.

The detected theme has an unfamiliar, custom-sounding name.

That often means a custom build or a marketplace theme the developer renamed in its folder. Check whether a parent theme is also reported — the parent is frequently the recognizable, purchasable framework underneath, such as Astra, GeneratePress, or Divi.

Fewer plugins showed up than I expected.

The detector can only see plugins that load front-end assets on the page you scanned. Back-end-only plugins, and any whose files were merged or renamed by a caching plugin, will not appear. Scan a different template — a contact page or a product page may load plugins the home page does not.

I pasted a URL and nothing happened.

Make sure the address includes the full domain and that the site is publicly reachable. Password-protected staging sites, intranet pages, and login-only URLs cannot be scanned because their content is not public.

Will it tell me where to buy the theme?

When the theme's header includes an author URL or theme homepage, the detector surfaces those links so you can go straight to the source. For renamed custom themes, look at the reported parent theme, which is usually the framework you can actually purchase.

Does it work on headless or block-based WordPress sites?

It tries, but results vary. A headless site renders its public pages outside the theme system, so the classic theme folder may not appear; a block theme using full-site editing leans on core block CSS and can return a sparse plugin list. The tool is reading the page accurately — these architectures simply leave fewer of the traditional footprints behind.

Is it safe and private to use?

Yes. The detector reads only the public page exactly as any visitor's browser would, without logging in or probing anything private. It requires no account, stores no personal data from you, and never modifies the site you scan.

Can I scan the same site repeatedly?

Yes. There is no daily limit, no counter, and no paywall. Scan as many sites as often as you like, which is exactly what you want during a research session comparing dozens of competitors.

Related Tools on Tools Hub

The WordPress Theme Detector pairs naturally with several other free utilities. Use them together to go from "what is this site running?" to building or optimizing your own.

• Website Screenshot Tool — capture a full-page image of any site you scan, so you have a visual reference alongside the theme name.
• Meta Tag Analyzer — inspect the title, description, and generator tags that often reveal platform and SEO setup details.
• DNS Lookup — see where a site is hosted and how its records are configured, complementing the theme and plugin picture.
• HTTP Header Checker — read the response headers a server sends, which can expose caching layers and security tooling.
• Image Compressor — once you recreate a design, shrink your theme's images so your own site loads fast.
• Favicon Generator — round out a new WordPress build with a crisp site icon in every required size.