How to find out what WordPress theme a site is using

01Why you'd want to identify a theme at all

You land on a site that looks exactly how you want yours to look — clean type, the right spacing, a layout that just works — and the obvious question follows: what is this built on? Identifying the theme is the fastest way to turn admiration into a shortlist you can actually shop from.

It's also a research habit worth having. Before you buy any theme, seeing it running on real sites tells you more than a polished demo ever will. Demos are staged; live sites show how a theme holds up with real content, real images, and a few years of edits behind it.

And it's a useful reality check on your own stack. Knowing what's under a site you admire — theme, builder, plugins — helps you judge whether the look comes from something portable you could own, or from a tangle of tools you'd be tied to forever.

The catch is that "what theme is this" rarely has a single clean answer. Modern sites layer a builder, a stack of plugins, and custom CSS on top of the theme. This guide gets you to the theme name reliably, then helps you read everything sitting on top of it.

02What to know before you start looking

A few facts about how WordPress serves a page make theme detection far more reliable, and save you from chasing dead ends on sites that have been deliberately tidied up.

The theme lives at a predictable path

WordPress loads a theme's stylesheet and assets from /wp-content/themes/<theme-folder>/. That folder name is the single most reliable fingerprint. If you can see it in the page source, you usually have your answer — the folder name is the theme's slug.

What you're really looking at

• The theme sets the foundation — the base templates, the default typography and color system, the global layout rules.
• A page builder (Elementor, Divi, Bricks, or the block editor) often controls the actual page layouts you see, sitting on top of the theme.
• Plugins add the sliders, forms, galleries, and widgets that you might assume are "the theme."
• Custom CSS reshapes all of it, which is why two sites on the same theme can look nothing alike.

When detection gets harder

Some sites rename their theme folder, strip identifying comments, or sit behind a caching layer or proxy that obscures the usual signals. Heavily customized or white-labeled builds can hide the theme entirely. If the easy methods come up blank, that's often the reason — not a flaw in your technique.

03Method 1: read the page source by hand

The manual method is the most trustworthy because you're reading what the server actually sent, not a tool's interpretation of it. It takes about a minute and works even when detector sites are blocked or wrong.

View source and search for the themes path

• Open the page, right-click, and choose View Page Source (or add view-source: before the URL).
• Use your browser's find (Cmd/Ctrl+F) and search for wp-content/themes.
• Read the folder name that follows — wp-content/themes/astra/style.css means the theme folder is astra.
• Cross-check by searching for Theme Name: — some stylesheets expose the human-readable name in a header comment.

Confirm with the stylesheet header

Open the style.css URL you found directly in the browser. Reputable themes keep a header comment at the top with the theme name, author, and version. That comment is the closest thing to a signature — if it's present and matches the folder, you can be confident.

