For years, “should I use a block theme?” had an easy answer: not yet. Full Site Editing was half-finished, the tooling was rough, and every serious project reached for a classic theme and a page builder instead. That answer has quietly stopped being true.
Full Site Editing has matured. Block themes are now the default for every new WordPress default theme, the editor is genuinely capable, and the design tools have caught up with what agencies actually need. If you last looked at block themes in their awkward early days, it’s worth looking again – because the trade-offs have changed.
What actually changed
The early objections to block themes were real, and most of them have been addressed:
- The design system grew up.
theme.jsonnow gives you a single, structured place to define colours, typography, spacing and layout — a real design system that keeps a site consistent instead of relying on scattered CSS. Global Styles let you (or a client) adjust the whole site’s look from one panel. - Templates are editable in the admin. Headers, footers, archives, single posts – the whole template hierarchy is now built and edited visually, with template parts and patterns you can reuse across the site.
- Patterns replaced the page-builder sprawl. Synced patterns give you reusable, centrally-managed sections – change once, update everywhere — without a third-party builder’s lock-in and bloat.
The case for going block-native
Performance. This is the big one. A block theme with no page builder ships far less CSS and JavaScript than the typical builder-driven site. For Core Web Vitals – and for the mobile visitors who make up most of your traffic – that difference is felt directly.
No third-party lock-in. Build on core blocks and your site isn’t hostage to a page builder’s licence, update cadence or business decisions. Everything is native WordPress, which ages far better.
A better editing experience for clients. Once a site is built with a clean set of patterns, handing it to a non-technical client is genuinely pleasant. They edit real content in something close to the final layout, without being able to break the design.
When a classic theme still makes sense
Block themes aren’t automatically the right call. There are still good reasons to stay classic:
- A large, working site on a builder. If a site is already built, stable and performing, a full rebuild into a block theme is a project – not a free upgrade. Migrate when there’s a reason to, not on principle.
- Heavy reliance on a specific builder’s ecosystem. Some sites lean on builder-specific add-ons that have no clean block equivalent yet. Forcing the move can cost more than it saves.
- Highly bespoke, app-like front-ends. For some projects a headless or custom front-end is still the better fit – though that’s a different decision entirely.
If you’re starting something new
For a new build in 2026, the default should now flip: start with a block theme unless you have a specific reason not to. You get a cleaner, faster, more maintainable site with no licence to renew, and a design system that keeps everything consistent as the site grows.
The honest caveat is that building a good block theme is a skill of its own. The tools are powerful, but a well-structured theme.json, a thoughtful pattern library and sensible template parts are what separate a block site that’s a joy to maintain from one that’s a mess of one-off overrides. The technology is ready; the craft still matters.
The takeaway
The block-versus-classic debate has quietly resolved for new work. Full Site Editing is no longer the risky early-adopter choice — it’s the faster, leaner, more future-proof default. The remaining question isn’t whether block themes are ready. It’s whether your next build is set up to take advantage of them properly.
Planning a new WordPress build or weighing up a move to a block theme? Get in touch – I build fast, maintainable block themes with a proper design system, and I’ll tell you honestly when a rebuild is worth it and when it isn’t.