Home
Articles
Hydrogen or Liquid? An Honest Decision Guide
Development
13
min read
Published
October 2, 2026

Hydrogen or Liquid? An Honest Decision Guide

Why Liquid is my default, the situations where Hydrogen earns its cost, and what the 2026 rebuild means for anyone planning a headless store.
Dark cover titled Hydrogen or Liquid, with a Liquid theme editor card listing sections and an app block, a Hydrogen route file loading a product through the Storefront API, a Liquid and Hydrogen toggle with Liquid marked as default, and a chip noting the Hydrogen developer preview since 17 June 2026

My default answer is Liquid. I say that as the founder of an agency that builds headless Shopify storefronts and is happy to do so when the case is right. The case is right less often than the confident advice online suggests. Some people will tell you Hydrogen is the only serious option for a growing brand, and others will call headless an expensive vanity project. Both are wrong often enough to be useless when you are the one signing off a six-figure rebuild.

This piece is for founders, ecommerce managers and CTOs choosing between a Liquid theme and a headless storefront built with Hydrogen. Instead of a feature comparison, I have built it around the situations that should decide it, with the projects where we made each call. You will also find what changed for Hydrogen in 2026, what headless takes away, how the three-year cost compares on two of our own estimates and a checklist to run before committing.

Where I land: stay on a well-built Liquid theme unless you can name a specific experience a theme cannot deliver, and you can fund developers to own a custom storefront for years. If both are true, headless can be the better investment. If either is missing, it rarely is.

Two architectures in plain language

A Liquid theme

Liquid is Shopify's template language, and a Liquid theme is the standard way to build a Shopify storefront. Shopify hosts the theme, renders the pages on its servers and serves them through its own infrastructure. Since Online Store 2.0, themes are built from sections and blocks that marketers can add, reorder and configure in the theme editor without code. Apps plug in through theme app extensions, which Shopify's documentation describes as integrating with Online Store 2.0 themes.

A Liquid theme also inherits a lot for free. The Online Store channel generates sitemaps, canonical tags and robots.txt, and with Shopify Markets it adds hreflang tags for international URLs automatically. Hosting, CDN, security and platform updates are Shopify's job.

A headless storefront on Hydrogen and Oxygen

Headless Shopify means Shopify still runs products, inventory, customers, orders and checkout, but the storefront customers browse is a separate application. It pulls data through the Storefront API and renders pages itself. When the customer is ready to pay, the cart's checkout URL sends them to Shopify's hosted web checkout.

  • Hydrogen
    Shopify's framework for headless storefronts. The current production version is built on React Router and provides components, utilities and patterns for working with Shopify's APIs.
  • Oxygen
    Shopify's global serverless hosting platform for deploying Hydrogen storefronts at the edge, using a worker-based JavaScript runtime.
  • Other headless stacks
    You can also build with Next.js or another framework, host it elsewhere and call the Storefront API directly. In 2026 that line is blurring.

Shopify's documentation calls Hydrogen and Oxygen its recommended stack for headless commerce.

Side-by-side architecture: a Liquid theme with app blocks and built-in SEO, rendered and hosted by Shopify, versus a headless storefront application hosted on Oxygen or Vercel that reaches the same Shopify backend through the Storefront API and sends shoppers to Shopify checkout via the cart checkout URL

Hydrogen is in the middle of a rebuild

2026 is the year Hydrogen stopped being tied to one framework. This is what has been announced on official channels:

  • 17 June 2026
    Shopify announced an early developer preview of the next Hydrogen, which moves commerce logic out of React Router into a framework-agnostic core so developers can build storefronts in any JavaScript framework with Shopify's commerce primitives.
  • 30 June 2026
    Shopify's changelog announced that the Hydrogen developer preview can be deployed to Vercel in a few clicks. A deploy button creates a repository from a Next.js starter template with a typed Storefront API client, cart, and product and collection pages already wired up.
  • Also 30 June 2026
    Vercel announced that the two companies are rebuilding Hydrogen from the ground up as open-source, runtime-agnostic layers (core, client and server), with support for frameworks such as Next.js, Nuxt and Svelte. At announcement the client layer was available for React on the preview branch, with more frameworks to follow. Vercel says its own commerce template will adopt Hydrogen once it is stable.
  • August to October 2026
    Shopify has shipped regular developer preview updates, including cart and customer account improvements. The October updates moved the Storefront API and Customer Account API to version 2026-10 and added Customer Accounts to the React Router template.

