New 24/7 monitoring and daily cloud backups now included in every Shield Pro plan.

WSOD

Learn how to fix the WordPress white screen of death.

A blank white page with no error message is one of the most common WordPress failures. PHP crashed before WordPress could render anything. This tutorial shows how to surface the real error and recover without guessing.

Time: 15-30 minutes Level: Intermediate
Neil McNaught, founder of BugShield and WordPress author
Written by
Written by
Updated
Updated

What this problem looks like

The white screen of death (WSOD) means PHP hit a fatal error and display_errors is turned off on your server. Visitors see nothing. You may still have hosting file access even when wp-admin is dead.

The fix is almost always a plugin, theme, or PHP version conflict. You need the real error message first, then you isolate the code that triggers it through File Manager, SFTP, or FTP.

Step 1: Turn on debug logging in wp-config.php

Connect via SFTP or hosting File Manager and open wp-config.php in your site root. It usually sits next to the wp-admin and wp-content folders. Search for WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY first. If those lines already exist, set them to the values below instead of adding duplicates. If none of them exist, paste these lines above the line that says stop editing. On a live site, log to file only and never print errors to visitors.

php
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Step 2: Read debug.log and hosting error logs

Reload the broken page once, then open wp-content/debug.log. The last lines usually name the plugin file and line number. If debug.log stays empty, check your host PHP error log in cPanel, Plesk, or Site Tools.

  • Look for fatal error, memory exhausted, or undefined function messages.
  • Note the full file path, especially anything inside wp-content/plugins/.
  • Check if the error started after a plugin update or PHP version change.

Step 3: Deactivate plugins at the file level

When wp-admin will not load, rename the plugins directory so WordPress cannot load any plugin PHP. If the site then loads, a plugin is causing the white screen.

  1. Go to wp-content/ in File Manager or SFTP.
  2. Rename plugins to plugins.disabled.
  3. Reload the site and wp-admin.
  4. If the site works, rename plugins.disabled back to plugins. WordPress will see the plugins again, but they should remain deactivated.
  5. In wp-admin, activate plugins one at a time and reload the site after each activation.
  6. When the white screen returns, the plugin you just activated is the culprit. Deactivate or remove it, then activate the rest as needed.

Step 4: Rule out the active theme

If disabling plugins does not help, switch themes at the file level. WordPress falls back to a default theme when the active theme folder is missing.

  1. Open wp-content/themes/.
  2. Rename your active theme folder, for example mytheme to mytheme.off.
  3. Ensure twentytwentyfour or another default theme folder exists.
  4. Reload the site.

Step 5: Check PHP version and memory limits

Hosts often migrate PHP versions without warning. Legacy plugins break on PHP 8.x. Temporarily switch PHP 8.2 to 8.1 in hosting only as a short test, not a permanent fix.

If logs mention memory exhausted, raise limits in wp-config.php in your site root, next to wp-admin and wp-content:

php
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

When to stop DIY and hire help

If the white screen persists after plugin and theme isolation, or the error log points at WordPress core files you did not change, stop guessing on a live site. BugShield fixes white screen errors at a confirmed price without hourly billing surprises.

Questions answered

WordPress white screen of death FAQs

Clear answers about finding the hidden error, restoring access, and fixing a blank WordPress screen safely.

Why is my WordPress site completely blank?

A PHP fatal error occurred and your server hides error output. Enable WP_DEBUG_LOG or read the hosting PHP error log to see the real message.

Can I fix WSOD without file access?

Only if recovery mode email works or your host offers File Manager. Without file access you need your host or a developer to intervene.

Will renaming plugins delete my settings?

No. Settings stay in the database. WordPress simply stops loading that plugin code until you rename the folder back.

How do I fix WSOD after a WordPress update?

Updates often expose incompatible plugins. Isolate plugins first, then update or replace the extension named in debug.log.

What is the difference between the WordPress white screen of death and a critical error?

Both usually mean PHP stopped with a fatal error. Newer WordPress versions may show a critical-error message, while some failures still produce a completely blank page.

Where can I find the error behind a WordPress white screen?

Enable WordPress debug logging and check wp-content/debug.log, then check the PHP error log in your hosting panel if that file stays empty.

Can low PHP memory cause the WordPress white screen of death?

Yes. An exhausted memory limit can stop PHP before WordPress renders a page. Confirm it in the error log before raising the limit.

Can the active theme cause a blank WordPress screen?

Yes. Rename the active theme folder only after testing plugins, and make sure a default WordPress theme is installed so the site has a safe fallback.

Should I restore a backup to fix the WordPress white screen of death?

Restore only when you know the backup predates the fault and you have protected newer orders, form entries, users, or content that a rollback could remove.

When should a developer fix the WordPress white screen of death?

Get help when the site handles live sales, no safe backup exists, file access is unavailable, or the logs still do not identify the failing code.

Would you rather a developer fixed it?

Request a fix at a confirmed price and speak directly with the BugShield developer working on your site.

Request a Fix