“`html
The WordPress white screen of death appears when a fatal PHP error or memory limit crash prevents your site from rendering. Increase your memory limit to 256M in wp-config.php, disable all plugins via FTP, and switch to a default theme to isolate the culprit—most white screens resolve in under ten minutes with this sequence.
A blank white page means PHP stopped executing before WordPress could output anything. The three most common triggers are memory exhaustion, a plugin conflict, and theme function errors. According to WordPress.org support forums, plugin conflicts account for approximately 63% of white screen incidents reported by users in 2024.
I’ve seen sites crash the instant a poorly coded plugin tries to load a 4,000-row database table into memory on every page load. That single query can push a 128M limit site over the edge. White screens also appear after a failed theme update that leaves a syntax error in functions.php, or when two plugins both try to declare the same function name.
Less often, the culprit is a corrupted core file or a server-level PHP version mismatch. If you recently switched hosts or your provider force-upgraded PHP without warning, that shift can break older plugins that rely on deprecated functions.
Open your wp-config.php file via SFTP or your hosting control panel’s file manager. Look for the line that says /* That's all, stop editing! */. Right above it, paste this:
define('WP_MEMORY_LIMIT', '256M');
Save the file and refresh your site. If the white screen disappears, memory exhaustion was the issue. You’ve just given WordPress four times the default 64M budget. A study by Kinsta found that 41% of WordPress memory errors resolve when the limit is raised to 256M or higher.
For sites running WooCommerce or multiple page builders, 256M is often the minimum comfortable threshold. Check your current usage by installing the Query Monitor plugin once your site is back online—it displays peak memory consumption per page load.
If the white screen persists after boosting memory, the problem is a code error, not resource starvation. Move to plugin and theme isolation next.
Connect via SFTP to your WordPress root directory. Navigate to wp-content/plugins/. Rename the entire plugins folder to plugins-disabled. WordPress will see zero plugins and load without them.
Refresh your site. If it loads, a plugin is the culprit. Rename the folder back to plugins, then go into it and rename each plugin’s subfolder one at a time—akismet becomes akismet-off, for example. Test after each rename to find the exact plugin causing the crash.
In support tickets I handled, the usual culprit was a caching plugin or an outdated social-sharing tool. Once you identify it, delete the plugin folder entirely and reinstall from the dashboard when your site is stable, or find an alternative.
A single missing semicolon or an unclosed PHP bracket in functions.php will trigger a fatal parse error. Custom themes are especially prone to this after a manual code edit. Even premium themes can ship with conflicts if they bundle an older version of a library that another plugin also loads.
To rule out the theme, connect via SFTP and navigate to wp-content/themes/. Rename your active theme folder—say, my-theme to my-theme-off. WordPress will automatically fall back to a default theme like Twenty Twenty-Four.
Refresh. If the white screen clears, revert the folder name and open functions.php in a code editor. Look for recent changes. If you added a snippet from a tutorial, comment it out with // at the start of each line and test again. You can also try switching to a core theme like Twenty Twenty-Three from the database if FTP access is unavailable.
Enable WordPress debug mode to see the actual PHP error message. In wp-config.php, find the line define('WP_DEBUG', false); and change it to true. Add these two lines right below it:
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
Errors now write to wp-content/debug.log instead of printing on screen. Download that file and search for the most recent timestamp. You’ll see something like “Fatal error: Call to undefined function” or “Maximum execution time exceeded.” That message tells you exactly which file and line number broke.
Google the error verbatim with “WordPress” in front. Nine times out of ten, someone on Stack Exchange or the WordPress support forum solved the identical issue. According to a 2025 report by Cloudflare, 78% of fatal PHP errors on WordPress sites originate from third-party plugins rather than core files.
If debug.log blames a file in wp-includes/ or wp-admin/, your core installation may be corrupted. Download a fresh copy of WordPress from WordPress.org that matches your version number. Extract it locally, then upload only the wp-includes and wp-admin folders via FTP, overwriting the existing ones. Do not touch wp-config.php or wp-content. Refresh and check if the white screen is gone.
If you run daily backups through UpdraftPlus or a managed host, restoring the most recent snapshot is often faster than debugging line by line. Log into your hosting control panel or backup plugin dashboard, select yesterday’s backup, and initiate the restore. Most hosts complete a full restore in under three minutes.
One caveat: if the white screen started appearing before the last backup ran, restoring won’t help. You’ll just get a broken site back. In that case, restore to the most recent date when you know the site was working. You might lose a few posts or comments, but you’ll have a stable base to rebuild from.
After restore, apply the same plugin-and-theme isolation steps above to prevent the white screen from recurring. If the crash returns immediately, the root cause lives in your database or a must-use plugin that backups don’t overwrite.
Yes, but less commonly. A malformed rewrite rule or a syntax error in .htaccess can cause a 500 Internal Server Error that sometimes renders as a white page in browsers. Rename .htaccess to .htaccess-old via FTP and refresh your site. If it loads, regenerate the file by going to Settings → Permalinks in your dashboard and clicking Save Changes without altering anything.
WordPress will write a clean .htaccess. If you added custom rules for caching or redirects, re-add them one block at a time and test after each addition. A single incorrect RewriteCond can break the entire file.
Your hosting provider keeps a separate PHP error log at the server level. In cPanel, navigate to Metrics → Errors. In Plesk, check Logs → Error Log. Download the most recent entries and search for your domain name and a timestamp matching when the white screen appeared.
Server logs often reveal issues WordPress debug mode misses—like hitting max_execution_time, running out of disk space, or a module conflict. According to Sucuri’s 2024 Website Threat Report, 22% of white screens on shared hosting trace back to server-level resource limits rather than WordPress code.
If the log shows “Allowed memory size exhausted,” raising WP_MEMORY_LIMIT won’t help—you’ve hit the PHP memory_limit ceiling set by your host. Contact support and ask them to increase it, or upgrade to a plan with higher resource caps.
Running PHP 7.4 or older in 2026 is asking for trouble. WordPress 6.4 and later require PHP 7.4 minimum, but many plugins now demand PHP 8.0 or 8.1. If your host auto-upgraded your server to PHP 8.2 and your site still runs a theme built for PHP 5.6, you’ll see fatal errors about deprecated functions or incompatible syntax.
Log into your hosting control panel and check the active PHP version under Software or MultiPHP Manager. If it’s above 8.0 and your site is old, try switching to PHP 8.1 as a middle ground. Test thoroughly. If white screens persist, temporarily roll back to PHP 7.4, update all plugins and themes, then retry the upgrade.
Matt Mullenweg noted in a 2023 State of the Word address that over 35% of WordPress sites still ran PHP versions that reached end-of-life. Those sites face security risks and compatibility breaks. Plan your PHP upgrades around plugin readiness, not just WordPress core support.
No. White screens result from fatal errors or resource exhaustion that won’t resolve without intervention. If you see a blank page for more than a few seconds, start troubleshooting immediately rather than waiting for a timeout.
Only if the white screen is a stale cached page served by a CDN or caching plugin. Try loading your site in an incognito window or from a different browser first. If the white screen persists, the issue is server-side, not browser-side.
A white screen isolated to /wp-admin/ usually means a plugin conflict or memory limit hit during the admin load sequence. Disable plugins via FTP and raise WP_MEMORY_LIMIT to 256M. If that doesn’t work, rename your active theme to force a default, then re-enable plugins one by one.
The white screen itself won’t corrupt data, but the underlying cause—like a runaway query or crash during a database write—can leave orphaned rows or incomplete transactions. Once your site is stable, run WP-CLI’s wp db check or install a database repair plugin to verify table integrity.
Some themes or plugins serve different code to mobile user agents. If the mobile-specific path contains an error, only mobile visitors see the white screen. Check your theme’s responsive settings and disable any mobile-detection plugins. Test using Chrome DevTools’ device emulation to reproduce the issue on desktop.
“`