Shopify Hydrogen vs Liquid: how to choose in 2026
Liquid themes and headless Hydrogen storefronts both have a place. The decision is rarely about which is "better" — it is about which fits the brief. Here is how I make the call.
The Shopify world has spent the last few years arguing about Liquid: Shopify’s templating language — the tags and filters used to build the layout and logic of a Shopify storefront theme. versus Hydrogen: Shopify’s framework for building headless storefronts with React, letting developers build a fully custom front-end that talks to Shopify behind the scenes. as if one must win. In practice, the right answer depends entirely on what you are selling, who is editing the store, and how much custom logic lives between the catalog and the checkout.
When Liquid: Shopify’s templating language — the tags and filters used to build the layout and logic of a Shopify storefront theme. is the right call
A well-built custom Liquid: Shopify’s templating language — the tags and filters used to build the layout and logic of a Shopify storefront theme. theme still wins for the majority of stores. It is the path of least resistance: themes install through the Shopify admin, merchants can manage sections and blocks natively, and the whole thing sits inside Shopify's hosting and checkout. The editing experience is one merchants already understand.
If the brief is a distinctive-looking store with strong branding, a handful of custom sections, and standard commerce flows, Liquid: Shopify’s templating language — the tags and filters used to build the layout and logic of a Shopify storefront theme. gets you there faster and keeps the handoff simpler. The performance ceiling is real, but for most catalogs it is perfectly good with some disciplined theme work.
When Hydrogen: Shopify’s framework for building headless storefronts with React, letting developers build a fully custom front-end that talks to Shopify behind the scenes. earns its keep
Headless starts to make sense when the storefront is doing things Shopify's templating layer was never designed for. Rich product configurators, deep integration with a CMS: A content management system — software that lets you create, edit and organise the words, images and other content on a website without writing code. or PIM, content-heavy storytelling around products, or a single front-end that pulls in data from multiple back-ends — these are the cases where a Hydrogen: Shopify’s framework for building headless storefronts with React, letting developers build a fully custom front-end that talks to Shopify behind the scenes. build on the Storefront API: Shopify’s API for reading a store’s products, collections and cart data so a custom front-end can display and sell them. pays off.
The trade-off is cost and complexity. You are now maintaining a React application, a deployment pipeline, and a mapping layer to Shopify. Editors lose the drag-and-drop section editor they know. None of that is insurmountable, but it is real ongoing work, and it should be priced and staffed accordingly.
The question I actually ask
I steer the decision with one question: will the thing that makes this store special fit inside a Liquid: Shopify’s templating language — the tags and filters used to build the layout and logic of a Shopify storefront theme. theme, or does it need a real application? Branding, layout, and merchandising fit in a theme. Bespoke product logic, multi-source data, and ambitious interactivity usually need headless.
Get that question wrong and you either over-engineer a simple store or fight a templating layer past its limits. Get it right and the rest of the build follows naturally.