What has not been announced matters as much. As of mid-October 2026, Shopify has not published a general availability date for the rebuilt Hydrogen, and the official update notes are still titled "developer preview". The docs label older Hydrogen versions as legacy and recommend the latest version, but they set no shutdown date for the existing React Router stack. I review this section every month until a stable release ships.

Timeline of the 2026 Hydrogen rebuild: early developer preview on 17 June, Vercel deploy and the Vercel rebuild announcement on 30 June, preview updates from August to October with APIs on version 2026-10, and no general availability date announced as of mid-October 2026

My reading is straightforward. Plan new headless projects with the new architecture in mind, but expect anything going live in the next few months to ship on the current, stable React Router version or on a Next.js build using the Storefront API directly. I would be wary of anyone promising a production launch on a preview framework without explaining the upgrade risk.

Seven situations that decide the architecture

These are the situations I ask clients about before we talk architecture. Most brands recognise themselves in two or three of them, and the answer falls out of that.

1. The shopping experience is the product

Configurators, builders, editors and personalisation flows with complex state are much easier to build as an application than as Liquid sections held together with JavaScript. This is the strongest case for headless, and two of our projects show it from different angles.

StoryKeeper sells family albums and life story books through a built-in online editor, used largely by adult and senior customers. We have supported and developed it as a headless Shopify build since September 2024, including a step-by-step album builder with a visible progress bar and a calmer interface with larger, more legible type. Album creation conversion rose by 48% and bounce rate fell by 64%. The album builder is the product, which is exactly where headless makes sense.

Ovrload is the second example, and a less obvious one. It sells creatine gummies, mostly on subscription, and its old store was not built for that. We designed a custom theme with a headless architecture around one guided path: choose a subscription frequency, pick flavours, check out. Over the six months after launch, conversion averaged 4.6% against 2.03% in the six months before, measured in Shopify Analytics. Here the experience was not an editor but a funnel, and owning every step of it was worth the extra engineering.

StoryKeeper headless Shopify storefront: the step-by-step order flow for a Life Story Book with large, legible type and a visible progress indicator

2. You mainly want a faster store

Headless storefronts can feel very fast after the first page, because later page changes happen in the browser. They can also ship large JavaScript bundles that hurt Interaction to Next Paint on mid-range phones. Liquid themes benefit from Shopify's rendering and CDN and can be very fast when apps and scripts are kept under control.

Stay on Liquid and fix the theme. A slow theme is a symptom of heavy apps, unoptimised media and too much JavaScript, all of which can be fixed without a rebuild. On Loco Love's store we removed unused apps and third-party scripts and reworked image loading inside the existing Liquid theme: load time fell by 88% and conversion rose by 35%, comparing the 60 days before the work with the 60 days after. Our guide to speeding up a Shopify store covers how.

3. You mainly want better SEO

Search engines rank pages on content, relevance, links and a sound technical foundation. Both architectures can provide those. Headless changes who is responsible for the foundation, so better SEO is not a reason to go headless.

Google can render JavaScript, but its documentation explains that rendering happens in a separate step, so content that only appears after client-side JavaScript runs is a weaker bet than content in the initial HTML. Hydrogen renders on the server, which avoids the worst problems, but custom code can still hide product information behind client-side requests. And headless sites often launch without complete sitemaps, canonicals, hreflang, structured data or redirects, simply because nobody built them.

