Hydrogen and headless Shopify
Headless buys you control of the storefront and costs you everything Shopify was doing for free: the theme editor your team relies on, app embeds that install themselves, and a rendering layer somebody else maintains. It is the right call for a minority of stores and an expensive detour for the rest. The most useful thing I can do at the start of this conversation is tell you which one you are.
A real answer on whether to go headless
A short assessment against what you actually need. If a well-built Liquid theme gets you there, I will tell you that; it is the cheaper and more maintainable answer more often than not.
Content your team can still change
The failure mode of headless is a storefront only a developer can edit. Metaobjects, sections and a real CMS integration keep day-to-day changes out of the deploy queue.
Cached and streamed at the edge
Hydrogen on Oxygen streams server-rendered React from Shopify's edge with sub-request caching, so the speed advantage survives contact with production traffic.
When headless earns it
A storefront experience genuinely outside what Liquid can express: configurators, complex personalisation, an app-like flow that a theme can only approximate.
One frontend serving several commerce or content backends, where Shopify is one source among many rather than the whole system.
An existing React or Next.js application that commerce needs to live inside, rather than beside.
A content operation heavy enough that a dedicated CMS is already the centre of gravity and Shopify is the transaction layer.
When it does not
"The site feels slow." A slow theme is usually slow because of apps and images, and headless does not delete either, it relocates them while adding a rendering layer you now maintain.
"We want more design control." Modern Liquid with sections and metaobjects covers considerably more than most teams have tried before concluding it does not.
"Headless is faster." Sometimes. A poorly cached Hydrogen app is slower than a well-built theme, and the difference is architecture, not the label on it.
If your marketing team edits the site weekly and does not want to file tickets to do it, that is a strong argument for staying on a theme, and it is worth saying out loud early.
How the build runs if it is the right call
Hydrogen is Shopify's React framework, built on Remix, deployed to Oxygen: Shopify's edge hosting, included with your plan. Data comes over the Storefront API, and the caching strategy is the architecture: which queries are cached, for how long, and what invalidates them. Get that right and it is fast everywhere; get it wrong and it is a slow site with better tooling.
Checkout stays on Shopify. This matters and is often misunderstood: headless means a custom storefront, not a custom checkout. Checkout remains Shopify's, with the same extension points described on the checkout extensibility page, which is also what keeps PCI scope where it is.
Content is planned before the build, not after. Metaobjects for structured commerce content, a headless CMS where editorial genuinely needs one, and a preview workflow so nobody is publishing blind. Skipping this step is the single most common reason a headless build gets rebuilt.
If Hydrogen is not the fit, an existing Next.js app, a team already fluent in another framework, the Storefront API works the same way from anywhere. The framework is a choice; the caching discipline is not.
Is this the right engagement?
A good fit
- Storefront requirements Liquid genuinely cannot express
- Existing React or Next.js applications that need commerce inside them
- Multi-brand or multi-region frontends over shared backends
- Teams with the engineering capacity to own a frontend long-term
Not a fit
- Stores going headless mainly for speed: fix the theme first
- Teams without a developer available for ongoing frontend maintenance
- Marketing-led sites that need daily editing without a deploy
- Anyone hoping to customise checkout beyond the extension points
Common questions
Does headless mean a custom checkout?
No. Checkout stays on Shopify regardless. Headless replaces the storefront only, which is what keeps PCI scope and payment reliability where they are, and it is why checkout extensibility still applies to a headless build.
Will our Shopify apps still work?
App embeds that inject into a Liquid theme will not. Apps with a Storefront API or headless integration will. The app inventory is part of the assessment, because for some stores it is the deciding factor on its own.
Is Oxygen hosting extra?
Oxygen is included with Shopify plans for Hydrogen storefronts. You can host Hydrogen elsewhere, but you then take on the edge caching and deployment story that Oxygen handles for you.
Start with the diagnosis
Send me your store and I will record a 20-minute walkthrough of what I would change and why. No call required, and nothing to unsubscribe from afterwards.