What Is a WordPress Block Theme?
A WordPress block theme is a theme built entirely from blocks, storing its templates as HTML block markup and enabling Full Site Editing, so you can edit headers, footers, and layouts visually in the Site Editor without PHP. It contrasts with a classic theme, which relies on PHP template files and the Customizer. Block themes use a theme.json file to define global colors, fonts, and spacing, giving consistent, editable styling. They offer more no-code control over structure and design, at the cost of a newer system and a learning curve.
- Definition
- A theme using block-based HTML templates that enables Full Site Editing (WordPress Developer docs)
- Key file
- A theme.json file defines global styles, colors, fonts, and layout settings (WordPress Developer docs)
- Versus classic
- Classic themes use PHP templates and the Customizer; block themes use the Site Editor
- Templates as HTML
- Templates live as block markup in a templates folder, editable visually
- Enables
- Full Site Editing of headers, footers, templates, and global styles without code
What a block theme is #
A block theme is a WordPress theme built from the ground up around blocks, the same building units you use in the editor, extended to the entire site. Instead of the PHP template files that define a classic theme, a block theme stores its templates as HTML block markup and enables Full Site Editing, letting you edit headers, footers, page layouts, and global styles visually in the Site Editor without writing code. This is a fundamentally different architecture from the classic themes that dominated WordPress for most of its history. A block theme also relies on a configuration file called theme.json to define site-wide colors, fonts, and spacing in a structured way. For site owners, the headline benefit is control: far more of a site's structure and design becomes editable through a visual interface rather than locked in code. Choosing a block theme shapes how a site is built and maintained, and it is an increasingly common decision in modern /services/wordpress-development as WordPress steers toward this model.
Block themes versus classic themes #
The clearest way to understand a block theme is to compare it with a classic theme. A classic theme is made of PHP files, header.php, footer.php, single.php, and so on, and structural changes require editing that code or using the limited Customizer. A block theme replaces those PHP templates with block-based HTML templates you edit in the visual Site Editor, and it swaps the Customizer for global styles driven by theme.json. In practice, this means a block theme lets an owner change the header, rework a template, or adjust sitewide colors without a developer, while a classic theme keeps most of that in code. Classic themes remain widely used and are perfectly valid in 2026, especially for sites with heavy custom PHP functionality, but WordPress's development direction favors block themes. Deciding between them is a real architectural choice during any /services/website-redesign, balancing the block theme's no-code flexibility against the classic theme's maturity and the tighter developer control it provides over how the site behaves.
The role of theme.json #
At the heart of a block theme sits theme.json, a configuration file that defines the theme's global settings and styles in a structured, predictable way. It declares the color palette, font sizes, spacing scale, and default styles that blocks inherit, creating a single source of truth for the site's design. This is a significant improvement over the scattered styling of older themes, because it brings a design-system approach to WordPress: set your brand colors and typography once, and they apply consistently everywhere, editable later through Global Styles. The example below shows a small theme.json. As an owner you rarely edit it by hand, since the Site Editor exposes most settings visually, but knowing it exists explains why block themes feel more consistent and controllable. Developers configure theme.json carefully during setup to give clients a clean, on-brand foundation. This structured approach to global styling is one reason block themes pair so well with disciplined /services/branding-design, turning brand guidelines into enforceable, site-wide defaults rather than loose suggestions.
{
"version": 3,
"settings": {
"layout": { "contentSize": "720px", "wideSize": "1100px" },
"color": {
"palette": [
{ "slug": "brand", "color": "#1a3d5c", "name": "Brand" }
]
}
},
"templateParts": [
{ "name": "header", "area": "header" },
{ "name": "footer", "area": "footer" }
]
}What Full Site Editing requires #
Full Site Editing and block themes go hand in hand: FSE is the capability, and a block theme is the requirement that unlocks it. You cannot use the Site Editor to visually edit templates, headers, and footers unless a block theme is active, because only block themes store their templates as editable block markup. Under a classic theme, the Appearance menu shows the Customizer; under a block theme, it shows the Editor, which is the gateway to Full Site Editing. This dependency is important for anyone deciding how much self-service control they want. If the goal is to let a content team adjust structure and design without a developer, a block theme is the prerequisite. If that flexibility is not wanted or needed, a classic theme suffices. Recognizing that FSE is unavailable without a block theme clears up a common source of confusion for owners who expected visual template editing but were running a classic theme. It is a foundational consideration when planning a build and the ongoing /services/care-plans that follow.
Advantages of block themes #
Block themes bring several genuine advantages. The biggest is no-code control: owners and teams can edit headers, footers, templates, and global styles visually, reducing reliance on a developer for routine design changes and lowering ongoing costs. They tend to be lighter than sites loaded with heavy page-builder plugins, because they use native WordPress capabilities rather than a bolted-on system, which can help performance, a frequent theme in /services/speed-optimization work. The theme.json approach enforces design consistency through global styles, keeping a site coherent as it grows. Block themes are also aligned with WordPress's future direction, so building on them is a forward-looking choice less likely to feel outdated. For content-heavy or growing businesses that value independence and want to expand their site over time without constant developer involvement, these benefits are compelling. The combination of visual control, native performance, and design consistency makes block themes an attractive foundation for many modern small-business sites being planned or rebuilt today.
Tradeoffs and limitations #
Block themes are not automatically the right choice for every site. As a newer system, the tooling has evolved rapidly, so the Site Editor and block theme conventions have changed across WordPress versions, and documentation or tutorials can lag behind. There is a real learning curve for owners and developers used to classic PHP themes, and the visual freedom can produce inconsistent results without discipline. Some complex custom functionality is still easier to implement with traditional PHP development, so heavily bespoke sites may favor a classic theme or a hybrid approach. The ecosystem of mature block themes, while growing, is younger than the vast library of classic themes. And migrating an existing classic-theme site to a block theme is a substantial project, not a simple switch. These tradeoffs mean block themes reward sites that value self-service flexibility and are willing to invest in the learning, while some established sites with deep custom code may sensibly stay classic. Weighing this honestly is part of good /services/web-design planning rather than assuming newer is always better.
Migrating to a block theme #
Moving an existing site from a classic theme to a block theme is closer to a redesign than a routine update, and it should be planned accordingly. Your content, the posts and pages stored in the database, generally carries over, but the site's structure, its header, footer, templates, and styling, must be rebuilt in the block theme's Site Editor, because the old PHP templates do not translate directly. Custom functionality tied to the old theme may need to be reworked or moved into a plugin. This makes the switch a real project best handled with a staging site, careful testing, and attention to preserving URLs and SEO, exactly the disciplines of a professional /services/website-migrations or /services/website-redesign engagement. Rushing it risks broken layouts, lost customizations, or performance regressions. Done well, though, the payoff is a modern, self-editable site aligned with WordPress's direction. The key is treating the migration as the significant undertaking it is, rather than expecting to flip a theme switch and be finished.
Choosing between block and classic #
For a small business deciding on a foundation in 2026, the honest answer is that both block and classic themes are viable, and the right choice depends on priorities. Choose a block theme if you value editing your own site's structure and design without a developer, want a lighter build than heavy page builders provide, and prefer to align with WordPress's future direction, accepting a learning curve in return. Lean classic if your site depends on deep custom PHP functionality, you prefer a mature and stable ecosystem, or you simply do not need visual template editing. Many new builds now start as block themes, while plenty of established sites remain productively classic. There is no universal winner, only the better fit for how your team works and what your site must do. If you are planning a new site or a rebuild and are unsure which path suits you, a short review through /contact or a /free-website-audit can help you weigh the tradeoffs against your specific goals before committing.
FAQ
How do I know if I have a block theme?
Check the Appearance menu in your dashboard. If you see Editor, you have a block theme with Full Site Editing. If you see only Customize, you are running a classic theme. Block themes also store templates as HTML files in a templates folder and include a theme.json file at the theme's root.
Is a block theme better than a classic theme?
Neither is universally better. Block themes offer no-code control over structure and design, are often lighter, and align with WordPress's direction, but they are newer with a learning curve. Classic themes are mature and better for deep custom PHP functionality. The right choice depends on whether you value self-service flexibility or established, developer-controlled stability.
What is theme.json in a block theme?
It is a configuration file that defines the theme's global settings and styles, colors, fonts, spacing, and layout, in a structured way. It acts as a single source of truth for design, so blocks inherit consistent styling. You rarely edit it by hand, since the Site Editor's Global Styles panel exposes most settings visually.
Can I switch my existing site to a block theme?
Yes, but it is a substantial project, more like a redesign than a theme swap. Your content carries over, but the header, footer, templates, and styling must be rebuilt in the Site Editor, and custom functionality may need reworking. Use a staging site, test thoroughly, preserve URLs, and ideally get professional help to avoid breakage.
Do block themes work with page builders like Elementor?
Some page builders offer compatibility, but block themes are designed to reduce the need for a separate builder by providing native visual editing through Full Site Editing. Mixing a heavy builder with a block theme can create overlap and add weight. If you adopt a block theme, it is usually best to lean on its native block editing.
Are block themes faster than classic themes?
They can be, because they use native WordPress capabilities rather than heavy page-builder plugins that add code and slow pages. Performance still depends on images, hosting, and how the site is built, so a block theme is not automatically fast. But its native approach avoids a common source of bloat, which helps speed optimization efforts.
How Local Web Advisor checks this for you
Is your own website getting web dev right?
Our free AI audit scans your site and tells you — in plain English — exactly what to fix for web dev and seven other areas, with the business impact and the fix for each. No login needed to start.
Run my free website audit →Was this helpful?