WordPress 7.1 Hides Classic Block from Inserter to Accelerate Block Editor Adoption

WordPress 7.1 introduces a subtle but impactful change: the Classic block is now hidden by default from the block inserter. This move marks a deliberate step away from legacy editing patterns inside the block editor, accelerating the transition toward a fully block-first content experience.

What Happened

As announced on June 23, 2026, WordPress 7.1 shipped a change that hides the Classic block from the block editor inserter by default. This means users cannot add new Classic blocks using the inserter interface, slash commands, or the block library, although the block itself remains registered and fully functional for existing content.

The Classic block continues to render and edit existing Classic content with no changes. The Classic Editor plugin and post types that do not use the block editor are unaffected by this change. The move is purely about steering new content creation away from the Classic block to encourage native block usage.

To preserve flexibility, WordPress introduced a filter wp_classic_block_supports_inserter allowing developers to re-enable the Classic block in the inserter either globally or conditionally based on post type. Additionally, a simple plugin named Enable Classic Block is available to toggle this behavior without code.

The decision was motivated by architectural consistency, reducing legacy block inflow, and reducing special-case maintenance overhead tied to the Classic block. Upcoming efforts will continue to improve migration tools and make the Classic block fully opt-in in the longer term.

Why This Matters

In real hosting environments and agency workflows managing multiple WordPress sites, transitioning fully to blocks is critical for long-term performance, maintainability, and compatibility. The Classic block has been an essential bridge during the block editor’s initial adoption but stands apart technically from other blocks.

Unlike native blocks that are individual nodes in the block tree, the Classic block encapsulates opaque HTML managed by TinyMCE embedded inside the block editor. This architectural inconsistency complicates block library improvements, introduces special-case code paths, and impacts editor performance and extensibility.

By hiding the Classic block from new insertions, WordPress reduces the creation of legacy content, effectively shrinking the Classic block footprint over time. This facilitates a cleaner, more uniform block editing environment and helps plugin and theme developers rely on consistent block behaviors without legacy exceptions.

Operationally, this also sets the stage for future optimizations. Loading TinyMCE conditionally only when Classic blocks are present can reduce scripts and assets loaded in the editor, decreasing load times and potential conflicts. This matters for agencies managing multiple sites where cumulative performance gains and maintenance simplicity translate into real cost savings.

The backward compatibility approach is key here. Existing content and workflows remain intact, and the Classic Editor plugin is untouched, avoiding disruption to users not yet ready or able to migrate. The opt-in nature of the change via filter or plugin provides an escape hatch for workflows dependent on the Classic block’s presence in the inserter.

From a business perspective, this move signals WordPress’s commitment to a block-first future while balancing legacy support pragmatically. It encourages plugin authors to focus development on block-native solutions and nudges site operators toward cleaner, more maintainable content structures.

What This Means for WordPress Users

Agencies and developers: If you manage sites or build plugins that rely on the Classic block, review your workflows and communicate this change to clients. Consider whether to keep the Classic block accessible in the inserter or begin migrating content to native blocks. Use the provided filter to control inserter visibility per post type if needed.

Site operators: You won’t see the Classic block as an option when adding new blocks, but existing Classic content remains editable. If you rely on Classic blocks for new content, you can enable it manually or via the Enable Classic Block plugin. However, evaluate whether converting to native blocks might improve content consistency and future-proof your site.

Plugin and theme authors: This change reduces the need for special-case Classic block handling, allowing you to simplify block integrations and focus on native block compatibility. Keep an eye on ongoing improvements to migration tools and the prospective full opt-in TinyMCE loading strategy.

Overall: This is a gradual but important shift away from legacy editing models toward a modern block-first editing experience. It improves editor architecture, performance, and long-term maintainability without breaking existing content or workflows.