How to pick a WordPress starter theme as a developer: structure, tooling, block support and upkeep, so you build on a base you will not regret.
What a starter theme does, in plain words
A starter theme is a thin foundation you build a custom site on, instead of a finished design you install and tweak. It supplies the files WordPress needs to recognise a theme, a sensible template structure and a few conventions for assets, functions and markup. It leaves out the opinionated visuals. The aim is that the first hour of a project goes into your design, not into removing somebody else’s.
Underscores, the starter theme maintained by Automattic, states the idea clearly. Its site advises against using it as a parent theme and recommends modifying it into your own theme. That is the key difference from a regular theme: you take a copy and own it from then on.
WPMusk has not run hands-on tests of any starter named here. This guide teaches you how to choose and offers real projects as examples, not rankings. This page carries no score: it is guidance for choosing, not a measured result.
How it works under the hood
Classic starters
These use PHP templates, a template hierarchy and functions files. Underscores’ site lists lean HTML5 templates, template tags, helper functions, a small script that turns the menu into a toggled dropdown on small screens and starter CSS, all under GPLv2 or later. You write PHP and CSS directly, so there are few abstractions between you and the output.
Templating layers on top of PHP
Some starters add a template engine. Sage’s site lists Laravel Blade templates, Vite, Tailwind CSS and Composer, plus Acorn, which brings Laravel features into WordPress. It also says Sage generates theme.json from the Tailwind config so that colours and fonts appear in the block editor. Timber’s repository describes a library that uses the Twig template engine to separate HTML from PHP logic, installed with Composer for its 2.x line. These layers give you clean separation but add tooling to learn and maintain.
Block-first starters
A block theme keeps design in theme.json and templates made of blocks. The WordPress handbook describes theme.json as a foundational piece of block theming, used to configure colours, default typography and front-end styles. The Create Block Theme plugin’s repository says it can generate a blank theme, a child theme or a style variation from within the Editor, and save fonts, style changes and template changes into the theme. For many projects this removes most of the build step.
Child themes as a middle path
The handbook describes a child theme as an extension of a parent that lets you change things without editing the parent’s files. In block themes a child can override templates, parts and patterns by using files with the same name, and output is layered from WordPress defaults through the parent and the child to user customisations. It is a reasonable way to build on a good existing theme when you do not want to own the whole codebase.
Who needs one (and who does not)
You benefit from a starter theme if you build several sites, hand work to clients who should not break it or need strict control over markup, accessibility and performance. A starter also makes sense when you have a house style and want the same foundation on every project.
You probably do not need one for a single small site that a ready-made block theme can handle. Building from scratch means you maintain everything, including compatibility with future WordPress releases. If you have never built a theme, a good ready-made block theme plus a child theme may take you further with less risk. See the block theme roundup for starting points.
Also ask who will maintain the site later. A custom build with a niche toolchain is hard to hand over. A conventional structure is easier for the next developer to pick up.
Types and approaches
| Approach | Stack | Typical strength | Typical risk |
|---|---|---|---|
| Minimal classic starter | PHP templates, plain CSS and JS | Few abstractions, easy to read | You write more by hand; block editor support is yours to add |
| Classic with a modern toolchain | Blade or Twig, a bundler, a CSS framework | Clean separation, component workflow | Build tooling and a learning curve for handover |
| Block-first theme | theme.json, block templates, patterns | Design tokens shared with the editor, little or no build step | Some logic still needs PHP; less control over exact markup |
| Child theme of a good parent | Parent theme plus overrides | Small codebase, parent handles core updates | Dependent on the parent’s decisions |
| Hybrid | theme.json for tokens, PHP for logic | Uses each tool where it fits | Two mental models in one project |
What to look for
Our theme scoring weights are speed impact 30%, reliability 25%, support 20%, value 15% and ease of use 10%. For a starter the last two are about developer experience and the cost of ownership.
Front-end output (speed impact, 30%)
Create a blank page from the starter and look at the output. Count stylesheets, scripts and fonts. A good starter ships almost nothing you did not ask for. Check that the build produces only the assets a page uses; see the Core Web Vitals guide for the metrics.
Design tokens and the editor
Look at how colours, type and spacing are defined and whether the editor and the front end share them. Sage’s site says it generates theme.json from its Tailwind configuration. A block-first starter defines them directly in theme.json. Either way you want one source of truth rather than values repeated in PHP, CSS and editor styles.
Build tooling and toolchain weight (ease of use, 10%)
List what a new developer must install: PHP and Composer versions, Node, a bundler and framework configuration. Sage’s site, for instance, describes installation with Composer and npm. If a project must run on a client’s hosting or in a CI pipeline, check that the tools fit. Fewer tools means fewer things to break in two years.
Block editor support
Even classic starters need to cope with the block editor. Check editor styles, wide and full-width alignment, block patterns and whether the editor preview matches the front end. Sage’s site mentions live editor preview with Vite hot module replacement and editor styles.
Structure and conventions (reliability, 25%)
Read the file layout. It should follow WordPress conventions closely enough that a new developer can find things. Look at how functions are organised, how assets are enqueued and whether template parts and patterns are separated clearly.
Accessibility and standards
A good starter includes sensible heading structure, skip links, focus styles and semantic landmarks. Do not assume it; test with a keyboard. Underscores’ site describes semantic HTML5 templates. Whatever you choose, your own markup decisions will dominate.
Upkeep and maintainer activity (support, 20%)
You will track WordPress changes yourself, but an active upstream shows you what is changing. Check the repository for recent commits, open issues and release notes. Note that Timber’s repository says Timber 1 has reached end of life and the Timber plugin on WordPress.org is closed, which shows how quickly a toolchain can shift.
Licence and value (15%)
WordPress themes must be GPL-compatible. Underscores is GPLv2 or later and Timber is MIT-licensed, according to their pages. Confirm the licence of any starter before using it on client work and keep the licence text in your repository.
Real products to look at
These are examples, not rankings. Descriptions come from each project’s own site or repository and should be checked against the current version.
Underscores (_s). Per its site, a starter theme by Automattic with lean HTML5 templates, custom template tags, a small navigation script and starter CSS, licensed GPLv2 or later. It is meant to be modified into your own theme. It fits developers who want a plain, classic PHP base.
Sage by Roots. Per its site, a starter that uses Laravel Blade, Vite, Tailwind CSS and Composer, and generates theme.json from the Tailwind config. It fits developers who already like a Laravel-style workflow and accept the tooling.
Timber. Per its repository, a library for building themes with Twig templates, installed with Composer for version 2. It is a library rather than a complete theme, so you pair it with your own theme code. It fits developers who want strict separation between logic and markup.
Create Block Theme. Per its repository, a plugin that creates and exports block themes from the Editor, including blank themes, child themes and style variations. It fits developers who want to design visually and export clean theme files; read its warning that changes can permanently alter a site or theme.
A block theme plus child theme. Twenty Twenty-Five, Frost and Ollie are ready-made block themes whose listings describe patterns and style variations. Used as a parent, they give you a base without owning the whole codebase.
A comparison checklist for your shortlist
| Question | Candidate A | Candidate B | Candidate C |
|---|---|---|---|
| Output of a blank page: size and requests? | |||
| Tools required: PHP, Composer, Node, bundler? | |||
| Where are design tokens defined? | |||
| Editor preview matches the front end? | |||
| Template hierarchy and file layout clear? | |||
| Licence and attribution requirements? | |||
| Last upstream release and open issues? | |||
| Hand-over: can a new developer start in an hour? | |||
| Deployment: does it build on your pipeline? |
Setup and migration steps
Before you start
- Write a short brief: number of templates, custom post types, design tokens, plugins, who edits content.
- Decide who maintains the theme after launch, and how updates will be deployed.
- Choose where the code lives: a Git repository with a staging site; see the staging guide.
- If you use custom fields or post types, decide whether they live in the theme or in a plugin; the custom post types guide weighs the options.
During the build
- Copy the starter, rename it and replace all names, text domains and function prefixes. Do this first, so no generic names linger.
- Define design tokens: colours, type scale, spacing.
- Build templates from the outside in: header and footer, single, archive, then special pages.
- Add only the scripts and styles a template needs.
Before and after launch
- Check the page output against your footprint target and run an accessibility pass.
- Remove demo content, unused template files and debug code.
- Document how to build, deploy and update. A short README saves the next developer hours.
- Add the theme to your regular maintenance routine; see the maintenance checklist.
Common mistakes and red flags
- Using a starter as a parent theme when its authors say to copy and modify it.
- Leaving the starter’s original name, text domain and prefixes in place.
- Adopting a heavy toolchain for a five-page site.
- Repeating design values across theme.json, CSS and PHP.
- Building features into the theme that belong in a plugin, so they vanish when the theme changes.
- No documentation of the build, so only you can ship an update.
- Ignoring the editor, so authors see one thing and visitors another.
- A starter with no recent releases and no public issue tracker.
Cost and risk of switching later
Because you own the code, there is nothing to switch away from in the usual sense. The cost is upkeep. You track WordPress changes, such as new theme.json features and editor behaviour, and update your templates yourself. A starter does not update itself the way a regular theme does.
Moving between starters later means rebuilding templates and assets, though your content stays in WordPress. The risk grows with how much logic sits in the theme: custom post types, shortcodes and business rules should live in plugins so they survive a redesign.
Toolchain churn is the other cost. A framework, bundler or template engine that is popular now may change its major version in a year or two. Pin your versions and keep a lockfile. If you pick a framework-heavy starter, accept that you will need to follow its releases.
A one-afternoon evaluation plan on a staging copy
- Setup time (20 minutes). Install the starter from scratch on a clean machine or container, following only its documentation. Pass: you reach a working theme without guessing.
- Blank-page footprint (15 minutes). Load a blank page. Record transferred size, request count and fonts. Pass: nothing loads that you did not ask for.
- Token test (30 minutes). Change the primary colour and the base font size in one place. Pass: the change appears in both the editor and the front end.
- Template build (40 minutes). Build a header, footer, single post and archive. Pass: you can do so using the starter’s conventions without fighting them.
- Block test (20 minutes). Add a pattern, wide and full-width blocks and an image. Pass: they look right in both views.
- Accessibility pass (20 minutes). Tab through the page with the keyboard. Pass: focus is visible, a skip link exists, headings are in order.
- Deployment test (25 minutes). Build for production and deploy to staging using your usual process. Pass: the build runs cleanly and the output works without development tools.
- Hand-over test (15 minutes). Ask someone who has not seen the project to find where a colour is set. Pass: they find it within a few minutes.
How we will evaluate it
WPMusk has not run hands-on tests of any starter theme, and this page contains no test results. When a full review is published, it will say what was built, on what setup and with what findings.
The planned method follows the evaluation plan above, judged against the weights listed earlier. Related reading: the ACF guide for the data side of a custom build, and the CSS framework guide if you plan a utility-first approach.
Questions people ask
Should I use a starter theme or a child theme?
A child theme suits a few changes on a good parent. A starter suits a custom design where you want to own the codebase.
Do I need a build step?
Not always. Block-first themes often need none. Add one when you have a clear need, such as a utility CSS framework or JavaScript modules.
Can I use a starter with the Site Editor?
Block-first starters are designed for it. Classic starters can support the block editor but usually do not use full-site editing unless you add it.
Is Underscores still a good choice?
Its site describes a classic PHP starter with lean templates. Whether it fits depends on whether you want classic PHP templates or a block-first approach.
How do I keep custom features if I change themes?
Put functionality such as post types and shortcodes in a plugin, and keep presentation in the theme.
Do I have to credit the starter?
Check the licence in the repository. GPL-compatible licences usually require you to keep the licence notice, not display a credit on the site.
How much will it cost to maintain?
Mostly your time. Plan for regular WordPress compatibility checks and dependency updates, and write them into your maintenance agreement.
This is a buyer’s guide for a type of product. It is based on public documentation, not on hands-on tests, and it carries no score.
← All reviews