4. Marketing ships pages every week

If your team launches landing pages, changes homepage content and runs promotions weekly, the theme editor is doing a lot of quiet work for you. Choose Liquid, unless you budget properly for a headless CMS and good tooling. Without that, every content change becomes a developer ticket, and campaigns slow down.

5. The store runs on a lot of apps

Reviews, upsells, bundles, loyalty, subscriptions and quizzes depend on theme app extensions or scripts injected into the theme. Apps with an API or headless SDK can be wired into a custom storefront with development work. Apps that only work through the theme cannot, and each one becomes its own small project. Here my answer is Liquid, or a headless plan that lists every app and how it will be integrated.

6. Several front ends share one backend

A web store, a mobile app, in-store screens and kiosks can share components and data logic. Brands publishing a lot of editorial content from a headless CMS, or running several brands from one design system, also benefit from a single front-end codebase. That is a real case for headless, provided the next point is also true.

7. You have engineers who will own it

Headless needs in-house developers or a long-term agency partner who owns the codebase, and the business has to fund that work continuously, not only the build. Without this, nothing else on the list matters, because headless without ongoing engineering capacity decays quickly. StoryKeeper works because we have been developing it every month since 2024. If ongoing development would eat a large share of your margin, a custom Liquid theme will give a better return. And if the goal is simply a distinctive design, a fully custom Liquid theme can look and feel unique too.

The middle ground most brands overlook

The choice is often framed as all or nothing, and it does not have to be. A custom Liquid theme can include rich, app-like sections where they matter, such as a product finder, a bundle builder or a guided size selector, built with modern front-end code inside the theme. You keep the theme editor, app blocks and Shopify's SEO defaults everywhere else.

ORCA is the project I point to when a brand asks for headless and does not need it. The UK goalkeeping brand wanted one store that sells gloves and training gear, offers subscriptions for replacements with savings of up to 20%, and books group training sessions by age group and venue. That sounds like three products in one, and it is all a single Liquid theme: the subscription options and the booking flow are theme sections backed by apps, a size guide makes glove choice easier, and the marketing team edits everything in the theme editor. It took a little over 150 hours.

The limit shows when the interactive part stops being a feature and becomes the whole experience. If most of the customer's time is spent inside a builder or editor, with complex state that has to survive across many steps, the theme starts working against you. That is the point where I would look seriously at headless again, as we did for StoryKeeper.

The other version of the middle ground is the staged rollout in the checklist below: build the custom experience as a headless application first, keep the rest of the store on Liquid, and decide on the full move only once the custom part has proved its value with real customers.

Decision tree: if you cannot name an experience a theme cannot deliver, stay on Liquid; if it is one or two features, build a custom Liquid theme with app-like sections; if it is the whole experience and you can fund developers for years, go headless in stages, otherwise a custom Liquid theme

What headless takes away

Everything a Liquid theme does by default becomes something your team designs, builds and maintains.

  • The theme editor
    Marketers lose drag-and-drop sections. You need a headless CMS, Shopify metaobjects with a custom rendering layer, or developer time for content changes.
  • Plug-and-play apps
    Theme app extensions are designed for Online Store 2.0 themes, so app blocks do not appear in a custom storefront on their own.
  • Built-in SEO plumbing
    Automatic sitemaps, canonical tags, theme structured data and Markets-generated hreflang belong to the Online Store channel. On a custom storefront they have to be built and tested.
  • Some international behaviour
    Markets still provides currencies, prices and catalogues through the API, but routing, language switching and redirects must be implemented in the storefront.
  • Hosting simplicity
    Oxygen removes much of this, within limits. Workers must be 10 MB or less, use at most 128 MB of memory and are limited to 30 seconds of CPU time per request (as of October 2026). Oxygen also does not support proxies in front of deployments, which Shopify notes can conflict with bot mitigation and cause SEO issues.
  • Analytics defaults
    Consent, analytics events and pixels need explicit implementation, although recent Hydrogen updates added consent-aware analytics and page view events.

