What is a block theme? A plain-English 2026 guide

01What a block theme actually is

A block theme is a WordPress theme whose templates are assembled from blocks — the same building blocks you already use to write a post — rather than from hand-written PHP. Instead of a header.php full of code, the header is a template made of a Site Logo block, a Navigation block, and so on, saved as HTML.

The practical consequence is that you edit the entire site in one place: the Site Editor, reached from Appearance → Editor. Headers, footers, the layout of a single post, the archive page — all of it is editable visually, in the browser, the same way you'd edit a page.

Underneath, two things define a block theme. First, its templates are block markup (HTML with block comments) instead of PHP. Second, it ships a theme.json file that declares the design system — colors, fonts, spacing, layout widths — in one structured place that both the editor and the front end read from.

That second file is the quiet star. theme.json replaces a sprawl of CSS and PHP settings with a single, readable config. It is also part of why block themes feel more standardized: they describe their design in a shared format rather than each author inventing their own options panel.

02Why the block theme shift happened

Block themes did not appear for novelty. They are the theme half of a much larger project — moving WordPress from a system you customize through code and scattered settings to one you shape visually, with a consistent set of tools across content and layout.

The problems they were built to solve

• Customization meant code. Changing a header or a post layout in a classic theme usually meant editing PHP or copying templates into a child theme. Block themes let you do the same things visually.
• Design settings were everywhere. Colors in the Customizer, spacing in custom CSS, fonts in a theme options panel — no single source of truth. theme.json pulls those into one file.
• The editor lied about the result. In classic themes, the post editor rarely matched the front end. Block themes aim for closer parity between what you edit and what visitors see.

What that buys you

• One mental model. The blocks you use to write a post are the same blocks that build the header. Learn one, and you can touch the whole site.
• Edits that survive updates. Site Editor changes save as user customizations in the database, separate from the theme's own files, so a theme update is less likely to clobber them.
• A standard others can read. Because the design lives in theme.json and block markup, your work is described in a shared format rather than one author's bespoke PHP.

None of this forces a rebuild of working sites. Classic themes still run. But for new builds, the block approach is where the platform's tooling and documentation are now pointed.

03How a block theme is put together

You rarely open these files by hand, but knowing the parts demystifies the whole thing. A block theme is a folder with a predictable structure, and each piece has one clear job.

Templates and template parts

Templates are the full-page layouts — the home page, a single post, a search results page — and they live in a templates folder as HTML files. Reusable chunks like the header and footer are template parts, kept in a parts folder so several templates can share one header instead of repeating it.

theme.json — the design system in one file

This file declares the palette, typography, spacing scale, and layout widths the theme offers, plus which controls show up in the editor. When you tweak a global style in the Styles panel, you are effectively layering your own values on top of what theme.json defines — without touching the file itself.

Patterns and blocks

Patterns are pre-arranged groups of blocks — a hero section, a pricing row — you can drop in and edit. They are the block-theme answer to the old demo-import-everything approach: composable pieces rather than one monolithic template you have to dismantle.

Put together, a block theme is mostly declarative: it describes layouts and a design system, and the editor renders them. That is a real departure from a classic theme, where behaviour is spread across PHP functions you cannot see without opening the code.

04How you actually use one day to day

The reason block themes matter to a site owner is simple: you can change things that used to require a developer. Here is what that looks like in practice once a block theme is active.

• Editing the header or footer. Open the Site Editor, click into the header template part, and edit it like a block layout — swap the logo, rearrange the menu, change the background. No header.php.
• Changing global styles. The Styles panel (the half-circle icon in the Site Editor) sets site-wide colors, fonts, and spacing in one place. Change a heading font once and it updates everywhere.
• Reworking a post layout. Edit the Single template to change how every post displays — where the title sits, whether the author shows, the featured image placement — without touching individual posts.
• Building pages from patterns. Insert a pattern, edit its text and images, and you have a section that would otherwise need custom markup.

The catch worth naming: this power lives in the Site Editor, and it is easy to change something global by accident. A staging copy, or at least a careful eye on what scope you are editing, is the right habit before you reshape a live site.

05Block themes vs. the classic way: the trade-offs

An honest comparison has costs on both sides. Block themes win on visual control and consistency; classic themes still win in a few real situations. Pretending otherwise just leads to a frustrating migration.

Where block themes are clearly better

• Visual, no-code editing of the whole site, not just post content.
• One design system in theme.json instead of settings scattered across panels and CSS.
• Update-safe edits that save to the database rather than into theme files.

Where classic themes still hold up

• Deep custom PHP. If your site relies on heavy custom template logic, a mature classic theme can be the more predictable home for it.
• Plugin compatibility. Some older plugins assume classic hooks and templates. Most have caught up, but check the ones you depend on.
• Familiarity. If your whole workflow is built around the Customizer and child themes, there is a real learning curve to the Site Editor.

The defensible position for 2026: start new sites on a block theme unless something specific pushes you the other way, and don't rush a working classic site over just to be current. Migration is a project, not a toggle.

06What it means for ownership and lock-in

This is the part that rarely makes the feature list but matters most for a site you intend to keep for years. A block theme changes where your work lives — and that changes how trapped you are by any one theme author.

• Your edits are more portable. Because Site Editor changes and global styles save to the database, switching block themes does not necessarily wipe your content layout the way swapping classic themes often did.
• The format is shared, not proprietary. Block markup and theme.json are platform standards. A theme that follows them is describing your design in a language other block themes also speak — less of it is locked to one author's private conventions.
• You are less dependent on the author for changes. When customization required PHP, you needed the theme author or a developer for many edits. When it is visual, more of it is in your hands.

It is not a magic escape hatch — patterns and bespoke blocks can still tie you to a specific theme, and a theme that ignores the standards can be as locked-in as any classic one. But the direction of travel is toward designs you can carry, not designs you rent.

That is the lens worth applying when you choose: does this theme lean on the shared standard, or does it reinvent everything in ways only it understands? The first is a theme you can keep and leave; the second is a theme that keeps you.

07Frequently asked questions

Do I need to know how to code to use a block theme?

No — that is much of the point. Editing templates, global styles, and layouts happens visually in the Site Editor. You only reach for code if you want a custom block or PHP behaviour the editor can't express, and most site owners never need to.

Will my old plugins work with a block theme?

Most modern plugins do, but it is worth checking the specific ones you rely on. Plugins that inject content via classic theme hooks or expect Customizer settings can behave oddly. Test on a staging copy before switching a live site that leans on older plugins.

Can I still use a child theme with a block theme?

Yes, the same parent-child mechanics apply. But you need them less often, because Site Editor changes are already update-safe. A child theme is mainly for overriding template files or adding PHP, not for the everyday styling the editor now handles.

Should I convert my existing classic site to a block theme?

Only if you have a reason to — a redesign, a theme that's no longer maintained, or a desire for visual editing. A working classic site does not need converting just to be modern. Treat it as a deliberate project with a staging copy, not a casual switch.

This is general editorial guidance to help you understand block themes, not financial, business, or legal advice. Every site is different — test changes on a staging copy and verify specifics against the official documentation before relying on them in production.