Both build headless Shopify storefronts. Both are React. Both are legitimate. The comparisons you find online tend to be written by people with a side to sell, so here is the version we would give a client on a call — including where Hydrogen is the better answer, which it sometimes is.
We build in Next.js. That is a bias worth stating up front so you can discount for it.
What each one actually is
Hydrogen is Shopify's own React framework for storefronts, built on Remix. It ships with commerce primitives — cart, product, analytics — already wired to Shopify, and it is designed to deploy to Oxygen, Shopify's hosting, which is included with a Shopify plan.
Next.js is a general-purpose React framework. It knows nothing about commerce until you connect it to the Storefront API, and it hosts anywhere.
Where Hydrogen genuinely wins
Being honest about this is the only way the rest of the post is worth reading.
It starts faster. Commerce primitives are already built. Cart state, product queries, analytics hooks — you are not writing them.
Hosting is solved and included. Oxygen deploys from Shopify, is priced into your plan, and you do not think about infrastructure. For a team without a platform engineer, that is real.
It stays close to Shopify. When Shopify ships something new, Hydrogen gets it first and idiomatically.
It is a genuinely good fit for a storefront that is essentially a well-executed commerce experience: browse, product, cart, checkout, some content. If that describes you, Hydrogen is a sound choice and a cheaper start.
Where Next.js wins
Your storefront is more than commerce. Editorial content, tools, calculators, quizzes, account areas, a booking flow, a community section. Next.js is a general application framework, so none of that fights the grain.
You need a real content layer. This is the one that decides most of our projects. Modelling content properly in a CMS — so marketing can build pages without a deploy — is work either way, but Next.js has no opinion competing with yours about how content and commerce combine.
Hosting is a decision, not a given. Oxygen being included is an advantage until you need something it does not do: a specific region, a particular edge configuration, co-location with other services you run.
The talent pool is much larger. If the relationship with your agency ends, hiring someone who knows Next.js is straightforward. Hiring Hydrogen experience is a narrower search — and that matters more than it sounds when you are two years in.
The question that decides it more often than any technical argument: is your storefront only a store? If yes, Hydrogen is a reasonable and cheaper answer. If it is a store plus a content property plus a couple of tools, Next.js will hurt less by year two.
Talk it through
Want a straight answer for your storefront?
Describe what your front end needs to do beyond browse-and-buy. We will tell you which stack fits — and we do recommend Hydrogen when it is the better call.
Ask us which fitsA real read within one business day — not a sales call.
The comparison that matters
| Next.js + Storefront API | Hydrogen + Oxygen | |
|---|---|---|
| Time to first working store | Slower — primitives are yours to build | Faster — commerce is pre-wired |
| Hosting | Your choice, your cost | Oxygen, included in your plan |
| Non-commerce features | No friction | Possible, against the grain |
| Content modelling | Fully yours to design | Fully yours, with Shopify conventions nearby |
| New Shopify features | You integrate them | Arrive first and idiomatically |
| Hiring later | Large talent pool | Much smaller pool |
| Lock-in | Low — the front end is portable | Higher — framework and hosting are Shopify |
The thing neither framework fixes
Most disappointing headless builds are not disappointing because of the framework. They are disappointing because the content layer was an afterthought and marketing now needs a developer to publish a landing page.
That failure happens identically in both. It is an architecture decision made in week one, not a property of Hydrogen or Next.js — which is why we treat the data and content model as the first deliverable on any headless project, before a single component is styled.
If an agency's answer to "which framework?" arrives before they have asked what your storefront needs to do, the framework is not the thing you should be worried about.
How we actually choose
Three questions, in this order:
- Is the storefront only commerce? If genuinely yes, Hydrogen is on the table and we will say so.
- How much does marketing need to ship without engineering? The more the answer is "a lot", the more the content architecture dominates — and the more we want a framework with no competing opinions.
- What else lives on this domain? Tools, editorial, account areas and portals push firmly toward Next.js.
We build in Next.js because most of the brands that reach us have already outgrown "only commerce". That is a statement about who calls us, not a claim that Hydrogen is bad.
If you are weighing the two, tell us what your front end has to do and we will give you a straight answer — including when the straight answer is Hydrogen, or that you should not be going headless at all.
About the author
Manpreet Singh
Manpreet Singh is the founder of Proscube, an ecommerce growth studio. He leads the studio's Shopify and Shopify Plus engineering, headless builds, CRO, and its work on AI engine optimization, and writes its guidance on how to grow a DTC brand without wasting money. He works directly with founders — no account-manager layers between you and the people doing the work — and would rather tell a client not to build something than sell them work they don't need.
More about Manpreet
