Picture this: you spend a Saturday afternoon installing the latest WordPress block theme everyone's raving about. You fire up the site editor, poke around for twenty minutes trying to figure out how template parts work, get frustrated when your header inexplicably moves to the wrong position, and then quietly reinstall your old classic theme like nothing happened. Sound familiar? That was me for most of 2024. I kept telling myself block themes weren't ready yet. Then I forced myself to actually commit to one for three straight months — and my opinions changed in ways I didn't expect.
I've now spent real time building and maintaining sites on both approaches. Not just playing around in a demo environment, but handling client work, debugging weird issues at 11pm, and explaining things to people who just want their website to work. Here's what I actually think.
What Finally Pushed Me to Give Block Themes a Real Shot
It wasn't a blog post or a YouTube tutorial. It was a client call. They wanted to change their homepage hero section — a completely reasonable request — and I had to bill them forty-five minutes to do something that should take five. Their classic theme had hardcoded that section in a PHP template, and even with the customizer open, there was no clean way to let them handle it themselves going forward.
Block themes promise something that actually matters in the real world: non-developers can edit the structure of their site without touching code or calling me. Full site editing, as WordPress has been rolling it out since version 5.9, is built around this exact premise. When it works, it genuinely delivers on that promise.
That specific client problem got me to stop dabbling and start building. And once I committed, I started noticing things that both impressed me and irritated me in equal measure.
The Learning Curve Is Real — Stop Pretending It Isn't
Block theme advocates have a habit of glossing over how confusing the transition actually is. The distinction between the regular post editor and the site editor trips everyone up at first. Clients who were perfectly comfortable making changes through the Customizer suddenly found themselves lost in nested template structures with no obvious way back.
Research from the Nielsen Norman Group consistently shows that users abandon tasks when they can't see clear progress toward a goal. The site editor, despite its power, gives you surprisingly little feedback when something breaks. Your layout just shifts. Sometimes the change you made three screens ago is what caused it, and tracing back is genuinely painful without some experience under your belt.
Government usability guidelines at usability.gov emphasize that design tools should reduce user error and make recovery from mistakes simple. The site editor still has work to do on that front. I've spent more hours debugging block template inheritance issues than I ever spent tweaking a `functions.php` file. That's a trade-off you should go in knowing about.
Where Block Themes Genuinely Win
Here's where I'll give credit where it's due, because the advantages are real.
Performance is the biggest one. A well-built block theme ships almost zero JavaScript by default. No jQuery dependencies, no page builder stylesheet overhead, no conflicts from bundled plugin libraries. My mobile PageSpeed scores went from the mid-60s on a popular classic theme to consistently hitting 92-96 on a lean block theme — same content, same server. According to the HTTP Archive Web Almanac, the median mobile web page still takes over four seconds to become interactive. A clean block theme can cut that dramatically without any caching tricks.
Global styles through `theme.json` are also genuinely elegant once you get past the learning curve. Instead of hunting through five separate Customizer panels to change your brand color, you update it once and it propagates everywhere. For designers who think in design systems rather than one-off customizations, this is a revelation. Our deep dive into theme.json breaks down exactly how the system works if you want to understand the mechanics before committing.
Where Classic Themes Still Hold Their Ground
Complex sites with custom post types, conditional template logic, and deep WooCommerce customizations are still easier to build and maintain with classic PHP-based themes. Full site editing's block-based approach was designed for content editors, not developers who need surgical control over template rendering.
I tried rebuilding a membership site's complex archive templates using block templates and spent three days on something that would have taken me four hours in a classic theme. The pattern system is powerful for straightforward content layouts, but it fights you when your requirements get specific. The University of Washington's web accessibility guidelines also note that complex interactive sites need careful template control to maintain proper semantic structure — something classic themes handle more predictably.
Plugin compatibility is another honest concern. Most major plugins were built with classic theme assumptions baked in. The majority work fine with block themes, but edge cases exist, and debugging them is less pleasant than block-theme proponents will admit.
My Actual Decision Framework
After a year of building on both, here's how I make the call now — and it's simpler than most comparisons make it sound:
- New content-focused site (blog, portfolio, brochure): Block theme. Better performance out of the box, future-proof, and clients can actually manage layout changes themselves.
- Existing site that's working: Stay on classic. Migration pain rarely justifies the gains unless there's a specific problem to solve.
- Complex e-commerce or membership platform: Classic theme or a hybrid approach. Don't fight the tools.
- Client who needs to self-manage layout changes: Block theme, but invest time in training. Don't assume they'll figure out the site editor alone.
The best block themes of 2026 are genuinely mature products now. If you haven't looked recently, our roundup of the best block themes covers what's worth your attention. The gap between block and classic has narrowed significantly.
What hasn't changed is this: the worst decision is picking based on what's trendy rather than what the actual project needs. Block themes are where WordPress development is heading. That doesn't mean they're right for everything you're building today. If you're switching themes on an existing site, please read our guide to switching themes safely before you touch anything in production. I've seen too many sites break from rushed migrations.
The Honest Bottom Line
I build new sites on block themes. I maintain existing sites on whatever they're already running. I stopped trying to migrate clients who aren't broken, and I stopped recommending classic themes to anyone starting fresh. That might feel like a cop-out, but it's genuinely the right call for most situations — and the developer docs at WordPress.org are finally good enough to support either path.