Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Guide

Classic Editor vs Block Editor: Should You Switch Back?

Short answer

To go back to the classic editor, install the official Classic Editor plugin from WordPress.org and activate it. Then go to Settings Writing, set Default editor for all users to Classic Editor, and save. Your posts stay intact, and you can return to the block editor by changing the same setting.

Key takeaways

  • The block editor became the default after WordPress 5.0 launched in December 2018, replacing the classic editor.
  • The official Classic Editor plugin restores the old editor and Edit Post screen, and version 1.7.0 was updated on 28 May 2026.
  • Set the default editor in Settings Writing, and set Allow users to switch editors to No to keep everyone on the classic screen.
  • The plugin does not work with full site editing and block themes, which rely on blocks.
  • Classic posts open as a single Classic block in the block editor, and Convert to blocks splits them into separate blocks.
  • WordPress.org recommends PHP 8.3 or greater, while WordPress still runs on PHP 7.4 and later.

Should you switch back to the classic editor?

Switch back if you write mostly plain text and the block editor slows you down.

The classic editor suits simple posts, short updates, and sites that rely on old-style meta boxes. The block editor suits rich layouts with columns, galleries, and patterns. Your content stays on your site either way, so the choice is about how you like to write.

WordPress.org's block editor guide says the block editor became the default after WordPress 5.0 launched in December 2018, and it replaced the classic editor (WordPress Block Editor). That date matters because posts written before it were all classic posts, and many older sites still carry them.

What is the classic editor, and how is it different from the block editor?

The classic editor is one text field with Visual and Text tabs, while the block editor builds a post from separate blocks.

A classic post is a single field where you type, paste, and format text in one place. A block post is a set of units, and each paragraph, image, heading, list, video, or gallery is its own block that you can move or style on its own.

The WordPress.org block editor guide lists blocks for paragraphs, images, headings, lists, videos, galleries, and more, and it says you can control the layout of the blocks to build pages (WordPress Block Editor). The classic editor does not offer that block layout work, and that is the main trade-off.

The Classic Editor plugin page describes the old screen as the previous WordPress editor and the old-style Edit Post screen, with TinyMCE and meta boxes (Classic Editor). Meta boxes are the small panels below the text field, such as the boxes for categories, tags, and the featured image.

FeatureClassic editorBlock editor
Editing unitOne text fieldSeparate blocks
Best forPlain text postsRich layouts and patterns
Layout toolsShortcodes and HTMLColumns, galleries, and patterns
Site EditorNot available with block themesNeeds a block theme
Learning curveShort for plain writingLonger, with more controls

What do you need before you switch back?

You need an administrator account, a backup, and a check of your theme type.

An administrator account lets you install plugins and change the writing settings. An editor or author account cannot do either step on its own, so ask an administrator if you do not have that role.

Make a backup before you change the editor, and keep a copy you can restore. Our guide to backing up WordPress walks through the options before you change anything on a live site.

Check your theme type next, because the plugin does not work with full site editing and block themes. The Classic Editor plugin page states that it does not work with full site editing and block themes, since block themes rely on blocks (Classic Editor).

How to check your theme type

  • Open Appearance in your dashboard.
  • If you see Editor in that menu, you use a block theme.
  • If you see Customize instead, you use a classic theme.

WordPress.org's Site Editor guide says the Site Editor is only available when you install and activate a block theme (Site Editor).

A block theme uses blocks for all parts of a site, including navigation, header, content, and footer. If your site uses a block theme, the classic editor will not give you the Site Editor, and you should stay with blocks for design work.

How do you install the Classic Editor plugin?

Install the official Classic Editor plugin from WordPress.org, then activate it.

The plugin is the official route back, and it is maintained by the WordPress team. The plugin page says it is an official plugin maintained by the WordPress team that restores the previous editor and the Edit Post screen (Classic Editor).

  1. Go to Plugins → Add New in your dashboard.
  2. Search for “Classic Editor” and check that the author is WordPress.org.
  3. Click Install Now, then click Activate.
  4. Open Settings → Writing to set the default editor.

