Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
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
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Visual Editor WordPress Not Working: Causes and How to Fix It

Visual Editor WordPress Not Working: Causes and How to Fix It

Short answer

First check that Disable the visual editor when writing is unticked in your profile. If it is, test for a plugin or theme conflict, clear browser and site caches, and make sure your CDN is not hiding your browser details from WordPress.

Key takeaways

  • The visual editor can be turned off per user in the profile.
  • CDNs that strip the User-Agent header can hide the Visual tab.
  • Plugin and theme scripts often break the editor toolbar.
  • Setting CONCATENATE_SCRIPTS to false can fix script loading issues.
  • In the block editor, the code view can be toggled on by accident.

Why is the WordPress visual editor not working?

The WordPress visual editor usually fails because it is turned off in your profile, a plugin or theme script clashes with it, a cache or extension blocks it, or a CDN hides your browser.

The visual editor can mean two things. In the Classic Editor, it is the Visual tab that shows formatted text, next to the Text tab with raw HTML. In the block editor, it is the normal editing view, as opposed to the Code editor view.

The fixes overlap, but start by working out which one you use.

SymptomEditorMost likely cause
Visual tab missing, only Text showsClassicProfile setting or browser detection
Visual tab blank or toolbar missingClassicJavaScript conflict or blocked scripts
Buttons do nothing when clickedClassicPlugin or theme script error
Block editor shows raw HTMLBlockCode editor mode switched on
Block editor white screenBlockPlugin conflict, REST API or cache

For wider block editor failures, see our guide on the WordPress editor not working. This article focuses on the visual view itself.

Is the visual editor turned off in your profile?

Yes, check this first, because each user has a Disable the visual editor when writing option, and when it is ticked the Visual tab disappears for that user only.

To check:

  1. Go to Users > Profile.
  2. Look for Visual Editor near the top.
  3. Untick Disable the visual editor when writing.
  4. Click Update Profile.
  5. Open a post again.

This setting is per user. If one person on your team cannot see the Visual tab but others can, this is almost always the reason.

Developers can see how WordPress decides this in the user_can_richedit function reference. That function checks the profile setting and the browser.

Is a CDN or proxy hiding your browser from WordPress?

A CDN or reverse proxy that strips or changes the browser's User-Agent header can make WordPress think your browser cannot run the visual editor, so it hides the Visual tab.

WordPress only loads the visual editor for browsers it recognises. It reads the User-Agent header to decide.

Some CDN setups, especially when they cache admin pages or rewrite headers, send WordPress a generic User-Agent. WordPress then falls back to the Text tab only.

Fixes:

  • Exclude /wp-admin/ from CDN caching and header changes.
  • Make sure your CDN forwards the original User-Agent header to the server.
  • Test by visiting the server directly, if your host gives you a temporary URL.

If the Visual tab appears on the temporary URL but not on your domain, the CDN is the cause.

Is a plugin or theme conflict breaking the editor?

A plugin or theme that loads broken or outdated JavaScript in the admin can stop the visual editor from loading its toolbar, show a blank box, or make buttons stop working.

The Classic Editor runs on TinyMCE, a JavaScript editor library from Tiny. Any script error that fires before it loads can stop it in its tracks.

Test for a conflict:

  1. Install the Health Check and Troubleshooting plugin, or use a staging site.
  2. Turn on troubleshooting mode, which disables plugins for you only.
  3. Open the editor. If it works, a plugin is the cause.
  4. Turn plugins back on one at a time until the editor breaks.
  5. Switch to a default theme to test the theme too.

Plugins that add editor buttons, shortcodes or page builder features are the usual suspects. Our guide on fixing a plugin conflict covers the full method.

Are blocked or cached scripts stopping the editor?

Yes, a browser extension, an old cached script, or WordPress script concatenation can stop the editor's JavaScript from loading properly.

Try these in order:

  • Use a private window. It runs without most extensions and with a fresh cache.
  • Turn off ad blockers and privacy extensions for your own site.
  • Clear your browser cache fully.
  • Clear your site cache and CDN cache. Our guide on clearing cache in WordPress covers each layer.

