How to Switch Back to the Classic Editor in WordPress

Updated 4 November 2026 · Standard formula, shown below

If you prefer the familiar editing experience of the original WordPress editorâ€”with its single text box, toolbar buttons, and no block structureâ€”this guide shows you how to switch back. You’ll need either the free Classic Editor plugin (recommended for most sites) or the ability to edit your theme’s functions.php file (for a code-based approach). Both methods are safe and reversible, and they work on both self-hosted WordPress.org sites and WordPress.com business plans.

What You’ll Need

Administrator access to your WordPress dashboard (you must be able to install plugins or edit theme files).
For the plugin method: a stable internet connection to download the plugin from the WordPress repository.
For the code method: a code editor (like Notepad++ or a plain text editor) and FTP access or the built-in Theme Editor in WordPress.

Step-by-Step

Method 1: Using the Classic Editor Plugin (Recommended)

Log in to your WordPress admin dashboard. Go to wp-admin by adding /wp-admin to your site’s URL (e.g., yoursite.com/wp-admin).
Navigate to Plugins â†’ Add New. In the left sidebar, hover over â€œPluginsâ€� and click â€œAdd Newâ€�.
Search for â€œClassic Editorâ€�. In the search box on the top right, type â€œClassic Editorâ€� and press Enter. The official plugin is by the WordPress Contributors team and has the description â€œEnables the Classic Editorâ€�.
Install the plugin. Click the â€œInstall Nowâ€� button next to the plugin’s name. Wait a few seconds for the installation to complete.
Activate the plugin. After installation, click â€œActivateâ€�. The plugin is now active.
Configure the plugin settings (optional but recommended). Once activated, go to Settings â†’ Writing. Scroll down to the â€œClassic Editorâ€� section. You’ll see two options:
- Default editor for all users: Choose â€œClassic Editorâ€� to make it the default for everyone.
- Allow users to switch editors: If you check this box, each user can choose their preferred editor in their profile. For a uniform experience, leave it unchecked.
Click â€œSave Changesâ€� at the bottom.
Verify the change. Go to Posts â†’ Add New (or Pages â†’ Add New). You should see the classic editor interface with a single text box and the toolbar at the top, not the block-based Gutenberg editor.

Method 2: Adding Code to functions.php (No Plugin)

Back up your site. Before editing any theme files, create a full backup of your WordPress files and database. This is a safety net in case something goes wrong.
Access the Theme Editor. In your WordPress admin, go to Appearance â†’ Theme Editor. If you don’t see it, you may need to enable it via FTP or your hosting file manager.
Select your active theme. In the top right corner, ensure your active theme is selected. Click â€œSelectâ€�.
Open the functions.php file. In the list of theme files on the right, click on functions.php.
Add the code snippet. At the very end of the file, before the closing ?> tag (or at the end if there is no closing tag), paste the following code:
```
add_filter('use_block_editor_for_post', '__return_false', 10);
add_filter('use_block_editor_for_post_type', '__return_false', 10);
```
This code tells WordPress to disable the block editor for all posts and post types, reverting to the classic editor.
Save the file. Click the â€œUpdate Fileâ€� button. If you’re using FTP, save the file locally and upload it, overwriting the server version.
Test the change. Go to Posts â†’ Add New. The classic editor should now appear.

Common Mistakes

Editing the wrong theme’s functions.php. If you have a child theme, you must edit the child theme’s functions.php, not the parent theme’s. Changes to the parent theme are overwritten when the theme updates.
Adding code to the wrong file. Some users accidentally paste the code into a theme’s style.css or a plugin file. The code must go only in functions.php of the active theme (or child theme).
Forgetting to save settings after activating the plugin. Even after activating the Classic Editor plugin, you may need to go to Settings â†’ Writing and explicitly select â€œClassic Editorâ€� as the default. If you skip this, the plugin might still use the block editor for new posts.
Using a page builder that requires the block editor. Some page builders (like Elementor or Beaver Builder) have their own interfaces and may not work with the classic editor for certain templates. This is not a mistake per se, but a compatibility consideration.

Tips

Use the plugin for simplicity. The plugin method is the safest and easiest. It also automatically handles future WordPress updates, so you don’t have to worry about the code breaking.
Keep the block editor available for certain users. If you have multiple authors, you can allow them to choose their editor by checking â€œAllow users to switch editorsâ€� in the plugin settings. This gives flexibility without forcing everyone to change.
Test on a staging site first. If you’re using the code method, try it on a staging copy of your site before applying it to your live site. This minimizes the risk of downtime.
Know that the classic editor is still supported. The Classic Editor plugin is actively maintained by WordPress and will continue to work for the foreseeable future. You’re not using an outdated or insecure method.

Troubleshooting

The block editor still appears after activating the plugin. First, clear your browser cache and any caching plugins (like WP Rocket or W3 Total Cache). If it still doesn’t work, go to Settings â†’ Writing and confirm the â€œDefault editor for all usersâ€� is set to â€œClassic Editorâ€�. Also, check that the plugin is active under Plugins â†’ Installed Plugins.
A white screen or fatal error appears after adding code to functions.php. This usually means there’s a syntax error. Immediately access your site via FTP or your hosting file manager, locate the functions.php file, and remove the lines you added. If you can’t access the file, use your hosting’s file manager or a recovery tool provided by your host. Always back up the file before editing.
The classic editor appears for posts but not for pages. The code snippet above disables the block editor for all post types. If you’re using the plugin, ensure you haven’t set a specific post type override in the plugin settings. If you’re using custom post types (like portfolios or testimonials), you may need to add additional filters for those post types.
The classic editor is missing some buttons or features. The classic editor relies on the â€œTinyMCEâ€� editor. Some plugins (like those that add custom buttons) may not be compatible. Check if any of your plugins are conflicting by deactivating them one by one and testing.

Frequently Asked Questions

Will the Classic Editor plugin stop working in the future?

No. The Classic Editor plugin is officially maintained by the WordPress team and will be supported until at least 2024, and it’s likely to continue beyond that. It’s the recommended way to keep the classic editor.

Does switching to the classic editor affect my existing content?

No. Your existing posts and pages will remain exactly as they are. The classic editor will simply display them in the classic format. If you had used blocks, they will still be there, but you’ll see the HTML or the block markup in the classic editor.

Can I use the classic editor for some posts and the block editor for others?

Yes, if you enable the â€œAllow users to switch editorsâ€� option in the plugin settings, each user can choose their preferred editor in their profile. However, you cannot set different editors per individual postâ€”it’s a global setting per user.

Is the classic editor less secure than the block editor?

No. The classic editor is just as secure. Security depends on how you manage your site, not on the editor you use. The Classic Editor plugin receives security updates just like any other WordPress component.

What if I’m using WordPress.com (not self-hosted)?

If you have a WordPress.com Business or eCommerce plan, you can install the Classic Editor plugin just like on a self-hosted site. For lower-tier plans, the plugin is not available, but you can still use the â€œClassic Editorâ€� option in the site’s settings if your plan supports it (check your plan’s features).

Will my custom meta boxes and custom fields still work?

Yes, the classic editor fully supports custom meta boxes and custom fields. In fact, many developers prefer the classic editor because it makes custom meta boxes easier to work with compared to the block editor.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.