Fixing the WordPress white screen of death

You opened your site and got nothing. Just a blank white page. No error message, no theme, no admin login. This is the WordPress “white screen of death” (WSOD) and it’s one of the most common WordPress problems. The good news: it’s almost always fixable in under 30 minutes once you know the order to check things.

First: turn on debug mode

WordPress hides errors by default. Turn them on temporarily.

Connect via SFTP or use the File Manager in your hosting panel. Open wp-config.php and find this line:

define( 'WP_DEBUG', false );

Change it to:

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

Now errors are written to /wp-content/debug.log instead of being silent. Reload your site, then check that log file. The last error before things broke usually tells you the cause.

Remember to turn debug mode off when you’re done — leaving it on in production is a security risk.

Cause 1: Plugin conflict (most common)

Symptom: white screen started after activating, updating, or removing a plugin.

Fix without admin access:

1. Connect via SFTP / File Manager
2. Navigate to /wp-content/
3. Rename the plugins folder to plugins-disabled
4. Reload your site

If it works now, the issue is a plugin. Rename back to plugins, then deactivate plugins one at a time (rename individual plugin folders) until you find the culprit.

Fix with admin access:

1. Go to Plugins → Installed Plugins
2. Deactivate all
3. Reactivate one at a time, checking the site between each

Cause 2: Theme issue

Symptom: white screen after changing themes, or after a theme auto-update.

Fix: rename /wp-content/themes/your-active-theme/ to your-active-theme-broken. WordPress falls back to the default Twenty-something theme. If the site loads now, your theme is the problem — restore from backup or contact the theme developer.

Cause 3: PHP memory limit

Symptom: WSOD only on specific pages, especially admin pages like the editor or plugins list.

WordPress can run out of allocated PHP memory, especially with bloated plugins. To increase the limit, add this to wp-config.php above the “That’s all, stop editing!” line:

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

If you’re on a Starter or Standard plan and hitting memory limits often, you’ve likely outgrown the tier — Business plans have more headroom by design.

Cause 4: Corrupted .htaccess

Symptom: white screen with weird URL behaviour, or 500 errors mixed in.

A plugin or update can corrupt your .htaccess file. To fix:

1. SFTP into your site root
2. Rename .htaccess to .htaccess.broken
3. Reload your site

If it works, the .htaccess was corrupt. To regenerate a clean one:

1. Log into WordPress admin (now that it loads)
2. Go to Settings → Permalinks
3. Don’t change anything, just click Save Changes

WordPress writes a fresh .htaccess.

Cause 5: Failed update mid-flight

Symptom: WSOD right after a WordPress core update that got interrupted.

Look for a .maintenance file in your site root. If it’s there, the update was interrupted. Delete the file. If WordPress still doesn’t load, you may need to manually re-upload WordPress core files (download from wordpress.org, upload everything except wp-content/ and wp-config.php).

When to ask for help

If you’ve tried all the above and still have a white screen, open a ticket with:

• The exact URL that’s broken
• Last error from debug.log (don’t skip this — it usually pinpoints the cause)
• What changed before the issue (update? new plugin? you don’t know?)
• Any FTP/admin credentials we’ll need (or a temporary admin account)

We’ve seen every flavour of WSOD. With those details we can usually identify the cause in under an hour.

Prevention

• Test plugin updates on staging first (every plan includes a staging environment)
• Keep WordPress, themes, and plugins updated — don’t let them go six months stale and then update everything at once
• Take a backup before any major change (your hosting plan includes automated backups, but a pre-change manual backup gives you a recovery point you can describe in a ticket)