How to Find Out What Theme Any Website Is Using

You land on a site with a layout you love, and the first question is obvious: what theme is this? For most platforms the answer isn't visible anywhere in the UI — you have to go looking for it, and where you look depends entirely on what the site is built on.

Start with the platform, not the theme

Before you can find a theme, you need to know what CMS a site is running. A handful of clues usually give it away without any tools at all:

• View source (right-click → View Page Source) and search for wp-content (WordPress), cdn.shopify.com (Shopify), or a <meta name="generator"> tag naming the platform directly.
• Check the URL structure. WordPress sites often expose /wp-json/; Joomla and PrestaShop both organize assets under a /templates/ or /themes/ path with the active theme's folder name right in it.
• Look for tell-tale JavaScript. Shopify stores embed a Shopify.theme object; Moodle sites set an M.cfg configuration object. Both are visible in page source without needing dev tools.

Finding the theme name manually

Once you know the platform, the theme name is usually one more step away:

• WordPress: every theme ships a style.css file with a standard header comment — Theme Name, Author, Version. Find the stylesheet under wp-content/themes/<theme-name>/ and open it directly.
• Shopify: the inline Shopify.theme object in page source includes the theme's name and ID outright.
• Drupal: look for an .info.yml manifest under /themes/custom/<theme-name>/.
• Joomla: a templateDetails.xml file lives at /templates/<template-name>/.
• PrestaShop: check for config/theme.yml under /themes/<theme-name>/.

Or skip the manual work entirely

All of this is exactly what a theme detector automates: fetch the page once, identify the platform, locate the right manifest or config file, and hand you back the theme name, version, and author in a couple of seconds. That's the whole premise behind this site's Auto-Detect page — paste a URL, and it does the platform-identification step for you before running the real scan.

The manual method works fine for a one-off lookup. It stops being worth it the moment you're checking more than one or two sites.

What you can't detect from the outside

Detection only ever sees what's publicly reachable. Heavily customized child themes, sites that block direct access to their asset folders, or installs that strip standard headers will return partial or no results — that's a deliberate server configuration, not a failure of the method.