Classic Editor

Quick take

Classic Editor is a compatibility and workflow plugin, not a content-design upgrade. This Classic Editor review recommends it when your site, plugins or editorial team still depends on the pre-block WordPress editing screen.

Best fit: Classic Editor makes the most sense for sites and editorial workflows that still depend on TinyMCE, classic meta boxes or plugins built around the pre-block editor. A different tool will usually make more sense for teams that want modern block-based layouts, patterns, reusable blocks and full-site editing workflows.

Classic Editor pricing is simple because there is no premium tier. The real cost is strategic: staying on the classic workflow can be useful, but it may delay migration to block-based publishing.

What Classic Editor actually changes

Classic Editor restores the traditional WordPress Edit Post screen and TinyMCE-based editor. It also preserves support for plugins that extend the old editing screen or rely on classic meta boxes.

For sites built before Gutenberg, that can remove friction immediately because editors return to the interface and plugin behavior they already know.

Editor control for administrators and users

Administrators can choose the default editor for the site and decide whether users are allowed to switch editors. When switching is allowed, users can choose the editor per post.

WordPress also remembers the last editor used for a post so content does not unexpectedly open in a different editing environment the next time someone works on it.

Where Classic Editor still makes sense

It remains practical when a plugin, custom meta-box workflow or editorial process was built specifically around the old Edit Post screen. It can also reduce retraining for teams that only need straightforward text editing and do not use block-based layouts.

I would treat those as deliberate compatibility reasons rather than install Classic Editor automatically on every site.

Classic Editor pricing

Classic Editor pricing is free. Version 1.7.0 is distributed as an open-source community plugin through WordPress.org, with no separate Pro edition.

That makes the buying decision easy, but the workflow decision still matters because choosing Classic Editor means giving up many block-editor features on the content you edit with it.

What you give up by staying classic

The classic editor does not provide the modern block-first workflow for layouts, patterns, reusable design components and other Gutenberg-native editing features. Teams that rely heavily on those features will get little value from switching back.

There is also a long-term maintenance consideration. A legacy workflow can be stable, but it is worth understanding which plugins or processes actually require it so you are not keeping the old editor out of habit.

Compatibility vs modernization

This is the central Classic Editor decision. If a business-critical plugin or workflow depends on the classic screen, compatibility wins. If the site is already block-first, installing Classic Editor usually adds another editing path without solving a real problem.

Who should use it

I see Classic Editor fitting established WordPress sites with legacy editorial systems, custom meta boxes or plugins that still work better on the classic editing screen. It is also useful during phased migrations where not every content type is ready for Gutenberg.

PluginSuggest verdict

This Classic Editor review recommends the plugin when there is a specific compatibility or workflow reason to use it. It is mature, free and does exactly what its name suggests.

I would not install it on a new block-first site without a clear reason. In that case, learning and standardizing the modern editor is usually the better long-term choice.

Classic Editor FAQs