Headless Shopify with Hydrogen: when it's worth it (and when it isn't)

"Should we go headless?" is one of the most common questions I get, and the honest answer is usually "probably not yet." Headless is powerful and, for the right store, transformative. For the wrong one it's a way to spend three times the budget to end up somewhere a good theme would have taken you. Here's how to tell the difference.

What "headless" actually means

A normal Shopify store uses a Liquid theme: Shopify renders your pages on its own servers and controls the storefront. Headless means you split the two apart — Shopify still runs the commerce engine (products, cart, checkout, orders) but you build the storefront yourself as a separate application that pulls data through the Storefront API.

Hydrogen is Shopify's own React framework for building that front end, and Oxygen is their hosting for it. So "Hydrogen build" usually means a React storefront, deployed on Oxygen, talking to Shopify through the API.

What you get for the extra work

• Speed and control. No theme constraints, no app scripts you didn't choose. You control every byte that ships to the browser, which is how the fastest storefronts get fast.
• Freedom in the UI. Anything you can build in React, you can build as your storefront — complex configurators, unusual navigation, app-like interactions.
• One front end, many back ends. If content lives in a separate CMS or you pull data from other systems, headless lets you compose them cleanly. Metaobjects arrive as structured data rather than HTML you have to parse.

What it costs you

None of this is free, and the costs are easy to underestimate:

• Build cost. You're building a web application, not configuring a theme. That's more time and a developer who knows React, not just Liquid.
• You lose the theme editor. Merchandisers can no longer drag sections around in the Shopify admin unless you rebuild that flexibility yourself. Teams that live in the theme editor feel this immediately.
• Apps get harder. Many Shopify apps inject themselves into Liquid themes. On headless, some won't work without custom integration, and some won't work at all — which changes the build-versus-buy calculation for every app you rely on.
• More to maintain. A codebase, a deploy pipeline, dependencies to keep current. It doesn't run itself.

Headless is a performance and flexibility tool, not a status symbol. The question isn't whether you can — it's whether the trade is worth it for your store.

When it's worth it

Headless earns its cost when at least one of these is really true:

• Speed is a measured business problem and you've already exhausted theme-level fixes.
• You need a storefront experience a theme genuinely can't express — not "nicer," but structurally different.
• Content or data lives in systems Shopify has to compose with, and a headless front end is the clean way to do it.
• You have the budget and the team to maintain a codebase, not just launch it.

When it isn't

Skip it if the honest answer is "our theme is a bit slow and we want it to feel more premium." A well-built theme, a performance pass, and disciplined app usage will get you most of the way for a fraction of the cost — and keep the theme editor your team relies on. I've talked more than one client out of headless, and none regretted it — the same reasoning as when Shopify itself is the wrong choice.

A middle path

You don't have to go all-in. You can take a single high-value page — a product configurator, a landing experience — and build just that headlessly while the rest stays on the theme. It's a way to get the benefit where it matters without rebuilding the whole store. I go through that split in more detail in Storefront API vs Liquid.