A discovery workshop we ran last year with a mid-market DTC brand, somewhere around hour three. The team was replatforming to Shopify, the architecture conversation had drifted toward Hydrogen, and one of the senior people in the room said something we hear in some form on most of these calls. One day, we might want a custom account portal. Or a loyalty experience we can't fully picture yet. We need the flexibility.
The room agreed. There was nothing on the current roadmap that Liquid couldn't handle. There was 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 mattered, because the conversation had stopped being about the day-one storefront. It had quietly become a conversation about a future that nobody could describe, and the team was about to commit twelve months and substantial budget to it.
Most of the headless decisions we sit in on aren't engineering decisions. They're decisions about a future that may never arrive, paid for in present-day complexity. And in 2026, that complexity is heavier, and harder to recover from, than it was three years ago.
The Future That May Never Arrive
By the time most brands ask whether they should go Hydrogen, the answer has already been shaped by everything except their own roadmap. Competitor sites they admire. Agency pitches that lean prestige. An internal champion who built a Hydrogen storefront somewhere else and wants 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 workshop. What was supposed to be an architecture conversation becomes a search for justifications: features that might need Hydrogen, hypothetical 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.
Once you notice that pattern, the next question becomes the harder one: what are people actually buying when they buy Hydrogen?
What Hydrogen Costs You
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.
Start with the CMS. On a Liquid theme, the Shopify online store is the CMS: sections, blocks, theme settings, the metaobject system. Editors know how to use it. Engineers don't have to build it. Hydrogen ships none of that. You pick a CMS, integrate it, and operate it—Sanity, Contentful, or whatever else fits the editorial workflow your merchandising team actually does. The picking is the easy part. The hard part is everything downstream: templates, scheduled publishing, metaobject integrations, the dozens of small editorial conveniences that Online Store gives you for free.
Then the apps. Backend apps still work fine: order management, fulfillment, tax, payments. Anything that interacts with the storefront is 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 doesn't give you the convenience of a theme editor toggle. Multiply that across the ten or fifteen apps a typical brand depends on, and the engineering bill starts getting scary.
Then infrastructure. 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 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's a hiring program, an upskilling track, and acceptance that some people on your current team won't make the transition. We've seen brands try to soft-pedal this and end up with a storefront nobody internally feels confident touching.
Every one of these is survivable. The question is whether the thing you're getting in exchange is worth carrying the burden.
The Headless Bet Got Worse, Not Better
This hasn't always been our point of view on the Hydrogen-vs-Liquid debate.
We're 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, and on the early projects we recommended it on, we built it well.
Then the bill came in. Not on day one, mind you, but quietly across the first eighteen months. Apps that didn't translate. Editorial workflows that had to be rebuilt because the headless CMS didn't behave the way merchandising teams expected. The slow widening of the operational surface area, where every quarter we'd find ourselves explaining a new piece of infrastructure to clients who thought they were buying a storefront. We changed our mind, and we changed our advice with it.
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 dotdev 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's still going there. The flywheel isn't 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 don't 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 isn't automatically the right answer today.
When Headless Is (Actually) Justified
This isn't a piece against Hydrogen. There are real reasons to go headless on Shopify in 2026. They're narrower than the proposals suggest, but they exist—and if you're in one of them, the costs above are a tradeoff worth making.
There are technical constraints you can't change on a Liquid-rendered storefront. URL structures locked in for SEO reasons, theme-layer behaviors that don't reach the surface you need. If the constraint is real and material to the business, Hydrogen gives you back the control.
There are storefronts so unconventional they don't fit the Homepage / PLP / PDP / Checkout shape Shopify themes assume. A generative AI storefront. An interactive editorial layer. An experience that isn't really a page in the traditional sense. If the storefront experience is the product, and not a wrapper around the product, Liquid will fight you and Hydrogen will fit.
There's multi-backend routing. A storefront that has to front Shopify in one market and a different commerce backend in another (e.g., Salesforce, a legacy bespoke platform, a marketplace integration) behind a single customer experience. Liquid wasn't built for that. Hydrogen can be.
There's 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 can't accommodate. Crossover commerce-content sites have always sat awkwardly on Shopify.
These are legitimate use cases, but having one of them is a reason to consider Hydrogen, not a mandate.
Treating Hydrogen as a default for ambitious brands is how the present pays for a future that may never arrive.
The Question You Should Be Asking
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 can't deliver—the headless conversation gets useful fast. If you can't, the conversation is happening in the wrong register.
Replatforming is already a big, messy project. (Anyone who tells you otherwise is lying.) Adding an architecture choice that nobody can defend in present-tense business terms is how messes become disasters.
Choose the Platform You Can Defend Now
A Hydrogen yes, in 2026, should feel like accepting a limitation as much as gaining a capability.
More often than not, the limitations you're accepting are larger and more durable than the capability you're gaining: a CMS to operate, a frontend app catalog to rebuild, infrastructure to maintain, a team to retool. Some brands are in the rare position where the capability outweighs all of that. Most aren't.
If the tradeoff still reads as worth it after you've evaluated the pros and cons, go for it. Otherwise, Liquid isn't the cautious choice. It's the right one.
If you're in the middle of this decision and want a second opinion from a team that's lived it on both sides, we should probably talk.
