Shopify Theme Development: Custom Theme vs Existing Theme
Should you build a custom Shopify theme or adapt an existing one? How themes work, what a custom build involves, costs of ownership and how to decide.
Quick answer
Shopify theme development means building or substantially extending the code that renders your storefront. Choose an existing theme, customized, when its structure fits your catalog and your brand can be expressed through its sections and styles; this is faster, cheaper and easier to keep updated. Choose a custom theme when your content model, brand or shopping experience would mean fighting an existing theme's structure, and you're prepared to own the code long term. Either way, the theme should use Online Store 2.0 sections and blocks so your team can edit it without a developer.
How This Guide Differs From Theme Customization
This article is about the build decision: adapt an existing theme or develop a new one. If you already have a theme and want to know what can be changed, see Shopify theme customization. If your requirement involves business logic rather than presentation, see Shopify custom development.
How Shopify Themes Are Built
A theme is a set of files in fixed folders. The diagram above shows them alongside how a product page is composed (Shopify theme architecture).
| Part | What it does |
|---|---|
| Layout (theme.liquid) | The shell around every page: head, header and footer groups |
| JSON templates | Define which sections appear on a page type and in what order; editable in the theme editor |
| Sections | Reusable modules such as a hero, product information or featured collection |
| Blocks and theme blocks | Smaller units inside sections that merchants can add, remove and reorder |
| Section groups | Editable areas such as the header and footer |
| Snippets | Reusable pieces of Liquid rendered from other files |
| Assets | CSS, JavaScript, fonts and images |
| Config and locales | Theme settings and translations |
Worth noting
App blocks and app embeds let apps add features to sections without editing theme code, which is why a theme's support for them matters when you rely on apps.
The Options, Side by Side
| Option | Best for | Watch out for |
|---|---|---|
| Free Shopify theme | New stores, standard catalogs, speed | Limited sections; widely used look |
| Paid Theme Store theme | More sections and features without code | Extra features add weight if unused |
| Existing theme, customized | Most growing brands | Customizations must survive theme updates |
| Custom theme from a base | Distinct brand or content model | Build cost and long-term ownership |
| Headless front end | Needs a theme can't meet | A different project; see Hydrogen |
When an Existing Theme Is the Right Choice
Existing themes are tested across many stores, maintained by their developers and designed to be edited in the theme editor. For most catalogs, a well-chosen theme covers the product page, collection page, cart and search patterns you need, and your brand shows through typography, colour, photography and copy.
- The theme's templates match your catalog: variants, collections, content pages
- Its product page handles your options well, such as swatches or many sizes
- It performs well on mobile with your real images and apps
- It supports app blocks for the apps you rely on
- Its developer updates it regularly
- Your brand can be expressed through its settings and a few custom sections
When a Custom Theme Is Worth It
A custom theme is worth the investment when the store's value depends on an experience an existing theme can't deliver without extensive rewriting. Typical signals: a content model built on metaobjects such as collections of looks, recipes or designers; product pages that need unusual configuration or comparison; a brand system that existing section styles can't express; or performance goals that require removing features the theme ships with.
It's not worth it just to look different. Customizing an existing theme and investing in photography and copy often achieves more for less.
What a Custom Theme Build Involves
A custom theme is a software project. It needs discovery, design, development, QA and documentation, and it continues after launch.
| Stage | Output |
|---|---|
| Discovery | Page types, content model, metafields and metaobjects, app list |
| Design system | Tokens, typography, components and states |
| Template design | Mobile-first designs for every template and state |
| Section architecture | Which sections and blocks exist, their settings and limits |
| Development | Liquid, CSS and JS built on a base theme, under version control |
| QA | Devices, accessibility, performance, theme editor behavior, apps |
| Handover | Documentation for editors and developers |
Editor Experience Matters as Much as the Storefront
A custom theme that needs a developer for every content change becomes a bottleneck. Design the theme editor experience deliberately: clear section names, sensible defaults, settings limited to what the team should change, and guardrails that keep layouts on-brand. Test it with the people who will use it.
Deciding between a theme and a custom build?
ZSpace reviews your catalog, brand and team workflow and recommends the least custom approach that fits.
Performance and Accessibility Standards
Set measurable targets. Shopify's Theme Store requires a minimum average Lighthouse performance score of 60 across home, product and collection pages on desktop and mobile (theme store requirements); custom themes should aim well above that and be checked against real-user Core Web Vitals after launch. Build to WCAG from the start: semantic HTML, keyboard support for menus, drawers and variant pickers, visible focus and sufficient contrast. See Shopify Core Web Vitals and accessible UI/UX design.
Development Workflow
Use Shopify CLI to develop locally against a development store, keep the theme in Git with Shopify's GitHub integration, run Theme Check in review, and preview changes on an unpublished theme before publishing. Keep theme settings and editor-managed JSON files in mind when merging, because merchants change them in the admin.
Cost of Ownership
The build is only the first cost. A custom theme needs bug fixes, new sections as the business changes, updates when Shopify introduces new theme features, and regression testing when apps change. A purchased theme spreads that maintenance across its developer's customers, but your customizations still need care. Compare the full lifecycle, not the launch invoice. See Shopify development cost.
Worked Examples
These are illustrative scenarios, not client case studies, showing how the same decision plays out differently.
A skincare brand with 40 products. Its needs are a strong product page with ingredients, routines and reviews, a quiz and subscription options. A well-chosen existing theme handles the catalog; custom sections for ingredients and routines, metafields for skin type and concern, and app blocks for reviews and subscriptions cover the rest. Verdict: customize an existing theme.
A furniture retailer with configurable products. Sofas come in several sizes, dozens of fabrics and multiple leg finishes, with dimension diagrams, sample ordering and delivery-service options. The product page would be rewritten in any existing theme, and the collection pages need room-based browsing with dimension filters. Verdict: a custom theme built from a lean base, with metaobjects for fabrics and a custom configurator section.
A fashion label with editorial campaigns. It publishes lookbooks linking many products, needs fast collection pages with size-in-stock filters and wants a distinctive brand. Most templates fit an existing theme; lookbooks can be built as metaobject-driven sections. Verdict: customize, unless the brand system can't be expressed without rewriting core layouts.
How to Decide
- List the templates and content types your store needs
- Shortlist two or three themes that fit that list
- Prototype the hardest template, usually the product page, in the best candidate
- Count how much would need rewriting rather than adding
- If most changes are additions, customize the theme
- If the core templates would be rewritten, plan a custom theme
- If the requirement is logic or data, not presentation, look beyond the theme
Need a Shopify theme your team can actually run?
Talk to ZSpace about Shopify theme development and store design.
Common Theme Development Mistakes
- Building custom when an existing theme would have fitted
- Hard-coding content that should be sections, blocks or metafields
- No version control, so changes in the admin and in code collide
- Shipping every feature to every page, hurting speed
- Ignoring app block support
- No documentation for editors or future developers
Conclusion
Most stores should start from an existing theme and customize it with discipline. Build a custom theme when the store's experience genuinely depends on it, set clear performance, accessibility and editor-experience standards, and plan for owning the code. For the full build picture, see Shopify store development.
Common questions
Building or substantially modifying the code that renders a Shopify online store: Liquid templates, JSON templates, sections, blocks, snippets, CSS and JavaScript. It ranges from building a theme from scratch to extending an existing one.