Hydrogen vs Theme-Based Shopify: Which Approach Actually Makes Sense?
When someone says 'Shopify build', they might mean two very different things. Here's an honest comparison of theme-based stores versus Hydrogen, and how to decide which fits your situation.
When people talk about building a Shopify store, they're often describing one of two fundamentally different approaches without realising it.
Theme-based Shopify is what most people picture: you're working within Shopify's Online Store, using Liquid templates, theme sections, and the native storefront features. This is where the vast majority of Shopify merchants operate.
Hydrogen is Shopify's headless framework. You're building a custom React application that talks to Shopify's APIs, with Shopify handling products, checkout, and commerce operations behind the scenes. The storefront itself is decoupled from Shopify's theme system entirely.
Both approaches can produce fast, beautiful, high-converting stores. The right choice depends on what you're actually trying to achieve, what you're willing to spend, and how much flexibility you genuinely need, versus how much you think you might need someday.
The cost and time question
This is usually where the conversation starts, and it's where theme-based stores have a clear advantage for most projects.
With a theme, you're starting from a working structure. Product pages, collections, search, cart: the fundamental ecommerce patterns are already built. You configure more than you code. A well-chosen paid theme gets you most of the way there, and customisation happens incrementally.
Hydrogen means building a storefront application from scratch. Routing, UI architecture, data fetching, caching strategy: you're implementing (or at least configuring) all of it. You need front-end specialists, and you're re-building things that themes give you essentially for free.
That's not a criticism of Hydrogen. It's just the reality of what "headless" means. You're taking on more responsibility in exchange for more control.
Theme-based works well for: MVPs, most SMBs, brands that want to iterate quickly without engineering overhead. Time-to-launch is typically shorter for equivalent scope.
Hydrogen works well for: larger brands with unique UX requirements, complex merchandising logic, or a long-term product roadmap for the storefront itself. The upfront investment can pay off, but only if you actually need what it offers.
What you'll keep paying for
The initial build is one thing. Ongoing costs are where the real differences emerge.
Theme-based stores need maintenance: theme updates, occasional fixes, agency time for improvements. But the increments are usually small. The hidden cost to watch is app sprawl: lots of apps means lots of monthly fees and lots of scripts loading on your pages. Keep the stack lean and a theme-based store can be extremely cost-efficient long term.
Hydrogen stores require ongoing engineering. You're maintaining a web application: dependencies, refactors, new features, monitoring, performance tuning. Hosting isn't free (though it's usually reasonable). Every integration (search, reviews, subscriptions) is yours to maintain.
You own more of the surface area with Hydrogen. That's power, but it's also responsibility. It's rarely the cheapest option unless you're genuinely benefiting from the flexibility.
The app ecosystem
This is where theme-based stores have a structural advantage that's easy to underestimate.
Most Shopify apps assume a theme-based storefront. They install via theme blocks, Liquid snippets, and script injection. Click install, configure settings, done. The ecosystem is mature and the friction is low.
The downside is that apps can conflict with each other, add scripts that hurt performance, and leave you relying on third-party code you don't control. But for most use cases, the convenience outweighs the downsides.
With Hydrogen, apps that operate in the admin, order management, or checkout still work fine. Shopify is still Shopify on the backend. But front-end widgets (reviews, recommendations, loyalty popups, subscription UIs) often require API integrations and custom UI components instead of drop-in widgets. You get more control over how things work and perform, but "install and go" becomes "build and integrate."
For some teams, that control is exactly what they want. For others, it's overhead they don't need.
Performance and Core Web Vitals
This is where people expect a simple answer. "Hydrogen is faster" or "themes are slow." Neither is quite true.
A well-built theme with minimal apps, optimised images, and careful design can achieve excellent Core Web Vitals. The problem is that theme-based stores tend to accumulate cruft over time: trackers, popups, review widgets, A/B tools, marketing scripts. Death by a thousand cuts. Performance degrades not because themes are inherently slow, but because they make it easy to add things without considering the cost.
Hydrogen gives you more control. You decide what ships to the browser. You can build a genuinely lean storefront with tight control over rendering and caching. But if your Hydrogen build ships huge bundles, over-fetches data, or recreates "app widget bloat" in custom code, you'll end up with mediocre performance too.
The honest answer: Hydrogen raises the performance ceiling and gives you more levers to pull. But it doesn't guarantee good results. A modern theme with disciplined app usage can outperform a rushed headless build in real user metrics.
Where pre-made themes fit
Paid themes from the Shopify Theme Store or reputable third parties deserve specific mention, because they're often the sweet spot for theme-based builds.
You get layouts, UX patterns, and sections ready to go. Lower upfront cost than custom design. Battle-tested patterns that often reflect what actually converts. Merchant-friendly editing through Shopify's theme customiser.
The tradeoffs are real: you may look like other stores using the same theme, deeper customisation can get expensive or fragile, and some themes are feature-heavy in ways that hurt performance. Heavy modifications can also make future theme updates painful.
The pragmatic approach is to start with a strong paid theme, customise within its system first (settings and sections), add custom code only where it directly supports business goals, and keep apps lean. That gets you a polished store quickly without headless-level complexity.
Making the decision
Here's a simple framework:
Choose a theme-based store if you want to launch quickly, keep costs sensible, your UX needs are mostly "standard ecommerce plus strong branding," you rely on apps for key functionality, and your team wants to manage things through Shopify's editor.
Choose Hydrogen if your storefront UX is genuinely a competitive differentiator (not just aesthetics), you need complex custom flows that themes can't accommodate, you have engineering capacity to build and maintain a storefront application, and you want deep performance control at scale.
If you're unsure, there's a pragmatic middle path: launch on a quality paid theme with disciplined app usage, measure what actually limits you (conversion, UX, performance, experimentation speed), and move to Hydrogen only if those limitations are structural rather than cosmetic.
That approach keeps you balanced. You don't overbuild early, but you don't paint yourself into a corner either.
At Deploy, we build on both Magento and Shopify, including Hydrogen projects where they make sense. If you're weighing up which approach fits your next build, we're happy to talk it through.