How to Fix the WordPress White Screen of Death

Few things cause quite as much panic as loading your WordPress site and being greeted by a completely blank white page. No error message, no clue what’s gone wrong, just an empty screen staring back at you. This is the WordPress white screen of death (WSoD) and it’s one of the most common yet frustrating issues that WordPress site owners encounter. Our guide to getting professional WordPress support explains when it makes sense to call in help. The good news is that it’s almost always fixable and in most cases you can resolve it yourself without needing to start from scratch. If you’d rather not troubleshoot alone, WordPress support and troubleshooting for business websites can get your site back on its feet quickly.

Sometimes the WSoD hits your entire site, sometimes just certain pages. It might show up on the front end, in your admin dashboard or both places at once. Getting to grips with what triggers it gives you the best shot at fixing it, so we’ll walk through the usual suspects and show you how to diagnose and sort out the problem.

What Exactly Is the WordPress White Screen of Death?

WordPress throws up a blank page where your website content should be. That’s the white screen of death in action. Older WordPress versions would show you absolutely nothing, but newer versions from 5.2 onwards brought in recovery mode that might display “There has been a critical error on this website” instead of the pure white screen. The root cause stays the same though. Something’s broken in the PHP code WordPress needs to function and your site can’t produce any output. You get zero information about what went wrong, which makes the WSoD absolutely maddening to deal with.

Common Causes of the White Screen of Death

Most WSoD cases come down to PHP fatal errors or your server hitting resource limits. The exact trigger changes from site to site, but there are common causes that crop up again and again. Recognise these patterns and you won’t waste time shooting in the dark.

Most white screen crashes come down to plugin conflicts. WordPress hosts over 60,000 plugins in its official directory and they don’t always get along. Maybe a plugin update went wrong or you installed something that doesn’t work with your theme. Sometimes plugins just can’t handle the current PHP version and throw fatal errors that kill your site completely.

Step One: Check Your Browser and Cache

Check the obvious before you start digging into server problems. Browser cache loves to show you old versions of pages even when everything’s broken underneath. Pop open an incognito window or clear your cache and try again. Caching plugins like WP Super Cache or W3 Total Cache can be stubborn too, serving up cached pages long after you’ve fixed the actual problem.

Does the white screen hit your front end and admin area equally? Front end dead but wp-admin still works means you’re looking at theme trouble. Both areas affected points to plugins or PHP issues. And don’t just check your homepage, if only certain pages show the white screen, you might be dealing with a shortcode or template rather than a site-wide meltdown.

Enable WordPress Debug Mode

Turn on WordPress debug mode and you’ll see exactly what’s breaking. Instead of hiding PHP errors, WordPress will display them right on screen so you know what needs fixing. You’ll need FTP, SFTP or your hosting provider’s file manager to make the changes.

Find your wp-config.php file in the root directory of your WordPress installation. for define('WP_DEBUG', false); and change it or add these lines if they’re missing:

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

All PHP errors get written to a debug.log file in your wp-content directory without showing up on your live site. Save the file, reload your site, then check wp-content/debug.log for error messages. You’ll see things like “Fatal error: Allowed memory size exhausted” or “Fatal error: Call to undefined function” with a file path pointing straight to the problem plugin or theme file. The WordPress debugging documentation explains all these options properly.

Diagnosing Plugin Conflicts

Debug log showing a plugin file as the problem? Deactivate all plugins and see if your site returns. Go to Plugins in your WordPress admin dashboard and turn everything off if you can still get in. Can’t access the dashboard? You’ll need FTP or your hosting file manager instead.

Go to your wp-content directory and rename the plugins folder to plugins-disabled or something similar. WordPress can’t find the plugins anymore, so they’re all deactivated at once. Reload your site and if that white screen vanishes, you’ve got a plugin causing trouble. Rename the folder back to plugins, then turn each plugin back on one by one through the dashboard until the white screen appears again.

Check for updates first when you’ve spotted the troublesome plugin. Browse the plugin’s support forum on WordPress.org and see what other users are saying about similar problems. Sometimes developers abandon their plugins or go silent, which means you’ll need to find something else that does the job. Our WordPress development team sorts out tricky plugin conflicts regularly and we can build custom solutions when standard plugins keep causing headaches.

Switching to a Default Theme