If the folder name is generic or renamed (something like theme or the site's own brand), the header comment is your fallback. And if both are stripped, you've learned something useful: this site was deliberately customized, and the look may not come from an off-the-shelf theme at all.

04Method 2: use a theme detector tool

Detector tools automate the same source-reading you'd do by hand, then layer on guesses about plugins, hosting, and the wider tech stack. They're fast and convenient — just treat the output as a strong hint, not gospel.

The workflow that works best: run a detector first for speed, then confirm anything important by hand. When a tool names a theme, verify it against the actual wp-content/themes/ path in the source. When tools disagree with each other, the source is the tie-breaker.

Browser extensions like Wappalyzer are handy because they report as you browse, but they often surface the framework or builder rather than the exact theme. Read their output as "what technologies are present," not "this is the theme," and you'll avoid the most common false confidence.

05Telling the theme apart from the page builder

This is where most people get the wrong answer. A site can run a lightweight, near-invisible theme while a page builder does all the visible work. If you copy "the theme" and ignore the builder, your result won't look anything like the original.

Signs a page builder is doing the heavy lifting

• Elementor: look for elementor in CSS class names and asset paths, and a /wp-content/uploads/elementor/ directory.
• Divi: classes prefixed with et_pb_ and a theme folder named Divi are the tell.
• Bricks / Oxygen: builder-specific class prefixes and inline-generated CSS rather than a rich theme stylesheet.
• Block editor (Gutenberg): wp-block- class names and a block theme folder mean the layout is built in core, not a third-party builder.

A practical clue: if the theme folder is one of the well-known lightweight bases (Astra, GeneratePress, Kadence, Blocksy) but the page is visually rich and bespoke, a builder is almost certainly involved. Those themes are popular precisely because they get out of the builder's way.

Why this matters for you: a theme is portable and relatively easy to leave. A page-builder layout is far stickier — its content is wrapped in proprietary markup that doesn't survive cleanly if you ever switch builders. Knowing which one you're admiring tells you how much lock-in you'd be signing up for if you recreated it.

06Common mistakes when identifying a theme

A handful of errors account for most wrong identifications. None are hard to avoid once you know to watch for them.

Trusting one tool's answer

Detector tools guess. They get fooled by renamed folders, caching, and white-label builds. Treating a single tool's output as final is the fastest way to chase the wrong theme. Always confirm against the page source before you act on it.

Mistaking the builder or plugins for the theme

The slider, the mega-menu, the fancy contact form — those are usually plugins or the builder, not the theme. Buy the theme expecting those features baked in and you'll be disappointed. Separate "foundation" from "add-ons" before you spend anything.

Assuming the demo equals the look

Even when you correctly identify the theme, the site you admired layered custom CSS, specific fonts, and curated images on top. The bare theme out of the box will look plainer. The theme gets you the bones; the polish is separate work.

Ignoring whether it's even WordPress

Before hunting for a WordPress theme, confirm the site is WordPress at all — the wp-content path is the giveaway. If it's absent, you may be looking at Shopify, Webflow, Squarespace, or a custom build, and WordPress theme detectors will just return noise.

07From identifying to maintaining: avoiding lock-in

Identifying a theme is the easy part. The real question is whether the look you admired is built on something you could own and maintain, or on a stack that would tie you down. That distinction should shape what you copy.

• Favor portable foundations. A clean theme plus the core block editor produces content that stays readable and movable. That's the version of "this look" you can live with for years.
• Be wary of builder lock-in. If the look depends entirely on a proprietary page builder, recreating it means buying into that builder's ecosystem — and its shortcodes — indefinitely.
• Check the theme's update story. A theme that's actively maintained and widely used is a safer base than an abandoned one, however nice it looks today.
• Separate look from plumbing. You can usually match the visual style with a different, better-supported theme rather than cloning the exact one, especially if the original is niche or unmaintained.

When you do want to test a candidate theme yourself, do it on a staging copy rather than your live site — a managed host like Cloudways makes spinning up a throwaway WordPress install for experiments straightforward. Activate the theme there, drop in real content, and judge it before it ever touches production.

08Frequently asked questions

Can I always find out what theme a site uses?

Usually, but not always. Most WordPress sites expose the theme folder in their page source. Heavily customized, white-labeled, or proxied sites can hide it, and a few aren't WordPress at all. When the source comes up blank, the look is probably bespoke rather than an off-the-shelf theme.

Is it legal to use the same theme as another site?

Buying and using the same commercial theme is entirely normal — that's what themes are sold for. What you can't do is copy a site's content, images, or branding. The theme is the reusable shell; the specific content and assets belong to that site's owner.

Why does the theme look so different on the original site?

Because what you saw is the theme plus a builder, plugins, custom CSS, specific fonts, and hand-picked images. The same theme on a fresh install will look plainer. Matching the original takes configuration and design work beyond just installing the theme.

A detector says "no theme detected" — what now?

Fall back to reading the source by hand and search for wp-content/themes. If that path is absent, check whether the site is WordPress at all. A renamed folder still shows up in the source even when detectors miss it, so manual inspection often succeeds where tools fail.

This is general editorial guidance, not financial or business advice. Detection methods and tool accuracy change over time, so verify specifics against the site's own page source and any tool's current documentation before acting on what you find.