Shopify unveiled Hydrogen and Oxygen this month at the SHOP event. After two years of headless Shopify being a third-party affair — through Gatsby, Next.js with the Storefront API, or one of the JAMstack frameworks — Shopify is now shipping its own React-based storefront framework. The announcement has caused the same flurry of ‘should we migrate’ calls that the Liquid-section update did three years ago.
The honest answer for most stores is the same answer we gave about headless WordPress last year: not yet, and not because of the architecture.
What Hydrogen actually is
Hydrogen is a React-based framework for building Shopify storefronts. It uses React Server Components (in alpha at this point), edge runtime hosting through Oxygen (Shopify’s edge-compute platform), and a set of pre-built Shopify components for product cards, cart, search, and checkout.
The pitch is that Hydrogen-on-Oxygen gives you the developer experience of a modern React framework with the operational simplicity of being inside the Shopify ecosystem. Oxygen handles deployment, scaling, and the connection to the Shopify backend without needing a third-party host.
The framework is open source. The hosting tier is invite-only for now.
What it is not
Hydrogen is not a drop-in replacement for Liquid themes. The data model on the front end is different — components consume Shopify Storefront API responses, not Liquid object trees. The component model is different — React, not Liquid filters and tags. The build pipeline is different — Vite, not the Shopify theme upload flow.
A migration from Liquid to Hydrogen is a full storefront rebuild. The Liquid code does not port. The theme settings do not port. The custom sections do not port. You are building a new storefront from a blank file.
What Liquid still does well
Liquid themes, especially since the 2.0 theme architecture shipped with sections-everywhere last summer, are genuinely capable. The merchant editing experience in the theme editor is mature. The performance, with a well-built theme, is fine — most of our Liquid stores hit Lighthouse mobile scores in the 70s to mid 80s.
The ecosystem of Shopify apps that hook into the theme runs primarily through Liquid. ScriptTag-based apps, theme extensions, app blocks — these all work on Liquid storefronts today. On a Hydrogen storefront in 2022, many of those apps either do not work or require custom integration.
The deployment model is also simpler. Liquid theme upload, preview, publish. No build pipeline. No deploy keys. For a merchant who has a single front-end developer or a part-time freelancer, Liquid is the lower-friction option by a wide margin.
Who Hydrogen is for, right now
The merchants we would advise to look seriously at Hydrogen in 2022 fall into three buckets.
First, merchants who are already on a headless Shopify stack with Next.js or Gatsby, and want to consolidate hosting onto Oxygen. The migration cost from one React-based stack to another is meaningfully lower than the migration from Liquid.
Second, merchants with a real software-engineering team in-house, building a custom commerce experience that goes well beyond what theme editor lets a merchant configure — configurators, B2B portals, deeply customized PDPs, real-time inventory dashboards. The React component model and the API-first data flow make those builds easier.
Third, merchants who are pre-launch and have not yet built a Liquid theme. Starting fresh on Hydrogen avoids the rebuild cost. The trade-off is that the merchant editing experience is less mature — Hydrogen’s tooling for non-developer storefront edits is much earlier than Liquid’s.
Who should stay on Liquid
Everyone else, for now. If you have a working Liquid theme, a working merchandising workflow, and a working app ecosystem, the case for migrating is not made by Hydrogen’s existence. It is made by a specific limitation you cannot solve in Liquid.
If you are hitting Liquid’s limits — really hitting them, not theoretically hitting them — that is the moment to evaluate Hydrogen. Some signals: you are loading multiple heavyweight third-party scripts to do what should be a single component. Your theme has accumulated more than a hundred theme settings to support increasingly bespoke campaign needs. Your engineering team is spending more time fighting Liquid than building features. Those are real signals.
The 18-month outlook
Our read is that Hydrogen will be a serious option for most mid-market stores by the end of 2023. The framework needs:
- A merchant-editable layer that approaches what theme settings + sections does today on Liquid
- Broader app compatibility
- Oxygen to leave invite-only
- The React Server Components story to stabilize beyond alpha
By the end of next year all four of those should be in better shape. Until then, the conversation we are having with prospects is: Hydrogen is real, Hydrogen is the future, but the right time to migrate is not the month Hydrogen launches. The right time is the month your Liquid theme starts costing you more than the rebuild would.