ThisCalculator

Everyday

WordPress White Screen of Death: Fix It

Updated · Standard formula, shown below

WordPress White Screen of Death: Fix It

The WordPress white screen of death (WSOD) shows a blank white page instead of your site, often with no error message, and it usually means PHP has crashed or hit a memory limit. The fix is to identify the cause—typically a faulty plugin, theme, or a PHP error—and then disable the culprit or increase PHP memory, which you can do in about 10 minutes even without dashboard access.

What Exactly Causes the White Screen

WordPress runs on PHP, and when PHP encounters a fatal error—like calling a function that doesn’t exist or running out of memory—it stops executing and outputs nothing, leaving a blank white page. The most common triggers are:

  • Plugin conflict – A plugin’s code throws an error, often after an update or a new install.
  • Theme issue – A broken theme file (usually functions.php) crashes the site.
  • PHP memory limit exhausted – The default limit (often 128M) is too low for some plugins, especially on shared hosting.
  • Corrupted core files – A failed WordPress update leaves missing or damaged files.
  • Syntax error – A typo in a theme or plugin file, often from editing code manually.

Sometimes the white screen appears only on the front end, only in the admin, or on a single page. That narrows down the cause: if the admin works but the front end is white, the issue is likely in the active theme; if both are white, it’s probably a plugin or core problem.

Before You Panic: Quick Checks

First, confirm it’s really the WSOD and not a browser cache or server issue. Try these in order:

  1. Hard-refresh your browser (Ctrl+F5 or Cmd+Shift+R) and clear your browser cache.
  2. Check if the site is down for everyone using a tool like downforeveryoneorjustme.com.
  3. Look at your browser’s console (F12 → Network tab) for a 500 error or a specific PHP message.
  4. Check your hosting control panel’s error log—this often shows the exact file and line number of the error.

If you see a message like Fatal error: Allowed memory size of 67108864 bytes exhausted, that’s a memory issue. If you see a path to a plugin file, that’s your culprit. If there’s no log, proceed with the systematic fixes below.

Fix 1: Disable All Plugins (via FTP or File Manager)

The fastest way to rule out a plugin conflict is to temporarily deactivate all plugins. If you can’t access the dashboard, do it via FTP or your hosting file manager:

  1. Connect to your site via FTP (FileZilla) or open the File Manager in cPanel.
  2. Navigate to wp-content/plugins.
  3. Rename the entire plugins folder to plugins_old.
  4. Reload your site. If it’s back, a plugin was the problem.
  5. To find which one, rename the folder back to plugins, then rename each plugin subfolder one by one (e.g., akismet → akismet_off) and reload the site until it works. The last renamed folder is the culprit.

If you can’t rename the whole folder (some hosts lock it), rename each plugin subfolder individually. This method works because WordPress skips any plugin whose folder isn’t found.

Fix 2: Switch to a Default Theme

If disabling plugins doesn’t help, the theme is likely the issue. Rename the active theme’s folder in wp-content/themes (e.g., twentytwentyfour → twentytwentyfour_off). WordPress will automatically fall back to a default theme (like Twenty Twenty-Four) if one is installed. If not, it will show a “theme missing” error but the site should still load with a broken layout—which confirms the theme was the problem.

If you have a child theme, also check its functions.php for syntax errors—a missing semicolon or an unclosed PHP tag can crash the whole site.

Fix 3: Increase PHP Memory Limit

If neither plugins nor theme are at fault, try raising the PHP memory limit. Add this line to your wp-config.php file, right before the line that says /* That's all, stop editing! */:

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

If that doesn’t work, your hosting may have a hard limit. You can also try adding a php.ini file in your root directory with:

memory_limit = 256M

Or, if your host uses .htaccess (Apache), add this line:

php_value memory_limit 256M

Some hosts (like WP Engine) don’t allow these overrides—check your host’s documentation. If 256M doesn’t fix it, the problem is likely a specific error, not memory.

Fix 4: Enable WP_DEBUG to See the Error

WordPress hides errors by default, but you can make them visible. Edit wp-config.php and replace the existing debug lines (or add them) with:

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

Reload the page. You should now see a PHP error message with the exact file and line number. If the error says something like “Call to undefined function”, it’s a plugin or theme conflict. If it says “Parse error: syntax error”, you have a typo in a PHP file—fix that line and the site returns.

Once fixed, set WP_DEBUG back to false to hide errors from visitors.

Fix 5: Re-upload Core Files

If the white screen persists, a corrupted core file might be the cause. Download a fresh copy of WordPress from wordpress.org, unzip it, and upload the wp-admin and wp-includes folders to your server, overwriting the existing ones. Do not overwrite wp-content or wp-config.php. This replaces any damaged core files without touching your content.

If you have access to the dashboard, you can also go to Dashboard → Updates and click “Re-install WordPress” to do this automatically.

Frequently Asked Questions

What if I can’t access wp-admin either?

If both the front end and admin are white, you’ll need to use FTP or your hosting file manager to apply the fixes above. The steps are identical—you just can’t use the dashboard. If you don’t have FTP credentials, your hosting control panel (cPanel, Plesk) usually has a File Manager that works in the browser.

Can a white screen be caused by a security plugin?

Yes. Security plugins like Wordfence or Sucuri can sometimes block access if they detect a false positive, or they can conflict with other plugins. If you suspect a security plugin, rename its folder in wp-content/plugins to deactivate it temporarily. You can re-enable it after the site is back.

Why does the white screen happen after a WordPress update?

Updates can introduce incompatibilities between the new core version and older plugins or themes. Also, a failed update can leave files half-uploaded, causing fatal errors. Re-uploading the core files (Fix 5) usually resolves this.

Is the white screen of death dangerous for my site’s data?

No. The WSOD is a PHP execution error—it doesn’t delete your content or database. Your posts, pages, and settings remain intact. Once you fix the underlying issue, your site returns exactly as it was.

How do I prevent this from happening again?

Always update plugins and themes one at a time, and test your site after each update. Keep a backup of your site (files and database) so you can restore quickly if something breaks. Also, avoid editing theme files directly—use a child theme so updates don’t overwrite your changes.

What if none of these fixes work?

If you’ve tried all the above and still get a white screen, the issue may be server-side—like a PHP version incompatibility or a corrupted database. Check your hosting error logs for more details, and contact your host’s support with the exact error message. They can often see server-level errors that aren’t visible to you.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.