Gutenberg is more than an editor. While the editor is the focus right now, the project will ultimately impact the entire publishing experience including customization (the next focus area).

Discover more about the project.

Editing focus

The editor will create a new page- and post-building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTML, or “mystery meat” embed discovery. — Matt Mullenweg

One thing that sets WordPress apart from other systems is that it allows you to create as rich a post layout as you can imagine — but only if you know HTML and CSS and build your own custom theme. By thinking of the editor as a tool to let you write rich posts and create beautiful layouts, we can transform WordPress into something users love WordPress, as opposed something they pick it because it’s what everyone else uses.

Gutenberg looks at the editor as more than a content field, revisiting a layout that has been largely unchanged for almost a decade.This allows us to holistically design a modern editing experience and build a foundation for things to come.

Here’s why we’re looking at the whole editing screen, as opposed to just the content field:

  1. The block unifies multiple interfaces. If we add that on top of the existing interface, it would add complexity, as opposed to remove it.
  2. By revisiting the interface, we can modernize the writing, editing, and publishing experience, with usability and simplicity in mind, benefitting both new and casual users.
  3. When singular block interface takes center stage, it demonstrates a clear path forward for developers to create premium blocks, superior to both shortcodes and widgets.
  4. Considering the whole interface lays a solid foundation for the next focus, full site customization.
  5. Looking at the full editor screen also gives us the opportunity to drastically modernize the foundation, and take steps towards a more fluid and JavaScript powered future that fully leverages the WordPress REST API.


Blocks are the unifying evolution of what is now covered, in different ways, by shortcodes, embeds, widgets, post formats, custom post types, theme options, meta-boxes, and other formatting elements. They embrace the breadth of functionality WordPress is capable of, with the clarity of a consistent user experience.

Imagine a custom “employee” block that a client can drag to an About page to automatically display a picture, name, and bio. A whole universe of plugins that all extend WordPress in the same way. Simplified menus and widgets. Users who can instantly understand and use WordPress — and 90% of plugins. This will allow you to easily compose beautiful posts like this example.

Check out the FAQ for answers to the most common questions about the project.


Posts are backwards compatible, and shortcodes will still work. We are continuously exploring how highly-tailored metaboxes can be accommodated, and are looking at solutions ranging from a plugin to disable Gutenberg to automatically detecting whether to load Gutenberg or not. While we want to make sure the new editing experience from writing to publishing is user-friendly, we’re committed to finding a good solution for highly-tailored existing sites.

The stages of Gutenberg

Gutenberg has three planned stages. The first, aimed for inclusion in WordPress 5.0, focuses on the post editing experience and the implementation of blocks. This initial phase focuses on a content-first approach. The use of blocks, as detailed above, allows you to focus on how your content will look without the distraction of other configuration options. This ultimately will help all users present their content in a way that is engaging, direct, and visual.

These foundational elements will pave the way for stages two and three, planned for the next year, to go beyond the post into page templates and ultimately, full site customization.

Gutenberg is a big change, and there will be ways to ensure that existing functionality (like shortcodes and meta-boxes) continue to work while allowing developers the time and paths to transition effectively. Ultimately, it will open new opportunities for plugin and theme developers to better serve users through a more engaging and visual experience that takes advantage of a toolset supported by core.


Gutenberg is built by many contributors and volunteers. Please see the full list in


This plugin provides 11 blocks.



How can I send feedback or get help with a bug?

We’d love to hear your bug reports, feature suggestions and any other feedback! Please head over to the GitHub issues page to search for existing issues or open a new one. While we’ll try to triage issues reported here on the plugin forum, you’ll get a faster response (and reduce duplication of effort) by keeping everything centralized in the GitHub repository.

How can I contribute?

We’re calling this editor project « Gutenberg » because it’s a big undertaking. We are working on it every day in GitHub, and we’d love your help building it.You’re also welcome to give feedback, the easiest is to join us in our Slack channel, #core-editor.

See also

Where can I read more about Gutenberg?


So it’s as bad as they say

I've waited a while to use Gutenberg in a project because word is that it's not a mature product and building pages can be a frustrating experience. I thought several months might be enough time for issues to be resolved, but nothing prepared me for how clunky this interface is. A couple hours later and I'm back using the Classic Editor.

A Huge Mistake, A Miserable Experience

What a nightmare! I've been developing sites since the *very beginning* of the web. I generally curse WYSIWYG, and find the "page builders" detestable. But this one is even worse than DIVI and BeaverBuilder and WPBakery and all those horrific experiences.


