Written by Steven Campbell
Horizon arrived as part of the Summer 2025 Edition, and it’s the biggest change to how Shopify themes are built since Online Store 2.0 landed in 2021.
Worth understanding what’s actually different, because it changes how I’d approach a new build, a redesign, and whether a store on an older theme should be thinking about moving at all.
Horizon is a framework, not a theme
That distinction matters more than it sounds.
Horizon isn’t something you install. It’s a theme framework that powers a collection of free themes, ten of them at launch with more since. The framework defines how blocks are structured, how the editor behaves, and how the AI tools plug into the design system.
The themes built on it share the same foundation. Different aesthetics, same bones. Once you’ve worked in one you can find your way around all of them, which isn’t something I could say about the old marketplace.
What’s different from Online Store 2.0
The headline change is block nesting. Online Store 2.0 themes like Dawn support two levels of nested blocks. Horizon supports eight.
That sounds like a technical footnote until you try to build something. With two levels you can put blocks inside sections. With eight you can build genuinely complex layouts visually, in the editor, without touching code. A product grid with a text block, inside a promotional banner, inside a split section with a video behind it. Enough to replace a lot of what previously meant a page builder or a developer.
The editor has been rebuilt around it. Sections are grouped by type instead of stacking up in one long list. Blocks can be duplicated, reordered and reused across pages. There are right-click shortcuts, which sounds trivial until you’ve spent a morning in Dawn’s flat structure trying to move one thing three places up. I have, more than once, and I don’t miss it.
Global sections work properly too. Change a header, a footer or a repeated element once and it updates everywhere, rather than page by page.
The out-of-the-box design quality is better as well. Spacing, typography and component styling need noticeably less remedial work on a fresh install than most Online Store 2.0 themes did.
The AI integration
Shopify Magic worked with older themes, but it was limited, because the block structure was never designed with AI in mind. Horizon was.
Blocks in Horizon have clear parent-child relationships and semantic logic. So when you prompt Magic to add or change something, what comes back sits inside your existing design instead of dropping in something generic you then have to rebuild. It respects the theme’s typography, spacing and colour system because it can actually see the hierarchy.
That matters more than it sounds. A marketing team that can build a landing page, change a collection layout or add a promotion without waiting for a developer is a real operational shift for most brands. Most of the requests I see come through as urgent development tickets are exactly that sort of job.
The performance question
Horizon is fast. It’s worth being precise about what that means.
The framework is web-native and server-rendered. Shopify’s principle is that the HTML renders server-side in Liquid, with client-side JavaScript used sparingly and only where it earns its place. No jQuery, no external carousel libraries, no polyfills. That produces clean, light pages.
In benchmarks on the default demo themes, mobile PageSpeed scores vary depending on configuration. Horizon themes tend to be more visually rich out of the box, with more imagery and more layout complexity, and that shows up in the numbers. On a well-implemented build with proper image optimisation and disciplined use of custom sections, performance is excellent. The framework gives you what you need to be fast. Getting there is still down to how you build it.
If you’re building now
For a new Shopify build, Horizon is the right starting point in almost every case. It’s where Shopify is putting its development, the editor is better, the design quality is higher, and the AI tools actually work with it.
Same answer for a redesign. If you’re rebuilding the storefront anyway, starting on Horizon rather than modernising an Online Store 2.0 theme gives you a better foundation and a much better day-to-day experience for the people who have to use the editor.
If you’re already on an older theme
More nuanced here.
If your theme performs well, converts well, and your team can handle content without pulling a developer in every week, there’s no urgent reason to move. Shopify will keep supporting Online Store 2.0 themes. Horizon isn’t replacing them overnight.
The triggers worth watching are these. If your team is regularly stuck on editor limitations and relying on a developer for changes that should be self-serve, Horizon is worth looking at. If a design refresh is coming anyway, do it on Horizon rather than extending the life of the old framework. And if you’re paying for a page builder app to work around your theme’s layout limits, Horizon’s native block system probably makes that app redundant, which takes its performance cost off your pages too. That’s usually the clearest bit of arithmetic in the whole decision.
Our UX and UI design service covers Horizon builds alongside everything else we do on Shopify. And if the app question is the one you’re stuck on, this is what those apps are costing you.
Have you had a look at Horizon yet?
One thing to be aware of
Horizon themes cannot be submitted to the Shopify Theme Store. If you’re an agency or developer building themes for third-party sale, Horizon isn’t the starting point for that work. For brands building their own store this isn’t relevant, but it’s worth knowing.
