Dawn vs Horizon
Both are free. The meaningful difference isn’t how they look — it’s how much your team can change without a developer.
This page covers what actually differs, where Dawn still holds up, and what the choice depends on.
What’s the actual difference between Dawn and Horizon?
Dawn is an Online Store 2.0 theme built on a section model with shallow block nesting. Horizon is a block-based theme with much deeper nesting, self-contained web components for core storefront elements, and AI-assisted block generation in the editor.
The consequence that matters is compositional. On Dawn, a layout that isn’t available as a section requires development. On Horizon, blocks nest several levels deep and can be reused and copied between templates, so a much wider range of layouts can be assembled in the editor rather than built in code.
| Dawn | Horizon | |
|---|---|---|
| Architecture | Online Store 2.0 sections | Nested blocks |
| Block nesting depth | Shallow | Substantially deeper |
| Core storefront elements | Standard theme markup | Self-contained web components |
| AI block generation | No | Yes, in the editor |
| Block reuse across templates | Limited | Global blocks, copy and paste |
| Design variation | Theme settings | Design presets |
| Release cadence | Maintenance | Active development |
| Cost | Free | Free |
Which is faster, Dawn or Horizon?
Neither theme is reliably faster than the other on a real store, because on any storefront that has been customized, page speed is driven far more by what’s been added to it than by the theme underneath.
Published theme-versus-theme benchmarks measure vanilla installations. A vanilla install has no apps, no third-party tags, no marketing scripts, no personalization tooling and no unoptimized imagery — which describes essentially no store in production.
On a mature store, the dominant factors are the number of apps loading scripts, the weight and format of images, how many third-party tags fire and when, and whether render-blocking resources have been managed. Those are the same on either theme.
The practical implication is that the theme is the wrong variable to optimize for speed. If page performance is a business priority, measure your own store, find where the weight actually sits, and address that. A rebuild is a genuine opportunity to shed accumulated weight — but that’s a property of rebuilding, not of Horizon.
Which has more sections and features?
Horizon ships with more sections than Dawn, and it adds new capability far more frequently.
The count matters less than the trajectory. Dawn’s section library is stable because Dawn is in maintenance. Horizon’s expands because Horizon is where Shopify is actively developing storefront capability.
Both themes now ship native colour and image swatches, which was a meaningful difference in earlier comparisons and no longer is. Feature-by-feature comparisons written before 2026 are unreliable on this point.
What can you do in the editor on each?
The editor is the substantive difference, and it’s where a merchandising team feels it.
You configure sections and reorder them. Anything outside what the section provides needs a developer.
Blocks nest inside blocks, can be copied between templates, and can be defined globally so a change propagates everywhere. AI-assisted block generation lets someone describe a block in plain language and receive working code.
On AI block generation specifically, the honest assessment is that it works well for simple blocks and is unreliable for complex ones. Treat it as a scaffold rather than a finished product. It’s a real capability, and it isn’t magic.
Is Dawn still supported?
Yes. Shopify has not announced any deprecation of Dawn, and Dawn continues to receive updates.
The distinction worth understanding is between support and development. Dawn receives the platform-level updates it needs to keep functioning — including support for standard storefront events and for app, agent and AI cart interactions. What Dawn no longer receives is significant new product capability.
Anyone telling you Dawn has a deadline is inventing one. The public release record shows an investment gap, not an end-of-life date.
Release history for both themes, updated quarterly →
Which apps work on each?
Most apps work on both, but apps integrated by editing theme code frequently break when moving from Dawn to Horizon.
The technical reason is that Horizon encapsulates elements like the variant picker, gallery and cart drawer as web components, and older integrations expected to reach into that markup directly. Apps using theme app extensions and app embeds are unaffected.
Can you switch between Dawn and Horizon?
You cannot switch between Dawn and Horizon in the sense of preserving your build, because there’s no automatic translation between the section model and the nested block model.
Shopify has not built a one-click migration, and this is a structural limitation rather than a missing feature. Switching themes means rebuilding your customizations on the new architecture — which is why moving a mature store is a project rather than a setting change.
Which should you choose for a new store?
For a new Shopify store, Horizon is the straightforward choice.
There’s no migration cost because there’s nothing to migrate, the editor gives a small team more independence from day one, and it’s where new capability will continue to land. The reasons to hesitate all relate to leaving an existing build behind, and a new store has none.
Which should you choose if you already have a store?
For an existing store, the answer depends on whether your current setup is limiting the business — and for a meaningful number of stores, it isn’t.
If your team can already make most changes without a developer, nothing is blocked, and you have no redesign planned. Dawn is supported and will continue to work.
If a redesign is already on the roadmap, your merchandising team routinely waits on developers, nobody in-house understands the theme any more, or you’re running multiple storefronts where every change gets made several times.
The deciding question isn’t which theme is better in the abstract. It’s whether your current architecture is costing you throughput you’d otherwise be using.
The full decision framework, including when the answer is no →
Frequently asked questions
What is the difference between Dawn and Horizon?
Dawn is an Online Store 2.0 theme built on sections. Horizon uses a nested block architecture, renders core storefront elements as self-contained web components, and supports AI-assisted block generation in the editor. The practical difference is how much a team can change without a developer.
Is Shopify Dawn being discontinued?
No. Shopify has announced no deprecation of Dawn, and Dawn continues to receive updates. What has changed is that new storefront capability is being developed on the newer block-based architecture.
Is Horizon faster than Dawn?
Not reliably. On any customized store, speed is driven mostly by apps, third-party scripts, tags and image weight rather than by the base theme. Theme benchmarks measure vanilla installations, which no production store resembles.
Can I switch from Dawn to Horizon?
Not directly. There is no automatic migration path between the two architectures, so switching means rebuilding your customizations on Horizon rather than transferring them.
Are Dawn and Horizon both free?
Yes. Both are free Shopify themes, available on any plan.
Should a new Shopify store use Dawn or Horizon?
Horizon, in almost every case. There’s no migration cost for a new store, and it’s where Shopify is developing new storefront capability.
Comparing themes is less useful than measuring your own store.
We’ll benchmark your storefront against three competitors on speed, accessibility and technical SEO. Free, two minutes, nothing to install.
Already decided? The Horizon migration is fixed price, four weeks, with four written guarantees.
