The WordPress Block Editor in 2026: A Practical Guide

The WordPress block editor (still widely called Gutenberg, after the project that built it) is the screen you use to write posts and pages in WordPress. Every paragraph, image, heading, button and embed is a separate block that you can add, move, style and reuse. It replaced the old single text box in WordPress 5.0, released on 6 December 2018, and it has been the default editor ever since.

As of October 2026, the current version of WordPress is 7.1.2, and the editor looks quite different from the 2018 original. You now get patterns (ready-made groups of blocks), List View for navigating long pages, Notes for leaving feedback on specific blocks, per-device visibility controls, block-level custom CSS and responsive styling. What you still do not get is Google Docs style real-time co-editing: it was pulled from WordPress 7.0 and is not in 7.1.

This guide explains how the editor works today, which tools save the most time, the keyboard shortcuts worth learning, and where the Classic Editor plugin stands if you are not ready to switch.

What the block editor is and how it is organized

Open any post or page and you see three main areas. The top toolbar holds the block inserter (the + button), undo and redo, List View, the preview control and the Save or Publish button. The canvas in the middle shows your content as it will roughly appear on the site. The settings sidebar on the right has two tabs: one for the whole post (status, permalink, categories, featured image) and one for the selected block (colors, typography, spacing, advanced options).

A block is a self-contained unit of content with its own settings. Core WordPress ships dozens of blocks, including Paragraph, Heading, Image, Gallery, List, Quote, Buttons, Columns, Group, Cover, Table, Embed and Query Loop. Recent releases added more: WordPress 7.0 introduced Breadcrumbs and Icons blocks, and WordPress 7.1 added Tabs and Playlist blocks. Plugins can register their own blocks, which is how form, slider and ecommerce plugins plug into the same interface.

Because blocks are stored as structured HTML comments in the post content, a page built with blocks keeps working if you change themes. That is one of the practical advantages over page builders that save layouts in proprietary formats.

Adding, moving and styling blocks

There are three common ways to add a block:

• Click the + inserter in the top toolbar and browse or search blocks, patterns and media.
• Click the small + that appears between blocks to insert one at that spot.
• Type / at the start of an empty paragraph, followed by the block name (for example "/image" or "/table").

To move a block, use the up and down arrows in the block toolbar, drag the handle, or drag it inside List View. To change a block into a different type (a paragraph into a heading, a list into a quote), click the block icon at the left of the toolbar and pick a transform.

Styling lives in the block settings sidebar. Depending on the block and your theme, you can set colors, typography, spacing, borders and dimensions. Two newer controls are worth knowing:

• Hide or show per device. Since WordPress 7.0 you can hide a block on certain viewports without affecting the others, which used to require custom CSS or a plugin.
• Block-level custom CSS. WordPress 7.0 also lets you add custom CSS to an individual block from the editor.

WordPress 7.1 added responsive styling, so you can set different styles per screen size from Global Styles or block settings "without custom CSS," in the words of the release announcement. If you are serious about mobile layouts, pair these controls with the advice in our guide to mobile-friendly WordPress design.

A handy shortcut for consistency: from a block's three-dot menu you can choose "Copy styles," then paste them onto another block of the same type.

Patterns: reuse layouts instead of rebuilding them

A pattern is a pre-arranged group of blocks: a hero section, a pricing table, a team grid, a call to action. You insert it from the Patterns tab of the inserter and then edit the content like any other blocks. Patterns come from three places: WordPress core, your theme, and the WordPress.org Pattern Directory. You can also create your own by selecting blocks, opening the three-dot menu and choosing "Create pattern."

When you create a pattern you choose whether it is synced. A synced pattern (formerly called a reusable block, renamed in WordPress 6.3) updates everywhere it is used when you edit it once, which is ideal for a newsletter signup or a disclaimer. An unsynced pattern is a starting point that becomes independent blocks once inserted. We cover the details, including pattern overrides, in our full guide to WordPress patterns.

List View, the Command Palette and other navigation tools

On long pages, clicking around the canvas to find a nested block is slow. List View opens a tree of every block on the page. You can select a deeply nested block in one click, drag blocks to reorder them, select several and group them, or rename Group blocks so the structure makes sense to the next editor. Open it from the toolbar or with Shift+Alt+O (Windows) or ⌃⌥O (Mac).

The Command Palette is a search box for actions and content. Since WordPress 6.9 it is available across the whole dashboard, and WordPress 7.0 put a ⌘K or Ctrl+K shortcut in the admin bar. Use it to jump to a page, open a template, toggle preferences or create a new post without hunting through menus.

