Table of contents
1. Server issues2. Clear cache3. Debug mode4. Deactivate plugins5. Default theme6. Memory limit7. Check code errors8. Check permissions9. Database issues10. Use WP-CLI 11. Restore backup12. Contact support13. Check error logs 14. Check cron jobs15. Use a staging site Next stepsAdditional resources
Get the industry’s fastest hosting for WordPress◦ 100% network uptime
◦ Comprehensive security
◦ 24/7 support
Explore options

WordPress Guide → Errors → White Screen

How to fix the WordPress white screen of death

Nothing derails your WordPress workflow faster than opening your site to find… nothing. Just a blank, white screen. No error message. No content. Just confusion.

Let’s walk through how to fix the WordPress white screen of death (WSOD), step-by-step—so you can get your site back online as quickly as possible.

What causes the white screen of death in WordPress?

The WSOD usually signals a fatal PHP or server-side error that prevents WordPress from rendering your site. But without visible clues, finding the root cause can be tricky. Common culprits include:

  • A broken or incompatible plugin
  • Errors in your theme’s functions.php file
  • PHP memory exhaustion
  • Incorrect file permissions
  • Syntax errors in custom code
  • Corrupt database or server misconfigurations

1. Check for server issues

Before digging into WordPress, make sure your hosting server is working.

  • Try accessing other websites on the same server.
  • Log into your hosting dashboard or cPanel to check for downtime or maintenance alerts.
  • Look for 500 errors or resource overages in server logs.

If your host is down or the server crashed, fixing WordPress won’t help until that’s resolved.

2. Clear your browser and site cache

Sometimes the white screen is only visible to you due to outdated or cached content.

  • Clear your browser cache completely (Chrome: Settings > Privacy > Clear browsing data).
  • Force-refresh the page (Ctrl + F5 on Windows, Shift + Reload on Mac).
  • If you use a caching plugin (like WP Super Cache), clear the cache in the plugin settings.
  • If you use a CDN like Cloudflare, clear the CDN cache too.

Still seeing a white screen? Move on to deeper fixes.

3. Enable WordPress debug mode

WordPress has a built-in debug tool to help uncover hidden errors.

  1. Open your wp-config.php file using FTP or your file manager.
  2. Add or update these lines just above the line that says “That’s all, stop editing!”:

    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_LOG’, true);
    define(‘WP_DEBUG_DISPLAY’, false);
  3. Visit your site again. WordPress will log any errors to a file located at wp-content/debug.log.

Check the log for clues like a faulty plugin or syntax error, then turn debugging back off once you’re done.

4. Deactivate all plugins

Plugins are the most common cause of the WSOD. If you can access the admin dashboard:

  1. Go to Plugins > Installed Plugins.
  2. Use the bulk selector to deactivate all plugins.

If you can’t access wp-admin:

  1. Use FTP to connect to your site. Here’s how in Linux. Here’s how in Windows.
  2. Navigate to wp-content/ and rename the plugins folder to something like plugins-disabled.
  3. This will deactivate all plugins at once.

Check your site. If it works again, one of the plugins was the problem. Rename the folder back and reactivate plugins one by one to find the culprit.

5. Switch to a default theme

If plugins aren’t the issue, the theme might be.

  • If you have admin access, go to Appearance > Themes and activate a default theme like Twenty Twenty-Four.
  • If not, connect via FTP and rename your active theme folder inside wp-content/themes.

WordPress will fall back to the default theme if it’s available. If the white screen disappears, the problem is with your theme.

6. Increase your PHP memory limit

Low PHP memory limits can prevent WordPress from completing requests.

  • Open your wp-config.php file.
  • Add this line near the top:
    define(‘WP_MEMORY_LIMIT’, ‘256M’);

You can also increase memory via your php.ini or .htaccess files, depending on your host. If your host enforces strict limits, you may need to contact support.

7. Check for syntax or code errors

