Most Popular Shopify Themes: 143K Store Study

TL;DR: Dawn was the largest named theme group in StoreInspect's February 18, 2026 extraction, with 17,000 of 143,211 store records, or 11.9%. Free, paid and custom classifications accounted for 39.5%, 35.2% and 25.3%. These are historical detections in our database, not global market share or evidence that a theme improves revenue.

Study scope and detection limits

The retained theme-data-summary.md records a February 18 extraction from 143,211 stored store rows. Its theme-stats.ts queries group stored theme names and classifications, rather than constructing a dated latest-successful-snapshot panel. All rows had a nonnull theme name; that is field coverage, not 100% identity accuracy.

The displayed publication date is February 13. It predates this retained extraction and does not describe the study's collection date. The database observations underlying February 18 were not restricted to a recent observation window. We reviewed the evidence and interpretations on October 10, 2026.

Public theme detection can use exposed Shopify theme information and storefront assets. A merchant can rename a theme, modify it extensively or use a third-party build. “Custom” is a classification that can include marketplace themes, not proof of a bespoke development team. Theme name does not establish version, app-block support, checkout configuration or performance.

Traffic tiers and Plus fields are detected or estimated. LeadFit uses technology signals, including theme-related inputs; it is not independently measured revenue, conversion or purchasing authority.

For an individual store, use the theme detector or extension as an initial observation, then validate the actual theme and functionality. A database record is a starting point for that check.

Largest named groups in the retained summary

“Custom” in this named-group table is different from the entire custom-type cohort. Other names also have a custom classification.

Dawn ranks first overall, but it does not lead every segment in the published study. In the under-50K estimated-traffic table, Custom had 10,788 records and Debut 7,224, ahead of Dawn's 6,962. In Hobby, Debut's reported 12.1% exceeded Dawn's 11.2%. The retained summary's universal Dawn claim is therefore too broad.

Popularity identifies a common installed base for compatibility research. It does not tell you which theme fits a particular catalog or customer journey.

Free, paid and custom comparisons

The summary retains these theme-type comparisons:

Paid-theme records had about 47% more counted app signatures on average than free-theme records: 2.2 ÷ 1.5 − 1. Counts include detectable payment technology and can miss native, backend or custom functionality.

The 78 versus 57 score comparison is about 37% higher, but the score itself uses technology signals. That is not a 37% conversion, revenue or lead-quality improvement. Buying a paid theme has not been shown here to produce better business outcomes.

Paid does not lead every reported metric. The published table assigned the custom cohort a larger mean catalog and a slightly higher share of records in the 1M+ estimated tier. We do not use the old mean-product values as current catalog evidence because the historical count treatment does not exclude known partial-catalog artifacts.

A free theme can serve a large business. The historical 5M–20M estimated-traffic cohort was reported as 27.6% free, 38.3% paid and 34.0% custom. This does not establish a longitudinal transition from free to paid to custom.

Correcting the Shopify Plus denominator

The source counted 96,967 stored rows with the Plus flag. Its top-theme query then limited results to 20 theme groups and calculated percentages using only the sum of those groups. The original article labeled those percentages as shares of all Plus records.

Using the full 96,967 flagged-row denominator gives:

These calculations preserve the numerator counts in the published historical table and apply the all-flagged denominator from the retained summary. They are not a refreshed plan-verification study. The complete historical query output is not retained alongside the summary.

Dawn's corrected 13.44% share is modestly above its overall 11.9%, rather than more than twice as high. Prestige and Impulse together account for 9.02% of all flagged records, not 18.1%.

A stored Plus flag can be wrong. Use Plus identification checks and merchant-side confirmation before treating these rows as verified Plus subscriptions or inferring a service budget.

Legacy names identify assessment candidates

The summary records 27,643 rows in the query's legacy free-theme group, or 19.3% of the sample. The group covers names such as Debut, Brooklyn, Minimal, Venture, Supply, Simple, Narrative and Boundless.

That count is useful for finding stores whose theme architecture may deserve a review. It does not establish that every installation is unmodified, broken, missing modern features or ready to buy a redesign.

Shopify's migration assessment, checked October 10, 2026, allows merchants to continue using a vintage theme if it meets their needs. Options include a newer theme, an updated version or a manual migration. Existing customizations and app compatibility affect the choice.

Before proposing work:

1. Confirm the theme identity and version where the merchant can provide them.
2. Identify the specific required feature or reproducible customer problem.
3. Check whether custom code already supplies that function.
4. Test relevant section and app-block behavior in the merchant's setup.
5. Agree on compatibility, preservation of customizations, budget and rollback.

See finding redesign prospects for a workflow focused on observable requirements.

Theme and app co-detection

The retained summary reports a 42.3% Klaviyo detection rate for the Prestige cohort. The published table reported 39.8% for Impulse, 25.0% for Dawn and 9.8% for Debut. These are historical co-detection rates under the query's recorded app identities, not evidence that one theme causes merchants to adopt Klaviyo.

The full historical app-by-theme output is not retained. We therefore do not use those provider rows to calculate a category-wide “missing reviews” audience. In particular, 100% minus Judge.me's rate is the share without that particular recorded identity, not the share without every review app. The same published tables also list Loox.

A proper reviews assessment needs a per-store union of all reviewed signatures and a functional storefront check. Native, backend or custom review tools can be missed. A paid theme without a detected reviews category is a research candidate, not proof of unmet demand or intent.

For compatibility work, use technology-stack research to plan questions about reviews, messaging and event integration.

Comparing category and country segments

The published segment tables show variation, but several original superlatives overstated it:

• Outdoor & Adventure's reported paid-type share was 39.6%, ahead of Baby & Kids at 39.5% and Beauty at 39.1%. Beauty was not the largest paid-theme segment.
• Prestige exceeded Debut in both the displayed France and Germany tables. France was not the only such country.
• Germany's 22.7% Dawn share is a concentration within that stored country cohort, not proof that German merchants prefer a particular design.
• A large Prestige share in one country does not establish that country's overall paid-theme share.

These are reported historical subsets, without a controlled representative sampling frame. Country detection, category classification, uneven sample sizes and observation ages limit comparisons. We removed claims about cultural aesthetics, neglected stores and implied budgets that the tables do not measure.

For a current trend question, use the separately dated matched-panel theme study. Installed-base counts and observed changes between repeat scans answer different questions.

Choosing a theme from the evidence

Use prevalence to identify relevant examples and compatibility needs. Then evaluate the actual requirements: navigation, product information, accessibility, international presentation, maintainability, performance and the functions supplied by existing tools.

Test the theme with a representative catalog and real customer journeys. Check current licensing and feature documentation directly before buying or recommending it. Measure performance and conversion in the merchant's analytics rather than substituting a LeadFit score.

For outreach, describe a verified problem and ask whether it is a priority. “Your theme name suggests this may be worth checking” is a research hypothesis; it is not evidence that the merchant needs a migration.