# How to Switch to the Classic Editor with JetHost Total Care

> Canonical: https://jethost.com/kb/disable-gutenberg-classic-editor-with-jethost-total-care/ · Last modified: 2026-10-21T11:18:07+00:00

Prefer the old WordPress editor? The **Disable Gutenberg and Use Only Classic Editor** option in [JetHost Total Care](https://wordpress.org/plugins/jethost-total-care/) switches your site back to the Classic Editor on any [JetHost WordPress hosting](https://jethost.com/hosting-for-wordpress/) plan. This guide shows how and when to use it.

## Switch to the Classic Editor

1. In your WordPress dashboard, open **JetHost Total Care → Admin Enhancements**.
2. Toggle on **Disable Gutenberg and Use Only Classic Editor**.

![Disable Gutenberg and use only Classic Editor option in JetHost Total Care](https://jethost.com/wp-content/uploads/2026/10/jtc-opt-classic-editor.png)With it enabled, posts and pages open in the familiar Classic Editor – a single formatting toolbar over a text area – instead of the block-based Gutenberg editor. You don’t need to install the separate Classic Editor plugin; this one setting handles it.

## Should you use it?

Choose the Classic Editor if your workflow, theme, or page builder was built around it, or if your team simply finds it easier. Keep Gutenberg if you rely on blocks or a block-based theme. Switching doesn’t delete content – existing block posts still open and work – so you can try one mode and change back if it doesn’t suit you. Page builders like Kadence and Elementor keep working either way.

## Gutenberg vs the Classic Editor

Since WordPress 5.0, the default editor is Gutenberg, which builds content from individual blocks. The older Classic Editor is a single rich-text area with a familiar toolbar, much like a word processor. Neither is “better” – they suit different workflows. Teams that learned WordPress on the Classic Editor, sites built around it, or content that was written before blocks often feel faster and more predictable in Classic mode, which is exactly what this option restores.

## Performance and compatibility

There’s a light performance angle too: Gutenberg loads block-editor assets in the admin and block-styling CSS on the front end, which the Classic Editor doesn’t. On a simple, content-only site that never uses blocks, Classic can mean a slightly lighter page. Keep Gutenberg if you rely on blocks or a block-based theme, where it’s the better fit. Switching modes never deletes content – existing block posts still open and work – and page builders such as Kadence and Elementor keep working either way, so you can try one and change back safely.

## JetHost Experts Tip

Moving an older site to JetHost whose content was written in the Classic Editor? Turning this on keeps everything editing exactly as the previous team expected, with no surprises.

## Need More Help?

Editor not switching as expected? [Reach out](https://jethost.com/contact-us/) and our team will help.