Block Editor vs Classic Editor: How to Decide for a Site You Have to Maintain
The Classic Editor is still officially supported as an official WordPress plugin, but only “until 2024, or as long as is necessary”. This language has been reiterated across multiple localized plugin descriptions and forum posts, making it a clearly time‑limited, transitional option rather than a permanent path.
WordPress sites have never had more editor options to choose from. With the introduction of the block editor (Gutenberg) in WordPress 5.0, WordPress fundamentally shifted how content is stored and edited. Alongside this new default, WordPress made available the Classic Editor plugin, an official plugin maintained by the WordPress core team that restores the previous "classic" editor and the "Edit Post" screen for posts and pages.
The Fork in the Road: Two Editors, One Platform
When the block editor was introduced, it represented a paradigm shift from a single monolithic content field to a block‑based approach. This move offered more flexibility and customization options, but it also meant a significant change for those accustomed to the Classic Editor.
The release of the Classic Editor plugin was a response to the concerns of users who needed to maintain continuity with existing workflows and plugins that were not yet compatible with the new block editor. Seeing this, the WordPress community has been left with a choice: to embrace the block editor or stick with the familiar Classic Editor. However, this choice is not as simple as it may seem, as the support and future of each editor are tied to WordPress's long-term roadmap.
How Long Classic Editor Really Has
The WordPress plugin description for Classic Editor states unequivocally: "Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, or as long as is necessary." This line appears across multiple locales, reinforcing the consistent commitment from WordPress.org.
However, the "as long as is necessary" qualifier is key. In an August 2021 announcement, WordPress Executive Director Josepha Haden said support would be extended by one year to 31 December 2023, with it not yet clear whether this would be the final deadline. This further echoes the support forum reply stating support is guaranteed "until at least 2022, or as long as is necessary," indicating the current peg of 2024 is temporary.
Initially, support was promised until 2022, with a commitment to re-evaluate the need for Classic Editor at that point. The lack of a guaranteed permanent support timeline, even as Classic Editor remains compatible with core releases up to WordPress 6.9.1, serves to underscore its transitional status.
What the Block Editor Assumes About Your Future
The block editor is clearly the long‑term default in WordPress's roadmap. One of the reasons for its dominance in the WordPress future is its flexibility; unlike the Classic Editor that presents a single content field, the block editor uses a block‑based model. This change means content is stored and handled differently, aligning it more closely with the modern approach to web development and content management.
WordPress even offers a Classic Block within the block editor, a TinyMCE‑style experience intended to serve as a "compatibility layer" for users who need a classic‑style editing experience. However, the very existence of the Classic Block within the block editor framework suggests that WordPress sees the block editor as the future, with the Classic Editor as a temporary bridge.
Maintenance Implications of Staying on Classic Editor
WordPress's official status of Classic Editor as a "fully supported and maintained" plugin is reassuring for the moment. The plugin is even signed for automatic updates.
However, this current maintenance status stands on a foundation of repeated annual extensions and "as long as necessary" language. A detailed look at how WordPress manages support suggests an expectation that plugins like this are on a path to deprecation, even if it’s not the immediate focus.
The very compatibility of the Classic Editor as an add-on to an ever‑evolving core introduces maintenance risks. As new WordPress versions roll out, those lingering on Classic Editor may face issues that the block editor community has already resolved.
Planning for Handover in a Block‑First World
As you consider a site's future, especially one that may need to be handed over to a new maintainer, the editor choice takes on additional weight. WordPress.com staff have suggested that the future of an editor cannot be predicted with certainty. The Classic Block within the block editor is a clear signal that WordPress aims to keep users within the block editor, even if they prefer a Classic‑style experience.
In this context, making a decision isn't about which editor you prefer now, but which path you anticipate will be most maintainable in the future. The block editor's dominance across WordPress's sites and future development efforts means a decision to stick with the Classic Editor may eventually necessitate a migration to the block editor, potentially increasing the long‑term maintenance burden.
How to Decide for a Site You Have to Maintain
When presented with the choice between the Classic Editor and the block editor, WordPress sites must weigh the official WordPress.org support windows, the state of the Classic Editor plugin, and the evolving role of the block editor. Advice should rest solidly on the documented positions, which currently offer a clear timeline of support through 2024, with recurring annual extensions allowed through phrases like "as long as is necessary".CONCLUSION
For sites that require long‑term maintainability and eventual handover, the decision on editors in WordPress is a decision tied to the future of the platform itself. The Classic Editor, despite being an official plugin, carries a clear expiration implied through support statements that point to 2024 as an endpoint with unspecified extensions. Meanwhile, the block editor has become the default, and within it, a Classic Block offers a smoother transition than staying with the standalone Classic Editor.
Ultimately, this leaves teams with a practical choice: align with WordPress's ongoing development by embracing the block editor now, or risk future maintenance hurdles if the Classic Editor support timeline shortens. At a minimum, planning should include regularly reviewing WordPress.org communication on editing tools, assuming that a complete shift to the block editor is likely necessary within the next few years.