Shopify theme or headless? How to decide

The short answer

Start with a theme. Shopify’s own developer documentation says to consider a custom storefront when what you need can’t be done with Shopify’s sales channels, custom themes and apps, and to make sure you’ll have developers for the ongoing work after launch.[1]

Shopify’s 2026 guide for commerce leaders says the same in business terms: headless works best when it solves a defined business problem, not as a technical goal.[2]

What each one is

A theme is Shopify’s standard storefront. Your team edits it in the theme editor: adding, removing and reordering sections on any page, and dropping in app blocks without touching code. Shopify’s free themes include the Horizon family, and paid themes in the Theme Store listed from $100 to $500 in October 2026.[3][5][6][7]

A headless storefront is a custom front end that talks to Shopify through its APIs. Shopify’s recommended stack is Hydrogen, its toolkit for building one, hosted on Oxygen, which comes at no extra charge on paid plans. A rebuilt Hydrogen, announced in Shopify’s Spring ’26 Edition and in developer preview since June 2026, also works with other frameworks, such as Next.js.[9][10][11]

Checkout is the same either way

A headless store still sends shoppers to Shopify’s own hosted checkout. Deeper checkout changes, like apps on the information, shipping and payment steps, need Shopify Plus on a theme and headless alike. So “we need a custom checkout” isn’t a reason to go headless.[12][13]

Side by side

Sources for the table: Shopify’s documentation on theme app extensions, its headless app collection, Shopify Markets, theme updates and API versioning, and Shopify’s performance blog. Time to launch is my own estimate.[5][14][15][8][16][20]

A theme is the right call when

• Your team wants to edit pages and launch campaigns without waiting on a developer.[3]
• Your store relies on App Store apps that add things to the storefront, like reviews, upsells, bundles or quizzes.[5][14]
• You sell in several countries and don’t have a developer to handle domains and routing.[15]
• Launch speed matters more than architectural freedom, or your team has limited engineering resources. Shopify’s 2026 guide lists both as signs headless may not be the right fit.[2]
• You can’t fund at least a yearly upgrade after launch.[16][17]

Headless is worth it when

• The experience you need truly can’t be built with a theme and apps, and you can name the feature.[1]
• One catalog has to power your website, a native app and other places, from the same back end.[18]
• You have developers, in-house or on retainer, for the work after launch.[1]

Not reasons to go headless

• “We need a custom checkout.” Checkout is Shopify’s either way, and deeper changes need Shopify Plus.[13]
• “Our site is slow.” Fix the theme first. In the 2025 Web Almanac, 76% of Shopify sites passed all three Core Web Vitals, and a 2026 Shopify rendering change sped up theme storefronts without any work from merchants.[19][20]
• “We want a design no one else has.” Custom sections let a theme carry a custom design, and your team can still edit it in the theme editor.[4]

There’s a middle path

Most “a theme can’t do that” problems are one missing piece, like a bundle builder or a comparison table, and a custom section fills it. If you outgrow that, Shopify notes you can start with a traditional storefront and bring in headless pieces later, without replacing the commerce engine underneath.[4][2]

What to ask any studio before you decide

• How will my team edit pages and launch campaigns after you hand it over?
• Which of the apps we use today will work, and what does it take to connect the rest?
• Who upgrades the storefront when Shopify retires an API version, and what does that cost each year?
• How will we know it’s faster, and what are we measuring today?