Zerstört bestehende Posts, HTML-Tags zu schreiben wird extrem erschwert. Zum Glück gibt es noch Plugins, die Gutenberg deaktivieren, sodass der alte Editor verwendet werden kann

Careful attention is required when updating

The features are great, but the design is very simple. However, if I prepare a rich trick against it, I will struggle with each update. I don't have the skills to develop plugins, but this high score comes from the existence of some great plugin creators.

More Flexibility Would Make It Better

What was one of the things that made WordPress great in the first place? The ability to customize, both in core and through plugins. Gutenberg isn't a great editor yet. It has the potential to be a great editor, but not if it veers too far away from that principle. During the thirty-six years in which I was a teacher, I was always an "early adopter"--someone who jumped on new technology as soon as it came out and often ended up promoting it to others. I'm mentioning that to point out that I'm not afraid of change. However, my first exposure to the Gutenberg editor horrified me. The key thing the developers need to keep in mind is that everyone's mind doesn't work in the same way (something I picked up from all those years in education). The diversity in the reviews indicates that clearly--the block editor fits the mental style of some users but not others. Some people want simplicity, with only the options they absolutely have to have available. Others want every conceivable tool in arm's reach. Some like Gutenberg as a page builder replacement. Others applaud it as a way to eliminate page builders in favor of a simpler paradigm. Clearly, they're not seeing it in the same way. When I started experimenting with Gutenberg, I didn't find it distraction-free. I was distracted wondering why the editing window was so small and where all the controls had gone. I was distracted by having to figure out how to wrap text around an image--doable in the end, but cumbersome compared to the classic editor. I was distracting figuring out how to make the column block work with more than two columns. Instead of offering an upfront choice, the way page builders have been doing for years, Gutenberg requires a user to click on an (invisible) point to select the column block and configure it for a different number of columns. Click in the wrong place, and a user selects the content of one of the columns instead. As I worked, I got faster at some of these operations, but certain things were inherently slower. Having to mouse up to the top of the screen to get some basic options is slower than having them in a TinyMCE toolbar right above where I'm writing. Using the classic block (which can't be made the default without another plugin) overcomes that, but it excludes all the third-party elements. For them, I have to scroll through the blocks--if I'm lucky enough to be dealing with a plugin developer who has already adapted. If not, I have to go find a shortcode and come back to the page or post I'm editing, either way chewing up more time than I should have to. I'm not even a big fan of the block metaphor to begin with. As an English teacher and writer, I see a document as an integrated whole, not as a group of individual blocks. For some things, it really doesn't matter. An embedded PDF, for instance, is probably going to be full-width, so having it in its own block is no big deal. On the hand, having elements like images, around which text is often wrapped, be in separate blocks is more cumbersome. Even small video windows might have had text wrapped around them before. Since blocks can't typically nest inside other blocks, getting the same format that would have been easy in the classic editor is a real chore in Gutenberg. In the end, I got Gutenberg to work for me by working around it. Essentially, my pages and posts are Elementor templates in a Gutenberg wrapper. As long as I can do that, I'm OK. I can edit much faster that way than I can in Gutenberg. I have the classic editor plugin for situations when the block editor throws up an error message. (Those are becoming less frequent as plugin developers become more aware of the possible JavaScript conflicts). I have TinyMCE Advanced, so that if I want to use Gutenberg, it will default to the classic block and have customized TinyMCE to my liking. That also creates an editing experience better for me than Gutenberg provides alone. To make Gutenberg better, I'd advocate a more flexible approach to development. One man's feature-rich environment will look bloated to someone else. And what to one man looks simple will to another look stripped down. What I'd suggest would be basically the same interface as the default, but with a lot more room for user customization. In an ideal world, people who found the classic editor more useful should be able to configure themselves an experience close to that. People who love Gutenberg can leave it alone. People can create all kinds of in-between experiences. If Gutenberg facilitates that flexibility (or at least leaves the door open through plugins, as it seems to now), I think all will eventually be well. If not, there will be a lot of dissatisfied people, some of whom may even leave the WordPress ecosystem completely. The mixed, but low-average reviews on this plugin, plus the millions of installs of plugins that either re-enable the classic editor or disable Gutenberg, support the idea that one size does not fit all.
Read all 2 791 reviews

Contributors & Developers

“Gutenberg” is open source software. The following people have contributed to this plugin.


“Gutenberg” has been translated into 44 locales. Thank you to the translators for their contributions.

Translate “Gutenberg” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.


For 5.9.2:

Bug Fixes

  • Fix Regression for blocks using InnerBlocks.Content from the editor package (support forwardRef components in the block serializer).

For 5.9.1:

Bug Fixes

For 5.9.0:



Bug Fixes