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?


Clients ask if they can update content? I ask if they can use MS Word?

I can’t understand why the team pushing it through don’t get this. The team / moderators keep responding to 1 star ratings asking for constructive criticism, and then not getting a response. It’s simple … we don’t want this editor. There was nothing wrong with classic. Anyone could start using it without training. Just leave it as a plugin please.

I feel sorry for the team behind it as they’ve obviously worked hard and are trying to be helpful. A lot of the 5 star reviews have been left in mistake and not wanting to offend anyone but I suspect many of those that do like it are a different user base to the masses of developers that have loved WP for years. It’s a brilliant CMS platform to build complex sites and along with things like ACF make it super simple for clients to use. I salute the WP team!

At launch the rating was 2.3 (so why force it through) and it’s now at 2.1. At launch Classic had 700, 000 installs and it’s now at 1+m. I’m not sure a plugin has ever had such a bump. With WP being the #1 CMS I’m surprised this has not made mainstream media with the whole New Coke comparison thing.

Final point, who came up with the late December launch date? Merry Xmas everyone!

Off to post selfies of me pouring coke down a drain in 80s garb.

gets 2 stars for ambition

really doesn’t deserve any stars yet – released too soon. Not sure what the user testing process looked like on this but it’s a failure.
Some nice plugins extend Gutenberg to being almost usable (allowing non-equal columns and easily edited elements such as padding, background elements etc) but the biggest issue is how hidden all the controls are. Did you learn nothing from the disaster that was the rollout of Windows 8? Or study what established WordPress page builders already do? You can’t make every control hidden until you figure out a magical space to hover your mouse. Sure it looks cleaner to read the page in the admin side, but its a usability disaster.
For the determined, the Gutenberg system can be learned, and made a powerful editing feature (again, not on its own yet, but requiring plugins to extend its features) but for the average user, it might as well be asking them to write HTML.

Constructive Criticism

I can see where WordPress / Gutenberg Team are going with this but…
I think it’s been released too soon.

Unless I’m missing something, you should be able to adjust the column widths and margins and paddings. I’ve been using Pagebuilder for a while now and if Gutenberg could do what this does, you’d be onto a winner. I can’t even change the background colour of the block very easily without having to write extra CSS. It is not good for SEO to keep adding CSS into the Customiser as this puts more and more code above the important information that you want Google to find.

Using the Variable Column Width plugin killed the 3 even columns that I had put above a 2/3rds – 1/3rd column layout I wanted to create. They all changed to a single column each.

The margin between columns is huge – 40px, there should be a way to adjust this setting.

On a good note, none of my sites have crashed (yet).

As time goes by, I may find more things I think should be included – such as colour coding the Code text. If it were up to me I would have done this before anything else.


Who thought this was a good thing? I can work around the terrible UI, but come one, I have this huge screen and it uses only 25% of it.


1. This plugin throws saving errors and makes the browser crash constantly.
2. Does not allow proper source code editing.
3. I could not find a way to do the simplest thing – publish a draft.
4. Ruins shortcodes.
5. RTL languages problems.
6. Too narrow for wide screens and does not look together well with the WP UI.

Is not supposed to be part of the core, IMHO.


Make this disappear from wordpress default.
Let me be honest, i bet people rated you positively until the day this went default, forcefully making this default.
Most of sites cannot adapt to it, resulting to negative ratings.
Meaning, if it used to adapt, people would & could freely install this plugin IF THEY PREFERED TO and not force-use, you’re giving a bad reputation to the real Gutenberg.

Read all 2,041 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