Hydrogen, And Other Futures That May Not Arrive · The Reluctant Guide to Shopify Migrations

Hour three of the discovery workshop.

A senior person at a brand we are not going to name says: “One day, we might want a custom account portal. Or a loyalty experience we can’t fully picture yet. We need the flexibility.”

Everyone nods. We nodded too. The conversation has been drifting toward Hydrogen for about forty minutes, in the way these conversations drift—not pushed by any one person, just gravitating that way, the architecture diagram on the whiteboard accreting boxes and arrows the closer the room gets to lunch. There is nothing on the brand’s current roadmap that Liquid couldn’t handle. There is no integration that would have failed. The day-one storefront could have been built on the Shopify online store in a quarter of the time and a fraction of the cost.

None of that matters. The conversation has stopped being about the day-one storefront. It has quietly become a conversation about a future that nobody in the room can describe—flexibility, capability, the experience we might want to build—and the team is about to commit two years and a substantial budget to it.

The question of whether to go headless on Shopify gets asked, in our experience, in one of two postures, and neither of them is the posture you want.

It gets asked too late. By the time the workshop convenes, the answer has already been shaped by everything except the brand’s own roadmap. A competitor site somebody admired in October. An agency pitch that leaned prestige. An internal champion who built a Hydrogen storefront somewhere else and would like to do it again. A creeping fear that staying on Liquid is the basic choice—the choice an ambitious brand wouldn’t make. The decision arrives pre-loaded into the room. What was supposed to be an architecture conversation becomes a search for justifications: features that might need Hydrogen, capabilities that might be useful, edge cases that might not fit Liquid. The reasoning is real. The framing isn’t. We aren’t asking what the brand needs to build; we’re asking what’s wrong with the platform we’ve already decided we don’t want.

The other version is the opposite. The question gets asked too early—before anyone has scoped the actual storefront. Headless is on the table because the platform decision was made in an executive meeting six months before there was anything concrete to build. The CTO went to a conference. A board member forwarded a thoughtful tweet. The architecture decision exists in advance of the storefront the architecture is supposed to serve.

Either way, the answer arrives without the evidence that should produce it.

What people are buying, when they buy Hydrogen, is a transfer.

A Hydrogen build moves a large amount of work from Shopify onto you. That transfer is the real price tag, and most proposals quantify the upside without quantifying the transfer.

A bulging, worn suitcase being passed across a bare doorframe from hands that release easily to hands that strain under the weight, with more luggage already piled on the receiving side. — What the proposal calls 'flexibility' arrives with checked baggage.

Start with the CMS. On a Liquid theme, the Shopify online store is the CMS—sections, blocks, theme settings, the metaobject system that ships with the platform. Your editors know how to use it. Your engineers don’t have to build it. Hydrogen ships none of that. You pick a CMS, integrate it, and operate it—Sanity, Contentful, whatever fits the editorial workflow your merchandising team actually does. The picking is the easy part. The hard part is everything downstream: templates, preview environments, role-based publishing, the dozens of small editorial conveniences the online store gave you for free, the workshop you are going to have to run with merchandising in week sixteen when they ask why the preview link does not behave the way it used to behave. Each of those is a Tuesday’s worth of work for somebody. There are a lot of Tuesdays.

Then the apps. The backend apps still work fine—order management, fulfillment, tax, payments. The storefront apps are a different story. Reviews. Wishlists. Swatch pickers. The merchandising UI a search vendor ships alongside their integration. Every one of those rebuilds from scratch, even when the vendor publishes an SDK. The SDK gives you primitives. It does not give you the surface area a Liquid app drops in via a theme editor toggle. The Liquid app was the toggle. The headless SDK is the substrate the toggle was sitting on. Multiply that across the ten or fifteen apps a typical brand depends on, and the engineering bill stops looking abstract.

Then Oxygen. The hosting that disappeared the day you went on Shopify reappears the day you go on Hydrogen. Deploys. Environments. Performance regressions. Edge runtime quirks. The slow accretion of platform-operations work that someone on your team—or someone we hire for you—has to own. It rarely shows up in the original estimate, because at planning time it looks like a flat cost. It isn’t. It compounds.

