'/%3e%3cpath%20id='Rectangle%202'%20d='M0%200H14.8684L8.14153%205.63973H4.55262L0%200Z'%20fill='var(--fill-0,%20white)'/%3e%3cpath%20id='Rectangle%203'%20d='M18.5238%200H22.0462L17.3702%205.63973H8.14153L18.5238%200Z'%20fill='var(--fill-0,%20%230A66FF)'/%3e%3c/g%3e%3c/svg%3e)
Starting a Shopify theme from scratch in 2025 is no longer the right call. The community has produced several strong starter frameworks that give you a structured project layout, a working build pipeline, and solved boilerplate before you write a single line of business logic. But not all frameworks are equal — they differ in philosophy, maintenance status, and the tradeoffs they make around build tooling complexity versus close-to-metal simplicity. This ranking evaluates four major options on developer experience, performance output, Shopify Theme Check support, and ecosystem momentum.
#1Dawn (Shopify's reference theme)
Dawn is the reference implementation for Online Store 2.0, maintained directly by Shopify's theme team. Every new OS 2.0 feature — section groups, JSON templates, app blocks, dynamic sources — lands in Dawn first. If you want to understand the canonical way to implement something in a Shopify theme, Dawn's source code is the authoritative answer. It ships with zero JavaScript framework dependencies: Web Components and vanilla JS only, which results in exceptional Lighthouse scores and a small JS bundle.
The tradeoffs are real, however. Dawn is opinionated about Web Components, and if your team prefers React or Vue for interactive sections, you're building on top of a paradigm that doesn't align with your stack. The theme ships with a custom CSS variables approach to design tokens, which works but requires learning its conventions before you can extend it confidently. There is also no build pipeline beyond Shopify CLI itself — no Webpack, no Vite, no PostCSS transforms out of the box. That simplicity is by design, but it means you'll add your own tooling if you want SCSS or TypeScript.
For agencies building production stores where long-term maintenance matters, Dawn is the safest bet. Breaking changes in the Shopify platform show up in Dawn's changelog before they affect your custom theme. Shopify won't deprecate the patterns their own reference theme relies on. That guarantee is worth more than any DX convenience another framework might offer.
#2Shopify Theme Lab
Shopify Theme Lab is a community-maintained starter that wires Dawn's Liquid foundation to a modern JS build pipeline. It ships with Vite, PostCSS, and optional Vue 3 integration — a stack that many frontend developers consider the sweet spot of developer ergonomics in 2025. Unlike raw Dawn, you get hot module replacement, TypeScript support, and PostCSS with Tailwind CSS (or any PostCSS plugin) out of the box. The result is a dramatically faster inner development loop, especially when building interactive sections.
The downside is abstraction debt. Every layer of tooling between your code and the deployed theme is a potential failure point. Shopify CLI and Vite's dev servers need to be kept in sync, and when Shopify changes the dev server protocol or asset pipeline, Theme Lab's glue code needs an update. The maintainer has historically kept pace, but there have been periods of lag after major Shopify CLI upgrades where the development workflow breaks temporarily.
Theme Lab is the right choice for teams that are already comfortable with Vite and want to bring that workflow to Shopify theme development. It's also a solid choice if Tailwind CSS is a non-negotiable for your design system — integrating Tailwind into raw Dawn is possible but more involved than it is in Theme Lab.
#3Slater (Archetype Themes)
Slater is a theme development environment originally built by The Taproom and later maintained by the broader community. It distinguishes itself with a clean project structure that maps well to how experienced theme developers think about code organisation: a clear separation between template-level Liquid, section Liquid, JavaScript modules, and SCSS. The CLI tooling wraps the Shopify Theme Kit workflow (and optionally Shopify CLI) with a layer of convention that reduces per-project setup time.
Slater's weakness in 2025 is its maintenance momentum. The original repository shows limited activity since Shopify deprecated Theme Kit in favour of Shopify CLI. Community forks have picked up some of the work, but there is no single authoritative maintained version. Before adopting Slater on a new project, check the fork you're considering: is it tracking Shopify CLI 3.x? Does it support OS 2.0 JSON templates natively? Some forks do; others are frozen at a 2021 feature set.
For developers who are comfortable with the Slater conventions and already have internal tooling built around it, continuing to use it on existing stores is fine. For greenfield projects, the lower ecosystem activity relative to Dawn and Theme Lab is a real risk to factor in.
#4Liquify
Liquify takes a different philosophical approach from the others: instead of scaffolding a theme, it focuses on improving the Liquid authoring experience at the editor level. The Liquify project includes a Language Server Protocol (LSP) implementation for Liquid, bringing features like autocomplete, inline documentation, and hover-based type information to VS Code and other LSP-compatible editors. For developers who write a lot of Liquid, this tooling is genuinely transformative — it's the closest thing Liquid development has to IntelliSense.
The Liquify framework also includes a build pipeline component with SYNCIFY — a file watcher and sync utility designed as a Theme Kit replacement with a richer configuration surface. It supports compilation of SCSS, TypeScript, and SVG sprites, and can inject snippets and sections using an import-style syntax that Dawn's raw asset pipeline doesn't support natively.
Liquify ranks fourth primarily because of ecosystem maturity. The tooling is ambitious and technically impressive, but the documentation has gaps and the project is largely driven by a single maintainer. If the LSP and build pipeline align closely with your workflow needs, evaluate the current state of the repository before committing. The VS Code extension alone is worth installing even if you don't adopt the full framework — the Liquid language intelligence it provides is a standalone productivity gain.
How to choose
Start with Dawn unless you have a specific reason not to. If your team already has a Vite-based workflow and wants Tailwind CSS, move to Theme Lab. If you're building heavily interactive UI and want a component framework, Theme Lab's Vue integration or adding Alpine.js to Dawn are both valid paths. Avoid Slater for new projects until ecosystem maintenance picks back up. Consider the Liquify LSP extension as a standalone productivity tool regardless of which theme framework you choose — it integrates with any Liquid codebase.
The single most important factor in a multi-year project is not which framework you start with — it's how closely the framework tracks Shopify's platform changes. An unmaintained theme framework that doesn't support the latest Shopify CLI authentication flow or app block protocol will create friction at the worst moments: client deadlines, emergency patches, and feature launches. Evaluate maintenance momentum before you commit.
Ranking criteria explained
This ranking weights four criteria equally. Developer experience covers how fast you can go from zero to a running dev server with hot reload — does the framework wire up Shopify CLI cleanly, and is the project structure intuitive? Performance output measures the Lighthouse scores you get on a default install — before any custom code — and how much bloat the framework itself adds. Theme Check support assesses whether the framework's conventions align with Shopify's official linter — frameworks that use deprecated filters, non-standard schema patterns, or custom Liquid tags that Theme Check flags will create friction when submitting to the Theme Store or onboarding new developers. Ecosystem momentum tracks GitHub activity, open issue response times, and how quickly the framework adapts to Shopify platform changes.
One criterion notably absent from this list is visual design quality. All four frameworks are development starting points, not finished visual themes — they ship minimal or no CSS and are intended to be styled by the development team. Choosing a framework for its visual design is a category error; choose it for its code structure and tooling, then build your design system on top.
A note on Alpine.js and React with any framework
None of the four frameworks prescribes Alpine.js, but it has become a popular add-on for teams who want a lightweight declarative JavaScript layer without the bundle size of React. Alpine's x-data directive and Liquid template rendering are a natural fit — Liquid renders HTML with Alpine attributes, and Alpine progressively enhances interactions. The combination works well with Dawn and Theme Lab alike.
React (and Next.js) enters the picture when teams want to go headless — decoupling the Shopify storefront from the Liquid rendering engine entirely and using the Storefront API. That is a legitimate architectural choice but puts you outside the scope of all four frameworks listed here. If your requirements push toward headless, the frameworks to evaluate are Hydrogen (Shopify's official React-based framework) and Next.js with the Shopify Storefront API — not any of the Liquid-based starters above.