You open your website to check something and instead of your homepage there’s nothing. No menu, no footer, no error message — just a blank white page. This is the WordPress white screen of death, and it’s one of the most stressful things that can happen to a site owner because there’s no obvious clue about what broke or why.
The good news is that a white screen is almost always recoverable, and you don’t need to touch a single line of code to fix most cases. It’s caused by a fatal error somewhere in PHP — usually a plugin, a theme, or a server running out of memory — and once you know where to look, getting back online is a process of elimination rather than guesswork.
In most of the sites I build and maintain, this happens right after a plugin or theme update, which is one of the reasons updates get their own careful process in the step-by-step guide to building a WordPress website. Work through the steps below in order and you should be back online within a few minutes.
Quick answer
The WordPress white screen of death (WSOD) is caused by a fatal PHP error, usually from a plugin or theme conflict, a corrupted file, or the site running out of memory. Fix it by turning on debugging to reveal the real error, deactivating plugins and themes one at a time through FTP, increasing the PHP memory limit, and restoring from a backup if none of that brings the site back.
Why this matters
A white screen doesn’t just look bad — it takes the entire site offline with zero information for visitors or search engines. Unlike a 404 page or a styling glitch, there’s nothing rendered at all, so every visitor who lands on the site during the outage bounces straight off it.
It’s also one of the few WordPress errors that gives you no clue from the front end. According to WordPress’s own documentation on common WordPress errors, both PHP errors and database errors can produce the exact same blank screen, so the cause has to be found by testing rather than guessing.
The fix is rarely complicated, but the order you troubleshoot in matters. Jumping straight to reinstalling WordPress or restoring an old backup can undo recent work and still miss the actual cause, which is usually one specific plugin or a memory limit set too low.
How to fix the white screen of death
Work through these in order. Most white screens are solved by step two or three — only move on if the site is still blank.
1. Check whether wp-admin still loads
Try loading yoursite.com/wp-admin before doing anything else. If the dashboard loads normally, the problem is likely limited to a theme or a front-end plugin conflict, and you can fix it from inside WordPress. If wp-admin is also blank, you’ll need FTP or your hosting file manager to make changes instead.
2. Turn on debugging to see the real error
A blank screen hides the actual PHP error by default. Open wp-config.php through FTP and set WP_DEBUG and WP_DEBUG_LOG to true, then reload the site. WordPress writes the specific error — including the file and line number — to a debug.log file inside wp-content, which tells you exactly which plugin or theme function is failing. Turn debugging back off once you’ve found the cause; it shouldn’t stay on for a live site.
3. Deactivate all plugins, then reactivate one at a time
If the debug log points to a plugin, or you can’t reach wp-admin at all, rename the plugins folder inside wp-content via FTP to something like plugins-disabled. WordPress treats this as deactivating every plugin without deleting any settings. Reload the site — if it comes back, rename the folder back to plugins, then reactivate each plugin individually from the dashboard until the white screen returns. That last plugin is the one causing the conflict.
4. Switch to a default WordPress theme
If plugins aren’t the issue, the theme probably is. Rename your active theme’s folder inside wp-content/themes via FTP — WordPress automatically falls back to a default theme like Twenty Twenty-Four if one is installed. If the site loads again, the theme has a fatal error or an incompatibility with your current PHP version, and you’ll need to update it, switch to a child theme, or contact the developer.
5. Increase the PHP memory limit
Sometimes neither plugins nor the theme are broken — the site is simply running out of memory while loading them all together. Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php above the line that reads “That’s all, stop editing!”. If that doesn’t help, your hosting plan’s PHP limit may be capped lower than that and need raising through your host’s control panel.
6. Restore from a backup if nothing else works
If you’ve worked through every step above and the site is still white, the safest option is restoring the last known good backup rather than continuing to guess. This is exactly why I recommend setting up a website backup schedule before you need it — restoring from a recent backup takes minutes, while rebuilding from nothing takes hours.
Practical tips
A few habits make white screens rarer and much faster to fix when they do happen:
- Run a check through the Site Health tool whenever you can still reach wp-admin — it flags low PHP versions and tight memory limits before they cause a white screen.
- Keep one default WordPress theme installed at all times purely as a fallback, even if you never use it.
- Use an FTP client like FileZilla rather than your host’s web-based file manager when you need to rename folders quickly — it’s faster and easier to undo.
- Check your host’s status page before troubleshooting anything. A server-wide outage looks identical to a plugin conflict from where you’re sitting.
- Treat plugin and theme updates as a deliberate process rather than a single click, especially on a live site with no staging copy.
Common mistakes
- Editing wp-config.php or theme files directly on a live site without a backup, which turns a five-minute fix into a much longer one if something else goes wrong.
- Deleting a plugin folder instead of renaming it — you lose all of that plugin’s settings the moment it’s gone.
- Reactivating every plugin at once after a fix, which just brings the same conflict straight back.
- Assuming the white screen means WordPress itself is broken and reinstalling core files first, when the cause is almost always a plugin, theme, or memory limit.
When to use this vs alternatives
Working through these steps yourself makes sense whenever you can still reach the server via FTP or a file manager — it’s free and usually faster than waiting on support. If you’re not comfortable editing files, or the debug log points to something inside core WordPress files rather than a plugin or theme, contacting your hosting provider’s support team is the safer route; most hosts can roll back a recent change or restore a backup from their end within minutes. Hiring a developer makes the most sense when the white screen keeps coming back after a fix, which usually points to a deeper compatibility issue worth solving properly. I’d also recommend reviewing how you update WordPress safely so the same conflict doesn’t reappear after the next core, theme, or plugin update.
If a memory exhaustion error is the root cause, increasing the PHP memory limit in WordPress is the direct fix — the process takes under two minutes and covers three methods depending on your hosting setup.
If you’re dealing with a blank page that shows no error code at all, the problem is likely different from a server error — read the guide on how to fix the WordPress 500 Internal Server Error for a step-by-step walkthrough that covers plugin conflicts, PHP memory, and .htaccess issues.
Conclusion
A white screen feels alarming, but it’s one of the most fixable problems in WordPress once you isolate the cause instead of guessing. Work through plugins, theme, and memory limit in order, and keep a recent backup on hand so the worst case is never more than a few minutes of downtime.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.