And then the team. A Liquid team and a Hydrogen team aren’t the same team. If you have one and need the other, that is a hiring program, an upskilling track, and an honest acceptance that some people on your current team will not make the transition. We have seen brands try to soft-pedal this part and end up with a storefront nobody internally feels confident touching. Headcount you do not have is a cost. Headcount you have to retire is a different one, and the second one is harder to put on a slide.

Every one of these is survivable. The question is whether the thing you are getting in exchange is worth carrying all of them for the next five years.

We have something to admit on that five-year question.

We held the other view first.

We are a deeply technical team, and Hydrogen had every reason to win us over. A modern stack on top of Shopify’s commerce engine. Real developer experience after a decade of Liquid’s idiosyncrasies. The promise of working inside Shopify’s ecosystem without inheriting its frontend constraints. On paper, joyful to work with. We were genuinely excited. The first projects we recommended it on, we built well.

Then the bill came in. Not on day one—quietly, across the first eighteen months. Apps that didn’t translate. Editorial workflows that had to be rebuilt because the headless CMS did not behave the way the merchandising team expected. The slow widening of the operational surface area, where every quarter we would find ourselves explaining a new piece of infrastructure to clients who thought they were buying a storefront. We changed our minds. We changed our advice with our minds.

The ecosystem-level case has gotten worse alongside our own reading of it. Shopify’s visible investment has moved elsewhere—AI surfaces, agentic commerce, the merchant-facing tools that drive their next phase of growth. Hydrogen release cadence has softened. Public commitments have softened. The volume of new documentation, the number of conference sessions, the velocity of the surrounding ecosystem—all of it has cooled relative to where it was in 2022. Fewer brands going Hydrogen means fewer frontend app vendors investing in headless SDKs, which means more rebuild-from-scratch work for whoever is still going there. The flywheel is not spinning the way it used to.

The wider industry hype that carried headless—composable, MACH, the whole storefront-as-frontend pitch—has moved on too. The buzzword stack today is AI. The peers and prestige signals that made Hydrogen feel inevitable in 2022 do not push the same way now. None of that, on its own, is a reason to reject the architecture. But replatforming locks you in for years, and trajectory matters as much as the current snapshot. The right answer in 2022 is not automatically the right answer today—and we are more comfortable saying that out loud because we held the other view first.

Most of the headless decisions we sit in on are not engineering decisions. They are decisions about a future that may never arrive, paid for in present-day complexity. In 2026, that complexity is heavier, and harder to recover from, than it was three years ago.

On the Headless Prestige Tax

A brief, not-unkind word about why so many brands arrive at the workshop with Hydrogen already half-decided.

Often it is because their competitor went headless and keeps posting about it on LinkedIn. The post says we replatformed to a composable architecture and shows a tasteful screenshot and a humblebrag about page speed. Nobody on the team knows whether the competitor’s traffic is up, or whether their conversion improved, or whether their engineering team is now drinking through lunch. The post does not say. (The post does not have to. It is a LinkedIn post.)

Often it is because the agency pitching the project leans prestige. Hydrogen feels modern. Hydrogen sounds like the brand is investing seriously in technology. Hydrogen is, also, a more interesting line item in a quarterly review than Shopify Liquid theme refresh. The board reads Hydrogen and assumes velocity. They read Liquid and assume housekeeping. This is not a real signal. It is, however, a powerful one.

Often it is because someone in the room—let us call them the architect—has been waiting for a project that lets them build Hydrogen, because the last job they had only let them build Liquid, and they are an ambitious technologist who would like, very reasonably, to do work that feels current. We have been the architect. We have a lot of sympathy for the architect. We also know, having been the architect, that the architect is not always the person to ask about whether to use Hydrogen.

None of these are bad reasons in the ordinary sense. They are just not the reason. Treating prestige as architecture is how the present pays for a future that may never arrive.

