Free WordPress Theme Detector

Find out what theme a WordPress website is using — the official title, version, author, and the base theme, plus the plugins that load on the page. This online tool reads public HTML and the theme files, opening style.css from the real href so CDN and subfolder installs still work, with technology fingerprints to confirm the site is built with WordPress. Custom, hardened, or headless sites can hide the theme.

How to detect what WordPress theme a site is using

Use this free WP theme detector when you need the public theme behind a domain, and the themes and plugins that leave traces on the homepage.

Paste a domain or URL above (for example example.com). One target per run.

Click Detect Theme. We fetch the homepage and read style.css from the real href, so a theme on a CDN or used on WordPress in a subfolder can still be detected.

Read the official title first. If the site uses a custom layer, the base theme appears as well. A version, author, theme URI, and screenshot appear only when those public files expose them. Plugins are listed when their files load on the page.

Need the full tech stack, not just the WordPress theme? Open CMS Detector. To see who hosts the site, use Hosting. DNS and registration stay on DNS Lookup and WHOIS Lookup.

What you get

Official title — taken from the style.css header when it is published. If the header is missing or blocked, we do not invent a marketplace name.
Base theme — when the active theme is a custom layer (the Template header in style.css).
Version, author, and theme URI — only when the header includes them. The hero shows the theme version, with the WordPress core version on a separate line.
Screenshot — the theme’s public screenshot.png or screenshot.jpg, when that file is reachable.
Plugins — slugs, and names when we can match them, from public /wp-content/plugins/ paths. Plugins that never load on the front end will not appear.
An honest miss — "Not a WordPress site", "Theme hidden", or "Theme folder only", with the caption "Folder only — not an official theme name".

What a theme detector tool can (and cannot) show

This WordPress theme detector answers which theme is being used, from public files and headers, and can be used on any WordPress website that publishes those files. If they use a WordPress theme, we try to detect a theme and list the WordPress theme and plugins on the homepage — not a dashboard login, vulnerability scan, or full inventory of installed add-ons.

How detection works

We fetch the homepage and look for WordPress paths such as /wp-content/themes/{slug}/, using the real href or src in the HTML so theme files on a CDN or in a subfolder still resolve. We then read the style.css header: Theme Name, Theme URI, Author, Version, Description, and Template (the base theme). Paths under /wp-content/plugins/ feed plugin detection. Technology fingerprints help confirm the site uses WordPress and may name well-known themes or plugins, but the official title in the hero comes from that header. A folder without a header is Theme folder only, not a marketplace title.

Custom layers and the base theme

Many sites run a custom layer on top of a base theme such as Astra, GeneratePress, or Divi; the base theme is the one you would actually install. If style.css contains a Template line, this detector shows both layers, each with the version and author those files publish. Installing only the custom layer without its base usually leaves a broken site. In WordPress this setup is a child theme on a parent theme.

Why some sites show "Not a WordPress site", "Theme hidden", or "Theme folder only"

If there are no public WordPress markers, we say the site is not WordPress. It may run Shopify, Webflow, a custom stack, or another CMS — in that case use the CMS Detector. If the site is WordPress but the theme path is rewritten, the style.css header is stripped or blocked, a security layer hides default folders, or the front end is headless, we say “Theme hidden”. When a folder is visible but style.css has no official title, we say “Theme folder only”. A miss is not proof that “no theme is used”. A failed fetch is reported as a fetch error, not as a hidden theme.

What this tool does not do

We do not log into wp-admin, list every installed add-on, scan for vulnerabilities, show theme prices or usage share, or export a bulk list of thousands of sites. We do not identify Shopify themes on this page. WordPress hosting belongs on Hosting; the rest of the public tech stack belongs on CMS Detector. Treat the result as a public-source clue, not as a certified audit.

Looking up a name before you buy or wait on a drop? Browse inventory in Karma.Domains.

Frequently Asked Questions

What does this WordPress Theme Detector show?

It shows the WordPress theme matched from the site’s public files: the official title from the style.css header, plus version, author, theme URI, and a screenshot when those exist. If a custom layer is active, the base theme is listed too. Plugins appear when their files load on the page. Use it to see the theme they’re using and the site’s design.

How does detection work?

We fetch the homepage, read public theme paths and /wp-content/plugins/ paths in the HTML, and open style.css from the real href. Technology fingerprints help confirm WordPress and may identify well-known themes or plugins. We only use what the site already publishes to visitors. This is a theme checker, not a wp-admin login.

Why does the result say "Not a WordPress site"?

We did not find public WordPress markers on the homepage. The site may use another platform. For the CMS and the rest of the public stack, use the CMS Detector.

Why does the result say "Theme hidden" or "Theme folder only"?

The site looks like WordPress, but the official title was missing, blocked, rewritten, or stripped. That happens with custom themes, hardened setups, some security layers, and headless front ends. If only a folder is visible, we return a separate Theme folder only status instead of treating the directory as a marketplace title.

Do you show child themes and parent themes?

Yes. When style.css includes a Template line, the active theme is the custom layer and we also read the base theme’s header. You need both layers if you want to install the same setup.

Do you detect WordPress plugins too?

Yes, when a WordPress plugin leaves a public /wp-content/plugins/ path on the page. Page builders, SEO plugins, forms, and caches often show up this way. Admin-only plugins usually do not, so the list is not a complete inventory of what is installed.

Can detection be wrong or incomplete?

Yes. Public files can be renamed, cached, or hidden. A screenshot may not match a heavily customized layer. Treat the result as a clue from public sources, not as a guarantee.

How is this different from the CMS Detector or the Hosting tool?

This page answers what WordPress theme a site is using, and which plugins load on the page — a theme and plugin detector. The CMS Detector answers what CMS and broader tech stack the site exposes. The Hosting tool answers who hosts it.

Is there a daily limit? Do I need an account?

No signup for the free tier. Limits match other Karma landing-tools: 1 target per run and the shared free daily domain limit of 10 per day.

How can I run more checks after the free daily limit?

Upgrade to the Pro plan for higher limits inside Karma.Domains, or pay as you go on RapidAPI / Apify.

Is there a Chrome extension?

Yes — the Karma Domains Chrome extension adds age and Karma Metric on SERPs and runs Checks from the popup.

Where can I browse expired domains to buy?

Alongside this free check, the full list of expired domains from 49 lists across 32 platforms (auctions, drops and buy-now listings) is on the Karma.Domains homepage, updated hourly.