What WordPress Theme Is That? 4 Ways to Find Out

To find out what WordPress theme a website uses, paste its public URL into a theme detector, then check the result against the theme files linked in the page source. A readable style.css header can reveal the theme name and, for a child theme, its parent.

That is the quick answer to “what WordPress theme is that?” The important catch is that a detector can return a folder name, an incomplete result, or nothing at all. Some websites do not use WordPress, and some WordPress-powered sites have a completely separate frontend.

I’ll walk you through four practical methods, explain what the clues actually mean, and show you when it makes sense to stop searching. You can do the main checks in your browser without installing a plugin on your own website.

Key Takeaways

• Start with the exact public page you like. A website’s homepage and its blog can use different systems.
• Use a detector for a quick lead, then look for matching theme assets and readable theme metadata.
• The folder after /themes/ is a clue. It may be renamed, custom, or part of a child-theme setup.
• A child theme’s Template field identifies the parent’s folder. Buying that parent does not reproduce the child’s customizations.
• Builders, block patterns, custom styling, and content all affect the finished design. Finding the theme name is only part of understanding the page.
• Respect blocked files and private pages. No public detector can promise a complete theme or plugin inventory.

First, Check Whether the Page Uses WordPress

A familiar-looking blog is not enough to establish which platform built it. Start by checking the footer for a WordPress or theme credit, then try a detector on the page itself.

If the main site gives you no result, check the public blog URL you actually visited. For example, a business might use a different platform for its homepage and WordPress under /blog/. The What WordPress Theme Is That FAQ specifically recommends entering the full blog or page URL in that situation.

In the page source, paths containing wp-content or wp-includes can provide supporting evidence. A WordPress generator tag can help too, when the site exposes one. None of these clues should be treated as an infallible platform check.

Missing those strings does not prove that WordPress is absent. WordPress allows changes to its content directory, and a separate frontend may not expose the usual paths. Equally, an old image or copied snippet can leave a WordPress-looking reference on a page built elsewhere.

My rule is simple: look for several consistent clues before making a confident claim. If the platform remains uncertain, keep that uncertainty in your notes.

Method 1: Use an Online WordPress Theme Detector

This is the easiest starting point when you want a name to research. A detector examines what the public page exposes and may supplement those clues with its own theme database.

Start With Kwebby’s WordPress Theme Detector

1. Open the Kwebby WordPress Theme Detector.
2. Paste the full public URL into the address box.
3. Select Detect and wait for the result.
4. Read the status and the Active Theme section, including any warning beneath the name.
5. If a parent theme appears, record that separately from the child theme.
6. Use the reported name as a starting point for verification, rather than assuming every linked directory page is a match.

I checked this article’s public URL while updating the guide. The detector returned the folder kwebby and explicitly said it could not read the theme’s style.css. It also listed reco as another referenced theme folder.

That is a useful partial result. It tells me which names to investigate, but it does not establish that either name is a downloadable theme responsible for every part of the current design. A reference inside an older article or screenshot can outlive the theme it describes.

Other Detectors You Can Cross-Check

If the first result is incomplete, try one other detector before switching to a manual check. These services have public theme-detection pages:

• What WordPress Theme Is That describes support for parent and child themes, alongside detectable plugins.
• WPThemeDetector looks for theme information and can report parent-theme details.
• Kinsta’s WordPress Theme Detector focuses on details such as the theme name, URL, version, and author.
• WPZOOM’s detector explains that custom builds, caching, and hidden markers can limit its findings.
• Scan WP offers theme and plugin detection. Its page also discloses that using the tool can open a promotional offer.

I reviewed those services’ public pages for this guide. The specific live example above is the Kwebby check, not a comparative accuracy test of every service.

Two tools agreeing is helpful, but both might be reading the same incomplete clue. If they disagree, compare the exact page scanned, the reported folder, and any child-theme information. Then use the next method.

Also keep the plugin list in perspective. WPThemeDetector’s own FAQ explains that some active plugins leave no detectable reference in the public HTML. A short list does not mean the website has only that many plugins installed.

Method 2: Find the Theme in the Page Source

You do not need to understand the whole page’s HTML for this check. You are looking for a small number of public file paths, then reading any useful information they expose.

Step 1: Look for Theme Asset Paths

1. Open the public page in a desktop browser.
2. Right-click an ordinary part of the page and choose View Page Source, where your browser offers it. Browser menu wording can vary.
3. Use the find command, usually Ctrl+F on Windows or Command+F on Mac.
4. Search for wp-content/themes/.
5. Inspect a stylesheet or script URL that contains the match. Do not rely on a match inside the article’s text alone.

A path might look like this illustrative example:

