Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The quickest way to identify a public site’s WordPress theme is to open its page source, search for /wp-content/themes/, and note the theme directory named in a stylesheet or asset URL. Then open that directory’s style.css and read its header, especially Theme Name and Template. If you administer the site, Dashboard → Appearance → Themes is the authoritative check because it shows the active installation setting.
A directory name is only a clue. The site may use a child theme, a custom theme, a page builder, rewritten asset paths, or extensive CSS and template changes. Use the process below to distinguish a detectable underlying theme from the design you actually see.
What you can and cannot learn from a public site
A visitor can often identify the theme files that a WordPress site exposes to the browser. The strongest public evidence is the standard header in the theme folder’s style.css file. That header can reveal the theme name, author, version, and, for a child theme, its parent theme.
Detection does not prove that the visible design is an unmodified commercial theme. A developer may have replaced templates, added extensive CSS, removed identifying comments, or built a private theme with a descriptive internal name. A page builder can also control most of the page’s appearance while the WordPress theme supplies only the basic layout and integration layer.
#1 Best Overall
Think of the result as an evidence chain:
- Asset path: a fast indication that a theme directory is being requested.
style.cssheader: the best public confirmation of the theme metadata WordPress recognizes.- Dashboard state: the authoritative answer when you control the installation.
Method 1: inspect page source manually
This method requires no account and works from a desktop browser when the site leaves recognizable WordPress asset paths in its HTML or linked CSS.
- Open the site’s front page in a desktop browser.
- Choose View Page Source. In most browsers you can also press
Ctrl+Uon Windows or Linux, orCmd+Uon macOS. Use page source rather than only the rendered Elements panel, because source exposes the original links sent by the server. - Use the browser’s find command:
Ctrl+ForCmd+F. - Search for
/wp-content/themes/. - Inspect every matching stylesheet, script, image, or font URL. The folder immediately after
/wp-content/themes/is the theme directory name. - Record the directory exactly, including capitalization, numbers, and hyphens. A site can load more than one theme-related path, especially when a child theme and parent theme both contribute assets.
A matching path may look like /wp-content/themes/theme-folder/css/main.css. In that example, theme-folder is the directory to investigate; css/main.css is only an asset inside it. Do not mistake a plugin path such as /wp-content/plugins/ for a theme.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Search additional source locations
The front page is not always the best page to inspect. Repeat the search on an article, an archive, and a contact or landing page if the home page has no result. Different templates may enqueue different stylesheets, and a cached page can omit assets that appear elsewhere.
Search for both themes/ and distinctive stylesheet filenames if the full path is split across HTML or escaped in an inline script. You can also inspect the source for a linked CSS file, open that file in a new tab, and look at its path. The directory name remains useful even when the HTML contains minified markup.
Method 2: verify the name in style.css
Once you have a theme directory, request its root stylesheet by replacing the asset portion of the path with style.css. The relevant file is conventionally located at /wp-content/themes/theme-folder/style.css. If the server returns the file, read the comment header at the top rather than relying on the folder name.
WordPress’s theme documentation explains that, when determining which themes are available to activate, WordPress searches each folder under /wp-content/themes for a style.css file. The header fields are therefore the clearest public representation of the theme metadata WordPress uses.
Free tools Windows power users keep installed
One-click scans. No signup required.
Fields to read
| Header field | What it tells you | How to use it |
|---|---|---|
Theme Name |
The human-readable name WordPress displays. | Use this as the detected theme name, not merely the folder slug. |
Author |
The credited developer, studio, or project. | Helps distinguish similarly named themes and identify a private build. |
Version |
The version recorded in the stylesheet header. | Report it as metadata from that file; it may not equal the version currently installed if files are cached or edited. |
Template |
The parent theme directory used by a child theme. | If present, inspect both the child and the parent before describing what the site uses. |
Headers commonly appear inside a CSS comment, with one field per line. Read the exact spelling and capitalization. A folder called modern-theme can have a different Theme Name, and a custom project may use an internal name that is not sold publicly.
When the stylesheet is blocked or missing
A server may return a 403 or 404 response, redirect the request, combine CSS into a generated file, or remove the standard header. Do not treat a failed request as proof that the site is not using WordPress. Use other source pages, inspect additional asset URLs, and look for a child-theme path. If no metadata is exposed, label the result inconclusive or custom rather than guessing from the visual design.
Child themes: check both layers
A child theme is a separate theme directory that inherits from a parent. The child can contain its own style.css, templates, scripts, and images while relying on the parent for other files. This is why a site can expose one directory in a URL while the commercial or base theme name is recorded elsewhere.
- Open the child directory’s
style.css. - Read its
Theme Nameand other header fields. - Look for the
Templatefield. Its value is the parent directory name, not necessarily the parent’s display name. - Open the parent directory’s
style.cssand read its ownTheme Name,Author, andVersion. - Describe the relationship precisely: for example, “a child theme named X with parent theme Y,” when both headers support that conclusion.
If the child’s Template value points to a directory that cannot be fetched, you can still report the child metadata and state that the parent could not be independently confirmed. Do not infer the parent from a similarly named folder.
Rank #3
Method 3: use the WordPress dashboard if you own the site
For an administrator, the dashboard is more reliable than public inspection because it reflects the installation’s active setting, including themes that expose no useful public clues.
- Sign in to WordPress.
- Open Appearance → Themes.
- Find the theme marked Active. Its card supplies the installed theme name and usually its author and version details.
- If a child theme is active, open its details and note the parent relationship. Keep the child as the active theme in your description, while naming the parent when the relationship matters.
This route answers “which theme is active?” rather than “which theme files happen to appear in one page’s HTML?” Those answers can differ when a plugin supplies assets, a cache serves stale markup, or a page is generated by a specialized template.
Classify block and classic themes
For a quick classification, open Appearance → Editor. Its presence usually indicates a block theme. Appearance → Customize usually indicates a classic theme. These labels are only a practical guide: permissions, WordPress versions, and theme capabilities can change which menu appears. Treat the active theme card and its details as the primary evidence, and use the editor menu as a secondary classification.
Theme versus page builder, plugins, and custom code
The theme is only one layer of a WordPress site. A page builder can generate the page structure and styling, while the theme supplies global styles, template fallbacks, accessibility features, and integration points. Plugins can add blocks, shortcodes, custom post templates, and their own CSS.
Report separate findings when the evidence supports them:
Rank #4
- Theme: the name in the active theme card or
style.cssheader. - Parent theme: the directory named by the child theme’s
Templatefield. - Builder or framework: only when source comments, recognizable asset paths, or dashboard information clearly identifies one.
- Customizations: a qualification based on child-theme files, custom CSS, unusual templates, or a private theme name.
A familiar theme name does not mean you can reproduce the site by installing that theme alone. The finished appearance may depend on design settings, block patterns, builder templates, widgets, menus, custom post types, and site-specific CSS that are not visible to a public visitor.
Comparison of detection methods
| Method | Access required | Evidence strength | Typical speed | Main failure risks |
|---|---|---|---|---|
| Page-source search | Any public visitor | URL clue; stronger when several pages expose the same directory | Usually under a minute | Rewritten URLs, combined CSS, cached markup, or no public theme path |
style.css header |
Public access to the theme file | Strongest public confirmation; standard metadata fields | A few additional minutes | Blocked file, missing header, custom naming, or inaccessible parent |
| Dashboard → Appearance → Themes | Administrator access | Authoritative active-theme state | Fast once signed in | Limited permissions, unfamiliar WordPress version, or confusion between active child and parent |
| Detector service | Usually only the public site address | Lead based on detectable public signals | Fastest for a first guess | False positives when assets are hidden, customized, or shared by plugins and builders |
Using a detector service without overtrusting it
A detector can save time by scanning source, stylesheets, and known signatures. Treat its output as a lead, not a final answer. Confirm the reported name in the theme folder’s style.css header or, for your own site, in Appearance → Themes.
When a detector reports a parent theme, check whether the site actually exposes a child-theme directory and a matching Template field. When it reports “custom,” look for a private or descriptive Theme Name rather than assuming no theme exists. If the service names a builder, verify that its assets or dashboard settings are present before presenting it as part of the stack.
Why theme detection fails and what to try next
No /wp-content/themes/ result appears
- Inspect more than the home page; templates can enqueue different files.
- Search for
themes/without the leading path and inspect linked CSS URLs. - Check whether a cache or optimization layer has combined and renamed CSS files.
- Look for a child-theme directory or a custom stylesheet loaded from another location.
- If you own the site, stop public probing and use Appearance → Themes.
The path exists, but the folder name is not recognizable
Use the folder name to locate style.css, then trust the header’s Theme Name over the slug. Developers often use abbreviations, project codenames, or names unrelated to the site’s branding.
The header says “custom” or uses a private name
That is a valid result. “Custom theme” means the public metadata does not identify a known marketplace product; it does not mean the site lacks a WordPress theme. Record the exact name, author, and version that are exposed, and explain that the public evidence does not establish a commercial origin.
Best Value
Several theme directories appear
Separate the active-looking path from unrelated files. A site may retain unused themes, load a parent and child together, or include assets from a plugin that happens to use a similar directory name. Public source alone cannot prove which installed theme is active; the dashboard can.
The stylesheet request returns an error
Try the exact path from the source, including any subdirectory, then test the root theme directory’s style.css. If both fail, note that the metadata is not publicly available. Avoid repeatedly requesting protected files or attempting to bypass access controls.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →How to report the result accurately
A useful report states what was observed, how it was verified, and what remains uncertain. Include the page or dashboard route you checked and the relevant metadata fields.
- Verified public theme: “The source references directory X, and its
style.cssheader listsTheme NameY, author Z, and version V.” - Child theme: “The active-looking child metadata lists
TemplateP; the parent stylesheet identifies parent name Q.” - Custom result: “The exposed header uses a private or descriptive name; no public evidence establishes a commercial theme.”
- Inconclusive result: “The site’s assets are combined or rewritten, and the theme stylesheet could not be confirmed.”
Keep the distinction between a detected theme and a recreated design. If you are documenting a site for a redesign, also record the builder, major plugins, custom CSS, and template features separately when you can verify them. That prevents a theme name from being mistaken for a complete specification of the site.
Quick Recap
A repeatable checklist
- Open the site and view page source.
- Search for
/wp-content/themes/. - Write down every distinct theme directory found.
- Open each relevant directory’s
style.css. - Read
Theme Name,Author,Version, andTemplate. - When
Templateis present, inspect the parent stylesheet too. - Separate theme evidence from builder or plugin evidence.
- If you administer the site, confirm the active theme at Appearance → Themes.
- If public signals conflict or disappear, report the uncertainty instead of guessing.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
