The Classic Editor is the old, familiar content editing interface in WordPress that served as the standard for many years. It looked like a simple text editor (based on TinyMCE) – similar to Word or older versions of CMSs. It allowed you to write text, insert images, format, and use shortcodes all in one field. Many people valued it for its simplicity and ease of use, but what about now?

In this article, you’ll learn about the history of the Classic Editor and find out if it still makes sense to use it in 2026 (you’ll still find it in WooCommerce, for example). Enjoy the read!

When was the Classic Editor replaced?

The change took place with the release of WordPress 5.0 (in December 2018). At that time, Gutenberg (now called the Block Editor) became the default editor. Gutenberg completely changed the approach to editing:

  • content is built using “blocks” (paragraph, heading, image, gallery, button, columns, etc.);
  • it allows for visual layout design without coding;
  • it is the foundation of themes based on Full Site Editing (FSE) – that is, editing the entire site (headers, footers, templates) using blocks.

The introduction of Gutenberg sparked a huge debate and resistance from the community. Many users complained about its initial flaws, slower performance with simple posts, and compatibility issues with older plugins. However, there was no turning back from the changes.

What about the Classic Editor plugin?

To ease the transition, WordPress has officially released the Classic Editor plugin. This is an official plugin maintained by the WordPress team. Despite discussions about its imminent end, the plugin has been doing surprisingly well for many years. Moreover, data from March 2026 shows over 9 million active installations!

The plugin continues to support the latest versions of WordPress (tested up to 6.9+), and due to its popularity, official support has been extended multiple times – currently at least until the end of 2026 (and likely longer, simply as long as it’s needed).

After installation, you can set the Classic Editor as the default for all users or allow them to choose. The plugin restores the old interface for posts, pages, and other content types. Old posts written in the Classic Editor are automatically opened in classic mode (or as a single “Classic” block in Gutenberg).

screenshot from the WordPress.org repository


Is the classic editor still used anywhere?

Yes – largely in WooCommerce. The default product description editor in WooCommerce is still based on the classic WordPress editor (TinyMCE). It is not a full Block Editor, which means that editing product descriptions is simple but less visually flexible. However, we can enable the Block Editor for WooCommerce products using additional code or a builder.

In 2026, WooCommerce also has an experimental “New Product Editor” (beta), but the classic product description interface still dominates in many stores. This may change in the future. And if you use the Classic Editor plugin site-wide, your WooCommerce products will also be edited in the old style.

Does the Classic Editor make sense in 2026?

Only two situations come to mind where it’s worth using the classic editor. The first is when you run a simple blog or content site and don’t need complex layouts. The second is when you have long-time users or editors who don’t want to learn blocks. However, you need to keep in mind that support for it will eventually end, and WordPress has been tied to the block editor for years.

Besides, more and more new features and plugins work only with blocks. There is always a risk of compatibility issues in the future (though support is solid for now), and old content in Classic Block in Gutenberg is less convenient to edit further. It’s better to adapt it to the block view.

Summary

The Classic Editor hasn’t disappeared and remains fully functional in 2026 thanks to an official plugin. In WooCommerce, product descriptions often still use the classic interface. It makes sense to keep it if simplicity and ease of use are your priorities. However, for most new projects and long-term development, we strongly recommend switching to Gutenberg – that’s the direction the entire WordPress ecosystem is heading.

Natalia Czubik
Latest posts by Natalia Czubik (see all)

Categorized in:

WordPress,