By Nikola, founder at ZEROX. We build headless and Hydrogen storefronts alongside standard Online Store 2.0 themes, so "should we go headless" comes up on most of our Shopify scoping calls. Last updated May 2026.
Headless Shopify Hydrogen gets pitched as the obvious upgrade the moment a store starts to feel constrained, and sometimes it genuinely is. But going headless is a real architectural commitment, not a performance toggle you flip, and plenty of brands adopt it for reasons a good Online Store 2.0 theme would have solved for a fraction of the cost and effort.
This is the honest version: what Hydrogen and the Storefront API actually buy you, what they cost you, and the criteria we use to decide. It is written for technical founders, ecommerce leads, and agencies weighing a rebuild. If you are hitting the limits of Liquid and wondering whether the jump is justified, this is for you.
What "headless" actually means on Shopify
Standard Shopify renders your storefront with Liquid, its server-side templating, inside the Online Store. Headless decouples that layer. Shopify keeps being the commerce backend (products, inventory, cart, orders, and checkout), and you build the storefront as a separate application that pulls data through the Storefront API, a GraphQL API.
Hydrogen is Shopify's own React framework for that frontend, built on Remix, and Oxygen is Shopify's global edge hosting for Hydrogen storefronts. Those three pieces, the Storefront API, Hydrogen, and Oxygen, are designed to work together. That tight integration is the main reason to pick Hydrogen over wiring the Storefront API into a generic Next.js app yourself.
One thing does not change: checkout. Even headless, the actual checkout still runs on Shopify's hosted, PCI-compliant flow. You are replacing the storefront, not the payment path, and that is a good thing.
What going headless actually buys you
- A higher performance ceiling. You control rendering, bundling, caching, and exactly what ships to the browser. A disciplined Hydrogen build on Oxygen can be very fast. Note the word ceiling, though, because a careless headless build is slower than a good Liquid theme.
- Custom UX that Liquid fights you on. Complex product configurators, heavily interactive product pages, app-like navigation, and animation-rich experiences are simply easier in React than in Liquid.
- Content-heavy commerce. If you want editorial and product to live in one composed experience, headless lets you blend Shopify with a dedicated headless CMS such as Sanity or Contentful and render both from a single frontend.
- Multi-brand or multi-region setups where sharing one component library across several storefronts matters.
- Access to the React ecosystem and your engineering team's existing tooling.
If none of those describe a real, current pain, headless is solving a problem you do not have yet.
What it costs you (the honest list)
- You lose the theme editor. This is the big one, and nobody feels it until launch. Merchandisers give up the drag-and-drop Customize experience, sections, and blocks. Every surface a marketer wants to edit has to be deliberately rebuilt, usually with Shopify metaobjects and metafields or an external CMS. Skip that work and your team is back to filing dev tickets for copy changes.
- More development, and ongoing developers. Headless is an application. It needs a build pipeline, staging, monitoring, and people who maintain it. It does not sit quietly the way a theme can.
- The app ecosystem gets harder. Many Shopify apps assume a Liquid theme and just install. On headless, an app works only if it exposes an API or explicitly supports headless integration. Otherwise it is custom work, or it gets dropped. Audit your must-have apps before you commit.
- Preview and QA get more involved. Editors can no longer preview a change in the theme editor, so you build preview flows yourself.
- You own more surface area. More control means more responsibility for the performance, accessibility, and SEO the platform used to handle by default.
When Online Store 2.0 is plenty (which is often)
Online Store 2.0 is far more capable than the headless crowd tends to admit. Sections everywhere, JSON templates, metafields and metaobjects, and app blocks let a well-built theme handle most catalogs, most campaigns, and a lot of custom UX without ever leaving Liquid. For a standard catalog, a small team, or a business that values merchant autonomy and predictable cost, a strong OS 2.0 theme is usually the right answer, and a good build closes much of the gap people assume only headless can. We cover that route in our guide to custom Shopify themes.
Stay on this path if your team is small, you want marketers to own the site day to day, your app stack is standard, or budget and timeline are tight.
So: is headless Shopify Hydrogen worth it?
Our rule of thumb is to go headless when you are hitting concrete Liquid limits and have the engineering capacity to own a frontend application, not because it sounds modern. It earns its keep when:
- You have specific UX or performance requirements a good theme genuinely cannot meet.
- You are blending content and commerce and a headless CMS is already part of the plan.
- You run multiple storefronts and want a shared component system.
- You have, or will hire, developers to maintain it.
It is not worth it when the honest driver is "our current theme is dated." That is a theme problem, and a rebuild on OS 2.0 fixes it faster and cheaper. Going headless to escape a bad theme just leaves you with a more expensive bad frontend.
FAQ
Is Hydrogen free?
The Hydrogen framework is open source, and Oxygen hosting is included with Shopify plans. Hosting terms and plan tiers change, though, so verify current pricing with Shopify before you budget. The real cost is development and maintenance, not licensing.
Can I go headless without Hydrogen?
Yes. The Storefront API works with any frontend, including Next.js. You lose Oxygen and take on more setup yourself, but it is a valid path. Hydrogen is the batteries-included option when you want Shopify's own tooling.
Do I lose Shopify checkout if I go headless?
No. Checkout stays on Shopify's hosted, PCI-compliant flow. Headless replaces the storefront, not the checkout, which keeps your compliance scope small.
Will my Shopify apps still work headless?
Some will, some will not. Apps that expose APIs or support headless integrate cleanly. Apps that rely on injecting into a Liquid theme often need custom work or a replacement. Audit your critical apps first.
Is headless better for SEO?
It can be, because you control rendering and performance, but only if you implement server-side rendering, metadata, and redirects correctly. Done carelessly, headless is a step backward, because the platform is no longer handling SEO for you.
Work with a team that will tell you not to
We do headless and Hydrogen builds as part of our Shopify development work, and we talk roughly as many brands out of it as into it, because the wrong architecture is expensive in both directions. If you are weighing the jump, tell us where Liquid is hurting and we will give you an honest read on whether headless earns its keep. No lock-in, fixed quote, and you own the code.