If you are reading this and you are the technical lead who was excited about Hydrogen—who spent a weekend prototyping it, who put the architecture diagram together, who has, possibly, sent some of these arguments to your director already—we want to be careful with you for a moment.

We were you.

The instinct to choose the more modern stack is, professionally, the right instinct most of the time. The choice to keep up with where a platform’s investment is going is the choice that has saved our careers more than once. That you ended up here, looking at Hydrogen, is not a failure of judgment. It is a sign that your judgment is calibrated to a world where new tooling usually does turn out to be the right call.

The argument we are making is narrower than the one you might be hearing. We are not saying you were wrong to want this. We are saying that in this specific case, in 2026, on this specific platform, with this specific roadmap, the costs got heavier and the bet got worse, and we want you to be the person in the room who knows that before the meeting.

If you read the bill and the answer still resolves to yes, this is worth it, you will get no argument from us. Some brands are in that position. We work with some of them.

If the answer does not resolve, we want you to be able to say so without feeling like you have lost.

We have lost this argument, at least once, in a meeting where the right move would have been to lose it sooner. (Ask us how we know.)

There are real reasons to go headless on Shopify in 2026. They are narrower than the proposals suggest, but they exist—and if you are in one of them, the costs above are a tradeoff worth making.

A figure rests a hand on a thick stone wall beside a narrow vertical gap, peering through at a different landscape beyond, deciding whether the gap is wide enough to be worth it. — The niches are real. They are also, genuinely, niches.

There are technical constraints on the Liquid-rendered side you genuinely cannot change. URL structures locked in for SEO reasons. Theme-layer behaviors that do not reach the surface you need. If the constraint is real and material to the business, Hydrogen gives you back the control, and that is what you are buying.

There are storefronts unconventional enough that they do not fit the Homepage / PLP / PDP / Checkout shape Shopify themes assume. A generative AI storefront. An interactive editorial layer. An experience that is not really a page in the traditional sense. If the storefront experience is the product—not a wrapper around the product—Liquid will fight you and Hydrogen will fit.

There is multi-backend routing. A storefront that has to front Shopify in one market and a different commerce backend in another—Salesforce in legacy markets, a marketplace integration in a third—behind a single customer experience. Liquid was not built for that. Hydrogen can be.

There is merchandising and personalization deep enough that integration with tools like Nosto or Algolia becomes the structural concern. When the duplication of HTML and styling across Liquid blocks is a bigger problem than the platform itself, the equation flips.

And there are brands that are partially publications: content workflows closer to a newsroom than a merchandising calendar, where the editorial complexity needs a frontend the online store editor cannot accommodate. Crossover commerce-content sites have always sat awkwardly on Shopify; sometimes Hydrogen is the door out.

These are real niches. Being in one of them is a reason to consider Hydrogen—not a mandate. If you cannot place yourself somewhere on the list, the answer is probably no.

The decision improves the moment you replace the platform question with a present-tense business question.

Not what might we want to build one day. That question never resolves. The right answer is always we don’t know, and headless will always look like insurance against that uncertainty. Insurance you pay for upfront, every quarter, regardless of whether you ever make a claim.

The question that resolves is the present-tense one. What are we trying to do that Liquid won’t let us do, now or in the next twelve months? If you can name the constraint—a specific roadmap item that hits a wall, a real cost of staying on Liquid that shows up in numbers, an experience your customer needs that the theme layer cannot deliver—the headless conversation gets useful fast. If you cannot, the conversation is happening in the wrong register.

Replatforming is already a big, messy project. (Anyone who tells you otherwise is selling you something.) Adding an architecture choice that nobody can defend in present-tense business terms is how messes become disasters.

A Hydrogen yes, in 2026, should feel like accepting a limitation, not gaining a capability.

The limitations you are accepting are larger and more durable than the capability you are gaining: a CMS to operate, a frontend app catalog to rebuild, hosting infrastructure to maintain, a team to retool. Some brands are in the rare position where the capability genuinely outweighs all of that. Most are not.

If the tradeoff still reads as worth it after you have named both sides honestly, go. We will help you.

Otherwise, Liquid isn’t the cautious choice. It’s the right one.