Skip to content
Black Friday 50% off + 15,000 credits Ends Nov 30 Ends Nov 30 see the deal
Black Friday15,000 free credits + 50% offends Nov 30

How to Fix the WordPress White Screen of Death

The white screen of death is a blank page with no error message: the site, wp-admin or just the editor shows nothing at all. It looks alarming, but the cause is almost always one plugin, the theme, a memory limit or a cache. Here is how to find which one, in order.

Updated WPOSAI + WordPress How-TosMaintenance & Security
In this article
  1. 01The short answer
  2. 02What a blank page means in 2026
  3. 031. See how far the white screen goes
  4. 042. Turn on the debug log
  5. 053. Turn off the plugin or theme that failed
  6. 064. Raise the PHP memory limit
  7. 075. Blank editor or wp-admin: check JavaScript
  8. 086. Purge every cache
  9. 097. Still blank?
  10. 10When it's fixed
  11. 11Where WPOS fits
Key takeaways
  • A blank white page means something stopped WordPress before it could show anything, with the errors hidden.
  • Since WordPress 5.2, most fatal errors show "There has been a critical error" instead, so a fully blank page narrows the causes.
  • Turn on WP_DEBUG_LOG and read the last error in wp-content/debug.log: it names the file that failed.
  • No wp-admin? Rename the plugin's folder, or the active theme's, with your host's file manager or SFTP.
  • A blank block editor is usually a plugin's JavaScript: check the browser console.
  • Purge the cache after each fix, then turn debugging off and delete debug.log.

The short answer

Turn on the debug log, reload the blank page, and read the last error in wp-content/debug.log. It names the plugin, theme or file that failed. Then:

  1. Turn off the plugin or theme the log names. Without wp-admin, rename its folder with your host’s file manager or SFTP.
  2. If the log says memory was exhausted, raise WP_MEMORY_LIMIT, or ask your host to.
  3. If only the editor is blank, it’s JavaScript: check the browser console and test plugins one at a time.
  4. Purge your page cache and CDN, then check the site in a private window.
  5. Turn debugging off again and delete debug.log.

If you see “There has been a critical error on this website” rather than a blank page, follow our critical error guide instead: WordPress has already caught the error and sent the admin a recovery link.

What a blank page means in 2026

WordPress’s own documentation describes it: PHP errors and database errors can show up as a white screen, a blank page with no information. Before WordPress 5.2 that was what most broken plugins produced. Since 5.2, WordPress catches most fatal PHP errors and shows the critical error message instead, with a recovery mode link for the admin.

So when the page is completely blank today, the cause is usually one of these:

  • An error WordPress couldn’t catch, for example a typo in wp-config.php, which loads before WordPress’s error handler starts.
  • The error handler is switched off, by define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); in wp-config.php.
  • A cached blank page. A page cache or CDN stored the page while it was broken and keeps serving it.
  • JavaScript, not PHP. A blank block editor or a blank part of wp-admin usually comes from a script that failed in the browser.
  • The server itself, such as PHP crashing or timing out, where only the host’s error log shows the reason.

1. See how far the white screen goes

A minute of checking tells you where to look:

What’s blankMost likely causeStart with
The whole site, front end and wp-adminA plugin, the theme, memory or wp-config.phpThe debug log (step 2)
The front end only, wp-admin worksThe theme, or a plugin that only runs on the front endSwitch to a default theme (step 3)
One page or postA block, shortcode or template used on that pageThe debug log while loading that page
Only the block editorA plugin’s JavaScript in the editorThe browser console (step 5)
Only for visitors, not when you’re logged inA cached blank pagePurge the cache (step 6)

Also note what changed just before: an update, a new plugin, a theme switch, or code you pasted in. That is the first suspect.

2. Turn on the debug log

Error messages are hidden on live sites, which is why the page is blank. The WordPress debug log writes them to a file instead of the screen. Open wp-config.php in the site’s root folder and add these lines above /* That's all, stop editing! */:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Reload the blank page, then open wp-content/debug.log and read from the bottom. Look for a line starting with PHP Fatal error. The file path in it tells you what failed: a path inside wp-content/plugins/ names the plugin, and one inside wp-content/themes/ names the theme.

If debug.log stays empty, the error happens before WordPress loads, often in wp-config.php itself, and only your host’s PHP error log will show it.

3. Turn off the plugin or theme that failed

If wp-admin works, deactivate the plugin under Plugins, or switch to a default theme such as Twenty Twenty-Five under Appearance → Themes. If the log didn’t name anything, deactivate all plugins, check the site, then turn them back on one at a time.

