
TL;DR: Start with the Shopify Theme Detector or Store Inspector extension, then inspect the public theme metadata if the result is unclear. A catalog ID is stronger evidence than a merchant's theme name. An unknown or custom label does not establish that a store bought bespoke development.
Some links in this article are affiliate links. We may earn a commission if you purchase through them, at no extra cost to you.
Finding the base theme helps you shortlist designs or scope a migration. It does not tell you which custom sections, apps, images or code produced the storefront you see. Record the evidence behind a result before buying a theme or pitching a redesign.
What Our Theme Records Actually Show
Our retained database summary, collected February 18, 2026, covered 143,211 store records with a recorded theme name. These are historical detection records, not a random sample of all Shopify merchants or a manual accuracy test.
| Recorded theme name | Store records | Share of the 143,211-record cohort |
|---|---|---|
| Dawn | 17,000 | 11.9% |
| Debut | 13,305 | 9.3% |
| Custom | 11,685 | 8.2% |
| Prestige | 5,196 | 3.6% |
| Impulse | 5,064 | 3.5% |
Method: The saved theme-statistics query grouped non-null theme names together with their stored theme type and calculated each row's share using the total store count. The retained summary contains the rows above. Individual scans were not all collected on February 18, and their age distribution is unavailable. These counts describe that saved dataset; they are not current adoption figures.
The important detection lesson is the 11,685 records named Custom. That label is a result of classification, not proof of 11,685 bespoke builds. A renamed catalog theme, an uploaded theme and a theme detected only through assets can all leave less useful public metadata. The count cannot tell us which explanation applies to each store.
What We Learned From Building the Detector
We inspected Store Inspector's theme-detection implementation on October 10, 2026. When public theme metadata is available, the extension prefers schema_name or schemaName over the editable name. It also retains available theme and Theme Store IDs. When that route fails, it falls back to public signatures, metadata, inline snippets and asset paths.
One fallback can return Custom (detected from assets) from a Shopify asset path. That tells you how the result was obtained; it does not identify the original theme. This explains why two detectors can return different names without either having proved a bespoke origin. This is an implementation review of our own detector, not a hands-on comparison of competing tools.
Shopify's authenticated OnlineStoreTheme API model distinguishes a merchant-set name from a nullable Theme Store ID. A competitor's public page may expose fewer fields, and the public object is not guaranteed to match the authenticated API. Treat absent metadata as an unresolved result.
Five Ways to Investigate a Store's Theme
1. Start With a URL Lookup or Extension
Paste the storefront URL into our free theme detector, or open the storefront with the Store Inspector extension. Record the returned name and any catalog ID or source clue.
Use the result as the start of your investigation. A detector cannot reconstruct private theme files, app settings or every customization. If it returns Custom or Unknown, continue with the checks below.
2. Inspect Public Theme Metadata
Open the storefront, choose View Page Source, and search for Shopify.theme, theme_store_id, schema_name and schemaName. Availability varies by storefront.
For example, an illustrative public object might look like this:
Shopify.theme = {
name: "Merchant-renamed theme",
schema_name: "Catalog theme name",
theme_store_id: null,
role: "main"
};
This example is not an observation of a real store. The merchant label and schema label can differ. A missing or null catalog ID leaves the origin unresolved; it does not prove either custom development or a specific purchase source.
When an ID or recognizable schema name is available, compare the candidate with its official Theme Store listing. A match can identify a base theme, but the live storefront may differ substantially from its demo.
3. Use Assets and Comments as Corroboration
Search public HTML or the browser's Network panel for theme-related CSS and JavaScript names. A filename such as dawn.css can suggest Dawn, but files can be renamed, copied or retained after a redesign. Shopify CDN assets corroborate the platform more readily than the original theme.
The /cdn/shop/t/…/assets/… path contains a store's theme asset identifier. Do not treat that number as the Theme Store catalog ID. Liquid templates are rendered on the server, so searching public HTML for a private layout/theme.liquid file is not a reliable method.
4. Compare a Second Lookup
A second detector can give you another candidate to investigate. Tools such as Koala Inspector and BuiltWith have different coverage and output conventions. A matching result is useful corroboration; two matching labels do not establish independent accuracy if both use the same public signal.
We have not documented a same-store comparison in this article, so we do not rank their accuracy or claim that every tool was tested. Check the current vendor page for access and pricing before selecting a paid workflow.
5. Confirm the Platform Before Interpreting Theme Clues
Generic /products, /collections or /admin routes are preliminary clues. They are not unique to Shopify. Corroborate the platform through Shopify-specific public HTML, CDN resources or network responses, and inspect redirects rather than assuming any login page proves Shopify.
This check establishes the context for theme research; it does not reveal the theme itself. A headless storefront may use Shopify commerce services while presenting a frontend that does not follow the usual Online Store theme structure.
How Much Confidence Should You Place in a Result?
| Evidence | Useful conclusion | What remains unresolved |
|---|---|---|
| Catalog ID with a matching listing | Candidate base theme | Live customizations and version |
| Recognizable schema name | Candidate base theme | Whether metadata was changed or copied |
| Merchant-assigned name | Store's visible label | Original theme and purchase source |
| Asset filename or comment | Candidate worth checking | Original theme without corroboration |
| Custom or Unknown result | Detector could not establish a catalog identity | Bespoke build, renamed theme or missing signals |
If you are an agency, verify a concrete problem on the live store before suggesting an upgrade. A free theme does not prove poor performance or budget, and a paid theme does not prove a merchant wants more development work.
Choosing a Theme After Identification
Compare the features you actually need: product options, navigation, search, international storefronts and the sections in your planned design. Test those features with representative products and images. Revenue thresholds do not determine which theme is appropriate.
Shopify supports free themes, paid Theme Store themes and theme uploads. Its theme installation guidance, checked October 10, 2026, explains that you can preview a paid theme before purchase, but must purchase it to publish it. A Theme Store license applies to the store for which it was purchased.
As specific price examples checked on October 10, 2026, Prestige was US$400, Impact US$400, and Focal US$320. These are three listing prices, not a market-wide range. Obtain a scoped quote for custom development rather than inferring a budget from a storefront's appearance.
Test the Configured Store's Performance
A theme name cannot give you a reliable speed score. Images, apps, custom scripts and configuration can change the result. Test the pages and device conditions relevant to your customers, and record the URL, date, configuration and repeated-run method when comparing lab tests.
For your own store, Shopify's web performance reports, checked October 10, 2026, report real-user loading, interactivity and layout stability. Use those measurements to investigate the actual experience. They are different evidence from a Lighthouse run on a theme demo.
Frequently Asked Questions
Can I detect a renamed Shopify theme?
Sometimes. A schema name or catalog ID may preserve a useful clue after the merchant changes the visible name. If only the edited name is exposed, the base theme may remain unknown.
Does Custom mean a custom-built theme?
No. In a detection result, it can mean the available signals did not map to a recognized catalog theme. Ask the owner or developer when provenance matters.
Can I copy a competitor's design by buying its theme?
Buying the same base theme gives you that theme's licensed features. It does not give you the competitor's custom code, content, brand assets or app configuration. Preview the candidate with your own content before deciding.
Can a store change themes without changing its products?
Shopify's theme guidance supports adding and previewing themes separately from the live theme. Check templates, app integrations and settings before publishing a replacement; identification alone does not establish migration effort.
Which method should I use first?
| Your task | Starting point |
|---|---|
| Check one storefront | URL lookup |
| Research while browsing | Store Inspector extension |
| Resolve an ambiguous label | Public metadata, then asset corroboration |
| Evaluate a theme for your store | Official demo and a preview with your content |
| Investigate performance | Measurements of the configured store |
Find Shopify Clients Worth Your Time
Search by niche, traffic, and tech stack. Export with verified founder contacts.Search stores by niche, traffic, and tech stack. Export with verified founder contacts so you can skip the research.
![Best Shopify Dropshipping Apps 2026 [1.36M]](/_next/image?url=%2Fimages%2Fblog%2Fbest-shopify-dropshipping-apps.webp&w=3840&q=75&dpl=dpl_DvYQBpGxU6SVCVBC68k3GBScEAy1)