https://example.com/wp-content/themes/sample-theme/assets/main.css

Here, sample-theme is the directory name. It is a useful search term, but the theme’s displayed name may be different.

Keep the entire path. If WordPress lives in a subdirectory, the real URL may contain /blog/wp-content/ rather than starting directly with /wp-content/. Do not discard the subdirectory when following a link.

For this refresh, the public article’s linked assets included /blog/wp-content/themes/kwebby/style.css and other files in that theme folder. That is stronger evidence of the page’s current assets than the old RECO references inside the article text.

Step 2: Read the Theme Header When It Is Public

If the page links to the theme’s style.css, open that stylesheet in a new tab. If you only found a different asset inside the theme folder, the conventional root stylesheet is style.css in that same folder. It may or may not be publicly readable.

The top of a readable stylesheet may contain fields such as these. This is an illustrative example, not output from a real site:

/*
Theme Name: Sample Studio
Theme URI: https://example.com/sample-studio/
Author: Example Studio
Version: 1.0
*/

Theme Name is the declared name. Theme URI may lead to a product or project page, while Author identifies the stated creator. Verify that the destination genuinely belongs to that developer before downloading anything.

The WordPress stylesheet documentation explains these header fields. It also makes clear that style.css contains theme-registration information. A random main.css file does not have to contain that same metadata.

A stylesheet can be unavailable, empty-looking, optimized, or blocked to visitors. In my live check, direct access to the observed Kwebby stylesheet was blocked, so I did not verify its header manually. Treat a failed lookup as a limit of the check and move on.

Step 3: Separate the Child Theme From Its Parent

A child theme can carry a completely different name from the theme it builds on. Look for a Template field in its header:

/*
Theme Name: Sample Studio Child
Template: sample-studio
*/

In this example, the child is called Sample Studio Child and its parent’s directory is sample-studio. WordPress requires the Template value to match the parent folder exactly, as its child-theme documentation explains.

If the child is bespoke, you might be able to obtain the parent while the extra styling remains private. That explains why installing the same parent can produce a very different-looking website.

Seeing two theme folders does not automatically prove a parent-child relationship. Old content, cached assets, or embedded examples can add extra names. The child’s header or confirmation from the developer gives you a clearer connection.

Step 4: Check Loaded Stylesheets if Source Search Fails

View Source shows the HTML response. The browser’s Inspect tools can help when you need to examine the current page or its loaded files instead.

1. Open the browser’s developer tools using Inspect.
2. Select the Network panel and reload the page while that panel is open.
3. Filter for CSS to narrow the list to stylesheets.
4. Look at the request URLs for theme-related paths, then examine a relevant public stylesheet.

Google’s Chrome Network guide documents the CSS filter and request inspection. You are reading what a normal page load exposes. There is no need to run unfamiliar console scripts or probe private endpoints.

If every stylesheet is combined into a cache file or served through a rewritten CDN path, the original theme name may be missing. WordPress also supports moving its content directory, so the default path is a convenient pattern rather than a universal rule.

Method 3: Use a Browser Extension You Trust

A technology-detection extension can be convenient if you inspect websites regularly. For example, Wappalyzer lists extensions for major browsers that report detected website technologies.

If you already use one, open the public page, let it load, and check the extension’s results for WordPress and any relevant theme or builder information. Record the exact name it reports instead of inferring a theme from a general “WordPress” label.

I would not install several extensions just to answer this one question. An online detector plus a source check is usually enough to establish whether a useful public clue exists.

Before installing an extension yourself, check its official listing, publisher, permissions, and privacy policy. Technology detection may involve reading page information or sending a URL to a service. Keep private admin pages and confidential client URLs out of casual checks.

No extension was installed or tested for this refresh. This is an optional workflow, and it has the same visibility limits as other public detection methods.

Method 4: Ask the Site Owner or Designer

When the public clues stop being useful, a short question can save you a lot of guessing. Look for a design credit or a normal contact page. You can ask:

“I like the layout of your website, especially the blog pages. Would you mind sharing the theme or builder you used? Was the design customized?”

That last question matters. A theme name alone may not explain a custom header, product layout, or block pattern. If a designer built the site, ask whether the theme is available publicly or whether it was created specifically for that client.

You may not get a reply, and the owner does not owe you their files or setup details. If the answer is private, use the site as design inspiration and choose a suitable foundation for your own project.

Why a WordPress Theme Detector Might Fail

An incomplete result is easier to handle when you know what could be missing. Here is how I would interpret the most common situations.

