How to Find What WordPress Theme a Website Is Using

Quick answer: view the page source and search for /wp-content/themes/. The directory name immediately after that path is usually the active theme or child theme. Open its style.css file and inspect the header for Theme Name, Theme URI, Author and Template.

Use the result as a technical clue, not permission to copy a site’s design, code or branded assets.

Method 1: Search the page source

Open a public page, right-click, choose View Page Source, and search for:

/wp-content/themes/

A stylesheet URL may look like:

https://example.com/wp-content/themes/sample-child/style.css?ver=1.4

Here, sample-child is the exposed directory name. Copy the stylesheet URL, remove the query string if necessary, and open it directly.

At the beginning of a conventional theme stylesheet, you may find:

/*
Theme Name: Sample Child
Template: sample-parent
Author: Example Studio
*/

The Template field indicates that this is a child theme and names its parent directory. A custom theme may use a generic folder name or omit useful public metadata.

Method 2: Use browser developer tools

Open Developer Tools and select the Network panel. Reload the page, filter by CSS, and inspect requests containing wp-content/themes.

This method helps when the source is crowded or stylesheets are loaded later. The Sources panel can also reveal theme asset paths for JavaScript, fonts and images.

If the page uses a combined cache file, inspect its initiator or source map, but do not assume the cache filename identifies the theme.

Method 3: Check WordPress clues first

Before looking for a theme, establish whether the visible frontend is powered by WordPress. Search for:

• /wp-content/ or /wp-includes/ assets;
• a link to /wp-json/;
• WordPress block classes such as wp-block-;
• the generator meta tag, when not removed.

None is individually conclusive. A CDN can rewrite asset URLs, and a headless WordPress site may render through a separate application with no public theme.

Why theme detectors fail

An automated detector may report nothing when:

• CSS and JavaScript are combined under a cache or CDN path;
• the theme directory was renamed;
• a custom theme has no public listing;
• the site uses a child theme with minimal metadata;
• WordPress supplies content to a headless frontend;
• access controls block the detector’s request;
• the page is a static export rather than a live WordPress response.

A failed result does not prove the site is not WordPress.

Parent theme versus child theme

If style.css contains Template: parent-folder, the visible directory is a child theme. The parent supplies most templates and code, while the child may override styling or files.

To understand the design, inspect both identities. However, a child theme can contain enough custom work that the parent demo looks completely different.

What a detected theme cannot tell you

The theme name does not reveal:

• page-builder layouts;
• plugin-generated headers, forms or sliders;
• custom blocks and post types;
• licensed fonts and stock images;
• brand settings and content;
• private code in a child theme or plugin.

If you want a similar capability, list the functional requirements—navigation behavior, content layout, filters, checkout—not merely the theme name. Then choose maintained software that fits your own project.

A reliable manual workflow

1. Confirm WordPress clues.
2. Search source for /wp-content/themes/.
3. collect every unique theme directory, not just the first result.
4. Open the public style.css where accessible.
5. Check Theme Name and Template metadata.
6. Verify the candidate against its official directory or vendor page.
7. Treat custom or hidden results as unknown rather than guessing.

Once you have selected a legitimate theme for your own site, use How to Install a WordPress Theme and test it with your content.