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?


Difficult To Use

I tried to get used to Gutenberg, but I just can’t. Simple tasks seem to take twice as many clicks as before. The whole concept of blocks is ridiculous and unhelpful. I still can’t believe they’re forcing this on everyone.

Disaster….in almost every way possible

The forced implementation of this update and what is represents is a joke! For the many valid and consistent reasons highlighted in this section of reviews on Gutenberg, I am shocked that this even made it out to a production version. PLEASE MAKE SURE THIS NIGHTMARE ENDS!!

Whoever designed this, he deserves to work for Microsoft

Gutenberg IS THE WORST, who needs a visual composer installed by default? I want my HTML code and preview mode, as always. If it works, why do you change that what made WordPress great? I have a 27″ screen and I can’t use more than 800px for post editing, a single title of 8-10 words uses 3 lines, 3 lines!!! with lots of free space right and left. Try to add more than 1 image at once, not a gallery, good luck. It’s messy for old and new users and WordPress does not seem user friendly any more. Who in the hell designed this crap and why is it installed by default with WordPress?

Guys you have to keep away from ‘JetPack’ ways, don’t force to install lots of crap only to use JetPack stats, people don’t like that kind of things. Offer Gutenberg as a PLUGIN for those who are not happy with classic WordPress editor … I guess only a few, and that’s why you force its installation … but, why? is somebody out there working for WordPress that needs to justify his salary making changes here and there with no sense? you’re going to get a lot of people uninstalling WordPress if you keep going this way.

Very disappointed, confused and frustrated !!!

I have followed the discussion regarding Gutenberg for almost an year. During all those months I really hoped that Automattic will abandon the idea of “blocks”. Ellas, despite all negative feedback and well argumented concern from all over the place WP 5.0 has been rolled out with Gutenberg in the core.

Now we are offered the Classic Editor plugin and at the same time it was already announced that it will be supported only until 2021. So, after 3 years, what should we do?

One of the most annoying issues with Gutenberg is the concept of blocks for text paragraphs. It is ridiculous to have a separate block for every single paragraph!! In our sites most of our articles are of 1000 to 2000 words and my last post is almost 8000 words. My writing process is not based on creating short paragraphs and I usually move sentences here and there, copy and paste, delete, etc and all this can be achieved very quickly with a few clicks or keyboard strokes with the “old” editor. Very often my colleagues just use Microsoft Word to write the content and then we copy it in WordPress. Now we are forced to use separate blocks for each paragraph and we don’t understand why.


If you think that Gutenberg is some kind of innovation, well… right now it is NOT. Innovation is when creativity process is useful for the people. And I don’t see any usefulness in the last WordPress 5.0 update in terms of improved writing process or user experience.

I have heard about ClassicPress and will follow their development, still I’m a bit hesitant to try it. For example two of our sites use WooCommerce and in their forum I’ve read that ClassicPress most probably will not support Woo. I would prefer not to have 3 sites with ClassicPress and 2 with WordPress/Gutenberg.

All in all, I’m very disappointed, confused and frustrated. 🙁

P.S. Let me just add that I have exactly 10 years of WordPress experience. I am not a developer, but a self-study end user who managed to learn WordPress. Up to now I have influenced a lot of my friends to start using WordPress. With version 5.0 I cannot recommend WordPress with pure heart anymore.

And now what?

OK, some people decided to add a visual editor in WordPress by default, this is something I can understand.
The purpose of eliminating the classic editor is totally beyond common sense!
All the problems that we have to cope with … all the plugin conflicts, the different way we MUST work because “some people decided to add a visual editor in WordPress” AND to throw away the classic editor.
Please do not bother to advise me to use the classic editor plugin. As we all know it does not have a future and it is a completely wrong idea.
The classic editor should be a standard option and the user should be able to toggle between editors (this can be done with most visual editors in the market).
I am really facing a dead end with most of my sites. After many trials in backup sites, it is clear now that I cannot update to the WordPress 5.0.
Thank you so much!

Bad Editor, Bad WordPress

I dont like gutenberg editor.
– new editor very slowly
– new editor use more resource hosting
– useless feature, ex: dropcap, LOL
– i cannot bulk edit convert old post, manual edit? really?
– i only want write article, not design article
give back classic editor to WordPress

Read all 1,812 reviews

Contributors & Developers

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


“Gutenberg” has been translated into 42 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.



  • Parser: Make attribute parsing possessive (Fix High CPU usage).