Last checked and updated on April 20, 2026What Is New in WordPress 5.0
WordPress 5.0 is a landmark release that fundamentally changes the content creation experience with the introduction of a new block-based editor.
| Category | Key Changes |
|---|---|
| New Features | Gutenberg block editor, Twenty Nineteen theme |
| Improvements | Accessibility enhancements, REST API endpoints |
| Developer | New JavaScript build process, updated coding standards |
How does the new editor change content creation?
The core of WordPress 5.0 is the Gutenberg editor, which replaces the classic TinyMCE editor. Instead of a single text area, you now build posts and pages using individual content blocks for paragraphs, images, galleries, and more.
This block-based approach offers more layout flexibility without needing shortcodes or custom HTML. In practice, it makes complex page designs more intuitive for end-users, though developers need to get familiar with the new JavaScript-centric way of creating blocks.
What theme comes with this release?
Version 5.0 includes the new Twenty Nineteen theme, designed to showcase the capabilities of the Gutenberg editor. It's a minimalist, blog-focused theme with a strong emphasis on typography and wide, full-width alignment options for blocks.
The theme's simplicity is its strength, providing a clean canvas that lets the content created with blocks take center stage. It's a solid default for blogs and sites that prioritize readability.
Are there updates for developers?
Yes, the shift to Gutenberg signifies a major move towards a more modern JavaScript-driven development workflow. The build process for core now uses Webpack and Babel, moving away from Grunt.
This matters because it aligns WordPress core development with contemporary front-end practices. Developers creating custom blocks will need to work with React, JSX, and the WordPress components library.
What about accessibility and compatibility?
The release includes specific accessibility improvements to the new editor, though the community noted it was an area requiring ongoing work. A key feature is the Classic Editor plugin, which allows users to disable Gutenberg and revert to the old editing experience.
Having the Classic Editor plugin available is crucial for mitigating upgrade risks on sites with complex meta boxes or custom fields that might not be immediately compatible with the new block editor.
FAQ
How do I disable the new Gutenberg editor?
You can install and activate the official Classic Editor plugin from the WordPress repository. This plugin allows you to completely revert to the previous editing experience.
Will my old posts break in the new editor?
No, existing content will be wrapped inside a "Classic" block. This preserves all your old formatting and shortcodes, making the transition backward compatible.
Do I have to use React to create custom blocks?
While the core blocks are built with React, you can create custom blocks using any JavaScript you want, including plain JavaScript or a different library. However, using the provided React components is the recommended path.
What happens to my custom meta boxes?
Custom meta boxes will appear in a new "Advanced" panel below the block editor. They still work, but their placement is less integrated than in the classic editor, which can be a jarring user experience.
Is the REST API updated in this version?
Yes, WordPress 5.0 includes new REST API endpoints, specifically for post types and taxonomies, giving developers more tools to interact with site data externally.