Someone with Shopify Plus budget asks "should we go Hydrogen?" every few months now. The answer is almost always "not yet." Not because Hydrogen is bad, but because the thing that triggers the question is usually solvable inside Liquid at 10% of the cost. This is the decision log I use to walk through it without the conversation running on vibes.
- Q01Is there a React Native app or other non-Shopify storefront surface in the next 12 months?Mobile apps, a marketing site that embeds live PDP content, or a third-party surface sharing cart/product components.
- Q02Do you need multi-region fulfillment or catalogs past what Shopify Markets handles natively?Region-specific catalogs, pricing rules, or shipping UX that Markets doesn't cover.
- Q03Does the PDP assemble content from sources that don't fit Shopify's data shape?If the product page pulls from three non-Shopify data sources and none of them are a Shopify product, this counts.
The fork in the road
The question comes up under three pressures. The first is performance: Core Web Vitals are failing and someone has decided Shopify is the problem. The second is creative ambition: the design team wants a storefront that doesn't feel like a Shopify theme. The third is surface growth: a React Native app, a separate marketing site, or a multi-region fulfillment setup has appeared on the roadmap.
Only the third is a genuine Hydrogen trigger. The first two almost always resolve inside Liquid if the theme architecture is sound. The DTC Shopify theme architecture for brands past 2M covers what "sound" actually means in practice.
What's at stake in this decision is real money. A custom Hydrogen build for a mid-market DTC brand runs $80K to $250K depending on scope, and the ongoing storefront engineering cost is ~$8K to $20K per month for maintenance alone. A production Liquid theme on Online Store 2.0 lands at $15K to $60K with substantially lower ongoing costs because Shopify maintains most of the platform surface for you.
Option A: Liquid (Online Store 2.0)
What you get. Native Shopify checkout, which is not a small thing. The checkout handles PCI scope, fraud screening, payment processors, subscription integrations, gift cards, tax calculation, and shipping rates without you owning any of that code. You inherit Shopify's CDN for images and assets, their cart state management, their metafield and metaobject data layer, and the entire app ecosystem that assumes a Liquid theme.
You also inherit Online Store 2.0 section composition, which is powerful once you architect the theme correctly. The metafield-driven sections pattern is the piece that most people don't realize is possible inside Liquid until they've built it. Once you have it, the "Liquid is limiting" complaint evaporates for 80% of DTC needs.
Core Web Vitals on Liquid are free in the sense that Shopify maintains the underlying render pipeline. You still have to ship careful theme code and avoid bloated third-party scripts, but the baseline is already good. The Core Web Vitals approach on DTC Shopify is the diagnostic I run when CWV is failing and someone has misattributed it to the platform.
What it costs. You hit a ceiling when your storefront needs to exist somewhere Liquid doesn't run. A React Native mobile app can't render Liquid. A non-Shopify marketing site can't share a Liquid PDP component. A multi-region setup with region-specific fulfillment logic past what Shopify Markets handles natively gets awkward fast. If any of those are firm requirements in the next 12 months, Liquid starts to cost more than Hydrogen.
You also pay a cost in the design ceiling, but it's smaller than people think. Liquid themes can look as custom as you want; the constraint is the checkout UI (which Shopify Plus lets you customize more now with checkout extensibility, but still not infinitely).
Option B: Hydrogen
What you get. Full React control over the storefront. Hydrogen 2 is built on Remix, which got rewritten into the React Router 7 architecture in 2024-2025, and now ships with React Server Components as first-class. Oxygen, Shopify's edge hosting for Hydrogen, is free for Plus merchants and serves the storefront from Shopify's global edge with low cold-start latency. The Hydrogen components give you cart, checkout handoff, and product data patterns out of the box, so you're not writing a Shopify client from scratch.
The bigger win is sharing the storefront code with other surfaces. If your React Native app, marketing site, and storefront all need the same PDP, the same cart drawer, and the same pricing logic, Hydrogen is the only path that doesn't duplicate the work three times.
You also get cleaner data flow for content-heavy storefronts. If your PDP assembles content from a headless CMS, a product data source, and a pricing service, Hydrogen's edge functions are a more natural fit than stitching three apps into a Liquid template.
What it costs. You own the performance story. CWV is no longer free. You have to ship careful code, manage hydration, cache aggressively at the edge, and handle every slow third-party script yourself. Shopify's CDN is still there for images, but the HTML render is yours.
You own the storefront engineering. Cart state, inventory consistency, checkout handoff, SEO (including schema markup, sitemaps, canonicals, noindex logic), accessibility, internationalization, and consent management all become your team's responsibility. You gain flexibility and lose the safety net that Liquid themes get for free.
You also lose a large chunk of the app ecosystem. Apps that patch themselves into Liquid themes don't work on Hydrogen. Most of them have Hydrogen-compatible alternatives now, but the migration cost is real and some niche apps still have gaps.
What I chose, and why
“The question is almost never "Hydrogen or Liquid." It's "do I have a non-Shopify surface that actually needs to share storefront code in the next 12 months?"”
For the DTC brand build I shipped in Q4 2025, I chose Liquid. The theme needed four layout variants for a content module, native Shopify checkout, the existing app stack for reviews and subscriptions, and Meta CAPI wired into the theme. None of those needed Hydrogen. The team was Liquid-fluent. There was no app roadmap, no marketing site sharing components, no multi-region expansion planned in the window that mattered.
The decision took about 90 minutes once we wrote down what we actually needed. The triggering question ("should we go Hydrogen?") had been sitting unanswered for three weeks before that, because nobody had framed it as a surface question instead of a platform question.
What made Liquid work for this case was the theme architecture. Thin sections, metafield-driven data, and theme-owned CAPI. If I'd been inheriting a messy theme with 800-line section schemas and app-owned tracking, the cost-benefit would have shifted, because a Hydrogen rewrite is not obviously more expensive than a Liquid rewrite once the existing Liquid theme is past repair. The skills I use for day-to-day Shopify development covers the toolkit that makes Liquid rewrites cheap enough to prefer.
What I'd revisit, with what evidence
A few triggers would push me back to Hydrogen on a future engagement:
- A React Native app landing in the next 12 months. Sharing a PDP or cart component across the storefront and the app is the single strongest Hydrogen argument, and it's a real argument.
- A marketing site that needs the live product data. Not "a marketing site with product links" (that's fine on any platform), but a marketing site whose pages embed real PDP content, live inventory, or live pricing.
- Multi-region fulfillment with per-region custom logic past what Shopify Markets handles natively. Some brands need region-specific catalogs, region-specific pricing rules, or region-specific shipping UX that Markets doesn't cover.
- A content model that genuinely doesn't fit Shopify's data shape. If your PDP assembles content from three data sources and none of them are a Shopify product, Liquid starts feeling bent in ways Hydrogen doesn't.
The trigger I explicitly don't count as evidence: "the design team wants more control." Liquid themes can be as custom as you want. If "more control" is the only driver, the conversation is about theme architecture, not about Hydrogen.
The reference Liquid implementation
If you've landed on Liquid (most of you will), the Shopify Theme Starter is the reference implementation I ship with: metafield-driven sections, Meta CAPI wired at the theme layer, Core Web Vitals tuned, and an agent-editable section template. It's the Liquid base I would build from on any new DTC engagement in 2026.
For the case study that grounded the decision above, see the four-layout theme build.
Is Shopify Hydrogen worth it for a DTC brand in 2026?
Only if you have a concrete non-Shopify surface in the roadmap, like a React Native app, a marketing site sharing storefront components, or a multi-region setup past what Markets handles natively. For most mid-market DTC brands, a well-architected Liquid theme covers what Hydrogen would give you at a tenth of the engineering cost.
Does Hydrogen have better Core Web Vitals than Liquid?
Not automatically. Liquid themes on Online Store 2.0 get a good CWV baseline for free because Shopify maintains the render pipeline. Hydrogen can be faster if you engineer it carefully, but you own every millisecond. Failing CWV on Liquid is usually a theme code or third-party script problem, not a platform problem.
What does a Shopify Hydrogen build cost in 2026?
A custom Hydrogen build for a mid-market DTC brand typically lands between $80K and $250K depending on scope, plus roughly $8K to $20K per month for ongoing storefront engineering. A production Liquid theme on Online Store 2.0 lands at $15K to $60K with substantially lower ongoing costs.
Can I still use the Shopify app ecosystem with Hydrogen?
Partially. Apps that inject themselves into Liquid themes don't work on Hydrogen. Most reviews, subscriptions, and post-purchase apps now have Hydrogen-compatible packages, but expect migration cost on each one and occasional gaps on niche apps.
Does Hydrogen work with Shopify Checkout?
Yes. Hydrogen handles the cart on your side and hands off to Shopify Checkout the same way a Liquid theme does. You don't rebuild checkout. Checkout extensibility on Shopify Plus lets you customize the checkout UI for both Hydrogen and Liquid storefronts.
Should agencies still recommend Hydrogen for new DTC builds?
Recommend it when the client has a real surface requirement or a specific content flexibility need that Liquid can't address. Don't recommend it because the client heard the word and wants it. The Hydrogen engineering bill is real and the maintenance commitment is long.
Sources and specifics
- Hydrogen 2 was released in 2023 as a Remix-based framework, with React Server Components adoption landing in Hydrogen 2 releases through 2024-2025.
- Oxygen edge hosting is free for Shopify Plus merchants as of 2026 and deploys Hydrogen apps to Shopify's global edge network.
- The DTC brand Liquid build referenced shipped in Q4 2025 across four layout variants against a shared metafield contract.
- Cost ranges cited reflect mid-market DTC engagements observed in 2024-2025 and vary significantly with scope and team location.
- Shopify Checkout extensibility (on Plus) applies to both Hydrogen and Liquid storefronts and is not a differentiator between them.