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

WordPress Editor Not Working? How to Fix It Step by Step

WordPress Editor Not Working? How to Fix It Step by Step

Short answer

When the WordPress editor is not working, the cause is usually a plugin or theme conflict, a blocked REST API, a browser extension or cached script, or low PHP memory. Clear the browser cache and try a private window first, then turn off plugins one by one and check Site Health for REST API errors.

Key takeaways

  • The block editor runs in your browser and talks to the server through the REST API, so both sides can break it.
  • A private browser window quickly rules out extensions and cached scripts.
  • Plugin and theme conflicts are the most common cause of a blank or crashing editor.
  • Security plugins, firewalls and wrong site URLs can block the REST API and stop saving.
  • The browser console and the debug log show the exact error, which saves guessing.

What does “editor not working” usually look like?

The WordPress editor can fail in a few distinct ways, and the symptom tells you whether to look at the browser, a plugin or the server.

Match what you see to the likely cause:

SymptomMost likely cause
White or blank screen when opening a postJavaScript error from a plugin, theme or browser extension
“The editor has encountered an unexpected error”A block or plugin script crashed
“Updating failed” or “not a valid JSON response”REST API blocked or returning an error
Editor loads foreverSlow server, low memory or a stuck script
Blocks look broken or show “invalid content”Block markup changed by a plugin or edited outside the editor
Old classic editor shows insteadClassic Editor plugin or a theme setting

Write down the exact message and when it started. If it began right after an update, that update is your first suspect.

Is the problem in your browser?

Often yes, so open the editor in a private window or another browser first, because extensions and cached files break the editor surprisingly often.

The block editor is a JavaScript app that runs in your browser. Ad blockers, grammar tools, password managers and translation extensions can all inject code that clashes with it.

Try these quick checks:

  1. Open the post in a private or incognito window with extensions turned off
  2. Hard refresh the page to reload scripts
  3. Clear your browser cache and cookies for the site
  4. Try a different browser entirely

If the editor works in a private window, turn extensions back on one at a time to find the culprit.

Is a plugin or theme conflict breaking the editor?

Plugin and theme conflicts are the most common cause, especially right after an update, so test with plugins turned off and a default theme active.

The safest way on a live site is the Health Check & Troubleshooting plugin. Its troubleshooting mode turns off plugins and switches to a default theme only for you, while visitors still see the normal site.

Turn plugins back on one at a time and reload the editor after each. When it breaks again, you have found the conflict. Our guide on finding which plugin is causing a problem covers this method in more detail.

When you find the plugin, check for an update, roll back to the last working version, or contact its developer with the error message.

Is the REST API blocked?

If the editor loads but will not save, the REST API is probably blocked or returning an error, because the editor saves through it.

The classic sign is the “Updating failed. The response is not a valid JSON response” message. Go to Tools > Site Health and look for a REST API warning in the Status tab.

Common causes include:

  • A security plugin or firewall that blocks REST API requests
  • WordPress Address and Site Address settings that do not match, such as http vs https
  • Broken permalinks or a damaged .htaccess file
  • A plugin printing PHP warnings into the API response, which breaks the JSON format the editor expects

Our guide to fixing the “not a valid JSON response” error walks through each one. The REST API handbook explains how the API works if you want the technical background.

What if you see “The editor has encountered an unexpected error”?

This message means a script crashed inside the editor, usually from a plugin block, a theme script or a browser extension.

Click “Copy error” on the message and paste it somewhere. The text often names the plugin or block that failed.

Then follow the same order as above: private window, then plugin conflict test. Our separate guide to fixing “The editor has encountered an unexpected error” covers this message step by step.

Could caching or a CDN be serving old editor files?

Yes, a caching plugin, server cache or CDN can serve outdated JavaScript after an update, which breaks the editor until the cache is cleared.

Purge every cache layer you use: the caching plugin, your host's server cache and any CDN. Then hard refresh the editor.

Good caching setups never cache wp-admin pages or logged-in sessions. If yours does, add an exclusion for /wp-admin/ and for the REST API path /wp-json/.

Also check optimization settings that combine or delay JavaScript. Those features are meant for the front end and can break admin scripts if they are applied too broadly.

How do you fix blocks that show “invalid content”?

A block shows an invalid content warning when its saved HTML no longer matches what the block expects, usually after a plugin update or an edit made outside the editor.

You will see a message such as “This block contains unexpected or invalid content” with a button to attempt recovery. Before you click anything, open the post's Revisions panel so you can go back if the result looks wrong.

Your options are:

  • Attempt Block Recovery: lets WordPress rebuild the block from its saved content, which works in most cases
  • Convert to HTML: keeps your markup exactly as it is inside a Custom HTML block
  • Convert to Classic Block: keeps the content in the older editing format

If many posts show the warning at once, a plugin that registers those blocks probably changed. Roll it back or ask the developer before fixing posts by hand, since a fixed plugin release may repair them all.

Is the server running out of memory or timing out?

A low PHP memory limit or short timeout can stop the editor from loading or saving, especially on large posts or sites with many plugins.

Open Tools > Site Health > Info > Server to see your PHP memory limit and version. Many hosts start at 128 MB, which can be tight for busy admin screens.

Your host can raise the limit, or you can set WP_MEMORY_LIMIT in wp-config.php if the plan allows it. Very long posts with hundreds of blocks also load slowly, so splitting them can help.

Turn on the debug log to catch server-side errors. The WordPress debugging guide shows the settings to add.

How do you read the browser console error?

Open your browser's developer tools and check the Console tab, because the red error lines usually name the file and plugin that broke the editor.

Press F12, or right-click and choose Inspect, then open Console and reload the editor. Look for errors that mention a plugin folder name under /wp-content/plugins/.

You do not need to understand the code. Copy the error and send it to the plugin developer or your host, which speeds up support a lot. The Chrome DevTools console guide explains the panel if you have not used it before.

Should you switch to the classic editor or a page builder?

Switching editors hides the problem but does not fix it, so use the classic editor only as a short-term workaround while you find the cause.

The official Classic Editor plugin restores the old editor for posts. Our guide on going back to the classic editor explains the trade-offs, since new block features will not be available.

If the problem is a page builder rather than the block editor, the causes differ. See our guide to fixing a page builder that will not load.

Frequently asked questions

Why is my WordPress editor showing a blank page?

A blank editor usually means a JavaScript error stopped it from loading. The cause is often a plugin, theme script or browser extension. Test in a private window, then turn off plugins one at a time to find the one causing it.

Why can I not save or update posts in WordPress?

Saving fails when the REST API is blocked or returns an error. Check Tools > Site Health for REST API warnings, look at security plugin and firewall rules, and make sure your WordPress and site addresses match.

Did a WordPress update break my editor?

It can. A core, plugin or theme update can introduce a conflict or leave old scripts in cache. Clear all caches first, then test plugins one by one. Roll back the plugin that breaks it until a fixed version is released.

Will I lose my content if the editor stops working?

Usually not. Your posts are stored in the database, not in the editor. WordPress also keeps revisions and autosaves, so you can restore earlier versions from the Revisions panel once the editor works again.

Is the WordPress editor broken for everyone?

Rarely. Editor problems are almost always specific to one site's plugins, theme, server or browser. If you see a problem right after a core release, check the WordPress support forums to see if others report the same error.

Sources

  1. WordPress Block Editor WordPress.org Documentation
  2. REST API Handbook WordPress Developer Resources
  3. Debugging in WordPress WordPress Developer Resources
  4. Health Check & Troubleshooting WordPress.org Plugins
  5. Console overview Chrome for Developers

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.