Skip to content

What WordPress Theme Is That? Free Theme and Plugin Detector

This free WordPress theme detector shows the theme, parent theme and plugins any site runs. It also flags plugins that are closed or no longer kept up to date.

Try

  • No sign-up or email
  • Evidence behind every result
  • Rules from the official docs
WordPress theme detector result showing the active theme, its parent theme and a list of plugins with update status
How it works

How to find out what theme a site uses

  1. Enter the site address

    The homepage is enough. Our server fetches it the way a browser would and reads the site's REST API index.

  2. See the theme and its parent

    Free themes link to wordpress.org. Premium themes link to the author's site from the theme header.

  3. Check the plugin health list

    Plugins at risk sit at the top. Closed plugins come first and outdated ones follow.

What it checks

What the WordPress theme detector finds

Each result shows the signal that found it. You can see how we know and check every line yourself.

Theme and parent theme

We read the theme's own style.css header for its real name, version and author. A child theme leads us to its parent.

Plugins from page files

We list every plugin folder in the scripts and styles the homepage loads. The version shows when the file carries one.

Plugins from the REST API

SEO, form and payment plugins register their own API routes. This finds plugins that load no files on the page.

Closed and outdated plugins

Each plugin is looked up on wordpress.org for its last update and tested version. Closed plugins come with the date and reason.

Hosting and CDN hints

Response headers can name the host or CDN, such as Cloudflare, Kinsta, WP Engine or SiteGround.

WordPress version or platform

The version comes from the generator tag when the site shows it. Shopify, Wix and other platforms are named when the site is not WordPress.

What WordPress theme is that site using?

To find out what WordPress theme a site uses, enter its address in the detector above. It reads the theme folder from the page source and opens that theme's style.css file. The header there gives the theme name, version and author, and a child theme names its parent.

You can do the same check by hand in about a minute. It works on any desktop browser.

  • Open the site and press Ctrl+U (Cmd+Option+U on a Mac) to view the page source.
  • Search the source for wp-content/themes/ and note the folder name that follows it.
  • Add style.css to the end of that folder path and open it in a new tab.
  • Read the Theme Name line. A Template line means this is a child theme and names the parent folder.

The manual check fails when a site serves its files from a CDN address you do not spot. The detector matches theme paths on any host and checks up to three theme folders on the page.

How does a WordPress plugin detector find plugins?

A WordPress plugin detector looks for the traces each plugin leaves on the public site. Many detectors only scan the page HTML for plugin folders. This one also reads the REST API index at /wp-json/ where plugins such as WooCommerce and Rank Math register routes.

SignalWhat it findsHow sure
Plugin folders in page filesPlugins that load CSS or JavaScript and their version when the file shows itConfirmed
REST API routesBack-end plugins such as WooCommerce, Yoast SEO, Rank Math and form pluginsLikely on its own
Generator tagsElementor, WooCommerce, WPML and Site KitLikely on its own
HTML commentsSEO and cache plugins that sign the page HTMLLikely on its own

A plugin found by two signals moves up to Confirmed. Each plugin is then looked up on wordpress.org for its last update, tested version and install count.

This matters most on WooCommerce stores. Payment plugins such as WooPayments, Stripe and PayPal Payments often load scripts only on cart and checkout pages. Their REST routes still show up in the index the homepage scan reads.

Why can't a detector find every plugin on a site?

No outside tool sees every plugin because many plugins leave no trace on public pages. Backup, security and admin tools often run only inside wp-admin. Cache plugins also merge CSS and JavaScript into one bundle that hides the plugin folders a detector reads.

  • Combined files: When the page shows few plugins and loads cached or minified bundles, the report marks the list as partial.
  • Blocked REST API: Some sites close /wp-json/ to visitors. The detector tries the ?rest_route=/ address before it gives up on that signal.
  • Homepage only: The scan reads the homepage. A plugin that loads only on product or checkout pages may not show in the page files.
  • Renamed folders: A site that moves or renames wp-content hides its folder names from every detector.

We would rather tell you a list is partial than guess at plugins we cannot see.

