Shopify Hydrogen vs Traditional Shopify: Is Headless Worth It?
Liquid theme, Hydrogen or your own Storefront API build? What Hydrogen 2026-10 changed, Oxygen limits, apps, Markets and a cost worksheet to fill in.
Should You Go Headless on Shopify?
For most stores, no. A Liquid theme is hosted by Shopify, edited by merchandisers in the theme editor, extended by theme apps and maintained with the least engineering. Headless earns its cost when the storefront itself must do something a theme can't do well, such as a complex configurator, content-led commerce from a separate CMS or several front ends sharing one catalogue, and when you can fund a web team to run it for years.
The choice also changed on 14 October 2026. Hydrogen 2026-10 turned Hydrogen from a React Router framework into a library you can add to React Router or Next.js. So the realistic options are now a Liquid theme, the Hydrogen library on your chosen framework (hosted on Oxygen or elsewhere), or your own build on the Storefront API without Hydrogen. In every case, checkout, orders and products stay on Shopify.
Key Takeaways
- Hydrogen 2026-10 is a framework-agnostic library with React Router and Next.js starters; existing Hydrogen storefronts keep working.
- Oxygen is included on every paid plan from Starter upward, but not on Agentic plans. Plus gets 25 public environments; other paid plans get 1.
- Theme app extensions work with Online Store 2.0 themes, so storefront apps need an API, SDK or rebuild when you go headless.
- The Storefront API has no fixed request limit for real buyer traffic, but it throttles checkout creation, and server-side calls should pass the buyer's IP.
- The main cost of headless is the team that keeps it running, not the hosting. Use the worksheet below with your own quotes.
What Changed With Hydrogen 2026-10
Shopify's changelog for 14 October 2026 describes the new Hydrogen as "a framework-agnostic JavaScript library to add Shopify commerce to your existing stack". React Router and Next.js have starters ready to deploy, and you "can host it anywhere, including Oxygen, which is still free". Existing Hydrogen storefronts "keep working as they do now".
Two practical consequences follow. First, the old question "Hydrogen or Next.js?" mostly disappears: a Next.js team can now use Hydrogen. The real question is whether you use Shopify's library at all or write your own Storefront API layer. Second, much of Shopify's existing Hydrogen documentation, including the Oxygen and analytics pages cited here, is now labelled as covering "Hydrogen versions 2026-04 and earlier". Treat the limits below as the current documented position and check the latest docs before you sign a build contract. If an agency proposal still describes Hydrogen as "React Router only", ask how it accounts for the new version.
Worth noting
Hydrogen 2026-10 was released one day before this update. Expect the documentation, starters and agency advice to keep changing for a while. Ask any partner which Hydrogen version and API version they will build on.
The Three Options in 2026
The table compares the three routes. "Rebuild" means your team writes the feature; "integrate" means connecting a third-party service or an app's API.
| Liquid theme | Hydrogen library (React Router or Next.js) | Storefront API without Hydrogen | |
|---|---|---|---|
| What you build | Theme sections and blocks in Liquid, CSS and JavaScript | A web app on your framework, using Shopify's library for commerce | A web app plus your own Shopify data layer |
| Hosting | Shopify | Oxygen (included on paid plans) or your own host | Your own host |
| Content editing | Theme editor | A CMS or custom tooling | A CMS or custom tooling |
| Storefront apps | Theme app extensions work | API or SDK integration, or rebuild | API or SDK integration, or rebuild |
| Checkout | Shopify Checkout | Shopify Checkout | Shopify Checkout |
| Team | Theme developer, merchandisers | Web developers on your framework, plus someone to run deployments | As Hydrogen, with more Shopify-specific code to own |
| Ongoing upkeep | Lowest | Higher | Highest |
What Changes When You Go Headless
This is the matrix to take into a scoping call. For each row, ask the agency or your team which of native, rebuild or integrate applies, and who maintains it afterwards.
| Feature | Liquid theme | Hydrogen library | Own Storefront API stack |
|---|---|---|---|
| Checkout | Native (Shopify Checkout) | Native (Shopify Checkout) | Native (Shopify Checkout) |
| Storefront apps (reviews, bundles, back-in-stock) | Native via theme app extensions | Integrate via app API or SDK, or rebuild | Integrate via app API or SDK, or rebuild |
| Content and layout editing | Native (theme editor) | Integrate a CMS | Integrate a CMS |
| Markets (prices, currencies, availability) | Native | Rebuild routing; prices via API context | Rebuild routing; prices via API context |
| Customer accounts | Native | Rebuild with the Customer Account API | Rebuild with the Customer Account API |
| Analytics and consent | Native via theme and pixels | Rebuild using Shopify's patterns and the Customer Privacy API | Rebuild |
| Search and filters | Native (theme plus Search & Discovery) | Rebuild via API or integrate a search service | Rebuild via API or integrate a search service |
| SEO basics (rendering, metadata, sitemaps, structured data, redirects) | Mostly native | Rebuild | Rebuild |
Oxygen: Which Plans Get It and How Many Environments
Oxygen is Shopify's hosting for Hydrogen storefronts. It is available at no extra charge on Starter, Basic, Grow, Advanced, Plus and Pause and build, and on development stores, Plus Partner Sandbox stores and trial plans. Shopify states that "Oxygen isn't available on Agentic plans".
The plan decides how many public environments you get. Environments are private by default, so only people logged in to your store can see them; a public environment is one shoppers can reach.
| Plan | Oxygen available | Public environments |
|---|---|---|
| Starter, Basic, Grow, Advanced | Yes | 1 |
| Shopify Plus | Yes | 25 |
| Pause and build | Yes | 1 |
| Plus Partner Sandbox stores | Yes | 1 |
| Development stores and trial plans | Yes | 0 (private only) |
| Retail, nonprofit and custom plans | Check with Shopify | 1 |
| Agentic plans | No | Not applicable |
Oxygen Runtime Limits
Shopify documents these limits for Oxygen workers and deployments. Oxygen also runs your storefront as a Web Worker, not a Node server, so Node APIs aren't available. That matters if your build relies on Node-only libraries, or if a Next.js team assumes a Node environment.
One public environment on most plans also means one live storefront on Oxygen. If you want a second public site, such as a separate brand or a campaign microsite, compare Plus with hosting the second site elsewhere.
- Worker size: 10 MB or less
- Startup time: 400 milliseconds or less
- CPU time: 30 seconds per request
- Memory: 128 MB maximum
- Custom environment variables: 110
- Outbound API requests: must complete within 2 minutes
- Runtime logs: kept for up to one month, so connect a log drain for longer retention
- Deployments: accessible for at least six months, and the 10 most recent per environment are always kept
Storefront API Limits That Affect Your Build
Shopify says that "requests from real buyers aren't subject to a fixed request-per-minute limit", but it "limits the amount of checkouts that can be created on the Storefront API per minute". Over that limit, you get a throttled response, and Shopify suggests queuing with exponential backoff. Tokenless access has a query complexity limit of 1,000.
When your server calls the API on behalf of a shopper, it should send the shopper's IP in the Shopify-Storefront-Buyer-IP header. Without it, Shopify says it "can't differentiate requests from different buyers", which can lead to throttling and weaker bot protection. Use a private token on the server and a public token only in the browser or app. Shopify releases a new API version every quarter and supports each stable version for at least 12 months, so a headless build needs a regular upgrade slot.
Apps, Markets and the Headless Channel
Apps. Shopify documents that theme app extensions "can integrate with Online Store 2.0 themes". Headless storefronts aren't mentioned, so any app that adds its feature only through a theme block won't appear on a headless site. Before committing, list every app that touches the storefront and ask each vendor whether it offers an API or headless SDK.
Markets. With the @inContext(country:) directive, the Storefront API returns prices in that country's currency and filters out products not published there. Passing a country in the cart's buyerIdentity sets the cart's estimated cost. Each country's currency must be enabled in payment settings, or prices fall back to the store currency. The guide doesn't cover domains or subfolders, so expect to build country routing, language switching and hreflang yourself. See Shopify Markets for how a theme store handles this.
Headless channel. A shop can have up to 100 active storefronts and access tokens, and Storefront and Admin API permissions are shared across them. Since January 2025, each Headless storefront is a separate channel for product publishing and order attribution, so publish products to every storefront that should sell them.
Analytics and consent. Shopify's Hydrogen analytics guide offers patterns for sending storefront metrics to Shopify analytics, and says you must handle consent before tracking, recommending the Customer Privacy API and Shopify's cookie banner. On a theme, much of this is wired in. Headless, you test it. The Shopify tracking audit has a test procedure you can reuse after launch.
Total Cost of Ownership Worksheet
Headless moves money from licences and apps to engineering. This worksheet has no prices on purpose: fill it in with your own quotes and salaries for each option, over three years, and compare totals. A blank in the "Owner" column is a risk in itself.
| Cost line | One-off | Monthly or yearly | Owner | What to ask |
|---|---|---|---|---|
| Front-end build | Which Hydrogen and API version? What is out of scope? | |||
| CMS licence and set-up | Per-seat or usage pricing? Who models the content? | |||
| Hosting | Oxygen (included on paid plans) or another host? How many public environments? | |||
| Monitoring and logging | Where do logs go after Oxygen's one-month retention? | |||
| App replacements | Which storefront apps need an API, SDK or rebuild? | |||
| Search, reviews and other services | Do any charge by traffic or catalogue size? | |||
| Markets and localisation | Who builds country routing, languages and hreflang? | |||
| Analytics and consent rebuild | Who tests events and consent after each release? | |||
| Quarterly API and framework upgrades | Is there a standing upgrade slot every quarter? | |||
| Feature work and fixes | In-house hours or retainer? What happens if the lead developer leaves? |
Weighing an agency's headless quote?
ZSpace Labs can run a headless readiness review against your apps, markets and team, and tell you plainly if a theme would do the job.
Decision Guide
| If you... | Consider |
|---|---|
| Have a small team and your needs fit themes and apps | Liquid theme |
| Rely on several storefront apps without headless SDKs | Liquid theme, or budget for replacements |
| Want merchandisers to change layouts without developers | Liquid theme, or headless with a strong CMS |
| Already run React Router or Next.js across your sites and need custom commerce experiences | Hydrogen library on that framework |
| Need several front ends (web, app, in-store screens) from one catalogue | Hydrogen library or your own Storefront API layer |
| Have strict requirements Hydrogen doesn't fit, and a team to own the data layer | Storefront API without Hydrogen |
When Headless Is the Wrong Choice
Headless is a poor fit when the main motivation is speed alone, when the team is one or two developers or an agency on an ad hoc basis, when daily merchandising depends on the theme editor, or when the store relies on storefront apps with no API. It is also risky during a busy trading period, because you are replacing every customer-facing page at once. A well-built theme with a few custom sections, a configurator embedded in a section, or metaobject-driven content pages often gets most of the benefit at a fraction of the upkeep. See Shopify theme development for that route.
Hypothetical example: a fashion brand on Advanced uses a reviews app, a back-in-stock app and a size-guide app, all through theme blocks, and two merchandisers update the homepage weekly. An agency proposes Hydrogen on Next.js for speed. Running the matrix shows three app rebuilds, a CMS for the merchandisers and Markets routing for two countries, with no in-house developer to own upgrades. Unless the brand also has a feature a theme can't deliver, a theme performance project is the more proportionate first step.
Performance and SEO: You Own Both
Headless can be faster, because you control rendering, caching and scripts. It can also be slower, with heavy client-side JavaScript or poor caching. Prototype a product page and compare measured results with your current theme. On SEO, a theme gives you server-rendered pages, canonical tags and sitemaps by default; a headless storefront must implement rendering, metadata, canonical and hreflang tags, sitemaps, structured data, redirects and filtered URL handling deliberately. See page speed and conversion and faceted navigation SEO.
Common Mistakes
- Choosing headless for page speed alone
- Signing a quote that still describes Hydrogen as React Router only, without asking about 2026-10
- Discovering after launch that storefront apps relied on theme app extensions
- No owner for Oxygen logs, monitoring and quarterly API upgrades
- Forgetting to publish products to each Headless storefront channel
- Assuming Markets routing, hreflang and consent come for free
Conclusion and Next Steps
Stay on a Liquid theme unless you can name a storefront requirement a theme can't meet and a team to maintain the alternative. If you do go headless, Hydrogen 2026-10 makes the Shopify library usable on React Router or Next.js, Oxygen hosting is included on paid plans, and checkout stays on Shopify. Next steps: fill in the feature matrix and the cost worksheet with your own quotes, list every storefront app and its headless support, and check the latest Hydrogen docs for any limit you depend on. For background, read headless Shopify explained, Shopify Hydrogen development and headless ecommerce architecture.
Want a second opinion before you commit?
ZSpace Labs is a remote-first technology studio that works with clients globally on Shopify development, including themes and headless builds. If useful, we can talk through a headless readiness review of your apps, markets and team.
Sources
Hydrogen and Oxygen: Shopify changelog: Hydrogen 2026-10 is now available (14 October 2026); Shopify: Hydrogen fundamentals and Oxygen plans and limits; Shopify: Oxygen environments; Shopify: Oxygen deployments; Shopify: Oxygen runtime; Shopify: Hydrogen analytics.
APIs, apps and channels: Shopify: Storefront API; Shopify: API versioning; Shopify: theme app extensions; Shopify: international pricing with the Storefront API; Shopify: manage Headless channels; Shopify changelog: unique publishing and order attribution per Headless storefront; Shopify Help Center: headless commerce.
Accessed 15 October 2026. Several Hydrogen and Oxygen pages are labelled for Hydrogen 2026-04 and earlier; plans, limits and documentation change, so check the current pages before relying on them.
Common questions.
A store using an Online Store theme built with Liquid. Shopify hosts and renders it, your team edits it in the theme editor, and apps add features through theme app extensions.
Since Hydrogen 2026-10, released on 14 October 2026, Shopify describes it as a framework-agnostic JavaScript library for adding Shopify commerce to an existing stack, with starters for React Router and Next.js. Earlier versions were React Router apps. Shopify says existing Hydrogen storefronts keep working as they do now.
Not any more. React Router is one of two starters; Next.js is the other. If your storefront was built on an earlier version, it keeps working, but Shopify recommends migrating older storefronts, so plan for that in your roadmap.
Shopify's documentation says Oxygen is available at no extra charge on paid plans, including Starter, and on development stores, Plus Partner Sandbox stores and trial plans. It isn't available on Agentic plans. Plus gets 25 public environments; other paid plans get 1.
No. Shopify's Help Center says customers on a custom storefront check out using the Shopify Checkout. You still customise it through checkout extensibility, with the same plan limits as a theme store.
Back-office apps usually do. Apps that add storefront features through theme app extensions don't, because Shopify documents those extensions as integrating with Online Store 2.0 themes. You need the app's API or SDK, or a rebuild of the feature.
Not automatically. Headless gives you more control over rendering, caching and scripts, and more ways to get them wrong. Compare measured performance of a prototype against your current theme rather than relying on the label.
Yes. The Storefront API returns local prices and filters products by country when you pass a country context, and the cart takes a buyer country. You have to build the routing, such as country subfolders or domains, in your own front end.
Yes. Shopify's Headless channel allows up to 100 active storefronts and access tokens per shop, and each storefront is treated as its own channel for product publishing and order attribution. Public Oxygen environments are a separate limit set by your plan.
Yes. Products, customers, orders and checkout stay in Shopify, so only the front end changes. Plan URLs and redirects, tracking, content migration and app replacements as you would for any migration.