The WordPress White Screen of Death is exactly what it sounds like: you visit your site and see nothing but a blank white page. No error message, no header, no content, just white. This is one of the most alarming WordPress errors because it gives you zero information about what went wrong. Behind the scenes, WordPress encountered a PHP fatal error so severe that it could not even render an error page. By default, WordPress hides PHP errors from visitors for security reasons, which means instead of seeing a helpful error message, you see nothing. The WSOD can affect your entire site, just the admin dashboard, or only specific pages. It is the second most common WordPress problem we fix, behind plugin conflicts. The good news: your content, database, and files are almost always completely intact. The WSOD is a code execution problem, not a data loss problem.
Fix This Error Now →WordPress White Screen of Death can be caused by several issues. Here are the most common.
This is the cause roughly 60% of the time. A plugin update introduced a bug, two plugins are interfering with each other, or a plugin is not compatible with your PHP version. The site was working fine, a plugin updated, and now it is a white screen. Security plugins, caching plugins, and page builders are the most common offenders because they hook deeply into WordPress core.
Your active theme has a PHP error that crashes WordPress before it can render anything. This happens after theme updates, when editing theme files (especially functions.php), or when a theme is not compatible with the current PHP version. Since WordPress loads the theme on every single page, a broken theme means a sitewide white screen.
WordPress has a configurable memory limit (typically 40MB to 256MB depending on your host). When a page requires more memory than allowed, whether from loading a page builder, processing a WooCommerce catalog, or running a heavy plugin, PHP kills the process and WordPress shows a white screen. This often affects only specific pages (like your heaviest pages) while simpler pages work fine.
If an update is interrupted by a timeout, a connection drop, or insufficient disk space, files are left in a half-updated state. WordPress cannot load because some files are the new version and others are the old version, creating fatal incompatibilities. You may also see a ".maintenance" file left behind that blocks the site.
Core WordPress files can become corrupted from failed updates, malware infections, file permission changes, or server disk errors. Even one corrupted core file (like wp-settings.php or wp-includes/class-wp.php) can cause a sitewide white screen because WordPress cannot complete its boot sequence.
When your hosting provider upgrades PHP (for example, from PHP 7.4 to PHP 8.2), plugins and themes that use deprecated or removed PHP functions will crash. This can happen without warning if your host auto-updates PHP. The site was working yesterday, and today it is a white screen because PHP 8.x removed a function your theme relies on.
Manually editing critical files and introducing a typo, a missing semicolon, an unclosed bracket, or a wrong quote character causes an immediate fatal error. Since wp-config.php loads before WordPress and functions.php loads before the theme renders, any syntax error in either file produces a white screen with no error output.
PHP has a maximum execution time (usually 30-60 seconds). If a script takes longer than this to run, such as an import, a large database query, or a backup process, PHP terminates it. If this happens during page rendering, the result is a white screen or a partial page load that cuts off abruptly.
Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php to capture the exact error message and file location causing the crash
Access the site via FTP or your hosting file manager to work around the white screen and make changes directly
Rename the wp-content/plugins directory to disable all plugins at once, then test if the site loads
If plugins are the cause, re-enable them one by one to pinpoint exactly which plugin is crashing the site
Switch to a default theme like Twenty Twenty-Four by renaming your active theme's directory, isolating whether the theme is the problem
Check and increase the PHP memory limit by adding define("WP_MEMORY_LIMIT", "256M") to wp-config.php
If a core update failed, manually download a fresh copy of WordPress and replace the core files (wp-admin and wp-includes directories) via FTP
Delete the .maintenance file from the root directory if an update was interrupted and left it behind
Check with your hosting provider to verify the PHP version and switch to a compatible version if needed
After fixing the root cause, test the site thoroughly including admin dashboard, frontend pages, and any WooCommerce or membership functionality
The WordPress White Screen of Death (WSOD) shows a completely blank page with no error message. It is usually caused by a PHP error, plugin conflict, or theme issue. Here is how to fix it.
Add these lines to wp-config.php: define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); This will create a debug.log file in /wp-content/ showing the actual error.
Add to wp-config.php: define('WP_MEMORY_LIMIT', '256M'); The WSOD often occurs when PHP runs out of memory during page generation.
Connect via FTP, go to /wp-content/, and rename the plugins folder to plugins_disabled. If the site loads, a plugin caused the issue.
Rename your current theme folder in /wp-content/themes/ to themename_disabled. WordPress will fall back to a default theme. If this fixes it, your theme has a bug.
Download a fresh copy of WordPress from wordpress.org. Replace /wp-admin/ and /wp-includes/ folders (not wp-content). Corrupted core files cause WSOD.
After enabling debug mode, check /wp-content/debug.log for specific error messages. This tells you exactly what file and line caused the crash.
If nothing works, restore from your last known good backup. Most hosts keep automatic backups in cPanel or your hosting dashboard.
DIY is great, but sometimes you need expert help. Consider calling us if:
You cannot access your site via FTP or hosting panel
The debug log shows errors you do not understand
You do not have a recent backup
The white screen only appears on certain pages or for certain users
You recently updated WordPress core and things broke
Fixed in 2 hours or your money back. We do not waste time.
No hourly billing. You know the price before we start.
Cannot fix it? You do not pay. Zero risk to you.
Our Broken Pages & Error Repair team has fixed thousands of sites with this exact issue. 2-hour turnaround, guaranteed.
The WSOD is when your WordPress site displays a completely blank white page instead of your content. In newer versions of WordPress (5.2+), you may see a "There has been a critical error on this website" message instead of a pure white screen, but the cause is the same: a PHP fatal error that prevents WordPress from rendering the page. Your data and content are safe. It is a code execution problem, not a data loss issue.
You cannot tell from the white screen itself because no error message is shown. The diagnostic process is: first, disable all plugins at once via FTP (rename the plugins directory). If the site loads, a plugin is the cause. Then rename the directory back and disable plugins one by one by renaming individual plugin folders until the site breaks again. The last plugin you enabled before it broke is your culprit. We do this process in 15-30 minutes.
This usually means a plugin or feature that only runs in the admin dashboard is causing the crash. Common culprits are admin-heavy plugins like page builders in edit mode, advanced custom fields, or admin theme plugins. It can also be caused by a corrupted user session or a plugin that adds admin menu items with buggy code.
You need to access your files directly through FTP (using FileZilla or similar), through your hosting provider's file manager (cPanel, Plesk), or via SSH if available. From there, you can rename plugin folders, edit wp-config.php, and switch themes without needing the WordPress admin panel. If none of these options are available to you, that is exactly what we do for you.
No. The WSOD is caused by a PHP execution error, which means the code that generates your pages is failing, not the data itself. Your database (all posts, pages, comments, settings, users) and media files are completely untouched. Once the code error is resolved, everything comes back exactly as it was.
WSOD fixes typically cost $49-$79. Plugin conflicts and theme errors (the most common causes) are straightforward to diagnose and fix, falling at the $49 end. More complex causes like corrupted core files, PHP version incompatibilities, or database-related crashes are $79. You get a quote before we start, and if we cannot fix it, you pay nothing.
Yes. WordPress 5.2 and later replaced the blank white screen with this more helpful message. It is the same underlying problem: a PHP fatal error. WordPress may also send a recovery mode email to the admin email address with a special login link that lets you deactivate the problem plugin from the admin panel. Check your email (including spam) for a message from WordPress.
Never update plugins, themes, or WordPress core on a live site without a backup. Better yet, test updates on a staging site first. Keep your PHP version compatible with your plugins (check plugin documentation before upgrading PHP). Do not edit functions.php or wp-config.php unless you know exactly what you are doing. Use a quality managed WordPress host that handles PHP updates carefully. Set up automated daily backups so you can roll back quickly if something breaks.
Yes. You introduced a PHP syntax error into the file. Connect via FTP, navigate to wp-content/themes/your-theme/functions.php, and either fix the syntax error or revert to the previous version. If you do not remember what you changed, replace the file with the original from your theme's download. This is why we always recommend using a child theme and editing via the code editor rather than the WordPress theme editor.
Get wordpress white screen of death fixed today. Expert engineers. 2-hour guarantee.
Fix My Error Now →