Fix WordPress White Screen of Death (WSOD): The Complete Troubleshooting Guide
What Is the WordPress White Screen of Death (WSOD)?
The White Screen of Death (WSOD) in WordPress is a critical error where the website displays a blank white screen, with no error messages or content. This issue may affect:
- The entire website (frontend and backend).
- Only the WordPress admin panel (wp-admin).
- Specific pages or posts.
Unlike traditional PHP errors that output a message, WSOD hides clues, making it harder to fix—especially for beginners.
Why Does WSOD Happen? (Most Common Causes)
| Cause | Description |
|---|---|
| Plugin conflicts | Two or more plugins are incompatible or poorly coded. |
| Broken or incompatible themes | Corrupted or outdated themes can break your site. |
| PHP memory limit exhausted | WordPress runs out of available memory to execute scripts. |
| Recent updates | Updates to WordPress core, plugins, or PHP can introduce conflicts. |
| Syntax errors | Manual code changes in functions.php or custom plugins often introduce typos. |
| Corrupt WordPress core files | Missing or corrupted core files may halt rendering. |
| Server misconfigurations | Issues with PHP versions, execution time, or file permissions. |
How to Fix WordPress White Screen of Death (WSOD): Step-by-Step
1. Enable Debugging to Reveal Errors
The white screen hides errors by default. Enable WP_DEBUG in wp-config.php to uncover the root problem.
- Connect via FTP or File Manager (cPanel).
- Locate and edit the wp-config.php file in the root directory.
- Add (or modify) the following lines:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Code language: JavaScript (javascript)- Save the file and reload the page.
- Check the debug log: wp-content/debug.log: If debug.log shows a specific plugin or theme error, jump directly to the relevant fix below.
2. Deactivate All Plugins
Faulty plugins are the #1 cause of WSOD.
Step 1: Rename the /wp-content/plugins/ folder to /plugins-disabled/ to force-deactivate all plugins.
Step 2: Visit your site:
- If it loads → one of the plugins is broken.
- If it’s still blank → proceed to next step.
Step 3: Rename the folder back to /plugins/.
Step 4: Reactivate plugins one-by-one via wp-admin or FTP until the white screen returns.
Pro tip: Start with the most recently installed or updated plugins.
3. Switch to a Default WordPress Theme
If the issue lies in your active theme (e.g., missing files, broken code), you can force WordPress to load a safe fallback.
Step 1: Connect via FTP or File Manager.
Step 2: Go to /wp-content/themes/.
Step 3: Rename your active theme folder (e.g., astra → astra-old).
Step 4: WordPress will automatically switch to a default theme (like twentytwentyfour).
If no default theme is available, upload one manually from wordpress.org/themes.
4. Increase PHP Memory Limit
Running out of memory can crash the page before rendering anything.
a) Edit wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );Code language: JavaScript (javascript)b) Or edit .htaccess:
php_value memory_limit 256Mc) Or edit php.ini:
memory_limit = 256MNote: Some hosts cap memory at the server level. Contact your host if it doesn’t apply.
5. Check for Recent Code Changes or Syntax Errors
Even a single missing semicolon or bracket can bring down your site.
Review any recent changes to:
- functions.php
- Custom plugins
- Custom templates
Validate modified PHP files using PHP Code Checker.
Note: Undo or revert changes you made just before WSOD appeared.
6. Reinstall WordPress Core Files
If a corrupted or incomplete update occurred, reinstalling the core files can help.
Step 1: Download the latest WordPress version from WordPress.org.
Step 2: Extract the .zip file.
Step 3: Upload all files except:
- wp-content folder
- wp-config.php file
Step 4: Overwrite existing files via FTP or File Manager.
This ensures no plugin/content is lost, but restores any damaged core files.
7. Clear Cache (Browser, Plugin, CDN)
Sometimes WSOD persists due to caching:
- Browser cache: Hard refresh (Ctrl + F5)
- Caching plugins: Clear cache from wp-admin or delete /wp-content/cache/
- CDN (like Cloudflare): Purge cache from CDN dashboard
8. Check File and Folder Permissions
Incorrect permissions can block file execution.
- Files: 644
- Folders: 755
- wp-config.php: 440 or 400 (secure)
- Ownership: Should match your hosting user (e.g., www-data for Apache)
9. Review Server Error Logs
If none of the above worked, inspect your server logs for PHP or database issues.
Where to find logs:
- cPanel → Metrics → Errors
- FTP → /logs/ folder
- Or request from your hosting provider
Look for errors like:
Fatal error: Allowed memory size exhausted...or
Parse error: syntax error, unexpected... in functions.php on line 42Code language: CSS (css)10. Restore a Clean Backup
If you’re stuck and changes were recent, restoring a backup is the safest option.
- Use tools like UpdraftPlus, Jetpack, or host-level backups.
- Be cautious not to overwrite media/content if only core files were broken.
WSOD in wp-admin But Frontend Works?
- Usually caused by a broken plugin or admin theme script.
- Still follow the same steps: debug → deactivate plugins → switch theme → clear cache.
Avoid WSOD in the Future
| Action | Description |
|---|---|
| Always backup before updates | Use automatic backups or staging sites. |
| Test updates in staging | Don’t update directly on live site. |
| Limit plugin count | Avoid bloated or unknown plugins. |
| Use a child theme | Avoid editing core theme files directly. |
| Enable health monitoring | Use Site Health tool (Tools > Site Health) and monitoring plugins. |
When to Contact Hosting Support
If WSOD persists after all steps above, contact your hosting provider. Provide:
- Error messages or debug logs
- Time of occurrence
- Steps you’ve tried
A good host should help identify server-level errors (like memory or file permission issues).
Conclusion
The WordPress White Screen of Death is intimidating but highly solvable. By enabling debug mode, isolating plugins/themes, and correcting memory or code issues, you can regain control of your website quickly. Always back up before making changes, and document what you did to avoid repeating the issue.
RELATED POSTS
