Dawn or Horizon?
Start from the job.

01 · Common ground

Most of it is the same.

Both are built and maintained by Shopify, both are free, and both are Online Store 2.0 themes: sections and blocks on every template, app blocks, metafield-driven content, JSON templates. Anything a developer can build for one can be built for the other, because the architecture underneath is identical.

That is why this is not a quality comparison. Neither is the fast one or the good one. They are two starting points on the same platform.

02 · The difference

How much is handed to you.

Dawn is deliberately minimal. It gives you clean structure and very little opinion, which is exactly why it is the most common base for customisation: there is less to unpick before your own design fits. Everything we added to Poppy Lissiman, Haoma and Bend in the Barrow sits on that clean base.

Horizon ships with more merchandising built in and a richer set of editor-level controls, so more of the storefront can be arranged without code. If your team wants to compose pages themselves and your requirements sit inside what it offers, that is genuine time saved. Umi & Umi runs on a customised Horizon across four languages.

The trade is the usual one. More built in means more to configure, more to switch off, and more surface area between your customisations and future theme updates.

03 · New build

Which base for a new store.

Choose Horizon when you want the store composable by non-developers, your merchandising needs are close to what it already does, and you would rather spend the budget on content than on layout.

Choose Dawn when a designer is bringing a specific visual direction, when the store needs purpose-made sections anyway, or when you want the lightest possible base to build on. If a developer is going to write custom sections regardless, the minimal base wins: less inherited opinion to fight.

04 · Migration

Should a Dawn store move to Horizon?

Usually not, and not for the reason people assume. Dawn is not deprecated and is still maintained. Moving means rebuilding your homepage and templates, re-doing theme settings, and re-attaching app blocks, in exchange for editor conveniences you may not need.

Move when you have a real reason: your team is blocked from making changes without a developer, and Horizon's controls unblock them; or your Dawn theme has been customised so far past the original that a fresh base is cheaper than continuing. That second one is a rebuild decision, and it deserves its own scoring rather than a theme-name comparison.

05 · Perspective

The base is not the outcome.

Nobody has ever bought from a store because of which default theme it started from. What visitors notice is whether the product page answers their question, whether it is fast on a phone, and whether they trust the checkout.

Both themes can deliver all three, and both can fail at all three. The base decides how much scaffolding you inherit. Everything after that is your work.

Quick check

Before you commit.

• You know whether non-developers need to compose pages.
• You listed the sections your store needs, then checked both themes against the list.
• You compared both on a phone with your real images.
• If migrating, the reason is a capability gap, not the theme's age.
• You have a plan for theme updates after customisation.
• The decision is written down with a reason, not a preference.

Pick the base that fights you least.

Dawn if you are bringing your own design and a developer. Horizon if you want your team composing pages without one. Either way the store is judged on the product page, not the starting point.

Questions

Questions people ask.