Outrank AI
Paid themes account for approximately 98.2% of Shopify's official catalogue. The Shopify Theme Store lists 1,359 themes, and 1,335 of them are paid, so free themes are only about 1.8% of what you see. That split reframes the buying question. You are not choosing between a handful of upgrades and a sea of free options. You are choosing inside a commercial marketplace, and a higher price still doesn't guarantee a faster store or a better one.
A paid Shopify theme is a one-time purchase that becomes the layout foundation of a single store. It can shorten a launch and hand you tested ecommerce pieces. It doesn't finish your brand, survive every app you install, or travel free to every regional storefront. The useful test is whether that entry fee still looks cheap after you load your own products, images, and apps.
Table of Contents
Paid Shopify Themes at a Glance and What They Cost
A paid theme is a commercial storefront template you buy once from the Theme Store and install as the design and layout base of a shop. You can preview it and change sections before you pay. You can't publish that paid theme to the live storefront until the purchase is done.
Across 310 paid themes, the median price is $300 and the average is $283.90, according to ShopThemeDetector's theme pricing breakdown. The set clusters in the middle, and more than half of those themes cost at least $300.
Price band (USD) | Share of paid themes | Themes in analysed set |
|---|---|---|
$100 to $199 | 21.9% | 68 |
$200 to $299 | 23.2% | 72 |
$300 to $399 | 42.3% | 131 |
$400 and above | 12.6% | 39 |
Most paid themes are a one-time capital purchase in the $200 to $400 range, not a monthly subscription. 68 themes (21.9%) cost $100 to $199, 72 (23.2%) cost $200 to $299, 131 (42.3%) cost $300 to $399, and 39 (12.6%) cost $400 or more.
A 2026 look at the first 24 paid listings showed a wider sticker, from $100 to $500, according to Market Intelligence Tools. The first screen of results can appear pricier than the median of the larger set. Sort by what you will publish, not by what sits at the top of the page.
How to read the fee
The theme fee is the entry cost. A lower-priced theme can cost more once custom sections, extra apps, and speed work are added. A higher-priced theme may ship more native merchandising and still need brand-specific build work, image handling, and cleanup.
Set the band first: Choose a budget range, including a reserve for customisation, before you browse the catalogue.
Say a candle brand grabs a $140 theme, then pays a developer to rebuild variant photos, a quiz block, and a campaign homepage the theme never included. The cheap line item wasn't cheap. Write the band down, then open the store.
What the Difference Buys You
Free themes win on cost and simplicity, while paid themes buy design range, built-in merchandising sections, and an official path to updates.
Factor | Paid theme | Free theme |
|---|---|---|
Upfront cost | One-time fee, usually $200 to $400 | No fee |
Share of Theme Store listings | About 98% | About 2% (24 listed) |
Purchase needed before publishing | Yes | No purchase needed |
Licence scope | Tied to the store where it was bought | Comes with the store, no separate paid licence |
Official support and updates | Available when the theme is licensed | Maintained with the platform, no paid licence to renew |
Built-in section and layout depth | Broad merchandising, media, and animation options | Usually narrower, more custom code needed |
Price is only one row. The practical gap is how much of the storefront you get before anyone writes new code, and whether a purchase stands between you and a live theme.
When free is enough
Free fits a single-product store with a small app stack and a tight budget. You need a homepage, one product template, a simple collection, and a cart. You aren't running weekly editorial shoots or five versions of the same product page. Setup stays smaller because there are fewer unused sections to configure, hide, or accidentally slow down.
A new maker selling one candle and a gift set can launch on a free theme, keep apps to payments and email, and spend the saved fee on photography. That trade is honest. The store looks plainer, and later campaign pages will take more custom work.
When paid earns the fee
Paid pays back when the brand needs distinct product templates, editorial layouts, variant-heavy product pages, or frequent campaign sections. Those pieces exist so a merchant can turn on a lookbook, a promo band, or a media-led homepage without commissioning each block from scratch.
If you would rewrite most of a free theme's sections, the saving shrinks quickly, and the paid price may be the cheaper route. A fashion label planning monthly drops will burn more in custom development than it saves by skipping the Theme Store fee.
If the free theme is only a shell you plan to replace, you are paying someone to rebuild what a paid theme already ships.
Match the theme to the heaviest page you will edit every week. Don't buy depth you will never turn on, and don't refuse it if your calendar is already full of campaigns.
How a Paid Theme Is Built Under the Hood
A paid theme works like a house kit. JSON templates are the rooms, sections are prefabricated walls you can move, and blocks and snippets are the fittings. The kit only works if you stop adding rooms you don't need.
Under that surface, a paid theme is a small application, not a picture of a homepage. Shopify's theme architecture docs describe the stack as Liquid markup, JSON templates, sections, blocks, snippets, configuration files, CSS, JavaScript, and localised assets. Liquid decides what content and logic render. CSS and JavaScript finish the look and the behaviour. Localised assets keep labels and currencies from being hardcoded in one language.
Why the rooms matter more than the paint
JSON templates matter most for day-to-day maintenance. Merchants can add, remove, and reorder sections, including app sections, without hard-coding a new page layout. A marketing lead can build a campaign page in the editor instead of opening a code file. Sections in Shopify are the movable pieces behind that freedom, and the architecture docs show how each one binds to a template and the blocks inside it.
The same flexibility is the performance risk. A feature-rich theme ships more sections, blocks, nested snippets, client-side scripts, and remote assets, and each one adds a step to the render or to the browser's work. That weight is already aboard before your own apps, images, and markets arrive. Two stores can buy the identical theme and ship very different speeds, because the number of unused section nests left switched on differs from one build to the next. Open the theme editor and count the sections enabled on each template. That inventory, not the feature list, is what your store carries on launch day.
Controls that belong in the build
Theme Check: Catch Liquid and schema issues before a template ships.
Theme Inspector: Profile Liquid so you can see which section is slow instead of guessing.
Data access: Load the product and collection data you need once, rather than asking for it inside every nested snippet.
Scripts: Defer or load JavaScript only on the templates that use it.
Template tests: Measure the home, product, and collection templates, because a fast homepage can hide a slow product page.
The configured storefront, not the price label, sets real performance. A higher fee buys more structure and more features to switch on. It buys no guarantee that your catalogue, imagery, and app stack will render quickly.
Performance Tests to Run Before You Buy
A paid theme is not automatically faster. More sections and merchandising features add weight, and Shopify's web performance guidance treats themes, apps, and manually added third-party code as major performance factors. The question isn't which theme wins a demo. It's how this theme behaves after your images, markets, scripts, and content are installed.
A simpler paid theme can beat a premium one once you add personalisation, subscriptions, reviews, analytics, and internationalisation. Feature lists don't show that. Your preview store can.
A repeatable routine
Install the candidate in a preview store, not on the live theme.
Load your real product, collection, cart, and content pages with your real image sizes.
Add the apps you will run, such as reviews, subscriptions, and pop-ups.
Run mobile lab tests and record LCP, INP, and CLS for each template.
Repeat each test three times and keep the median, not the best run.
Compare those medians with the performance budget you set for launch, using the same pages every time.
Note which section or script causes each regression before you blame the whole theme.
A Core Web Vitals audit is the right frame for those three metrics, split by page type, device, and geography. Lab tests tell you what broke in the preview. Real-user results tell you what customers felt after launch.
Template to test | Metrics to record | Regression sign |
|---|---|---|
Home page | Mobile LCP, INP, CLS | A heavy hero or a long section stack delays the largest element |
Product page | LCP, INP, CLS with variants and media loaded | Variant switching adds visible input delay |
Collection page | LCP and CLS with filters open | Filter scripts shift the layout |
Cart page | INP and CLS with apps active | App widgets block taps or move the layout |
Content page | LCP with embedded media | Oversized images or extra font files slow the first paint |
Watch the product page with a real variant set, not a single demo product. Open the collection filters. Trigger the cart drawer with the review and subscription widgets on. If a pop-up steals the first tap, that is an INP problem you can see before you pay.
This short walkthrough shows how to read a theme preview with speed in mind, before any of those template checks.
Set a post-launch performance budget in writing, with a median target for home, product, and collection on mobile. Repeat the same seven steps after every app install or theme update. A theme that passed on Monday can miss the budget on Friday because one script changed.
Accessibility and Licensing Risks After You Customise
A theme can pass Shopify's review and still produce a store where the cart drawer cannot be closed with a keyboard. The review is a factory inspection of the baseline product. Your launch adds aftermarket parts: promo bars, quiz pop-ups, review widgets, subscription selectors, campaign banners, and localised copy. Those pieces sit outside the score, and they are the ones most likely to break the experience after a campaign or an app install.
Shopify's theme store requirements call for keyboard access and an average Lighthouse accessibility score of at least 90 across core templates, plus a minimum average performance score of 60 on a benchmark store, according to Shopify's theme store requirements. Those gates describe the submitted theme, not your production shop after merchandising, analytics, apps, media, and custom code are added. A higher price can buy more built-in sections and app support. It does not buy a faster store or a cleaner accessibility result once your own widgets load.
Checks on representative templates
Use a template that carries your real apps and campaign modules, not the demo content.
Keyboard path: Move through the menu, cart drawer, and forms with the keyboard only.
Focus: Confirm every button, link, and field shows a visible focus state.
Headings: Check that heading levels follow the page, not the visual size of a promo.
Errors: Submit a form with a missing required field and confirm the message is announced to a screen reader.
Alt text: Review product images, including variant and campaign media.
Contrast: Keep body text at a contrast of at least 4.5:1 against its background.
Motion: Honour reduced-motion settings on sliders and entrance effects.
Apps: Open each pop-up, tab through it, and confirm focus returns to the control that opened it after close.
Someone has to own the failures. If a review app ships an inaccessible widget, the theme vendor didn't introduce it, and the app vendor may not fix it on your schedule. Assign the remediation to your developer or agency, file it against the app, and don't treat the original theme score as a waiver. Our notes on ADA accessibility requirements are a practical place to park that ownership before a seasonal launch.
The licence doesn't follow the brand
A paid theme is licensed to the store where it was bought. Shopify's guidance on unlicensed themes is direct. Shopify Plus expansion stores need their own licences, and unlicensed themes aren't eligible for official support or updates when new features ship. Copying a theme file onto a second storefront doesn't create that licence.
Track the theme version on every store. Duplicate the live theme before you add custom code. Review updates in the theme library before you publish them. Put a recurring accessibility audit on the same calendar as those updates, not as a one-time task at purchase.
Choose and Confirm Your Paid Theme
A paid theme is an entry ticket, not a performance guarantee. The price buys a starting structure and often more built-in sections. It does not buy speed on your catalogue, with your apps, at your image sizes. Treat every shortlist decision as a test you run in a preview store before you pay.
Brand situation | Theme profile to prioritise | Verify before buying |
|---|---|---|
Single store, small catalogue, low app budget | Lean, section-light theme | Mobile speed on the product page |
Subscriptions, reviews, and quizzes | Clean support for app sections | Script weight and widget accessibility of each app |
Multiple regional or Plus expansion stores | Stable theme with a clear update path | Licence per store and the upgrade process |
Editorial or brand-led storytelling | Strong media and layout sections | Image weight and motion settings |
Migration from another platform | Theme that fits your data and URL structure | Data mapping and redirect plan |
A fashion label launching frequent drops should bias toward variant-heavy product templates and fast collection pages, then prove both in the preview. A multi-store brand should bias toward a theme the vendor still updates, because each storefront will carry its own licence and its own customisations. A higher price often means more features and more scripts. A lower price often means more custom build work. Neither side is automatically the better store.
Score the shortlist
Score each finalist from 1 to 5 on six lines: price, measured speed, section fit, accessibility baseline, maintainability, and licence plus update path. Price is one line, not a veto and not a tie-break by itself. Measured speed comes from the preview routine, not from the theme's marketing page. A theme that scores 5 on a demo with no apps and 2 with your subscription widget is a 2 for your store.
Presidio builds premium Shopify themes named Broadcast, Palo Alto, and Modular. Over 20,000 stores have been built using one of those themes. Broadcast is powerful, feature rich, and designed to incentivize sales. Even with that kind of starting point, the same six-line score still applies, because your app stack is not the demo's.
When a preview is close, collect client design approvals against the actual theme, not a slide deck the store cannot reproduce. Layout, type, and section order are what stakeholders need to sign.
Confirm, then buy
Shortlist three to five themes that match the profile in the table.
Preview each one in a Shopify store. Shopify lets merchants preview up to 19 paid themes at the same time before buying, according to the Shopify Help Center.
Run the performance test on your real content and the apps you will keep.
Run a keyboard-only pass and a contrast check on the home, product, collection, and cart templates.
Confirm a licence for every store that will use the theme, including Plus expansion stores.
Buy the winner. A paid theme has to be purchased before it can be published.
Drop any theme that fails the speed or keyboard check once your real widgets are installed. Don't average that failure away with a pretty homepage preset.
Buy the theme that passes your speed and accessibility checks with your real apps, is licensed for every store, and has the clearest update path.
If two themes tie, take the clearer update path. A slightly leaner section library is easier to live with than a theme you can't safely upgrade next season.
Presidio builds and supports Shopify and Shopify Plus storefronts, including theme implementation, speed work, and accessibility fixes that sit on top of a paid theme. If you want a second set of eyes on a shortlist, or a storefront that stays maintainable after the apps go in, visit Presidio and tell us which templates and markets you need to launch.
