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?


Half Baked

This is a risky move for WordPress. Not entirely because this plugin is imperfect nor because it's different. Instead this major move is both imperfect and probably too different. The user experience WordPress offered already was mostly effective. Using dynamic JS could improve the process however this plugin abandons the UX workflow it has established and aims to replace it all for no particularly good reason. Additionally, the hyper minimalism (mostly white and soft gray lines) makes the experience more vague and unintuitive. I assumed I would be able to use this plugin immediately and easily. I can not. I found myself clicking on the incorrect buttons producing the incorrect results. I'm sorry but you need to go back to the drawing board. Some meaningful changes need to be made. This isn't really it.

One of the best developments for WordPress (german)

Es ist sehr schade, dass der Editor für das Jahr 2019 zuvor mit identischem Namen bereits als Plugin erschienen ist und die Wertung für immer versaut hat. Für diesen klasse Editor kleben jetzt für ewig die Bewertungen in der Statistik, als er noch für viele Tester oder Nutzer Probleme bereitete. Andere müssen offensichtlich immer noch ihren Senf im Kanon dazu singen, was eine unnötig hohe Anzahl von Negativ-Bewertungen zur Folge hat. Ich kann es überhaupt nicht nachvollziehen, warum es heute immer noch solche extremen Negativwertungen gibt. Ich jedenfalls, werde nie wieder den alten Editor verwenden. Er bietet nur Vorteile und sehr viel Kreativität. 10 stars, if I could forgive them!!

Please Staaph! If It Ain’t Broken…

If only there was an option to give no star!. Some pertinent questions.. 1)Was there market research before hand to investigate user needs? 2)Was there a demand for Gutenberg as a product before and after roll-out? 3)Was the ongoing feedback in multiple platforms factored in before going full mode into WordPress releases that include it as a forced default feature? Its difficult to train a client with no technical knowledge on how to add content to a site with Gutenberg unless it is COMPLETELY DISABLED with yet another plugin. Nightmare for both beginners and seasoned developers. Here's an idea.. Google discontinued their Google Plus and url shortener and many other products when they didn't work! Alternatively, return it as a plugin, let people decide for themselves if they wish to install it. I hardly comment, i only logged in just to comment on Gutenberg. #removegutenberg

Not too excited about it

I'm sorry to say that the general unhappiness about this plugin is at least partially warranted. I simply don't like working with this editor (it's like being forced to suddenly use a block-based editor in Microsoft Word). The best way for to get me to use it would probably be if I would see well-known and respected WP developers adopting it successfully in numerous projects and recommending its qualities. I appreciate that a lot of work went into building Gutenberg but forcing it upon me or putting me in the position where I have set aside time to "fix" client websites is bound to raise some frustrations on my part.


I've been using WordPress for years but after an hour trying to figure out this editor, I couldn't even figure out how to add a simple image with text.

A waste of time.

I tried to place an image and text side-by-side, but could not control the positioning. The text and images appeared in random positions on the webpage. I uninstalled it, then I installed Page Builder by SiteOrigin which does it perfectly! It lets you keep the familiar classic editor and works side-by-side with it, and it was very easy to learn.
Read all 2٫632 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.3.0.



Bug Fixes