Choosing between a free theme, a paid one and a custom build is a more interesting decision this year than it was last. This summer Shopify shipped ten new free themes, all built on the newer Horizon architecture, and made that family the default for new stores, so the free tier now starts from a far higher standard than it used to. The gap between free and paid has narrowed; the gap between a template and a custom build has not moved at all.
We work with Shopify every day, so here is how we determine which is the best option for our clients.
Are Shopify's free themes good enough to sell with?
Yes, and it is not close to the old "free theme = starter theme" assumption. The new free lineup is design-literate in a way free templates rarely are: generous type, considered spacing, editorial layouts that would have been paid-theme territory three years ago. The Horizon architecture underneath adds nested blocks, so sections are more composable than the old model, and Shopify's AI section building can rough out layouts from a description. For a store with a focused catalogue and good photography, a free theme is a perfectly professional shop.
Two caveats belong in the same breath. First, the Horizon family is new, and the reported experience is mixed: the flagship Horizon theme sat at roughly 35% positive across its Theme Store reviews as of July, with merchants reporting theme updates overwriting customisations, mobile niggles and a steeper learning curve than Dawn. Second, Dawn itself has not gone anywhere: it still ships, still gets updates, and its years of stability are a fair reason to prefer it for a store that values boring reliability over new machinery. Free is the right tier for many stores; which free theme is now a real question, and "the newest one" is not automatically the answer.
When does a paid theme earn its price?
A paid theme is not a better-looking free theme; it is a bundle of built-in features. Theme Store prices are typically a few hundred dollars as a one-off, and the maths turns on the app stack you avoid: if a paid theme's built-in mega menu, lookbook, quick-buy or B2B pricing replaces two or three £15-a-month apps, it pays for itself inside a year while loading faster than the app pile would.
The mistake we see is buying paid for the aesthetics. Free themes now match paid themes on design taste; what you are buying is functionality, support and (with the established sellers) a long update track record. Read a paid theme's feature list against your actual app wishlist before you pay, and if the overlap is thin, keep the money.
When does custom design pay back?
When the brand is the reason people buy, and the template is the reason they hesitate.
Every theme, free or paid, is a set of decisions someone else made for the average store. That average fits most stores well, which is why templates are the right call for most stores. It stops fitting when your product needs its own way of being shown, when your store's look is drifting into sameness with competitors on the same theme, or when conversion work keeps hitting the template's ceiling: the layout you need does not exist as a section, the interaction you want fights the theme, and each workaround adds another app.
That boundary, template working until it does not, is one we have written about properly in our guide to premium ecommerce beyond the templates, and the crossover maths lives in our ecommerce cost guide. The short version: custom is an investment case, not a vanity case, and it is judged in conversion and brand equity, not in how the homepage looks in a screenshot.
The trap: heavily customising a free theme
The worst position in 2026 is the middle one nobody chooses on purpose. A free theme bent far out of shape with edits and app-injected code carries template constraints and bespoke fragility: you have the ceiling of someone else's decisions plus a maintenance burden nobody owns, and the Horizon family's update-overwrites-customisations complaints show exactly how that bill arrives. When we take over stores, this is the pattern we untangle most often, and it usually cost more in patches than honest custom work would have.
The rule we give clients: customise a theme's settings freely, and treat the first request for edited theme code as the fork in the road. Either the need is small enough to resist, or it is real enough to plan properly, at which point you are choosing between a paid theme that has the feature built in and a deliberate custom build. Drifting between tiers one code edit at a time is the only way to pay for all three.
The advice we give most often costs nothing
Here is the part that surprises people who expect a design studio to talk them upwards. The recommendation we make more than any other in these conversations is to keep the free theme and spend the budget on photography, because a beautiful theme showing mediocre photographs is a mediocre store, and the reverse is not true. Product photography does more for a template store's conversion than any theme purchase, and it travels with you when you do eventually go custom, which makes it the rare spend that is never wasted.
So before you shortlist anything, write down what the store must do that themes might not, look hard at your photography, and let those two answers pick the tier. If you want a second opinion on your specific store, send it over: telling you a free theme is enough takes ten minutes and costs you nothing, and when the answer is the other one, we design and build Shopify stores for exactly that case.
Get in touch - we're happy to chat.



