You can find what theme a website is using in under ten seconds with a detector tool, or in a couple of minutes by reading the page source yourself. Both work. The right method depends on the platform - a Shopify store leaves obvious fingerprints in its assets folder, a WordPress site exposes a style.css path, a Wix or Squarespace site hides almost everything behind their builder. This guide walks through every detection method, what each one actually reveals, and the platform-specific quirks that trip people up.

Key Takeaways
1
A theme detector is the fastest path - you'll have the theme name, version, and developer in seconds for most platforms.
2
Manual detection works on every site that ships its CSS or templates publicly, and it teaches you what fingerprints to look for next time.
3
Some platforms (Wix Studio, Squarespace 7.1) intentionally obscure templates - knowing why saves you hours of pointless source-digging.

Why It Pays to Know What Theme a Site Is Using

The first reason most people land here is competitive research. You like a competitor's storefront, you want the same look, and the fastest path is finding their theme and either using it directly or briefing a designer with a clear reference. Knowing the theme converts "I want a site that looks like that" into a specific product you can buy or fork.

The second reason is design inspiration without the guesswork. Detecting the theme tells you whether what you're looking at is a stock template (replicable for $200) or a heavily customized build (likely thousands in agency time). That single data point changes your budget conversation.

The third - less obvious - reason is pre-purchase due diligence. If you're buying a Shopify store on a marketplace, the theme's age, support status, and license tell you how much technical debt you're inheriting. A site running a 2018 ThemeForest theme that's no longer updated is a different acquisition than one on a current Shopify-supported theme.

Agencies and freelancers also use detection daily for client onboarding. Knowing the existing theme before quoting a redesign tells you whether you can extend the current setup or you're starting from zero.

Method 1: Use a Theme Detector Tool (Fastest)

If you don't care how the detection works and you just want the answer, paste the URL into a detector. We built one for every major platform - paste once, get the theme name, version, and developer in a single pass.

Use the right detector for what you're investigating:

What a good detector gives you that the source code does not is a clean answer with confidence: theme name spelled the way the developer spells it, version number, link to the marketplace listing if one exists, and a flag if the site is using a heavily modified or completely custom build. Manual detection eventually gets you there, but you'll spend ten minutes parsing minified CSS for what a tool returns in two seconds.

Method 2: Read the Page Source Manually

If a tool comes back blank or you want to verify what it found, read the source yourself. Right-click → View Page Source on any browser, or hit Ctrl+U (Windows) / Cmd+Option+U (Mac).

What you're looking for varies by platform, but the universal first step is the <link> tags in the <head>. Stylesheet paths give away the theme name in plain English on most platforms. A path like /wp-content/themes/astra/style.css tells you Astra. A path like /cdn/shop/t/12/assets/theme.css tells you Shopify but not the theme - you'll need a different fingerprint for that (more on Shopify below).

Generator meta tags are the second universal tip. Most CMS platforms inject <meta name="generator" content="..."> with the platform name and sometimes a version. WordPress, Drupal, Joomla, and Squarespace all do this by default, though it can be disabled.

Asset folder names are the third giveaway. Look at the URLs of images and scripts. If you see /sites/all/themes/{name}/, that's Drupal. If you see /templates/{name}/, that's Joomla. /wp-content/themes/{name}/ is WordPress. /cdn/shop/t/ with a numeric ID is Shopify but the theme name is hidden - keep reading.

Method 3: Use Browser DevTools and Extensions

If you do this often, install the platform-specific browser extensions for one-click detection on every site you visit. Most major theme detectors offer a Chrome extension that puts the theme name in a popup the moment a page loads.

For ad-hoc detection, the browser DevTools Network tab is more powerful than View Source. Open DevTools (F12) → Network tab → reload the page → filter by "css" or "js". You'll see every asset the site loaded, in order, with full paths. This catches themes that are only referenced in dynamically loaded scripts and miss the View Source pass.

The Console tab can also help. On a Shopify site, type Shopify.theme and press Enter - it returns an object with the theme name, ID, and role. That single command answers the question on any Shopify storefront in two seconds. WordPress sites sometimes expose WP_THEME or similar in the JS scope; less reliable, but worth a try.

Platform-Specific Detection Tips

Shopify

Shopify is the easiest platform to detect once you know the trick. The theme name doesn't appear in the source path - Shopify renames assets with a numeric ID - but the JavaScript object Shopify.theme exposes the name, version, and role on every storefront. Open the browser console, paste Shopify.theme, hit Enter, done. For stores that have set theme.role to "unpublished" or that block console access, our Shopify Theme Detector uses additional fingerprints (Liquid markers, default section IDs) to identify the theme anyway.

