WordPress Theme Detector

A WordPress theme detector reads a public page and works out which theme is rendering it. You paste a site address and get the theme name, its version and author, whether it is a child theme and what its parent is, the WordPress version behind it, and the exact signals each of those answers came from. It is the fastest way to answer "what theme is this" without asking the person who built the site. Plugins are a separate question with separate evidence, so they are a separate tool: the [WordPress plugin detector](/tools/plugin-detector) lists what is loading on the same page.

The detection works because WordPress publishes its own structure in the pages it serves. Themes load their stylesheets from /wp-content/themes/<slug>/, core files come from /wp-includes/, the REST API is advertised in a link tag and in a Link header, and many installs still emit a generator meta tag naming the WordPress version. Each theme also ships a style.css whose header block states the theme name, the version, the author and, for a child theme, the parent it extends. This tool reads the page, then asks that theme folder for its own style.css, so the name it reports is the one the theme gives itself rather than a guess from a folder slug.

A worked example shows what comes back. Scan a typical WooCommerce store and the report opens with the theme it is running, the site address and the WordPress version. The Theme card gives the name, the version from style.css, the folder slug, the author and, if there is one, the parent theme the site is a child of. A stack row names anything worth calling out on its own, such as WooCommerce, Elementor or a page builder. Underneath, What this is based on lists the literal signals the answer rests on: the generator meta, the theme asset path, the REST API link, the body classes.

The honest part matters more than the clever part. A site behind a managed host that rewrites or blocks /wp-content/ can be WordPress and still show no theme at all, and reporting that as "not WordPress" would be a confident wrong answer. So the report distinguishes between what was found, what could not be checked, and what was ruled out, and it always says which source each answer came from. The version in style.css is the theme author's number rather than proof of what is installed: a customised theme can carry a version its files no longer match. A custom theme that was never published anywhere will return a folder name and nothing else, because there is no style.css header worth reading and no catalogue entry to match. Every one of those limits is stated on the report rather than buried in an FAQ. The scan runs on our server, because a browser cannot fetch another site directly, and nothing about the sites you check is stored. It is free, no signup.