Should I use a Shopify theme or go headless? (2026)

Use a Shopify theme unless you have an engineering team and a storefront requirement a theme genuinely cannot express. A headless storefront (Hydrogen, or Next.js on the Storefront API) still hands off to the same Shopify checkout, but it gives up the theme editor, theme app blocks and Shopify run hosting, so every one of those becomes software your team builds and maintains.

Below: what headless actually is, the verified plan and hosting facts as of 4 October 2026, a count of what the theme editor gives you for free, and where the SEO argument really lands.

What is a headless Shopify storefront?

"Headless" means Shopify keeps running your backend (products, inventory, orders, checkout) while a separate frontend, built and hosted by your team, talks to it through the Storefront API. A theme, by contrast, is Liquid and JSON that Shopify itself renders: no separate frontend, no separate hosting, no API layer to maintain.

Which Shopify plans can run a headless storefront?

More than most guides say. Shopify's Hydrogen documentation states that "Oxygen is available at no extra charge on paid Shopify plans: Starter, Basic, Grow, Advanced, Plus, Pause and build," and that "Oxygen isn't available on Agentic plans." Development stores and trial plans can deploy to Oxygen for testing, but those deployments sit behind a store login rather than a public URL.

So the common belief that headless requires Shopify Plus is wrong. Note the asymmetry with themes: Shopify's help centre says "You need to be on the Basic plan or higher to sell with an online store," so a Starter store cannot sell through a theme at all, while Oxygen lists Starter as eligible. The plan is almost never the real constraint. The engineering is.

When does headless actually make sense?

• You have, or will hire, a dedicated engineering team. Headless is software you own. No team, no headless.
• Your storefront is genuinely custom. Complex product configurators, editorial content merged with commerce, interactions a section based theme cannot express.
• Scale and architecture demands. Very large catalogs with custom search, or several brands and regions sharing one frontend codebase.

Large brands do this well and the investment pays back for them. The key word is investment: the framework and the Oxygen hosting cost nothing extra, but the developer time to build the storefront and keep it running is the bill, and it never stops.

What do you give up when you go headless?

The theme editor, and everything stored in it

This is the cost people underestimate, so we counted it. On 20 September 2026 we parsed 28 complete Shopify themes from our own build archive. The typical one stores about 72 values a merchant can change without code: 23 global theme settings (colors, fonts, logo, favicon, social links) plus a median of 49 section and block values across 10 JSON templates. Across all 28 themes that was 481 section instances holding 934 values and 534 blocks holding another 1,170.

On a theme, each of those is a field in a sidebar. On a headless storefront, each one is either hardcoded (so changing it is a developer ticket) or a field your team models in a CMS and wires up. Swapping a banner, reordering a homepage, or editing a testimonial stops being a two minute job. The full breakdown of where those values live is in will I lose my customizations if I update my Shopify theme.

Theme app blocks and app embeds

Shopify's documentation describes theme app extensions as the way apps "add dynamic elements to their themes," and says they "can integrate with Online Store 2.0 themes." A Hydrogen or Next.js storefront is not a theme, so reviews widgets, upsell blocks, bundles and similar storefront features have no place to render. Admin and backend apps keep working; storefront ones become custom integrations or headless specific alternatives.

Themes are not automatically safe here either. An app block can only go into a section whose schema declares a block of type @app. When we measured our own archive on 12 September 2026, 0 of 663 section files declared one, which meant an empty Apps tab in every theme until we fixed it. The difference is that on a theme that is a one line schema fix, and on headless there is nothing to fix because the mechanism does not exist. Details in why can't I add my app's block to my Shopify theme.

Shopify's rendering, caching and on call

Even on Oxygen, the code that renders the page is yours. Performance, accessibility, caching rules and broken pages are your team's problem. When the storefront fails at 2am, it is your pager.

What you do not give up is checkout. Headless stores hand the cart off to Shopify's checkout, so the most conversion critical page in your store is identical in both architectures.

Is headless better for SEO?

No, and this is the most persistent myth in the debate. Shopify themes are rendered on Shopify's servers and cached on its CDN, so search engines get complete HTML on the first request. Headless gives you more control over rendering, and control cuts both ways: done well it matches a theme, done casually it introduces pages that need JavaScript to show content, broken canonicals, and slower first loads.

Structured data is the clearest example. Every Themr theme ships a json-ld snippet as a default file; in the generated themes we checked it emits Product, Organization, WebSite, BreadcrumbList and Article markup without anyone touching code. A headless build gets the same markup only if someone writes it. The realistic claim is parity, not superiority: rankings come from content, structure, markup and speed, and only one of the two architectures needs an engineering team to deliver them.

Is a theme too limiting for serious design?

Less than its reputation says. Online Store 2.0 themes support sections on every page, JSON templates, metafields, and unrestricted custom CSS and JavaScript. The reason so many stores look generic is rarely the platform ceiling. It is the creative layer: most merchants do not have original imagery, an art directed hero, motion, or copy in their own voice, so every store on the same template looks the same.

That creative layer is what Themr builds. It generates product and lifestyle imagery, an art directed hero, scroll animation and section copy for your brand, and assembles them into a complete Shopify 2.0 theme with conversion sections built in (the ones that otherwise cost about $780 a year in apps). Ownership works like a theme, because it is one: you download a ZIP of real Liquid, upload it in your own admin, edit it in the theme editor, and keep it. A free theme costs nothing, and the full AI designed store is $29 once, not a month. You can judge the output in the showcase first.

Theme vs headless, side by side

How do you decide in one minute?

Choose headless if you have an engineering team, a storefront requirement themes cannot express, and the budget to treat your storefront as a software product.

Choose a theme if you are anyone else. Checkout, apps, POS and SEO all work on day one, and the design gap that used to justify custom builds is the part AI generation now covers. If you are weighing vibe coding tools as a middle path, read what Lovable and Replit's Shopify connectors actually give you (and why Bolt has none), or compare every option in the best AI website builder for Shopify.

Whichever theme you land on, it still has to install cleanly. If Shopify rejects your upload, the eleven errors that stop a theme ZIP from uploading covers every rejection message and its fix.