There is something particularly unhelpful about a blank page. An error message at least tells you where to look. The WordPress white screen of death gives you nothing — no message, no error code, no hint. Just white.
The good news is that the causes are few and predictable. Work through them in order and most sites are back within twenty minutes.
First, work out how much is broken
Before changing anything, check three places. The answer narrows the search considerably.
- Is the whole site blank, or just one page? One page usually means a specific plugin or a broken template file. Everything blank points to a plugin, theme or memory problem.
- Can you reach /wp-admin? If the admin loads but the front end is blank, the theme is the prime suspect. If both are blank, the cause sits deeper.
- What changed recently? An update, a new plugin, an edited file, a host migration. The white screen almost always follows a change.
Turn the error messages back on
WordPress hides PHP errors in production. That is sensible normally, and unhelpful now. Edit wp-config.php and add this above the line that says to stop editing:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
This writes errors to wp-content/debug.log instead of showing them to visitors. Reload the broken page, then open that file. The last few lines usually name the exact file and line number causing the problem.
This one step solves most cases outright. Turn debugging off again once you are finished.
Cause 1: A plugin conflict
The most common trigger by a wide margin. A plugin update introduces code that clashes with another plugin, your theme, or your PHP version.
If you can reach the admin, deactivate all plugins at once. If the site returns, reactivate them one at a time, checking the site after each. The one that breaks it is your answer.
If you cannot reach the admin, use FTP or your host's file manager. Rename wp-content/plugins to plugins-off. That deactivates everything. Reload the site, then rename it back and disable plugins individually by renaming their folders.
Cause 2: The theme
If the admin works and the front end does not, suspect the theme. Rename your theme folder inside wp-content/themes. WordPress will fall back to a default theme automatically.
If the site returns, the problem is in your theme — often a recent edit to functions.php, or an update that removed a function your child theme relied on.
Cause 3: PHP memory exhausted
A script asks for more memory than the server allows, PHP stops, and you get a white page. This is common on sites with page builders, large media libraries, or WooCommerce.
Raise the limit in wp-config.php:
define('WP_MEMORY_LIMIT', '256M');
If that does not hold, the limit is capped at server level and your host needs to raise it. Treat this as a temporary fix — if a site suddenly needs far more memory than it did last week, something is wrong beyond the limit.
Cause 4: A syntax error in edited code
If the WordPress white screen of death appeared the moment you saved a change in the theme editor, this is almost certainly it. A missing semicolon or bracket is enough to stop PHP entirely.
The debug log will name the file and line. Fix it, or restore the previous version of the file. This is also a strong argument for never editing live code through the dashboard — there is no undo, and a mistake takes the whole site down.
Cause 5: A PHP version mismatch
Hosts upgrade PHP, sometimes automatically. Older plugins and themes using removed functions will fatal-error on the new version.
Check which PHP version your host is running. If it changed recently, that timing is your answer. Update the plugin or theme to a compatible version, or temporarily move back a PHP version while you sort it out.
Cause 6: Corrupted core files
Less common, but it happens after a failed update or an interrupted file transfer. Download WordPress at your version and replace wp-admin and wp-includes entirely. Leave wp-content and wp-config.php untouched.
When a blank page means something worse
Occasionally the white screen is not a bug at all. Malware that fails partway through can leave a blank page behind, and some infections deliberately break the admin to slow you down.
Treat it as suspicious if the site was working with no changes made, if the debug log points to a file you do not recognise, if there are new admin users, or if it returns after a clean fix. In that case, stop troubleshooting and start investigating — our guide to removing malware from WordPress covers what to check.
Making it less likely next time
Most white screens are avoidable. Test updates on a staging copy before applying them live. Keep automatic backups so you can roll back in minutes rather than debugging under pressure. Remove plugins you do not use. Stay on a supported PHP version rather than being moved onto one unexpectedly.
That is the routine work our managed website plans handle — updates tested before they go live, backups running, and someone monitoring so a blank page is spotted before your customers find it.
Stuck on a blank screen right now?
If you have worked through this and the page is still white, or you would rather not risk making it worse, our WordPress error fixing service can take it from here. We diagnose the actual cause rather than guessing, fix it, and tell you plainly what went wrong.
Get in touch with your web address and what changed just before it broke. That detail usually gets us most of the way there.
Get Shielded
We build, host, secure and monitor business websites — cleaning up hacks and keeping sites online for clients across the UK, USA, Australia and the UAE.
