How to Fix the “White Screen of Death” on Your WordPress Site

If you’ve ever visited your WordPress website and been greeted by a blank, white page, you’ve encountered what’s known as the “White Screen of Death” (WSoD). It’s a common issue that can cause panic, but with the right steps, you can usually resolve it quickly—even if you’re not a technical expert.

This guide will walk you through the most effective ways to get your site back online, using clear, actionable steps. Whether you’re a business owner, a marketer, or just managing your own website, these tips are designed to save you time and stress.

---

What Causes the White Screen of Death?

The WSoD is typically caused by:

• A conflict between plugins or themes
• PHP errors or running out of memory
• Corrupted files or incorrect file permissions
• Incomplete updates or server issues

Let’s get your site back up and running.

---

1. Check If the Problem Is Site-Wide

First, determine whether the issue affects your entire site or just certain pages (such as the admin area). If you have more than one website on the same hosting, check those as well. If all your sites are down, it could be a hosting or server problem—contact your provider for assistance.

---

2. Clear Your Browser and Site Cache

Sometimes, the problem is simply a cached version of your site.

• Refresh the page (Ctrl+F5 on Windows or Cmd+Shift+R on Mac).
• Clear your browser cache.
• If you use a caching plugin, clear your WordPress cache.
• If your host provides server-level caching, clear that as well.

More on clearing cache

---

3. Enable WordPress Debug Mode

Debug mode can help reveal hidden errors.

• Access your site’s files via cPanel File Manager or FTP.

• Open wp-config.php in your site’s root directory.

• Add or edit these lines before “That’s all, stop editing!”:

  php

  Copy

  define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_LOG’, true ); define( ‘WP_DEBUG_DISPLAY’, false );

• Save the file and reload your site. Check the new wp-content/debug.log file for error messages that may point to the cause (such as a plugin, theme, or code error).

How to enable debug mode

---

4. Deactivate All Plugins

A faulty plugin is the most common cause.

• If you can access the dashboard, go to Plugins > Installed Plugins and deactivate all.
• If you can’t access the dashboard, use FTP or File Manager:
  • Go to wp-content/
  • Rename the plugins folder to plugins_old
  • Reload your site. If it works, a plugin is the culprit. Rename the folder back and reactivate plugins one by one to find the problem.

Step-by-step plugin deactivation

---

5. Switch to a Default Theme

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

• Via FTP or File Manager, go to wp-content/themes/
• Rename your active theme’s folder (for example, astra to astra_old)
• WordPress will revert to a default theme (such as Twenty Twenty-Four). If your site loads, the theme was the issue.

---

6. Increase PHP Memory Limit

Low memory can cause the WSoD, especially on shared hosting.

• Edit wp-config.php and add:

  php

  Copy

  define( ‘WP_MEMORY_LIMIT’, ‘256M’ );

• Some hosts require you to increase memory in .htaccess or php.ini as well.

How to increase memory

---

7. Check for Corrupted or Missing Files

• Ensure core files like index.php, wp-settings.php, and .htaccess are present and not corrupted.
• File permissions should be 755 for folders and 644 for files.
• If necessary, re-upload a fresh copy of WordPress core files (excluding wp-content and wp-config.php).

---

8. Restore a Recent Backup

If all else fails, restore your site from a recent backup using your hosting control panel or backup plugin. Always back up your current site before restoring, in case you want to investigate further.

---

9. Contact Support

If you’re still stuck, reach out to your hosting support team. Provide them with any error messages from your debug log—they’ll be able to help you more efficiently.

---

Prevention Tips

• Keep plugins, themes, and WordPress core updated.
• Only use reputable plugins and themes.
• Maintain regular backups.
• Avoid editing core files unless you’re confident in what you’re doing.