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?


I’ve had to disable it on 90% of my 60+ clients’ sites

I’ve had nothing but complaints from clients since updating to 5.0 last week. Everyone from older sites running on shared servers getting 500s and fatal out of memory errors, to larger clients running brand new themes like X on expensive VPS hosts, and having nothing but problems trying to edit their content.

I updated i think 63 clients in the last few days and in pretty much every case i’ve had to install the classic editor in response to a variety of complaints ranging from, ‘it broke my site’ to ‘i don’t need all this extra junk just to post blogs, what is this block nonsense?” It really has been a mess.

Let the developers retain control

Very sad piece of software. Sure there is a plugin to disable but I’m sure that won’t be an option for long.
This is sad but like most tech companies with their altruistic monologues, they turn out to be the most greedy and power hungry companies there are. This is the first step in pushing out thousands of small web design companies by locking down the once open source WordPress.
I would be fine if they charged $25 to $50 per download of WordPress instead of slowly locking it down into a Weebly model.
I hope I’m wrong but if you follow the greed and hunger of power in tech companies I think this is the direction they’re going.

Frustrating To Use and Breaks Vital Elements

The concept of an easy click and work module would seem like a good idea but the Gutenberg plugin causes so much frustration that any perceived ease is not worth it. The black background make it very difficult to see what you are doing as you are working and whats worse it causes many elements including vital ones the like the headers to not work at all. This is completely unacceptable.

Soooo nicht!

Da wird einem einfach die Entscheidung abgenommen, ob man das haben will oder nicht? O_o

Optional okay.. Aber warum Pflicht? Musste tatsächlich ein PlugIn installieren, um dieses ZwangsPlugIn zu vermeiden! Das kanns doch nicht sein, liebe Leute…

Am liebsten 0 Sterne für diese Block-kiste!

Vielleicht bin ich ein Gewohnheits-Mensch?! Aber zwingen lasse ich mich nicht!

So bad…

… no choice??? I just installed another plugin to get rid of it! It looks soooo bad.

Read all 1,824 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).