“Gutenberg” is a codename for a whole new paradigm in WordPress site building and publishing, that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word. Right now, the project is in the first phase of a four-phase process that will touch every piece of WordPress — Editing, Customization, Collaboration, and Multilingual — and is focused on a new editing experience, the block editor.

The block editor introduces a modular approach to pages and posts: each piece of content in the editor, from a paragraph to an image gallery to a headline, is its own block. And just like physical blocks, WordPress blocks can added, arranged, and rearranged, allowing WordPress users to create media-rich pages in a visually intuitive way — and without work-arounds like shortcodes or custom HTML.

The block editor first became available in December 2018, and we’re still hard at work refining the experience, creating more and better blocks, and laying the groundwork for the next three phases of work. The Gutenberg plugin gives you the latest version of the block editor so you can join us in testing bleeding-edge features, start playing with blocks, and maybe get inspired to build your own.

Discover More

  • User Documentation: See the WordPress Editor documentation for detailed docs on using the editor as an author creating posts and pages.

  • Developer Documentation: Extending and customizing is at the heart of the WordPress platform, see the Developer Documentation for extensive tutorials, documentation, and API reference on how to extend the editor.

  • Contributors: Gutenberg is an open-source project and welcomes all contributors from code to design, from documentation to triage. See the Contributor’s Handbook for all the details on how you can help.

The development hub for the Gutenberg project is on Github at:

Discussion for the project is on Make Blog and the #core-editor channel in Slack, signup information.


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.

What’s Next for the Project?

The four phases of the project are Editing, Customization, Collaboration, and Multilingual. You can hear more about the project and phases from Matt in his State of the Word talks for 2019 and 2018. Additionally you can follow updates in the Make WordPress Core blog.

Where Can I Read More About Gutenberg?

Where can I see which Gutenberg plugin versions are included in each WordPress release?

View the Versions in WordPress document to get a table showing which Gutenberg plugin version is included in each WordPress release.


پروری 26, 2021
Classic should be the default, at least for WordPress-installed websites, but even in sites Classic should always be available. As someone who has an installed WordPress, my real worry about this is that it might be incompatible with sites that rely on old plugins and themes that have stopped updating for good, like Comic Easel and Easel that my site uses. To be fair, it returns to the Classic Editor for a custom post-type that my plugin uses. It clashes with the current backend's look, at least for my installed WordPress. Another worry are the frequent updates that might mess with the CSS styling if I change WordPress' defaults. And well, a lot of us aren't in the mood to style everything again because of Gutenburg. I pity websites that have hundreds if not thousands of posts to check. You have to install a plugin to use Classic again! Sure, I think most of us here are the "it's new so it sucks", but that's because "If it ain't broke, don't fix it." But then again... No one likes being forced to use something, and this just frigging replaces the Classic Editor without prompt IIRC plus it bloats WordPress installations for those of us who don't use it. I was pretty surprised and pissed off when Gutenburg suddenly showed up when I was trying to post something, so just for this it already turns this plugin (or rather the forced inclusion by WordPress) a 1 out of 5. If it stayed a plugin and not replaced Classic, I think a lot of us would be happier. I can just scroll down while seeing everything in Classic. I can hide stuff I don't need and change the layout to 1/2 columns with Screen Options. It takes a lot longer for the preview to load up in Gutenberg for some reason.
پروری 25, 2021
You have put a sort of builder in the place of an EDITOR, where people would like to create CONTENT, with some formatting. At first I believed it would be a help for better formatting but I wouldn't dream of offering less, and even that making it hard. It's a joke really; lists, highlights etc. just not work. Shame, I have to go back to the old editor. And if that would not be possible, I left wp as it was.
پروری 27, 2021
please take this piece of junk out of the wordpress default plugins. if you want, you can install it, but you can't force 3 million users to uninstall it just because 300,000 like it.
پروری 17, 2021
They thought they knew how to improve their product, they realized their mistake, and then Coca-Cola Classic rose to heights never dreamed of. Think about it.
Read all 3,298 reviews

Contributors & Developers

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


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


To read the changelog for Gutenberg 10.0.2, please navigate to the release page.