If wp-admin is blank too, do it from the files:

  • Rename the plugin’s folder in wp-content/plugins/, for example from slider-pro to slider-pro-off. WordPress deactivates a plugin whose folder it can’t find.
  • Not sure which plugin? Rename the whole plugins folder to plugins_old, as WordPress’s documentation suggests, which turns them all off. Rename it back, then rename plugin folders one at a time.
  • For the theme, rename the active theme’s folder in wp-content/themes/. WordPress then falls back to a default theme, if one is installed.

With WP-CLI, the same steps are commands:

wp plugin deactivate slider-pro
wp plugin deactivate --all
wp theme activate twentytwentyfive

Once the site is back, update or replace the plugin or theme that failed, or check with its developer, before you turn it on again.

4. Raise the PHP memory limit

If the log says Allowed memory size of ... bytes exhausted, PHP ran out of memory partway through the page. Raise WordPress’s limit in wp-config.php:

define( 'WP_MEMORY_LIMIT', '256M' );

WordPress can’t go above what your hosting plan allows. If the error comes back, ask your host to raise PHP’s memory_limit, and look for the plugin that needs so much, often an import, a page builder or a backup job.

5. Blank editor or wp-admin: check JavaScript

When the page appears but the block editor stays empty, PHP is usually fine and a script failed in the browser:

  1. Open the editor, press F12 and look at the Console tab. Red errors usually name the plugin that loaded the script.
  2. Deactivate plugins one at a time, starting with anything that adds blocks or editor features, and reload the editor after each.
  3. Add define( 'SCRIPT_DEBUG', true ); to wp-config.php while you test. WordPress then loads its unminified scripts, so the errors are easier to read.
  4. Clear your browser cache too. An old copy of a script after an update can cause the same blank editor.

Health Check & Troubleshooting can turn plugins off for your browser only while visitors see the normal site, but check its listing first: on 9 November 2026 it was last updated in July 2024 and tested up to WordPress 6.6.

6. Purge every cache

Once the cause is fixed, visitors can still get the blank page if it was cached. Clear the plugin or host page cache, then the CDN (such as Cloudflare), then check the site in a private window. If it’s blank only for logged-out visitors, the cache is the likely cause on its own.

7. Still blank?

  • Reinstall WordPress’s own files. Under Dashboard → Updates, use Re-install, or upload fresh wp-admin and wp-includes folders from wordpress.org. This replaces core files and leaves your content, plugins and themes alone.
  • Check the PHP version. A plugin or theme that doesn’t support your host’s PHP version can fail as soon as it loads. Most hosts let you switch the version in their dashboard.
  • Ask your host for the PHP error log and whether anything changed on the server.
  • Restore a backup from before the problem started, then update one thing at a time.

When it's fixed

  • Turn debugging off: set WP_DEBUG back to false, or remove the lines you added.
  • Delete wp-content/debug.log. It can show visitors file paths and errors if it’s left there.
  • Update one plugin at a time from now on, and try big updates on a staging copy first.
  • Check the key pages after every update. Our WordPress security checklist covers the rest of that routine.

Where WPOS fits

WPOS can’t repair a site that won’t load. Its agent works inside wp-admin, so when the whole site is blank, start with the steps above. Where it helps is the routine that prevents the next one: the agent checks its own render with a browser screenshot before it reports a change as done, and the free trial comes with a staging sandbox next to the live site for trying updates first. A check after updates becomes one request:

“Open the home, pricing and contact pages and every page in the main menu, take a screenshot of each on desktop and phone, and list any that come back blank or show an error.”

WPOS is our product, so weigh this section accordingly; you can try it free for 30 days with 5,000 credits, a live site plus a staging sandbox, and no card.

Frequently Asked Questions

Something stops WordPress before it can show anything, with error messages hidden. Usually it's a PHP error in a plugin, the theme or wp-config.php, PHP running out of memory, or a blank page stored by a cache. A blank editor is usually a JavaScript error instead.

Use your host's file manager, SFTP or SSH. Turn on the debug log in wp-config.php to see the error, then rename the plugin's folder in wp-content/plugins, or the whole plugins folder, or the active theme's folder in wp-content/themes. WP-CLI can deactivate plugins and switch themes too.

It's the same kind of problem. Since WordPress 5.2, most fatal PHP errors show the critical error message and send a recovery link to the admin email instead of leaving a blank page. A fully blank page now points to an error WordPress couldn't catch, a cache, or JavaScript.

A blank block editor is almost always a JavaScript error, often from a plugin that adds to the editor. Open the browser console (F12) to see it, then turn plugins off one at a time until the editor comes back.

Yes. If a page cache or CDN stored the page while it was blank, visitors keep getting the blank copy after you've fixed the cause. Purge the cache after every fix, and test in a private window.

Usually not. Posts, pages and settings are stored in the database, and a white screen means the code that displays them failed. Back up the files and the database before you change anything, so you can undo a step.

Black Fridayends Nov 30

Start free with 15,000 credits.

Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.

Claim 15,000 credits