Troubleshooting
WordPress Edit Post White Screen: Causes and How to Fix It

Short answer
A white screen when editing a post usually means the block editor's JavaScript crashed or a PHP error stopped the page. The common causes are a plugin or theme conflict, too little PHP memory, a blocked REST API, or a caching or optimisation tool changing admin scripts. Check the browser console and debug log, then test with plugins disabled to find the culprit.
Key takeaways
- Open the browser console first; it usually names the failing script.
- Plugin and theme conflicts are the most common cause.
- Low PHP memory and PHP errors can blank the editor too.
- Script optimisation and CDN features can break admin pages.
- Health Check's troubleshooting mode tests safely without affecting visitors.
Why is the edit post screen white?
The editor screen goes blank when its JavaScript fails to load or crashes, or when a PHP fatal error stops the page before the editor appears.
The block editor is a JavaScript application. One broken script can stop the whole screen from rendering.
That is why the admin bar and menu often still appear while the editing area stays empty.
| Symptom | Likely cause | First check |
|---|---|---|
| Blank page, admin bar visible | JavaScript error | Browser console |
| Completely white page | PHP fatal error | Debug log |
| Editor loads then disappears | Plugin block or script conflict | Disable plugins |
| Only some posts are blank | Broken block or post content | Code editor view |
| Blank after enabling a CDN | Script optimisation | Exclude admin |
If the whole site is white, not just the editor, our guide on the white screen of death covers site-wide causes.
How do you find the error?
Open the browser's developer tools on the blank editor screen, check the Console tab for red errors, and turn on WordPress debug logging to catch PHP errors.
Chrome's Console documentation shows how to read script errors and the files they come from.
The file path in an error often includes a plugin or theme folder name, which points straight to the cause.
Copy the full error text. It is the most useful thing to send to a plugin developer or your host.
Our guide on enabling debug mode shows how to log PHP errors without showing them to visitors.
How do you test for plugin conflicts?
Deactivate all plugins, reload the editor, then reactivate them one by one until the white screen returns; the last plugin activated is the conflict.
Use a staging copy if the site is busy, so visitors are not affected.
Start with plugins that add blocks, editor panels or admin scripts, such as page builders, SEO plugins and custom field tools.
The Health Check and Troubleshooting plugin has a troubleshooting mode that disables plugins only for you, while visitors still see the normal site.
Our guide on fixing plugin conflicts walks through the testing order.
What about the theme?
Switch to a default theme in troubleshooting mode and reload the editor; themes that add editor styles or scripts can break it too.
If the editor works with a default theme, contact your theme's developer with the console error.
Child themes can cause the same problem when they enqueue editor scripts incorrectly.
Could low memory cause the blank editor?
Yes. The editor loads many scripts and, with heavy plugins, can hit the PHP memory limit, which stops the page with a fatal error and a blank screen.
The debug log will show an allowed memory size exhausted message if this is the cause.
Our guide on fixing memory exhausted errors explains the message and longer-term fixes.
Our guide on increasing the PHP memory limit shows where to raise it.
If memory keeps running out, look for a plugin that loads far more than it needs in the admin area.
Is the REST API blocked?
The block editor loads and saves posts through the REST API, so security plugins, firewalls or server rules that block it can leave the editor blank or unable to load content.
Tools > Site Health reports REST API problems.
Our guide on fixing REST API errors covers the usual blockers.
Check firewall logs for blocked requests to paths containing wp-json while you open the editor.
Some security plugins have an option to disable the REST API for visitors. Make sure logged-in editors are still allowed to use it.
Can caching or CDN features break the editor?
Yes. Features that combine, minify or delay JavaScript, or CDN tools that rewrite scripts, can break the admin editor if they are applied to logged-in or admin pages.
Cloudflare's Rocket Loader documentation explains how it changes script loading, which can conflict with complex admin scripts.
Exclude wp-admin and logged-in users from script optimisation and page caching.
Server-level optimisation, such as automatic minification by a host, can cause the same problem. Ask your host whether it applies to admin pages.
Clear all caches after changing these settings, then reload the editor with a hard refresh.
Is a browser extension the cause?
Sometimes. Ad blockers, privacy tools and script blockers can stop editor scripts, so test in a private window with extensions disabled or in another browser.
If the editor works there, re-enable extensions one by one.
Keep your browser updated. The editor relies on modern browser features.
Corporate devices sometimes run security software that filters scripts. Try a personal device if the problem only happens at work.
Clearing the browser cache can fix problems caused by old cached editor scripts after an update.
What if only one post shows a white screen?
A single blank post usually has broken or unusual content, such as a block from a removed plugin or invalid markup, which crashes the editor when it loads.
Open the post with the code editor view, if possible, and look for unusual blocks.
Restore an earlier revision from the post's revisions screen to see if the problem disappears.
If revisions also fail, copy the content from the database or a backup into a new post and rebuild the layout.
Our guide to the WordPress editor not working covers broken block messages and recovery.
Can you use the classic editor as a workaround?
Yes. The Classic Editor plugin lets you keep editing while you investigate, though you should still fix the root cause because new features rely on the block editor.
Our guide on going back to the classic editor shows how to switch.
Use it as a temporary fix, especially on busy publishing sites.
Remember to switch back after fixing the cause, or some blocks and patterns will not be editable.
Did an update cause the white screen?
If the problem started right after updating WordPress, a plugin or a theme, that update is the prime suspect; check the console for errors from the updated item and look for a fix release.
Rolling back the plugin temporarily can restore editing. Our guide on rolling back a plugin update explains how.
Report the error to the plugin developer with the console message.
Check the plugin's support forum first. Others often report the same problem within hours of a faulty update.
What if nothing above works?
Check the server error log, try a different PHP version supported by your host, reinstall WordPress core files from Dashboard > Updates, and ask your host whether a server rule blocks editor requests.
Reinstalling core replaces core files only. Content, themes and plugins stay in place.
Could a PHP version change cause it?
Yes. Older plugins and themes can throw fatal errors on newer PHP versions, so if the editor broke after a PHP upgrade, check the debug log for errors from those files and update them.
Collect the console errors and debug log before contacting support. They speed up any diagnosis.
Note the time the problem started and any changes made just before it. That timeline usually points to the cause faster than anything else.
Keep backups current while troubleshooting, in case a change makes things worse.
Frequently asked questions
Why is my WordPress post editor blank?
Usually a JavaScript or PHP error stops the block editor. Plugin or theme conflicts, low memory, a blocked REST API or script optimisation are the most common causes.
How do I find what breaks the WordPress editor?
Open the browser console for script errors and enable WordPress debug logging for PHP errors. The file paths usually point to the plugin or theme involved.
Can a caching plugin cause a white editor screen?
Yes, if it minifies, combines or delays scripts on admin pages. Exclude wp-admin and logged-in users from these features, then clear all caches.
Why does only one post show a white screen?
That post probably contains a broken or unsupported block. Open the code editor view or restore an earlier revision to recover it.
Is it safe to test plugins on a live site?
Use the Health Check plugin's troubleshooting mode, which disables plugins only for you, or test on a staging copy to avoid affecting visitors.
Sources
- Console overview Chrome for Developers
- Health Check & Troubleshooting WordPress.org Plugins
- Rocket Loader Cloudflare Docs
- Debugging in WordPress WordPress Developer Resources
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


