The fastest way to find what WordPress theme a site is using is to paste the site URL into a WordPress theme detector. You'll get the theme name, author, version, and child-theme status in under five seconds. If the tool returns an ambiguous answer (which happens with heavily-secured sites that scrub the standard fingerprints), you can pull the theme directly from the site's wp-content/themes/{theme-name}/style.css file, which every standard WordPress install exposes publicly.
This guide walks through seven reliable detection methods, including the two that work even when a site uses security plugins specifically designed to hide the theme name. WordPress is the easiest CMS to fingerprint because every theme leaves a trail of breadcrumbs in the page source. Knowing where to look means you can identify any WordPress theme in any state, including the one critical detail most articles skip: telling parent themes apart from child themes.
Method 1: Use a WordPress Theme Detector (Fastest)
Paste any WordPress site URL into our WordPress Theme Detector and you'll see the theme name, author, version, license, parent theme (if it's a child theme), and a snapshot of the installed plugins. The tool reads the same public storefront data you'd inspect manually, but it parses the style.css header, the body class names, and the asset URLs for you in one pass.
This is the right method for 90% of sites. Use the manual methods below when the tool returns an ambiguous result (typically a renamed theme on a heavily-secured WordPress install), when you want to verify the answer for client work, or when you specifically need to know which theme is the parent versus which is the active child.
Method 2: View Source for wp-content/themes Paths
Right-click anywhere on the WordPress site and choose View Page Source (Ctrl+U on Windows, Cmd+Option+U on Mac). Press Ctrl+F to search the source and look for wp-content/themes/. Every CSS, JS, and image asset on a WordPress site loads from a path like:
https://example.com/wp-content/themes/{theme-name}/assets/style.css
https://example.com/wp-content/themes/{theme-name}/script.jsThe folder name right after /themes/ is the theme handle (usually lowercase with hyphens). On most sites you'll see the name immediately. If you see two different theme paths in the source, the site is using a child theme. The path that loads the main stylesheet last is the active child; the other path is the parent.
Method 3: Read the style.css File Directly
This is the most reliable manual method because it pulls the data from the canonical WordPress source. Every WordPress theme must include a style.css file with a specific comment header that WordPress reads to register the theme. Visit the file directly:
https://example.com/wp-content/themes/{theme-name}/style.cssThe first 10 lines of the file look like this:
/*
Theme Name: Astra
Theme URI: https://wpastra.com/
Author: Brainstorm Force
Author URI: https://wpastra.com/about/
Description: Fast, lightweight, customizable WordPress theme.
Version: 4.6.10
License: GNU General Public License v2 or later
Template:
Text Domain: astra
*/The Theme Name field is the full theme name (not the lowercase handle from the URL). The Template: line is the key one for child-theme detection. If Template: is empty, this is a standalone or parent theme. If it contains a value (e.g. Template: astra), this is a child theme and the value names the parent theme handle.
Method 4: Inspect the Body Class for Theme-Specific Names
WordPress themes often add theme-specific class names to the <body> tag. Search the source for body class= and look for class names like:
theme-astra,astra-theme,astra-default: the Astra theme.generatepress,gp-default: GeneratePress.divi-theme,et_pb_*(Elementor-related class prefixes): the Divi builder.avada,fusion-*: the Avada theme.hello-elementor: the Hello theme used with Elementor.oceanwp: OceanWP.
This method is faster than opening style.css when you recognize a popular theme by its body class signature, and it works even on sites that have moved the themes folder to a non-standard path.
Method 5: Use a WordPress Theme Detector Chrome Extension
If you research dozens of sites per week, a Chrome extension turns a 30-second check into a one-click answer in the address bar. Search the Chrome Web Store for "WordPress theme detector" or "what WordPress theme is that" and you'll find extensions that read the body class, asset URLs, and style.css metadata, then surface the result as a popup with the theme name, author, and download link.
The trade-off: third-party extensions have varying accuracy on heavily-modified or white-labeled themes, and several try to upsell paid plans for what's a 10-second free check. For occasional lookups, the standalone tool method (Method 1) is just as fast without installing anything.
Method 6: Identify Parent vs Child Themes
When a site loads from two different wp-content/themes/ paths, it's running a child theme. The difference matters because the design choices, custom CSS, and template overrides come from the child; the underlying engine and core features come from the parent. To tell them apart:
- Open the child theme's
style.css(the path that loads its CSS last in the source). - Read the
Template:line in the header. The value (e.g.Template: astra) names the parent theme. - The parent theme handles the framework (functions, hooks, default templates); the child theme handles the customizations and branding.
If you want to recreate the look of a site you're inspecting, you usually need both: install the parent theme first, then build a similar child theme on top of it. Some popular parent themes (Astra, GeneratePress, Hello, Genesis) have their own child theme marketplaces if you don't want to build from scratch.
Method 7: Check When the Theme Is Hidden by Security Plugins
A handful of WordPress security plugins (Sucuri, Hide My WP, WPS Hide Login) actively scrub the theme path from the source. If wp-content/themes/ doesn't appear anywhere in View Source, try these fallbacks in order:
- Check the RSS feed. Most WordPress sites serve
/feed/or/?feed=rss2. The feed XML often leaks the generator string and asset URLs the scrubbing plugin didn't touch. - Check robots.txt. Some themes mention their own admin or sitemap paths in robots.txt that confirm the theme handle.
- Check the WordPress REST API. Visit
/wp-json/on the site. If the response is JSON, the site is WordPress, and the namespace plugins reveal hints about the active theme. - Use the body class method (Method 4). Body classes are harder to scrub completely because removing them breaks most theme styling.
If all four fail, the site has gone to unusual lengths to hide the theme. At that point your best option is matching the visual design against popular themes manually, or asking the site owner directly.
What to Do After You Identify the Theme
Knowing the theme is step one. What you do next depends on why you wanted to know.
You want to use the same theme yourself
If the theme is in the WordPress.org repository (free themes), search the theme name at wordpress.org/themes and install it directly from your WordPress admin. If it's a premium theme, the author's website (linked in the style.css Author URI field) sells it directly. Many premium themes are also sold on ThemeForest. Our roundup of the top 10 WordPress themes covers the themes that consistently power the best-performing WordPress sites.
You want a faster alternative
If the site you inspected is slow, the theme is often part of the problem. Performance-focused themes like Astra, GeneratePress, and Kadence load with significantly less CSS and JavaScript than design-heavy themes like Avada or Divi. Our list of the fastest WordPress themes ranks themes by real-world load time, not just developer claims. If the site you inspected is a WooCommerce store specifically, our roundup of the best WooCommerce themes ranks free and premium picks by how they handle product pages, cart drawers, and checkout speed on real hosting.
You want to know if it's worth buying
Once you have the theme name, check its rating and review count on WordPress.org or ThemeForest, the developer's other themes for consistency, and how many active installs the theme has (high numbers mean a battle-tested theme; low or declining numbers mean abandoned or replaced). For a primer on WordPress as a platform, see our guide on what WordPress is and how it works.
Common Issues and How to Fix Them
The detector says one theme but View Source shows another
This usually means you're looking at a parent theme path in View Source while the site is running a child theme. The detector is reading the child theme's style.css (the active theme), and View Source is showing both parent and child paths. Trust the detector for the active theme name and check the child's style.css Template: line if you also want the parent.
No wp-content/themes/ path appears anywhere
Either the site isn't WordPress, or it uses a security plugin that scrubs theme paths from the source. Confirm WordPress first by checking /wp-json/ or /wp-admin/ (both should return non-404 responses on a WordPress site). If WordPress is confirmed, use Method 7's fallbacks.
The theme name is "twentytwentyfour" or another default theme name
The site is running one of WordPress's default themes (Twenty Twenty-Four, Twenty Twenty-Three, etc.), usually a fresh install, a basic blog, or a developer's placeholder. The defaults are perfectly fine themes but are rarely the answer when someone wants to recreate a sophisticated design.
This isn't WordPress at all
If /wp-json/ and /wp-admin/ both return 404, and no wp-content/ paths appear in the source, the site isn't on WordPress. It might be on Shopify, Squarespace, Wix, or a custom platform. Use our Theme Detector on the main page to identify the underlying platform first, then apply the right detection method for that platform.
Conclusion: Finding Any WordPress Theme
For 95% of sites, the one-click WordPress Theme Detector gives you the answer in seconds, including the parent theme if it's a child setup. For the remaining edge cases, reading style.css directly at /wp-content/themes/{theme-name}/style.css is the most reliable manual fallback because the theme metadata header is canonical WordPress data. When even that fails, the body-class fingerprint and the RSS feed fallback handle nearly every security-plugin scenario. For the broader question of identifying themes on any platform (not just WordPress), see our pillar guide on how to find what theme a website is using.
* read the rest of the post and open up an offer
