What Is the WordPress Block Editor (Gutenberg)?
The WordPress block editor, also called Gutenberg, is the default content editor built into WordPress since version 5.0. It breaks a page or post into individual blocks, each a self-contained element like a paragraph, heading, image, button, or gallery, that you arrange and configure visually. Instead of one open text field, you assemble content block by block, seeing roughly how it will look as you build. It replaced the older classic editor and now powers full-site editing in modern block themes.
- Default since
- WordPress 5.0, released December 2018 (WordPress.org)
- Project name
- Gutenberg, after the printing-press inventor
- How content is stored
- As HTML wrapped in comment delimiters marking each block
- Powers
- Full Site Editing in block themes (WordPress Theme Handbook)
- Classic option
- The old editor stays available via the Classic Editor plugin
What the block editor is #
The WordPress block editor, known by its project name Gutenberg, is the standard way to create pages and posts in modern WordPress. Rather than typing into a single large text box, you build content from blocks, discrete units such as a paragraph, image, heading, list, button, table, or embedded video. Each block has its own settings for spacing, color, alignment, and typography, shown in a sidebar when the block is selected. You stack and reorder blocks to compose a page, and the editor previews the layout as you work, so what you see is close to the published result. This block model extends beyond posts: modern block themes let you edit headers, footers, and entire templates with the same interface. For a business running WordPress, the block editor is what your team will use daily to publish, and understanding it shapes how smoothly content updates go. Our /services/wordpress-development builds are set up to make the block editor predictable for non-technical staff.
How blocks work #
Each block is a small, independent component that WordPress knows how to render and store. When you add a paragraph block and type into it, WordPress saves that content wrapped in special HTML comments that mark where the block starts and ends and record its settings. This is why the block editor produces clean, structured markup rather than a tangled blob of HTML. Blocks come in categories, text, media, design, widgets, theme, and embeds, and plugins can register their own, which is how tools like WooCommerce or a forms plugin add product grids or contact forms as blocks. You can nest blocks inside container blocks such as Group or Columns to build multi-part layouts without touching code. Because settings live on each block, you control spacing and color per element instead of globally. This granularity is powerful once it clicks, though it means more clicking for simple posts. Understanding the block-and-container model is the key to using the editor efficiently and confidently.
Block editor versus classic editor #
The block editor replaced the classic editor, and the difference is fundamental. The classic editor gave you a single formatted text area powered by TinyMCE, much like a word processor, plus a separate HTML tab. It was simple and familiar, but layout beyond basic text meant shortcodes, custom HTML, or a page builder. The block editor instead treats every element as a configurable block, so columns, buttons, and media layouts are built in without extra tools. In practice, the classic editor is faster for plain text articles, while the block editor is stronger for visually structured pages. Some teams still prefer the classic experience and keep it via the official Classic Editor plugin, which Automattic has committed to supporting for now. Others adopt blocks fully to unlock site-wide editing. There is no single right answer; it depends on your content and comfort. If you are weighing a switch, our /services/wordpress-development team can migrate content and retrain staff so the transition does not disrupt publishing.
What block markup looks like #
Behind the visual editor, each block is saved as HTML wrapped in comment delimiters that name the block and store its attributes. Here is how a simple heading and paragraph are stored in the database.
<!-- wp:heading -->
<h2 class="wp-block-heading">Our Services</h2>
<!-- /wp:heading -->
<!-- wp:paragraph -->
<p>We build fast WordPress sites for local businesses.</p>
<!-- /wp:paragraph -->Patterns, synced blocks, and templates #
Three features make the block editor efficient at scale: patterns, reusable blocks, and templates. A block pattern is a pre-designed arrangement of blocks, such as a hero section or pricing table, that you insert and then edit freely; WordPress ships a library and themes add their own. A reusable block, now called a synced pattern, is a saved block you can drop onto many pages where editing one instance updates them all, ideal for a call-to-action or address block that must stay consistent. Templates and template parts define the structure of whole page types, like every blog post or the site footer, in block themes. Together these turn repetitive layout work into a few clicks and enforce brand consistency across a site. For a growing business, setting up a small library of on-brand patterns means staff can publish professional pages without a designer each time. We often build a custom pattern set during a /services/website-redesign so future content stays visually coherent without ongoing help.
Full Site Editing and block themes #
Full Site Editing, or FSE, extends the block editor from content into the whole site. In a block theme, you edit the header, footer, sidebars, and page templates using the same block interface you use for posts, all under the Editor menu. This means you can change your site-wide navigation, adjust the footer, or restyle every blog post without touching PHP template files or a separate customizer. Global Styles let you set fonts, colors, and spacing once and apply them everywhere. It is a significant shift from classic themes, where such changes required code or theme options. FSE is powerful but still maturing, and not every theme is a block theme; many popular themes remain classic and use the traditional Customizer. Whether FSE suits you depends on your theme and how much design control your team wants. For businesses that update their site often, a well-configured block theme can reduce reliance on a developer, though initial setup benefits from professional /services/wordpress-development to get the structure right.
Pros and cons for business owners #
For business owners, the block editor has clear trade-offs. On the plus side, it is built into WordPress at no extra cost, produces clean and portable markup, enables rich layouts without a paid page builder, and, through block themes, can control the entire site. It is also actively developed, so it keeps improving. On the downside, it has a learning curve for anyone used to the classic editor, simple text posts take more clicks, and older plugins or themes may not fully support blocks, causing occasional layout quirks. Very complex designs can still be easier in a dedicated builder like Elementor. Performance is generally good because blocks output lean HTML, but stacking many nested blocks can bloat a page if unmanaged. The honest summary is that the block editor is capable and free but rewards a little training. Weigh it against a page builder based on your team's skills and how visually complex your pages truly need to be.
Common frustrations and their fixes #
A few block editor frustrations come up repeatedly, each with a fix. If the editor feels slow or glitchy, an outdated plugin or theme that predates blocks is often the cause; updating or replacing it usually resolves it. If your layout looks different in the editor than on the live site, the theme may not load its front-end styles into the editor, a known gap that better themes handle. If staff find blocks fiddly, locking certain templates and providing ready-made patterns removes guesswork. If you truly prefer the old experience, the Classic Editor plugin restores it site-wide, and a Classic block can embed old-style content within the new editor. Accidental block deletion is recoverable through the editor's revision history. Most complaints trace back to either a training gap or a legacy plugin, both fixable. If your site fights you constantly in the editor, a /free-website-audit can pinpoint whether the theme, a plugin, or setup is the real culprit, and point to the specific fix rather than leaving you to guess through trial and error.
What we recommend #
For most new WordPress sites in 2026, we recommend embracing the block editor rather than fighting it. It is the platform's present and future, receives ongoing investment, and avoids the cost and lock-in of some paid builders. The practical path is to pair a solid block theme with a curated set of custom patterns so your team can build on-brand pages quickly and safely. Invest an hour in training staff on blocks, containers, and synced patterns; that small effort pays back every time someone publishes. If you run an older site on the classic editor and it works well, there is no urgent need to switch, but plan for blocks eventually, since classic support is a plugin, not a permanent guarantee. When you do move, migrate deliberately and test key templates. Our /services/wordpress-development team sets up block-based sites so publishing is genuinely easier for non-technical owners, which is the whole promise of the editor when it is configured well.
FAQ
Is Gutenberg the same as the block editor?
Yes. Gutenberg is the development project name; the block editor is what that project produced and shipped as the default WordPress editor in version 5.0. People use the two terms interchangeably. Gutenberg also refers to the standalone plugin where new editor features are tested before landing in core WordPress.
Can I still use the classic editor?
Yes. The official Classic Editor plugin restores the old TinyMCE experience site-wide, and Automattic has committed to supporting it while it remains widely used. You can also insert a Classic block inside the block editor to edit content the old way within an otherwise modern page when you need to.
Does the block editor work with page builders?
It can, though they overlap. Builders like Elementor or Divi replace the block editor on pages you build with them, storing layouts their own way. You can use the block editor for posts and a builder for complex pages on the same site, but running both adds weight, so pick a primary approach.
Will switching to blocks break my old posts?
Usually not. Existing classic content loads inside a single Classic block and continues to display correctly. You can convert it to blocks when you next edit it, or leave it as is. Test a few important pages after any editor change, since heavily custom HTML can occasionally need small adjustments afterward.
Do block themes require Full Site Editing?
Block themes are what enable Full Site Editing, letting you edit headers, footers, and templates with blocks. Classic themes do not offer it and use the traditional Customizer instead. You can run the block editor for content on a classic theme without FSE; FSE only comes with a block theme.
Is the block editor free?
Yes. The block editor ships with WordPress core at no cost, including patterns and, in block themes, Full Site Editing. You never pay a license fee to use it, unlike some premium page builders. Costs only arise if you hire help to set up custom patterns or a block theme for you.
How Local Web Advisor checks this for you
Is your own website getting web dev right?
Our free AI audit scans your site and tells you — in plain English — exactly what to fix for web dev and seven other areas, with the business impact and the fix for each. No login needed to start.
Run my free website audit →Was this helpful?