Other built-in aids:

• Zoom out view gives a condensed overview of a whole page so you can rearrange sections (Shift+Ctrl+0 or Shift+⌘+0, when the template is shown in a theme that supports full site editing).
• Spotlight mode greys out every block except the one you are editing.
• Distraction free mode hides the interface while you write.
• Code editor shows the raw block markup, useful for fixing a broken block.

Notes: feedback without changing the content

Notes arrived in WordPress 6.9 (December 2025) and gained more features in 7.1. They let collaborators leave comments directly on the content they are reviewing. To add one, select a block, open the three-dot menu and choose "Add Note." You can also select specific text in a Paragraph block and use the comment icon in the text toolbar to attach an inline note.

According to the official Notes documentation, as of 7.1 you can:

• keep several separate note threads on the same block,
• use rich text and @mention other users,
• reply in threads, edit or delete your own notes,
• resolve notes when they are handled and reopen them later.

Notes never appear on the published page. Administrators and Editors can see and add notes on all posts; Authors and Contributors only on their own posts; Subscribers cannot use them. By default, the post author gets an email when someone leaves a new note and users get an email when they are mentioned, which you can change under Settings > Discussion. Notes are not available in the Site Editor (templates and template parts).

Notes are asynchronous. Two people still cannot edit the same post at the same time the way they can in Google Docs. WordPress contributors announced in September 2026 that real-time collaboration will be explored as a feature plugin first, with no date for core. If you are deciding who should be able to review versus publish, our guide to WordPress user roles explains the permissions involved.

Keyboard shortcuts worth learning

You can open the full list inside the editor with Shift+Alt+H (Windows) or ⌃⌥H (Mac). These are the ones most editors use daily, taken from the official keyboard shortcuts documentation:

The full, current list is on the WordPress.org page Use keyboard shortcuts (Block Editor).

The Classic Editor plugin in 2026

Many older sites still use the Classic Editor plugin, which restores the pre-5.0 editing screen. As of October 2026 it is at version 1.7.0, has 8+ million active installs, is published by WordPress.org and was last updated on 28 May 2026. Its description still says it "will be fully supported and maintained until 2024, or as long as is necessary." In practice, it is still maintained, and no end date has been announced. Do not plan around a specific shutoff date, but do not plan around it lasting forever either.

A few practical points if you are on Classic Editor:

• New features, such as Notes, patterns, per-device visibility and the AI tools being built around the editor, are designed for blocks. The official "AI" plugin from WordPress.org, for example, states that the Classic Editor is not supported.
• Switching is usually low risk for content. Older posts open inside a Classic block, which has a "Convert to blocks" option, so you can convert one post at a time.
• The bigger migration work tends to be theme templates, shortcodes and custom meta boxes, not post content. Our comparison of Gutenberg vs the Classic Editor for development covers that in more depth.

Block editor vs Site Editor

The block editor is for content: posts, pages and custom post types. The Site Editor (Appearance > Editor) uses the same blocks to edit templates, headers, footers, navigation and global styles, but it is only available when a block theme is active. If your theme is a classic theme, you will use the block editor for content and the Customizer, widgets and menus for the rest. See our guides to the WordPress Site Editor and block themes vs classic themes for that side of the picture.

Tips for teams using the editor every day

• Build a small pattern library. Turn your most common layouts (service intro, testimonial row, FAQ, CTA) into patterns so writers do not rebuild them from scratch.
• Lock what should not move. Blocks can be locked against movement, removal or both (a lock icon then shows in the toolbar and List View), which helps protect layouts handed to clients.
• Name Group blocks in List View. "Hero," "Pricing," and "FAQ" are easier to navigate than ten nested "Group" entries.
• Use headings in order. The editor does not stop you from skipping heading levels, but screen readers and search engines rely on a logical outline.
• Keep plugin blocks in check. Every block plugin adds scripts and styles. Install the ones you use, not entire block libraries "just in case."
• Test on staging before major updates. With three major releases planned for 2026, editor changes arrive faster than they used to.

Conclusion

The block editor in 2026 is mature, fast to work in once you learn List View, patterns and a handful of shortcuts, and it is where all new WordPress features land. Notes make review cycles easier, but real-time co-editing is still not in core. If you are still on the Classic Editor, there is no forced deadline, though the gap between the two experiences keeps growing. For more guides like this one, browse the WordPress resource hub. If you would rather have someone set up patterns, editor permissions and a clean block-based build for you, eSEOspace offers WordPress website development.

Frequently asked questions