If you recently edited your theme’s functions.php file, a plugin, or custom code, even a missing semicolon can break your site.

  • Revert any recent changes you made manually.
  • Use an IDE or code editor with linting to identify syntax issues.
  • If you have a Git or backup system, restore the last known good version.

8. Check file and folder permissions

Incorrect file permissions can block WordPress from loading files properly.

  • Files should usually be set to 644 and folders to 755.
  • Use your FTP client or hosting file manager to check and correct permissions.

9. Check for database issues

A corrupted or unreachable database can cause the WSOD too. If you see an “Error establishing a database connection” message:

  • Log into phpMyAdmin to check credentials and status.
  • Add this line to wp-config.php to enable database repair:
    define(‘WP_ALLOW_REPAIR’, true);
  • Then visit yoursite.com/wp-admin/maint/repair.php to repair your database.

Remember to remove that line after repairing.

10. Use WP-CLI to fix from the command line

If you’re comfortable with command line access and have WP-CLI installed:

  • Deactivate all plugins:
    wp plugin deactivate –all
  • Activate a default theme:
    wp theme activate twentytwentyfour
  • Run checks:
    wp config get WP_DEBUG
    wp core verify-checksums

WP-CLI can be faster than using FTP or a file manager.

11. Restore from a backup

If you have a full-site backup from a plugin or your host:

  • Log in to your host or backup dashboard.
  • Choose the most recent known-good backup.
  • Restore the full site or just the affected parts (e.g., plugins or themes).

If your site has auto-backups from your host, ask support for help restoring. Get full details on, How to restore a WordPress site from a backup.

12. Contact your hosting provider or WordPress support

If nothing works, your hosting support may be able to help. They can check:

  • PHP errors
  • Memory logs
  • Auto-update failures
  • Server-side configuration issues

You can also visit wordpress.org/support or the WordPress Stack Exchange to ask for help.

13. Try checking error logs at the server level

Your server may have its own logs beyond WordPress.

  • In cPanel or Plesk, look for “Errors” or “Logs.”
  • FTP users can often find an error_log file in /public_html or root folders.
  • Look for recent entries like PHP Fatal error or Allowed memory size exhausted.

This can point you to the exact plugin, theme file, or line number that caused the failure.

14. (Advanced method) Check cron jobs and auto-updates

If your site went down without warning, a background update may have broken something.

  • Install the WP Crontrol plugin (if you can access admin) to check scheduled cron jobs.
  • Disable automatic background updates in wp-config.php:
    define(‘AUTOMATIC_UPDATER_DISABLED’, true);
  • Re-enable only after you’ve stabilized your site.

15. Use a staging site to test fixes safely

If your live site is down but you want to test plugin or code changes:

  • Set up a staging environment through your host or with a plugin like WP Staging.
  • Replicate the issue and try fixes without risk.
  • Once fixed, push changes to your live site.

This is a best practice for major updates, troubleshooting, and testing new code.

New subscriber notification FAQs

The white screen of death (WSOD) is a blank page shown when WordPress hits a critical error that prevents it from loading. It usually hides error messages, making it harder to identify the cause.

It could be caused by:

  • A broken or incompatible plugin
  • A theme with syntax errors
  • PHP memory exhaustion
  • A failed update
  • File permission or server issues

Enable debug mode in wp-config.php, log errors, deactivate plugins, switch themes, and increase memory limits. If needed, check server error logs or use WP-CLI.

If you have access:

  • Use your caching plugin settings (e.g., W3 Total Cache or WP Super Cache).
  • Clear browser cache and CDN cache (e.g., Cloudflare).
  • Or manually delete the wp-content/cache/ directory via FTP.

Additional resources

Diagnosing WordPress errors on your site →

Even more common errors, how to troubleshoot them, and how to solve them

Fixed: WordPress failed to write file to disk →

Learn how to fix the “Upload: Failed to Write File to Disk” error in WordPress with easy troubleshooting steps.

What is managed WordPress hosting? →

What it means, what it includes, and how to decide if it’s right for you