Written by Steven Campbell
If you’ve been paying attention to what Shopify is doing with its theme architecture, you’ll have noticed Horizon. It launched as part of the Summer 2025 Edition and it’s the most significant change to how Shopify themes are built since Online Store 2.0 arrived in 2021.
It’s worth understanding what’s actually different, because the answer affects decisions about new builds, redesigns, and whether stores on older themes should be thinking about moving.
Horizon is a framework, not just a theme
This is the important distinction to make upfront.
Horizon isn’t a single theme you install. It’s a new theme framework that powers a collection of free themes. At launch Shopify released ten themes built on the Horizon framework, with more being added. The framework itself defines how blocks are structured, how the editor works, and how AI tools integrate with the design system.
The themes built on it all share the same underlying architecture. Different aesthetics, same foundation.
What’s actually 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 might sound like a technical detail, but it has a significant practical impact on what you can build without writing custom code.
With two levels, you can put blocks inside sections. With eight, you can build genuinely complex layouts visually inside the editor. A product grid with a text block, inside a promotional banner, inside a split section with a video. Complex enough to replace a lot of what previously required a page builder or custom development.
The editor experience has been rebuilt alongside this. Sections are organised by type rather than stacking in a single list. Blocks can be duplicated, reordered, and reused across pages. Right-click shortcuts speed up working with complex layouts. For anyone who’s spent time in the Shopify editor fighting with Dawn’s flat structure, it’s a meaningfully better experience.
Global sections are properly supported. Changes to a header, footer, or repeated design element update across the whole store rather than needing to be made page by page.
The design quality out of the box is also worth noting. Horizon themes use a more polished design system from the start. Spacing, typography, and component styling require less remedial work than most Online Store 2.0 themes did on a fresh install.
The AI integration
Shopify Magic worked with older themes, but it was limited because the block structure wasn’t designed with AI in mind. Horizon was.
Because blocks in Horizon are structured with clear parent-child relationships and semantic logic, when you prompt Shopify Magic to add or modify something, the result integrates with your existing design rather than dropping something generic in that needs significant rework. The AI understands the content hierarchy and respects the theme’s typography, spacing, and colour system.
This matters more than it might sound. Marketing teams being able to build new landing pages, update collection layouts, or add promotional content without waiting for a developer is a genuine operational improvement for most ecommerce brands.
The performance question
Horizon is fast. But it’s worth being precise about what that means.
The framework is web-native and server-rendered. Shopify’s principle with Horizon is that HTML is rendered server-side using Liquid, with client-side JavaScript used sparingly and only when it adds genuine value. No jQuery, no external carousel libraries, no polyfills. This approach produces clean, lightweight pages.
In benchmark tests on the default demo themes, mobile PageSpeed scores can vary depending on configuration. Horizon themes tend to be more visually rich out of the box, with more imagery and layout complexity. On a well-implemented Horizon build with proper image optimisation and careful use of custom sections, performance is excellent. The framework gives you what you need to build fast. Getting there requires implementation discipline.
What it means if you’re building now
For new Shopify builds, Horizon is the right starting point in almost every case. It’s where Shopify is investing its development, the editor experience is better, the design quality is higher, and the AI tools work properly with it.
For brands considering a redesign, the same logic applies. If you’re rebuilding your storefront, starting on Horizon rather than modernising an Online Store 2.0 theme gives you a more future-proof foundation and a better editor experience for your team going forward.
What it means if you’re already on an older theme
This is where the answer is more nuanced.
If your current theme is performing well, converting well, and your team can manage content without constant developer involvement, there’s no urgent reason to move. Shopify will continue to support Online Store 2.0 themes. Horizon isn’t replacing them overnight.
The triggers worth paying attention to are these. If your team is regularly frustrated by the limitations of the editor and relies on a developer for content changes that should be self-serve, Horizon is worth considering. If you’re planning a design refresh anyway, do it on Horizon rather than extending the life of an older theme framework. And if you’re using a page builder app to compensate for the layout limitations of your current theme, Horizon’s native block system probably makes that app redundant – and removes the performance penalty that comes with it. Our UX and UI design service covers Horizon builds alongside everything else we do on Shopify.
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.