• A name appears, but no product page exists. It may be a custom theme, a renamed directory, an unavailable product, or a weak match. Search the declared author and theme name together, then seek confirmation.
• Only a child theme appears. Look for the parent name or a readable Template field. You may be able to use the parent, but not the site’s custom child files.
• The tool reports that it cannot read a stylesheet. Keep any directory evidence, but do not invent missing metadata. A blocked request is a reason to stop that lookup.
• The homepage fails, but the blog works. The site may use several platforms, or those pages may expose different assets. Compare the exact URLs.
• You find only cache or CDN files. Optimization or rewritten URLs may have removed the recognizable path. Try the normal loaded-file inspection, then accept an inconclusive result if the clues are absent.
• The page is powered by WordPress but looks unrelated to a theme demo. A builder, custom templates, or extensive design settings may control the visible result.
• No WordPress clues appear. The page could use another platform, or a headless architecture could conceal its WordPress backend. “Not detected” is not the same as a verified platform audit.

For headless websites, the distinction is especially important. WordPress can supply content to a separate application through its REST API. The interface you see may therefore be built outside the normal WordPress theme-rendering system. There may be no conventional frontend theme for a public detector to identify.

The Theme, Template, and Page Builder Are Different Clues

A WordPress theme provides the site’s presentation framework. A template controls a particular kind of page within that setup. A page builder can add another layer of layout and styling.

For example, Elementor’s Theme Builder documentation describes templates that can override parts of the active theme’s layout and styles. A detector could correctly identify the base theme while still telling you very little about the design you admire.

The same caution applies to block themes. Site-level style choices, patterns, and custom content can make two websites using the same theme look quite different. Check the WordPress theme-structure guide if you want to understand the files involved.

For me, the useful question is often more specific than “what theme is that?” Try “what creates that navigation?” or “is that landing page a builder template?” You will know what to investigate once you separate the overall theme from the feature you want.

What to Check Before Using the Theme You Found

Once you have a credible theme name, visit the official developer page or the WordPress Theme Directory. Compare the author, documentation, and demos with the clues you collected.

Then check the things that matter for your own website:

• Your content: Will the theme handle your articles, products, portfolio, or booking pages comfortably?
• Editing workflow: Does it use the block editor, a builder you want to use, or a custom system you will need to learn?
• Support and maintenance: Is the developer maintaining it, and is useful documentation available?
• Mobile and accessibility: Try navigation, readable text, forms, and keyboard access in the demo.
• Performance: Test a realistic version of your own site. A fast empty demo does not establish how your images and plugins will behave.
• License and extras: Check what you can use, whether a particular demo needs additional products, and what ongoing support costs.

Keep your own copy, images, branding, and layout decisions original. For more design ideas, see my guide to making a WordPress site look better. If you are building a custom project, the WordPress starter-theme guide may be a useful next stop.

Before switching an existing site, back it up and test the change in a safe staging environment. Also review how theme and plugin changes can affect SEO, so the visual refresh does not introduce an avoidable technical problem.

Frequently Asked Questions

How can I find out what WordPress theme a site uses for free?

Enter the public page URL into a free theme detector, then check the page source for theme asset paths. If the relevant style.css is readable, its header can provide the declared theme name. You do not need to install a WordPress plugin on your site for these checks.

Can a detector identify premium WordPress themes?

Yes, when the public files or recognizable markers expose enough information. Being a paid theme does not automatically prevent detection. The result does not grant a license or give you access to its paid files.

Can I identify a custom or renamed theme?

Sometimes. A custom theme may still publish its name and author in a readable stylesheet. A renamed folder might retain those header details. If both the public paths and metadata are hidden or changed, you may need to ask the site owner.

Why do two different theme names appear?

You might be seeing a child and parent theme, but that is not the only explanation. Old references, cached files, and embedded examples can also produce extra names. Check which assets the page actually loads and whether a child-theme header establishes the relationship.

Does an Elementor result tell me the WordPress theme?

Not by itself. It identifies a builder-related clue. You still need the theme name, and you may also need to know which templates and customizations produced the page’s design.

Does “no theme found” mean the website is not using WordPress?

No. A failed result can reflect missing markers, a blocked request, rewritten assets, or a separate frontend. It can also be a non-WordPress website. Public detection alone may not settle which explanation applies.

Will installing the same theme make my website look identical?

Usually, there is more work involved. The original site may use a child theme, builder templates, different typography, premium add-ons, or custom code. Use the theme as a foundation and create a design that fits your own content.

Final Thoughts

I would start with the exact page URL in a detector, verify any useful result against public theme assets, and stop when the evidence runs out. If the site uses a child theme or builder, look at those layers before deciding what you need.

Knowing what WordPress theme a site uses can shorten your research. Understanding the limits of that answer is what helps you choose the right starting point for your own website.