WordPress joins admin scripts into one request to save time. On some servers this breaks. Add this line to wp-config.php to turn it off as a test:

define( 'CONCATENATE_SCRIPTS', false );

If the editor works after that, leave the line in place and ask your host about server compression or security rules that alter scripts. The wp-config.php documentation explains this constant.

How do you read the error that is breaking the editor?

Open your browser's developer tools, go to the Console tab, reload the editor and look for red errors that name a file, which usually points to the plugin or theme at fault.

In Chrome, press F12 or right-click and choose Inspect. Google's guide to the Chrome DevTools Console explains what you are looking at.

Look for paths such as /wp-content/plugins/plugin-name/. That folder name tells you which plugin threw the error.

Errors about tinymce or wp-tinymce point to the editor files themselves. Those can mean a failed update. Reinstall WordPress from Dashboard > Updates > Re-install to replace core files.

For server-side errors, turn on debug logging. Our guide on enabling debug mode shows where to add the settings.

Why does the block editor show code instead of the visual view?

The block editor shows raw HTML when the Code editor view is switched on; switch back from the Options menu or press Ctrl+Shift+Alt+M on Windows or Cmd+Shift+Option+M on Mac.

To switch back:

  1. Click the three dots in the top-right corner of the editor.
  2. Under Editor, choose Visual editor.

This setting is remembered per user, so it can seem like the editor broke when someone simply pressed the shortcut by mistake.

If the visual view loads but blocks show This block contains unexpected or invalid content, that is a different issue. Our guide to the WordPress editor not working covers block recovery.

To learn more about how the block editor works, see what the WordPress block editor is.

Should you switch between the Classic and block editors?

Switching editors can be a workaround, but fix the root cause first, because the same plugin or cache problem often breaks both editors.

If you prefer the Classic Editor, the official Classic Editor plugin restores it. Our guide on going back to the classic editor shows the settings.

If you want the block editor back after using Classic, see enabling the Gutenberg editor.

Page builders such as Elementor have their own editors. If those fail to load, see our guide on Elementor editor not loading.

What should you try if nothing works?

If none of the steps fix it, reinstall WordPress core, test on a fresh browser profile, check the server error log, and ask your host whether a firewall rule is blocking editor scripts.

A final checklist:

CheckWhy it matters
Profile settingHides the Visual tab per user
Private windowRules out extensions and browser cache
Troubleshooting modeRules out plugins and theme
CONCATENATE_SCRIPTSRules out script joining problems
CDN and proxyRules out User-Agent and cache issues
Re-install coreReplaces damaged editor files
Host firewallRules out blocked admin requests

Web application firewalls sometimes block editor requests that contain code, such as script tags or long HTML. Your host can check their logs for blocked requests at the time you tried to edit.

Frequently asked questions

Why is the Visual tab missing in WordPress?

Usually the Disable the visual editor when writing option is ticked in your profile, or WordPress did not recognise your browser because a CDN or proxy changed the User-Agent header. Check the profile first, then test without the CDN.

Why does the visual editor work for one user but not another?

The visual editor setting is saved per user, so one profile can have it turned off. Browser extensions and cache also differ between people. Check that user's profile setting and ask them to try a private window.

Can a theme break the WordPress visual editor?

Yes. Themes can load scripts and styles in the admin, and an error there can stop the editor from loading. Switch to a default theme briefly to test. If the editor works, contact the theme developer or check for an update.

Will reinstalling WordPress fix the visual editor?

It can, if editor files were damaged during an update. Use the Re-install option on the Updates screen, which replaces core files without touching your content, plugins or themes. Take a backup first to be safe.

Is the Classic Editor still supported?

The Classic Editor plugin is still available and maintained, though the block editor is the default in WordPress. Check the plugin page for its current support status, and plan for the block editor in the long term.

Sources

  1. user_can_richedit() WordPress Developer Resources
  2. Editing wp-config.php WordPress Developer Resources
  3. Classic Editor plugin WordPress.org Plugins
  4. Console overview Chrome for Developers
  5. TinyMCE Tiny

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

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.