What you keep matters too. Products, inventory, discounts, Shopify Functions, customer accounts and Shopify's checkout all stay on Shopify, and checkout customisation works through checkout extensibility in both setups.

What three years of each option cost

Headless cost is mostly people rather than platform. Shopify includes Oxygen at no extra charge on paid plans from Starter to Plus, including the Pause and build plan, and the Shopify plan itself is the same whichever storefront you choose. Shopify Plus starts at $2,300 a month on a three-year term. Hosting elsewhere, such as Vercel, has its own pricing.

The ranges below are based on our projects and market quotes, as of October 2026. They vary with scope.

  • Custom Liquid theme
    $20,000 to $70,000 to build a custom Online Store 2.0 theme for an established DTC brand, or $5,000 to $20,000 for a premium theme with custom sections. Ongoing development sits in the lower half of the $2,000 to $15,000 a month retainer range, because marketers handle most content changes themselves, and most apps install directly through app blocks.
  • Headless build with Hydrogen or Next.js
    $80,000 to $250,000 or more, driven by the custom experience, the CMS and the number of integrations. Ongoing development sits in the upper half of that retainer range or above it with in-house engineers, because most storefront changes need developers. Add a headless CMS, search and monitoring, which together can cost several hundred to several thousand dollars a month, and framework and API upgrades, including the 2026 Hydrogen transition, which are your responsibility.

To make that concrete, I put two of our 2026 estimates side by side, one for each architecture, for brands of similar size. The custom Liquid theme came to about $45,000 to build, a $3,500 monthly retainer and around $400 a month in apps. The headless storefront came to about $140,000 to build, a $9,500 monthly retainer, around $1,500 a month in CMS, search and monitoring, and an allowance for one framework upgrade. Over three years that is roughly $185,000 against $556,000, three times as much. Most of the gap came from the monthly retainer, not from the build.

Two of our 2026 estimates over three years with the Shopify plan excluded: a custom Liquid theme at about $185k ($45k build, $126k retainer at $3,500 a month, $14k apps) and a headless storefront at about $556k ($140k build, $342k retainer at $9,500 a month, $54k CMS, search and monitoring, $20k framework upgrade), three times as much, with most of the gap in the retainer

Compare three-year totals, never build quotes alone. Headless is only worth that multiple if the custom experience produces a measurable revenue difference, as it did for StoryKeeper's album builder. For theme-based budgets in more detail, see what a custom Shopify website costs.

Timelines

A custom Liquid theme takes 8 to 14 weeks in our projects, and a headless build takes 4 to 9 months. Faster launches are possible on a different scope. Thrsty went live in 30 days and Quantum Padel in four weeks because both were built on Dawn, Shopify's free reference theme: we started from Dawn, added the custom sections each brand needed (a bundle builder and subscription flow for Thrsty, a short player-first path to checkout for Quantum Padel) and ran design, development and QA as one compressed cycle with an expanded team. A fully custom theme or a headless storefront does not compress like that.

SEO and speed criteria for a headless launch

If you do go headless, write these into the brief as acceptance criteria rather than hoping they get done:

  • product names, prices, availability and descriptions present in the server-rendered HTML;
  • product, breadcrumb and organisation structured data on the right templates;
  • XML sitemaps that cover every indexable URL and update when products change;
  • correct canonical tags and hreflang for every market and language;
  • a 301 redirect for every old URL, especially when moving from a Liquid theme;
  • robots.txt rules, including access for AI crawlers, set as a deliberate choice.

For speed, use Core Web Vitals as the neutral yardstick. Google's thresholds for a good experience are a Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of real visits. Put those targets in the brief and measure them on real devices after launch, whichever architecture you choose. On StoryKeeper we check the PageSpeed Insights report for the live storefront after every release, starting with the field data from real visits at the top of the report rather than the lab score below it. A move from Liquid to headless should be treated like a platform migration, with redirects and monitoring planned accordingly.