Your theme could be causing trouble if switching off plugins doesn’t work. Template files throw PHP errors just like plugins do and themes sometimes can’t handle newer WordPress versions or clash with plugins. Switch to Twenty Twenty-Four or Twenty Twenty-Five through Appearance then Themes if you can still get into your dashboard.

Can’t reach the dashboard? Connect via FTP, find wp-content/themes and rename your current theme folder to something else. WordPress notices the active theme has vanished and switches to whatever default theme you’ve got installed. No default theme sitting there means you’ll be downloading one from WordPress.org and uploading it manually.

Site comes back after the theme switch? Your theme code’s got issues. Custom themes usually show you exactly which file and line number in the error log, but third-party themes need updates or you’ll have to contact whoever made them.

Increasing the PHP Memory Limit

WordPress pages need PHP to process everything from your theme to active plugins to the core itself. When that combined memory usage hits your server’s limit, PHP just stops and you get a blank page. Shared hosting plans often set pretty restrictive memory limits, so sites running multiple plugins or complex layouts run into this wall regularly. Add this line to your wp-config.php file and you’ll bump up the memory limit:

Adding define('WP_MEMORY_LIMIT', '256M'); to your wp-config.php file tells WordPress to request up to 256MB of PHP memory. For admin-side operations, WordPress separately uses WP_MAX_MEMORY_LIMIT which defaults to 256MB.

Your hosting provider might cap this at the server level though. So if you’re on shared hosting where they’ve set PHP memory to 128MB maximum, changing wp-config won’t push you past that ceiling. Quality WordPress hosting providers get this right from the start. They allocate proper resources and tune their servers for WordPress specifically, which means fewer headaches down the line.

Checking for Corrupted Core Files

Corrupted core files don’t happen as often as plugin crashes, but they’ll definitely trigger the white screen. Failed updates cause this or interrupted file transfers or someone accidentally editing core files. Grab a fresh WordPress download from wordpress.org and upload the wp-admin and wp-includes folders to overwrite what’s there.

Your content, themes, plugins and uploads stay completely safe because they’re all stored in the wp-content directory that you’re not touching. You’re just swapping out the core WordPress files for fresh, clean versions. Once everything’s uploaded, pop over to your site and check wp-admin since WordPress might ask you to run a database update if there’s been a version change.

Server-Side Issues and Error Logs

Server problems can trigger that blank screen just as easily as WordPress code. Your host might’ve changed the PHP version, there could be a wonky .htaccess file or you’ve hit resource limits on the server. Check your server’s error log through your hosting control panel and look for something like “Error Logs” or “Raw Access Logs” because these often show problems that WordPress debug logs miss completely.

Made recent changes to your .htaccess file? Rename it temporarily via FTP and see what happens. WordPress creates a basic.htaccess file automatically when you go to Settings, then Permalinks in your admin dashboard and hit Save. Corrupted.htaccess files cause more site problems than you’d expect, especially after security or caching plugins mess with rewrite rules. Regular WordPress maintenance keeps error logs monitored and configurations tidy, which stops small issues becoming complete site disasters.

Preventing the White Screen of Death

Prevention beats fixing every time the WSoD. Keep WordPress core, themes and plugins updated because most white screen problems are totally avoidable with proper site management. Updates patch bugs and compatibility problems that would otherwise cause fatal errors, so this single habit prevents more incidents than any other measure you can take.

Testing updates on staging catches problems before your visitors see them. Quality hosting providers usually include one-click staging environments where you can spot plugin conflicts or theme issues without any risk. Something breaks during testing? You’ve sorted the problem without touching your live site or damaging search rankings.

• Run regular backups so you can restore quickly if something goes wrong. A daily backup gives you a recent restore point that limits data loss.
• Keep the number of active plugins to what you need. Every additional plugin increases the chance of conflicts and adds to the memory footprint of each page load.
• Monitor your PHP error logs periodically, not just when things break. Non-fatal warnings and deprecated function notices can signal problems before they become critical.
• Choose well-maintained plugins and themes from reputable developers. Check the “last updated” date and active installation count before installing anything new.
• Make sure your hosting environment meets the recommended WordPress server requirements, including a supported PHP version and adequate memory allocation.

When you first see that white screen, it feels terrifying. But these errors aren’t random chaos. Plugin conflicts cause most cases, with theme errors and memory limits close behind. Start with basic checks then work through more complex troubleshooting until you find the culprit. Sites that can’t afford downtime need professional support for quicker fixes. Good hosting combined with regular updates and proper testing stops most problems before they start.