WordPress

WordPress is the most transparent platform - the theme folder name is in the source on every uncached page. Search the page source for /wp-content/themes/ and the next path segment is the theme slug. From there, search "{slug} wordpress theme" to find the marketplace listing. Note: a parent/child theme setup will show the child theme path; the parent is in the child's style.css header (look for "Template:"). For sites that strip wp-content from URLs (some security plugins do this), our WordPress Theme Detector falls back to other fingerprints.

Squarespace

Squarespace 7.0 templates were easy - the template family showed up in HTML class names like tpl-bedford. Squarespace 7.1 changed everything: every site uses the same underlying template engine ("Fluid Engine"), so the old detection trick fails. What you can still detect is the original template the site started from, which Squarespace stores in the page metadata. Our Squarespace Template Detector handles both 7.0 and 7.1 sites and is honest about when 7.1 detection is approximate.

Wix

Wix is the hardest platform to detect because Wix users heavily modify their starting template, and Wix doesn't expose the original template ID in the source by default. The detection works on freshly created sites, gets fuzzy on heavily customized ones, and breaks entirely on Wix Studio sites (Wix's newer builder, which doesn't use templates the same way). When our Wix Template Detector says "no template detected," it usually means either Wix Studio or a deeply customized site - not a tool failure.

PrestaShop, Drupal, Joomla

All three follow the WordPress pattern: the theme/template folder is in the source. PrestaShop uses /themes/{name}/, Drupal uses /sites/all/themes/{name}/ or /themes/contrib/{name}/, Joomla uses /templates/{name}/. Use our PrestaShop, Drupal, or Joomla detectors for one-click answers, or grep the source yourself.

What to Do When You Can't Detect a Theme

About 5–10% of sites you'll check come back as undetected, and that's not always a bug. Three real reasons it happens:

The site is fully custom. Plenty of agencies build storefronts from scratch, especially on headless commerce stacks (Next.js + Shopify Storefront API, etc.). There's no theme to detect because there isn't one. The detector returning blank is the right answer.

The site is heavily modified. A starting theme that's been gutted and rebuilt may show fingerprints of the original - sometimes inconsistently. If our tool returns a low confidence score, that's typically what you're seeing.

The platform actively obscures the template. Wix Studio and Squarespace 7.1 are the main offenders. There's no source-code fingerprint to read.

When you hit one of these, your next step is reverse engineering the design rather than the theme. Capture the colors, fonts, and layout, then brief a designer or use that as a Figma starting point.

What to Do Once You Have the Theme Name

Finding the theme name is step one. Here's what to do with that information:

If you want to use the same theme: Search the theme name on the platform's official marketplace - Shopify Theme Store, ThemeForest, WordPress.org, etc. Confirm it's still available and actively maintained (look for the last update date). A theme that hasn't been updated in two years may have compatibility issues with the current platform version.

If you're briefing a designer: The theme name gives the designer a concrete starting point. They can buy the same theme and customize it to match, or use it as a visual reference for a bespoke build. Either way, "I want something like the [theme name] theme" is a much better brief than a screenshot.

Before briefing your designer, it also helps to know your own screen resolution so they can build and review designs at the right size for your display. Our free screen resolution checker shows your current display dimensions and available viewport in one click.

If you're buying a site that uses this theme: Check whether the theme license transfers. Shopify themes are licensed per store - you'll need to purchase a separate license after an acquisition. ThemeForest licenses are similarly store-specific. Factor this into the acquisition cost.

If the site is heavily customized: The theme is just the foundation. Ask the seller or agency for a list of customizations, plugins, and apps that produce the specific features you're interested in. The theme explains the design base; it doesn't explain everything you see on the page.

Related Posts

Want to go deeper? Explore these related guides:

Finding Any Website's Theme: The Right Method for Every Situation

For 90% of sites, a theme detector gets you the answer in seconds - paste the URL into the platform-specific tool or our Theme Detector and you're done. The manual methods (View Source, DevTools, the Shopify.theme console trick) are worth knowing for the times the tool is ambiguous, the platform actively obscures templates, or you want to teach yourself the fingerprints. For more context on choosing the right ecommerce platform once you know what you're looking at, see our complete guide to website builders for ecommerce.

Show More

* read the rest of the post and open up an offer