What does it mean when a WordPress plugin is closed?

A closed plugin has been removed from the wordpress.org directory and is no longer available for download. Reasons include a security issue, a guideline breach, a license problem or a request from the author. Sites that installed it before the closure can keep running it.

The detector shows the closure date and the reason wordpress.org gives. The directory adds the reason to its notice 60 days after the closure.

Outdated is a softer warning. We flag plugins with no release in over two years and plugins tested three or more major WordPress releases behind the current one.

  • Replace a closed plugin with a maintained plugin that does the same job and delete the old one.
  • Test outdated plugins on a staging copy before the next WordPress or WooCommerce update.
  • Run the WordPress vulnerability scanner on the same site to match its versions against known security holes.

What is the difference between a child theme and a parent theme?

A child theme sits on top of a parent theme and changes only the parts it overrides. Its style.css header carries a Template line that names the parent theme folder. Updates to the parent then leave the child theme's changes in place.

When the detector finds a child theme, the report names the parent as the main theme. The parent is the one you can download or buy. The child is often custom code written for that one site.

Want the same setup on your own site? Follow our guide on how to create a WordPress child theme.

Can I use the same WordPress theme as another site?

Yes, you can install the same theme the detector found on your own site. WordPress.org treats themes as derivative works of WordPress that inherit its GPL license. A premium theme still needs its own purchase for updates, support and the demo content.

What you cannot copy is the other site's text, photos, logo and brand. The theme is also only part of the look. Page builder layouts, custom CSS and imported demo pages make up the rest.

Sources

More free tools

More free tools for WordPress sites

FAQ

Theme detector questions

Short answers on finding themes and plugins and how far a detector can see.

Ask us a question

Yes. There is no sign-up, email or plugin to install. You can run up to 120 checks an hour from one connection before the tool asks you to wait a little.

Our server fetches the public homepage, the theme stylesheet and the REST API index. The result is kept for 6 hours under that address and a repeat check in that time loads from the cache. The tool reads nothing behind a login.

None of the WordPress signals showed up on the homepage. When the HTML matches another platform the report names it, such as Shopify, Wix, Squarespace or Webflow. A heavily customized WordPress site can also hide every signal.

Yes, when the theme folder appears in the page source. The report reads the name and author from the theme's own style.css and links the author's site. Themes that are not on wordpress.org show no update history.

Confirmed means the plugin's own files load on the page or two signals agree. Likely means one signal found it, such as a REST route or an HTML comment. If it is your site, check a Likely plugin in wp-admin.

The plugin folder was found but wordpress.org has no listing under that name. It is usually a paid plugin, a custom build or a renamed folder. The detector has no update history to check for it.

Only when the site prints the WordPress generator tag in its HTML. Many sites remove it and the report then says the version is hidden. When the version shows, the report compares it with the latest release.

You can make detection harder by combining files and limiting the REST API. That does not make a site any safer on its own. Keeping every plugin updated matters far more than hiding plugin names.

Found weak plugins on your own site? We keep them current

The detector answers "what WordPress theme is that" and shows the plugins behind it. Our WordPress care plans update plugins, themes and core on a staging copy before anything goes live. Abandoned plugins get flagged with a suggested replacement.

Support within hours A real person replies
14-day money back Fair terms
Always compatible Latest WP and Woo
Custom builds Made for your store

Why store owners pick us

What comes with every plugin you buy.

  • 26 premium WooCommerce plugins
  • 500+ five-star reviews
  • Served in 158+ countries
  • Elite Author on Envato
  • HPOS and latest Woo ready
  • Support that replies in hours
Pedro Lima, DevDiggers customer Kareem Al Samman, DevDiggers customer Valentina Dancheva, DevDiggers customer Diego Lopes, DevDiggers customer 5 star rating from 500+ reviews

Trusted worldwide

Store owners in 158+ countries run on DevDiggers.

Alan, DevDiggers customer Shiyanthan M, DevDiggers customer Pawel Pytasz, DevDiggers customer Marius, DevDiggers customer

Proven on Envato

Elite Author with $125,000+ in sales.