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?


clunky, slow, time wasting

I got to say I wasn’t going to leave a review as I know that I should be embracing change and all that but this new update is slow. The old wordpress editing was so simple to use, yes I understand that it was basic but boy was it easy. Gutenberg just makes adding new content so long winded, why would they add this to wordpress core without ironing out the issues first, yes again I know that Gutenberg has been around for ages but its not really fit for purpose and adding it to the core of wordpress during the busiest retail time of the year was also a real clever idea.

Anyway thankfully there is a plugin that can revert you back to the old classic editor with over 1 million active users, this really speaks volumes, if you need this plugin here is the link:

Un fracaso total

Hay editores por bloques que son gratuitos y funcionan y se ven muy bien. Pero este gutenberg es un total fiasco, partiendo por algo tan básico y molesto como la doble barra de scroll en el lado derecho! Por favor! qué clase de desarrolladores están detrás de esto! Sin dejar de mencionar los fallos con plugins de terceros como Calendarize IT! y otros. Afortunadamente los “colaboradores de WordPress” han creado un plugin sencillo para volver al editor clásico. En serio señores de WordPress, cuando IMPONGAN algo que la gente NO HA PEDIDO, por lo menos tengan la decencia de INCLUIR un botón para desactivar y seguir con la aplicación base o clásica, no sean autoritarios!

Add me to the list

I am sorry. I know a lot of people probably put a lot of work into this, but Gutenberg is dreadful. The editor is clunky, unintuitive and nowhere near as flexible as it should be (or as Classic Editor was)

What used to be a 5 or 10 minute blog post in Classic Editor now becomes a 30 minute exercise in frustration. How long it took me just to add an image into a post and have it right aligned to the first paragraph. Trying to make similar changes to an existing page was so unfruitful I gave up in the end. I could insert an image in the editor but it would never appear when previewing the page. Was it going to appear when I published it? Yes but the preview certainly didn’t show that.

Text runs off the right edge of the page.

And when I get a few paragraphs in I have to work around a theme-based toolbar across the screen that hides what I’m trying to write behind it. (Maybe not Gutenberg’s fault but was never an issue under Classic Editor)

The page editor is now a portrait-sized window even though I set the page to be “one column” to cover a wide page. I had HTML templates which I had been using with zero issues for composing pages and now it’s so frustratingly difficult to do what used to be a fairly simple task. I wanted to like Gutenberg but I find it too much a step backwards.

While this editor seems like a good idea and could be in the future, it should be an “opt in” approach rather than force everyone onto it, especially when it clearly seems to be full of bugs and quirks that need to be ironed out. And certainly needs to be a lot more user friendly.

As I said I understand that a lot of people volunteered their time into making this editor, but at the same time there are many thousands of us who have volunteered hours of their own time writing content who are seeing their work either distorted or much much harder to produce.

Gutenberg needs a lot more time in the workshop before it could have even been considered for a widespread release.

If I could give this NO STARS I would!!!

It doesn’t take a genius to look at the HUGE number of negative reviews to realise that the mandatory inclusion of this JUNK editor is a whopping mistake on the part of WordPress. I have about 15 customer WordPress sites and I am being inundated by them asking what THE [ REDACTED ] has happened to their editor? This is a freaking design and usability catastrophe, both for me as a seasoned and experienced designer/developer and also for my clients who are Mr & Mrs Average who have little to no experience.

The “Classic Editor” plugin has had + Million installations (15 of them for my sites!). You think people go to the trouble of removing this JUNK for the [ redacted ] of it?

WordPress, for the love of all that is good and sweet and reminds us of the baby jesus and that donkey and that other animal, what was it… WHAT THE [ REDACTED ] WERE YOU THINKING?????????????

Read all 2,038 reviews

Contributors & Developers

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


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



Performance improvements

  • Optimize isViewportMatch
  • Performance: BlockListAppender: 1.7x increase on key press
  • Date: Optimize the usage of moment-timezone to save some kilobytes
  • RichText: selectionChange: bind on focus, unbind on blur
  • RichText: only replace range and nodes if different
  • Cache createBlock call in isUnmodifiedDefaultBlock
  • Edit Post: Select blocks only once multiple verified
  • RichText: Do not run valueToEditableHTML on every render
  • RichText: Reuse DOM document across calls to createEmpty
  • Only initialise TinyMCE once per instance
  • Optimize the insertion point component
  • Avoid rerending the current block if the previous block change
  • Avoid getBlock in block-list/block
  • Pass the registry argument to withDispatch to allow selectors to be used

Bug fixes

  • Annotations: Apply annotation className as string
  • RichText: Ensure instance is selected before setting back selection
  • Meta Boxes: Don’t hide disabled meta boxes by modifying DOM
  • Fix: Problems on Media & Text block resizing; Load wp-block-library styles before wp-edit-blocks
  • When a post is saved, check for tinymce and save any editors.
  • Fix: Undoing Image Selection from Media Library in Image Block breaks it
  • Add an end-to-end test for the HTML block
  • Fix regression when copying or cutting content in the editor
  • Fix issue where default appender has icons overlaying the text
  • Set document title for preview loading interstitial
  • Fix: Upload permissions error on end-to-end inline tokens test
  • Ensure classic block caret is in correct position after blur
  • Fix tab navigation sometimes skipping block UI
  • Improve font size picker accessibility: Use a menuitemradio role and better labels
  • Don’t show trashed reusable blocks in the editor or frontend
  • Rename functions, removing gutenberg_ prefix
  • Add block switcher end-to-end tests
  • Allow links in plugin group in the editor more menu
  • Introduce searching of block categories from slash inserter
  • Convert HTML formatting whitespace to spaces
  • Label link format with selected text, not full text
  • Ensure permalink panel is only displayed when a permalink is allowed
  • Allow the user to convert unembeddable URLs to links and try embedding again
  • Improve the top bar tools interaction and consistency
  • Fix overflowing content in the facebook embed preview screen
  • Add an action to set a category icon and correct block categories documentation
  • Fix: pasting a tag that is part of a transform and not matched ignores the content.
  • Packages: Extract Eslint config package
  • Add end-to-end test to catch revert of title during a preview after saving a draft
  • Avoid react warnings when merging two adjacent paragraphs
  • Avoid PHP notice in the recent comments block
  • Editor: Restore the block prop in the BlockListBlock filter