If you formed your opinion of the WordPress block editor in 2018 or 2019, that opinion is out of date.
If you formed your opinion of the WordPress block editor in 2018 or 2019, that opinion is out of date. It may still be correct in places. But the editor you remember, with its rough edges, its missing features and its arrival as a forced change, is not the same product you would be judging today.
This essay argues that the block editor deserves a second look, especially from site owners who switched it off, installed a page builder to avoid it, or never gave it a fair trial. It is not an argument that it is perfect, or that everyone should stop using a page builder. It is an argument that the cost of looking again is low and the possible gain is large.
Why so many people wrote it off
WordPress 5.0 shipped on December 6, 2018, with a new block editor as its headline feature. The release notes promised that “each piece of content is in its own block and easily maneuverable”, and offered the Classic Editor plugin for people who preferred the old screen, with support promised through 2021.
The reaction was mixed, and the complaints were fair. The new editor changed a workflow people had used for years. Plugins and meta boxes did not all behave. The interface felt different, and for long-form writers the old screen was simply faster. Many sites installed the Classic Editor and moved on.
That choice has stuck. The Classic Editor plugin’s own directory page says it will be fully supported and maintained until 2024, or as long as is necessary, and shows more than eight million active installations. Millions of sites decided, once, that the old editor was good enough, and have not revisited it since.
Deciding once is reasonable. Deciding once and never again, for years, while the software changes, is a different thing.
What is actually different now
Rather than recite a changelog, here are the changes that matter to a site owner, described in terms of what you can do.
Reusable layouts through patterns
Patterns are saved arrangements of blocks you can insert in one click: a hero section, a pricing table, a testimonial row, a call to action. They remove the biggest practical objection to blocks, which was having to rebuild the same layout by hand every time. Our advanced block editor guide to patterns and the query loop shows how to build a set for your own site.
Editing the whole site, not just the post
With block themes, headers, footers and templates are made of blocks as well. You can change a page layout, a blog archive or a footer in the same editor you use to write, rather than in a separate theme options screen or a code file. See our list of the best block themes for WordPress if you want to try this.
Dynamic content without a plugin
The Query Loop block lists posts, products or custom content by criteria you choose, with a layout you design visually. Work that once required custom theme code or a separate plugin can often be done on the page.
Design settings in one place
Colours, typography and spacing can be defined once for the site and reused by every block, so changing a brand colour does not mean hunting through pages. This is the part that quietly matters most over the life of a site.
None of this is an unreserved endorsement. We have not benchmarked these features against alternatives and will not claim they are faster or better than a given product in a given case. The point is simpler: the editor can now do things that, in 2018, you needed other tools for.
The case that matters most: content stays portable
Here is an argument that gets less attention than it deserves. The block editor stores content as plain HTML. According to the developer documentation, blocks are saved in the post content as ordinary HTML, with each block wrapped in an HTML comment that marks where it begins and ends, and its attributes stored as JSON in the opening comment. The documentation describes this as a way to keep a single source of truth for the content.
Think about what that means in practice. Your pages are readable HTML. If you later change themes, the text, images and headings remain in your database in a form any system can parse. Compare that with content built in a proprietary page builder, where leaving can mean losing the layout, or ending up with a page full of shortcodes that mean nothing without the plugin.
This is not a claim that every page builder locks you in. Several store clean output, and the details differ by product. It is a claim about the default: when you use core blocks, your content lives where WordPress itself keeps it, and moving away costs you much less. For anyone who has ever dreaded a redesign, that is worth something.
It is the part of WordPress that gets maintained
A second argument is about direction. The block editor is not an optional add-on. It is where WordPress core is investing. Features that arrive in core arrive for blocks first. Themes are increasingly designed around them, and a growing set of tools in the ecosystem assume them.
That has a consequence for the long run. If you build everything on a layer WordPress is not developing, you will increasingly be the one doing the compatibility work, either through plugins that bridge the gap or through your own effort. If you build on the editor, you move with the platform. That is not a guarantee, and platforms change course. But betting with the maintainers is usually a safer default than betting against them.
The strongest counter-argument: page builders are still better at some jobs
The fairest objection is that the block editor, for all its progress, is still not the best tool for every kind of site. Dedicated page builders often offer finer visual control, richer interactions, extensive template systems and mature workflows for agencies building many pages. If your business is building complex marketing sites visually, a builder may serve you better and no honest essay should pretend otherwise. Our comparison of WordPress page builders goes through the options.
Another objection is about learning cost. You and your team already know your tool. Switching takes time, and time has a price. That is true, and it is the reason the trial below is small and reversible.
A third objection is that the editor has a history of change, and that change may continue. Also true. Features have moved and interfaces have been reworked. If you prefer software that stays put, that is a real consideration.
But notice that none of these objections says the block editor is bad. They say it is not always the best. For a very large number of sites, such as blogs, small business sites, brochure sites, documentation and shops where the product pages come from a plugin, “good enough, portable and maintained” beats “the most powerful tool available”, because those sites do not need the most powerful tool. They need to be edited by ordinary people without fuss.
Where it still falls short
An honest second look includes the weak spots. Expect these.
- Some plugins and meta boxes still assume the old editor. Check any plugin that adds fields or panels to the post screen before you switch a workflow.
- Complex layouts can take more steps than in a dedicated builder. Responsive controls and advanced interactions are areas where specialist tools often go further.
- Long documents can feel heavy. Very long posts with many blocks can be sluggish in the editor, depending on your device.
- The learning curve is real. The mental model of blocks, groups, patterns and templates takes a little time.
- Quality varies across third-party block plugins. Core blocks are consistent. Add-on block packs are not, and each one adds code. See our argument for deleting plugins you do not need before you add a pack of blocks you will use twice.
These are reasons to test, not reasons to avoid testing.
A fair, low-risk way to try it
You do not have to migrate anything. Run an experiment you can walk away from.
- Use a staging copy. Follow the staging site guide, or spin up a throwaway install. Never experiment on the live site first.
- Start from a block theme. A theme designed for blocks shows you the editor at its best. Using a classic theme and judging the block editor by it will give a distorted picture.
- Write one real post. Not a demo, a post you actually need. Notice what slows you down and what you like.
- Build one reusable pattern. Take a section you repeat, such as a call to action, and save it as a pattern. Insert it on three pages. This is where the value usually shows.
- Edit a template. Change a footer or an archive layout in the site editor. Decide whether doing it visually feels better than your current method.
- Check your must-have plugins. Open the screens of the plugins you rely on and confirm they work in the new context.
- Take the tutorial route if you are new. Our block editor basics tutorial covers the tools in order.
- Decide with a rule. For example: if you can finish the same task in about the same time and keep the result portable, switch for new content. If not, record why and return in a year.
Take a backup before you test anything on a real site. If you do not have a routine, our backup routine tutorial is a good place to begin.
Do not rewrite everything
A word of caution in the other direction. A second look is not a mandate to rebuild your site. If you have hundreds of pages in a page builder that works, converting them is a project with real cost and real risk, and the benefit may not justify it. The sensible default is to use blocks for new content, and to convert old content only when you are touching it anyway.
Likewise, if you use the Classic Editor on a site with simple needs and it works, no one is entitled to tell you to stop. The argument is only that the decision should be made with current information, not a verdict from years ago.
Performance and simplicity as tie-breakers
When two approaches can do the job, the simpler one usually wins over time. A site built on core blocks and a good block theme usually has fewer moving parts than one built on a theme, a page builder and an add-on pack. Fewer parts means fewer updates, fewer conflicts and fewer places to look when something breaks.
That is a general principle, not a measured claim about any product, and your results depend on the theme and plugins you choose. If speed matters to you, measure your own site, and our WordPress speed optimization guide shows how. But as a tie-breaker, less machinery is a sound instinct.
Conclusion
The block editor you rejected in 2018 was a first release. The one available now has patterns, whole-site editing for block themes, dynamic query blocks and a design system built around it, and it stores your content as portable HTML. It is also where core WordPress is investing.
It will not suit everyone. Complex visual builds may still belong in a dedicated builder, and some plugins still lag. But the cost of an afternoon on a staging site is small, and the possible result is a simpler, more portable site that moves with the platform instead of against it. Give it that afternoon, write one real post, build one pattern, and then decide with fresh facts.