Shopify Hydrogen entered the headless commerce conversation as “the official Shopify way to go headless,” which made a lot of teams assume it should be the default choice for any Shopify-backed headless build. In practice, we reach for plain Next.js more often than Hydrogen, and the reasons come down to real engineering trade-offs, not a preference for one framework over another.
What Hydrogen actually is
Hydrogen is Shopify’s own React-based framework, purpose-built for Shopify storefronts, with deep native integration into Shopify’s Storefront API, built-in cart and checkout handling patterns, and deployment optimized for Shopify’s Oxygen hosting. It’s genuinely well-designed for what it’s built for: getting a Shopify-backed storefront up with less custom integration glue than building the same thing from scratch.
What plain Next.js gives up, and what it gets back
Building headless on Next.js means writing your own integration layer against Shopify’s Storefront API (or any other commerce backend) rather than getting it out of the box. That’s real additional work upfront. What you get in exchange: genuine platform independence - the same architecture works whether you’re on Shopify, a different commerce platform, or a multi-vendor setup pulling from several sources - and access to the much larger Next.js ecosystem, hosting flexibility (Vercel, AWS, anywhere that runs Node), and a broader talent pool of developers who already know Next.js versus the smaller pool specifically experienced in Hydrogen.
The actual decision framework
- Are you committed to Shopify long-term, with no realistic scenario of multi-platform or platform migration? If yes, Hydrogen’s tighter integration and less custom glue code is a genuine time-to-market advantage worth taking.
- Do you need to pull data from more than just Shopify - a separate CMS, a different commerce backend for part of the catalog, a loyalty platform, anything beyond Shopify’s own data? Next.js’s platform-agnostic architecture handles this more naturally than a framework built around one specific backend’s data model.
- How much do you value hosting and deployment flexibility? Hydrogen is optimized for Shopify’s own Oxygen hosting. If you need specific hosting requirements - data residency, existing infrastructure investment, a particular cloud provider - plain Next.js gives you that flexibility natively.
- What’s your team’s existing expertise? A team that already knows Next.js ramps up faster building on it directly than learning Hydrogen’s specific patterns and constraints, even though Hydrogen is also React-based.
Where we’ve actually built each
For a single-brand D2C client fully committed to Shopify with no near-term plans to diversify platforms, Hydrogen got them to a fast, well-integrated storefront with less custom work than we’d have needed building the same integration ourselves in Next.js. For a multi-brand retailer running some catalog on Shopify and some through a separate system, plain Next.js with a custom integration layer was the clear right call - Hydrogen’s Shopify-native assumptions would have fought us at every point where the second data source came in.
The honest bottom line
Hydrogen isn’t slower or worse than Next.js - it’s more specialized. That specialization is a genuine advantage if your use case matches it exactly, and a real constraint if it doesn’t. We don’t default to either one; we ask about platform commitment, data sources, and hosting requirements before recommending, because those answers determine the right call more than any benchmark does.
We build both as part of our e-commerce development work. If you’re scoping a headless Shopify build and want an honest read on which fits your actual setup, get in touch.