Shopify Hydrogen vs Liquid Themes: When Headless Is Worth It
Headless Shopify with Hydrogen promises speed and flexibility, but a good Liquid theme often delivers the same for far less. Here is how to decide which your store needs.
Every few months a Shopify merchant asks me whether they should "go headless". Usually someone has told them it will make the store faster, more flexible and more modern. Sometimes that is true. More often, a well-built Liquid theme would get them the same result for a fraction of the cost and none of the extra maintenance. Here is how I think about the decision.
The two options, briefly
Liquid themes (Online Store 2.0)
This is the standard way Shopify stores are built. Your theme is written in Liquid, Shopify's templating language, and rendered on Shopify's servers. Online Store 2.0 added JSON templates, sections on every page and app blocks, so merchants can rearrange pages in the theme editor and apps can plug in without anyone editing code. Hosting, CDN, checkout and the editor all come as part of the platform.
Hydrogen (headless)
Hydrogen is Shopify's React-based framework for building a custom storefront. Instead of a theme, you build a separate web application that pulls products, collections and carts from Shopify through the Storefront API. You can deploy it to Oxygen, Shopify's hosting for Hydrogen storefronts, which runs your app on a global edge network. Shopify still handles products, orders, payments and checkout; you own everything the customer sees before checkout.
That last sentence is the whole trade-off. Headless means you own the storefront: its flexibility and its upkeep.
Cost
A Liquid theme build is a well-understood project. You can start from a solid theme and customise it, or build a bespoke theme on Shopify's conventions. Either way, the ongoing cost is modest: occasional theme updates and new sections as marketing asks for them.
A Hydrogen build is a software project. You are paying for a custom React application, a content model, integrations with every service that would otherwise have been an app, and someone to maintain it all after launch. Oxygen is included with most paid Shopify plans, so hosting is not the expensive part. The development and upkeep are. I break down where the money goes on custom builds in the true cost of a custom website, and the same logic applies here with bigger numbers.
Speed
This is where the headless pitch is most often oversold. A Hydrogen storefront can be very fast, because you control every byte and pages render close to the visitor, the idea I cover in edge rendering explained. But a Liquid theme can be very fast too. Shopify's servers and CDN are quick; slow Liquid stores are slow because of apps, scripts and bloated themes, not because of Liquid.
If your current store is slow, fix that first. The steps in how to speed up a slow Shopify store will usually get you most of the way for a small slice of a headless budget. And a headless build loaded with the same tracking pixels and third-party widgets will end up just as slow.
Flexibility
Headless genuinely wins here. With Hydrogen you can build things a theme struggles with: a product configurator with complex logic, a storefront that merges content from a headless CMS with product data, several brands or regions sharing one codebase, or a site where the shop is only one part of a bigger content platform. If you have been told "the theme cannot do that" more than once, headless is where that stops being true.
That said, Online Store 2.0 covers far more than most people assume. Metafields and metaobjects let you model structured content, and well-designed custom sections give marketers real control over layouts without a developer. Check what a good theme can do before deciding you have outgrown it.
App compatibility
This is the cost people discover too late. Many Shopify apps work by adding blocks or scripts to your theme. In a headless storefront there is no theme, so those apps either do not work, or only work through an API you have to integrate yourself. Reviews, loyalty, subscriptions, search, wishlists: each one becomes a small integration project.
Before committing, list every app you rely on and check whether it supports custom storefronts. If most do not, add the integration work to your budget, or accept that some will need replacing.
Who maintains it
With a Liquid theme, a merchant can change a lot on their own in the theme editor, and any competent Shopify developer can pick up the codebase. With Hydrogen, you need React developers who understand the Storefront API and the framework's conventions, and the framework moves quickly. Dependencies need updating, API versions need keeping current, and someone has to own deployments. If there is no in-house team or retained developer, that responsibility does not disappear. It just goes unmet until something breaks.
Side by side
| Liquid theme (Online Store 2.0) | Hydrogen (headless) | |
|---|---|---|
| Build cost | Lower; a standard theme project | Higher; a custom React application |
| Ongoing maintenance | Light; occasional updates | Continuous; dependencies, API versions, deployments |
| Speed | Fast when apps and theme are kept lean | Fast when built well; not automatic |
| Flexibility | High, within Shopify's theme model | Almost unlimited |
| App compatibility | Most apps work out of the box | Theme-based apps need custom integration or replacing |
| Merchant editing | Built-in theme editor | Needs a CMS or custom tooling |
| Hosting | Included and managed by Shopify | Oxygen, or your own hosting |
| Who can maintain it | Any good Shopify developer | React developers who know Hydrogen |
My recommendation
Small and growing stores
Use a Liquid theme. Put the money you would have spent on headless into photography, copy and a clean app stack. You will get more from better product pages than from a new architecture.
Established brands with a strong content side
Still Liquid, for most. Consider headless only if content and commerce genuinely need to merge in ways a theme and metaobjects cannot handle, and you have budget for development after launch, not just before it.
Larger businesses with a development team
This is where Hydrogen makes sense: multiple markets or brands, custom experiences that are core to how you sell, and people who can own the code. If that is you, headless can be a real advantage. If you are weighing platforms more broadly, Shopify vs WooCommerce and headless vs traditional CMS cover the wider picture.
The question to ask
Do not ask "is headless better?" Ask "what can we not do today, and is a custom storefront the cheapest way to do it?" If you cannot name the specific thing, you do not need headless yet.
Weighing up a rebuild? Tell me what your store needs to do and I will give you a straight answer on whether Liquid or Hydrogen fits, including when the answer is neither.