Version 1.7.0 is the current version as of November 2026, and the plugin page shows it was updated on 28 May 2026. The 1.7.0 changelog notes a hotfix for crowded elements in the publishing actions area in WordPress 7.0.

The plugin page also states that the plugin will be fully supported and maintained until 2024, or as long as is necessary. That wording is still on the page as of November 2026, and the May 2026 update shows maintenance is still happening.

How do you set the classic editor as the default for everyone?

Open Settings → Writing, pick Classic Editor under Default editor for all users, and save.

  1. Go to Settings → Writing in your dashboard.
  2. Find Default editor for all users.
  3. Select Classic Editor.
  4. Set Allow users to switch editors to No if everyone must use the classic screen.
  5. Click Save Changes.

The plugin page says administrators can select the default editor for all users, and the settings live on the Settings → Writing screen (Classic Editor). By default, the plugin hides the block editor and restores the classic editor when you use a classic theme.

Each post opens in the last editor used to edit it, regardless of who edited it last. The plugin page lists that rule as one of the main behaviours, and it keeps the editing experience steady when several people work on the same post.

How do you let some users keep the block editor?

Set Allow users to switch editors to Yes, then let each user pick a default in their profile.

  1. Go to Settings → Writing.
  2. Set Default editor for all users to Classic Editor.
  3. Set Allow users to switch editors to Yes.
  4. Click Save Changes.
  5. Ask each user to open Users → Profile and pick a default editor under Personal Options.

The plugin page says administrators can allow users to change their default editor, and users can then choose which editor to use for each post (Classic Editor). This mixed setup suits a slow move, where one team writes in the classic editor and another keeps blocks.

Version 1.6.4 added support for administrators to choose the default editor for other users, as shown in the plugin changelog. That change helps on team sites where an administrator sets the editor for each person instead of asking everyone to change a profile setting.

How do you switch editors for one post or page?

Use the Switch to classic editor link in the block editor menu, or the Switch to block editor link in the classic editor sidebar.

In the block editor, open the three-dot menu at the top right and choose Switch to classic editor. The plugin page says that link sits in the main block editor menu. In the classic editor, use the Switch to block editor link in the Editor box in the sidebar.

This per-post switch only works when switching is allowed. If Allow users to switch editors is set to No, the links do not appear, and every post opens in the site default.

If you compare the two editors first, read our Gutenberg vs page builders guide for how block editing differs from builder tools.

Our Gutenberg vs Elementor guide covers one common builder comparison.

What happens to your old posts and pages after you switch?

Your old posts stay intact, and block posts open as a single Classic block when you edit them in the block editor.

Switching the default editor does not delete or rewrite your content. A post written in the classic editor keeps its text, images, and links, and it opens in the classic editor when that is your default.

WordPress.org's Classic block guide says the Classic block looks just like the classic editor, but in block form, and custom TinyMCE buttons are found in this block (Classic block). That block is what you see when a classic post opens in the block editor.

How to turn a Classic block into separate blocks

  • Open the post in the block editor.
  • Click inside the Classic block.
  • Open the block toolbar options and choose Convert to blocks.
  • Review each new block, then save the post.

The Classic block guide says you can add a Classic block with the Block Inserter or by typing /classic in the editor. The Convert to blocks option converts the content to blocks.

Check headings, images, and lists after a conversion, because a complex post may need a small fix by hand.

How do you check that the switch worked?

Open a post and confirm it loads in the classic editor, with the Visual and Text tabs at the top.

  1. Go to Posts → All Posts and open a draft post.
  2. Check that you see one text field with Visual and Text tabs.
  3. Check that the meta boxes for categories, tags, and the featured image sit below or beside the field.
  4. Create a new post from Posts → Add New and confirm it also opens in the classic editor.
  5. Ask one other user to open a post if your site has a team.

If a post still opens in the block editor, recheck Settings → Writing and confirm the default is Classic Editor and switching is set to No. Also check the post itself, since each post opens in the last editor used to edit it.

If the plugin is old or inactive, check its status before you blame the settings. Our guide on finding abandoned WordPress plugins shows how to check a plugin's last update date and its tested-up-to version.

When should you stay with the block editor instead?

