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


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?


It definitely has potential but needs more time

The concept of Gutenberg and the idea of block-builders in general makes the utmost of sense. A lot of us love WordPress but aren't necessarily developers or don't want to spend additional time creating page templates and new layouts which may be used for single blog posts or pages. Wordpress' Gutenberg in my opinion was supposed to be a "proper" and "lean" drag and drop builder which would render a lot of the third party plugins irrelevant, however the UX is clunky and leaves a lot to be desired. Instead of streamlining the act of writing a blog post, it's not much harder to write a simple piece of content. In theory there are more options but overall it feels more restrictive when every element needs to be a seperate block. The fact it doesn't work as an either or option, or in tandem with classic editor is also quite frustrating and doesn't allow users to dip their toes into the water. Instead you get the cold shock of this unfamiliar interface and writing a quick piece of content becomes a pain. - It's certainly not all doom and gloom though and undoubtedly a lot of the poor feedback (mine included) is because we all as humans don't like change. With a few tweaks and new functionality, I can definitely see this working. My issue is that right now it feels like it's in beta and shouldn't have been released just yet. Reputation wise I think it has suffered for this but I trust the awesome WordPress team to eventually get this right and make us all forget/stop installing classic Editor!

counter intuitive and incompatible

Gutenberg looks like something that existed before WordPress was created. It is a HUGE step back for WP, and something I really hate using: it is counter intuitive and breaks a lot of things on my sites (theme, plugins, DB). Everything seems slower and more complicated than before. One of my copywriters even quit because it was a mess to use. Please hear the admonestation of Humanity, and bring WordPress back, and let Gutenberg coexist as a standalone plugin (for those who really want to use it).

This editor makes simple things complicated

Every time I start a new WordPress project, I give Gutenberg (the new default editor) a chance. Yet, every time I end up turning away from it. The reason is simple: It makes simple things way too complicated. This editor is only good for ONE thing: Writing. And that is exactly the number of stars it deserves. WordPress is supposed to be a full-featured CMS. Yet this editor makes an u-turn and turns WordPress back to a blogging platform.

Was better before

I'm a long user of WordPress, now i'm disappointed that the Gutemberg editor is the only choice in WP. I would like to have the default as the classical editor, i hate Gutemberg
Read all 2.701 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.5.0.



Bug Fixes