Checklist before you commit to Hydrogen

  1. Name the experience a theme cannot build
    If you cannot point to a specific feature, stay on Liquid.
  2. Confirm who owns the code
    In-house developers or a long-term partner, for at least three years.
  3. Audit every app and integration
    Mark which offer an API or headless SDK and which only work through the theme.
  4. Decide how marketers will edit content
    Choose a headless CMS or a metaobject-based approach before design starts.
  5. Model the three-year cost
    Include build, retainer or salaries, CMS and software, and framework upgrades.
  6. Pick the framework path
    Current React Router Hydrogen, the new Hydrogen preview or a Next.js build, with a documented upgrade plan.
  7. Write SEO and performance criteria
    Use the list above and set a JavaScript budget per page type.
  8. Stage the rollout
    Where possible, launch the custom experience first and move the rest of the storefront once it proves itself.

Frequently asked questions

Do I need Shopify Plus to go headless?

No. Headless storefronts and Oxygen hosting are available on standard paid plans. Plus becomes relevant for other reasons, such as expansion stores, B2B depth or heavier API and checkout needs, not because headless requires it.

Should I wait for the new Hydrogen?

If your project launches in the next few months, plan on the current stable stack and budget for a later upgrade. If you are starting a long project now, prototype on the preview and follow Shopify's update notes, but do not tie a production launch date to a framework still labelled a developer preview.

Can I go back from headless to a Liquid theme?

Yes. Products, customers and orders stay in Shopify, so switching back mainly means rebuilding the storefront as a theme and redirecting any URLs that change. It is a significant project, but your store data is not locked in.

Bring me the feature you think needs headless

Hydrogen is a powerful tool for brands whose storefront is a product in its own right. For everyone else, a well-built Liquid theme delivers most of the benefit at a fraction of the cost and keeps marketing in control. Our headless and Hydrogen team builds both kinds of store. If you tell me which experience you are trying to build, I will give you my honest view on which architecture fits it.

Sources

Teplin team
Want us to find your store's biggest wins?
We'll record a free video audit of your Shopify store and show you exactly what to fix first.
Free audit

Get a free Shopify store audit

A senior CRO specialist records a personalised video walkthrough of your store and the changes that will move revenue
Conversion & UX review
Speed & Core Web Vitals check
Prioritised list of quick wins
AUDIT - YOURSTORE.COM
Shopify store audit preview
Shopify store audit report
Claim your free audit
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Newsletter

Stay ahead of the curve

Monthly Shopify updates, ecommerce trends and proven conversion tactics – straight to your inbox. No fluff.
Keep reading

More from our resources

Development
11
min read

What We Freeze in a Shopify Store Four Weeks Before Black Friday

Our real freeze log from two Shopify stores: what we shipped, what waited until December, what we refused and this year's dates.
26.10.2026
Vlad Teplin
Vlad Teplin
November 2026 calendar with every day from 30 October frozen and Black Friday on 27 November marked, under the words 4 weeks of frozen code before Black Friday
Shopify Plus
16
min read

Is Shopify Plus Worth $2,300 a Month? Here Is the Real Bill

Every line on a Shopify Plus bill, the maths on when it beats Advanced, and the cases where I tell brands not to upgrade.
16.10.2026
Vlad Teplin
Vlad Teplin
Shopify Plus plan card showing $2,300 a month on a three-year term
AI Search
8
min read

Getting Your Shopify Store Into ChatGPT and AI Search Answers

How Shopify, Google and OpenAI actually get products into AI answers, and what we find when we audit client stores for it.
15.10.2026
Vlad Teplin
Vlad Teplin
Illustration of a generic AI assistant chat: a shopper asks for vegan creatine gummies that are easy to take daily and the answer shows two in-stock product cards with cited sources, tagged Route 1 Feed and Route 2 Open web, beside the title Getting your store into AI answers