Stay with the block editor if you use a block theme, build rich layouts, or need new editor features.

A block theme needs blocks for its templates, header, and footer, and the Classic Editor plugin does not work with full site editing and block themes.

The Theme Handbook says a block theme is a new theme from WordPress 5.9, built mainly with HTML and a theme file, and composed entirely of blocks (Theme Handbook).

The block editor is also the part of WordPress that gets new features. The Gutenberg versions guide in the Block Editor Handbook lists which Gutenberg version ships in each WordPress release, and WordPress 6.8 ships with Gutenberg 20.4 (Gutenberg versions in WordPress).

The Gutenberg project itself lives on GitHub, where its code and issues are kept (Gutenberg on GitHub).

WordPress.com's editors guide adds a clear warning for hosted sites: the Classic Editor was the default before the WordPress editor launched, it is still available, but it has fewer features and is no longer actively developed (About WordPress editors).

That note covers WordPress.com, not self-hosted sites, but it shows where development effort goes.

Stay with blocks if your site relies on patterns, block-based widgets, or plugins that only work in the block editor. Switching back would hide those tools, and you would lose the layout work they provide.

What mistakes should you avoid?

Do not switch on a live site without a backup, and do not expect the plugin to change your theme or your content.

  • Do not install a copy of the plugin from an unknown site; use the WordPress.org listing only.
  • Do not set the default to Classic Editor on a block theme and expect the Site Editor to keep working.
  • Do not run Convert to blocks on every old post at once; convert one post, review it, and then decide.
  • Do not forget the per-user setting when switching is allowed, since a user profile can override the site default.
  • Do not skip the PHP check on an old site.

WordPress.org's requirements page recommends PHP 8.3 or greater, with MariaDB 10.11 or greater or MySQL 8.0 or greater (WordPress Requirements).

It also says WordPress still runs on PHP 7.4 and MySQL 5.5.5, but those versions have reached end of life. The Classic Editor plugin itself requires WordPress 4.9 or newer, so an old install may need a WordPress update first.

The PHP project's own support page lists PHP 8.3 with security fixes until 31 December 2027, and PHP 8.4 with security fixes until 31 December 2028 (PHP Supported Versions).

If your host still runs PHP 7.4, fix that before you judge either editor, and read our guide on which PHP version to use for WordPress for the next step.

Frequently asked questions

Is the Classic Editor plugin still supported in November 2026?

Yes, it is still maintained. The plugin page lists version 1.7.0, updated on 28 May 2026, with a hotfix for WordPress 7.0. The page still says the plugin will be fully supported and maintained until 2024, or as long as is necessary, and the May 2026 update shows maintenance is still happening.

Will switching back to the classic editor delete my posts?

No. Switching the default editor changes the editing screen, not your stored content. Old posts keep their text, images, and links. When a classic post opens in the block editor, it appears as a single Classic block, and you can turn it into separate blocks with Convert to blocks if you want.

Can I use the classic editor with a block theme?

No, not for site design. The Classic Editor plugin does not work with full site editing and block themes, because block themes rely on blocks. You can still edit posts in the classic editor on a classic theme, but the Site Editor needs an active block theme, so a block theme site should stay with the block editor.

How do I go back to the block editor after switching?

Go to Settings Writing and set Default editor for all users to Block editor, then save. If switching is allowed, you can also use the Switch to block editor link in the classic editor sidebar for one post. Each post opens in the last editor used to edit it, so check a post after you change the setting.

Does the classic editor work on WordPress.com?

WordPress.com treats the two editors differently from self-hosted WordPress. Its editors guide says the Classic Editor was the default before the WordPress editor launched, is still available, but has fewer features and is no longer actively developed. On a self-hosted site, use the official Classic Editor plugin from WordPress.org instead.

Sources

  1. Classic Editor WordPress.org
  2. WordPress Block Editor WordPress.org
  3. Classic block WordPress.org
  4. Site Editor WordPress.org
  5. Gutenberg versions in WordPress WordPress Developer Resources
  6. Theme Handbook WordPress Developer Resources
  7. About WordPress editors WordPress.com
  8. PHP Supported Versions PHP.net

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test