9 Ways to Fix the WordPress White Screen of Death

The contractor's phone rang at 2:14 AM. On the line was a small business owner whose WooCommerce store had just disappeared — every page, every product, every order — swallowed by a blank white screen. No error message. No 404. Just emptiness where a revenue stream used to be.

That white screen is the WordPress White Screen of Death (WSOD), and it can strike anyone: a blogger who just updated a plugin, a developer tweaking a functions.php file, or a store owner who hit "update" and watched their site vanish. The most common cause is a PHP memory limit exhaustion or a fatal plugin conflict, and the quickest fix is often as simple as renaming a plugin folder via FTP or adding a single line to wp-config.php.

Before you try anything, back up your site — both files and database — and, if you can, enable WPDEBUG so WordPress shows you the actual error instead of a blank screen. If your hosting panel provides a staging environment, clone the site there first. Everything below assumes you want the site back up in minutes, not hours.

What causes the White Screen of Death?

The WSOD is a PHP fatal error that WordPress cannot render, so it outputs nothing. Below are the usual suspects, ordered by frequency:

9 ways to fix the WordPress White Screen of Death (ordered from fastest to most advanced)

1. Clear your browser and site cache

A cached version of a broken page can masquerade as a WSOD. Clear your browser cache, then navigate to /wp-admin directly. If the admin dashboard loads but the front end is white, bypass any caching plugin by appending ?nocache=1 to the URL or temporarily renaming the cache plugin's folder via FTP (wp-content/plugins/cache-plugin-name → wp-content/plugins/cache-plugin-name-old).

If your host uses a server-level cache (like Varnish or Redis), flush it from the hosting control panel. This step alone resolves roughly 10% of WSOD cases — always start here because it costs nothing and takes thirty seconds.

2. Increase the PHP memory limit

When WordPress exhausts the default PHP memory limit (often 32 MB or 64 MB on shared hosting), it can't load the page and returns a white screen. Open your wp-config.php file via FTP or your host's file manager and add this line just before the / That's all, stop editing! / comment:

define('WPMEMORYLIMIT', '256M');

If the admin area is also white, add this line as well:

define('WPMAXMEMORYLIMIT', '512M');

Save the file and reload the site. Most hosts allow up to 512 MB without a support ticket. If the white screen clears, the issue was a memory limit — you can later reduce it to a stable number like 128 MB or 256 MB.

3. Deactivate all plugins via FTP

If you cannot reach the WordPress admin dashboard, plugins are the number one culprit. Access the wp-content/plugins folder via FTP, select all folders, and rename the entire plugins directory to plugins-old. This forces WordPress to load with zero plugins enabled.

Visit your site's front end. If the white screen disappears, you know a plugin was the cause. Now rename the folder back to plugins and reactivate plugins one by one from the WordPress admin — after each activation, reload a page. When the screen goes white again, that plugin is the offender. Delete it or find an alternative.

4. Switch to a default theme via FTP

A broken or incompatible theme can also trigger the WSOD. Navigate to wp-content/themes and rename your active theme's folder (e.g., my-theme → my-theme-old). WordPress will automatically fall back to one of the default themes — Twenty Twenty-Five, Twenty Twenty-Four, or Twenty Twenty-Three.

Refresh your site. If it loads, your theme was the problem. You can either fix the original theme (look for syntax errors in functions.php or a recent template change) or choose a new, well-maintained theme.

5. Enable WPDEBUG to see the actual error

A blank screen tells you almost nothing. Turn on debugging so WordPress shows or logs the fatal error. In wp-config.php, find the line define('WPDEBUG', false); and change it to:

define('WPDEBUG', true);
define('WPDEBUGLOG', true);
define('WPDEBUGDISPLAY', false);

Now visit the broken page. The error will be logged to wp-content/debug.log. Download that file — it will contain a message like "PHP Fatal error: Uncaught Error: Call to undefined function …". That specific function name tells you exactly which plugin or theme file is the problem. Once you fix the issue, set WPDEBUG back to false to avoid exposing sensitive data to visitors.

6. Restore a corrupted .htaccess file

A corrupted .htaccess file can cause Apache to return an empty response. Rename .htaccess to .htaccess-old via FTP, then visit any page on your site. If the white screen clears, navigate to Settings → Permalinks in the WordPress admin and click "Save Changes" — this regenerates a fresh .htaccess file with WordPress's standard rewrite rules.

If you cannot reach the admin at all, create an empty .htaccess file locally, upload it to your root directory, and then regenerate permalinks once the site is back. Common causes of .htaccess corruption include botched security rules, caching plugin conflicts, and manual edits with missing syntax.

7. Repair the database

Sometimes a corrupted database table causes the WSOD only on specific pages (like a particular post or product). Add this line to wp-config.php above the / That's all / comment:

define('WPALLOWREPAIR', true);

Then visit https://yoursite.com/wp-admin/maint/repair.php and click the "Repair Database" button. After the repair completes, remove that line from wp-config.php — leaving it enabled is a security risk because anyone with the URL can trigger a repair.

If you prefer phpMyAdmin, select your database, check the "Check All" box, choose "Repair table" from the dropdown, and run it. This method is slower but does not require a separate URL.

8. Reinstall WordPress core files

An interrupted automatic update or a corrupted core file can cause a system-wide WSOD. Download a fresh copy of WordPress from wordpress.org, unzip it, and — using FTP — upload the wp-admin and wp-includes folders to your server, overwriting the existing files. Do NOT upload wp-content (that holds your themes, plugins, and uploads) or wp-config.php.

Overwriting these two core folders replaces dozens of potentially corrupted PHP files without touching any of your data. After the upload completes (it may take a few minutes), refresh the site. If the WSOD remains, the problem is almost certainly in a plugin or theme, not core.

9. Increase server resources or switch PHP version

If none of the above works, the problem may be server-level. Log into your hosting control panel and check: disk space usage (a full disk can cause PHP to fail silently), PHP version (WordPress recommends PHP 8.1 or higher; very old versions like 5.6 cause compatibility issues), and the PHP error log (often found under cPanel's "Error Log" or your host's dedicated tool).

If you see errors like "Allowed memory size exhausted" or "Maximum execution time exceeded", ask your host to raise those limits. Some shared hosting plans cap memory at 128 MB — upgrading to a VPS or a managed WordPress host often resolves persistent WSOD issues. If switching PHP versions is an option, try the next version up (e.g., from 7.4 to 8.1) and test again.

How to prevent the White Screen of Death from coming back

Once your site is healthy, a few preventive habits reduce the odds of a repeat WSOD. First, always test plugin and theme updates on a staging site before applying them to production. Second, enable automatic daily backups — your host may provide this, or you can use a plugin like UpdraftPlus or BlogVault. Third, keep a minimal, well-coded plugin set: every plugin you add increases the surface area for a fatal error.

Finally, consider using a managed WordPress platform or a maintenance service that monitors uptime and PHP errors in real time. If you run a content-heavy site — especially one that depends on fresh articles for traffic — a broken site costs you readers and search engine trust.

Speaking of keeping your site healthy while publishing consistently: nativeWP is an AI content automation platform that lets you bulk-generate SEO-optimized articles and auto-publish them to WordPress (or Shopify) with your own OpenRouter API key. Once you fix the technical foundation, nativeWP handles the pipeline from draft to live post — no manual copy-paste, no broken formatting. If you are ready to streamline your editorial workflow, check out nativeWP here.

Frequently asked questions about the WordPress White Screen of Death

Is the White Screen of Death the same as the WordPress maintenance mode screen?

No. The maintenance mode screen shows a brief message like "Briefly unavailable for scheduled maintenance." It appears when WordPress is updating core, themes, or plugins. The WSOD is a completely blank, white page with no text, HTML, or source code.

Can I fix the WSOD without FTP access?

Yes, if your hosting control panel provides a file manager (most do) or if you use a plugin that can be managed remotely. You can also ask your host's support team to deactivate plugins or rename the theme folder from their end. If none of these are available, the quickest route is often to contact support and request a PHP memory limit increase or a PHP error log export.

Will resetting permalinks help?

Sometimes. A corrupted .htaccess file — which stores permalink rules — can cause a white screen on specific URLs. Renaming .htaccess and then saving permalinks from the WordPress admin (if accessible) is a low-risk fix that takes under a minute.

Does a WordPress White Screen of Death affect SEO?

Yes, if it lasts more than a few hours. Search engine crawlers encountering a blank page may treat it as a soft 404 or a server error. If you have the site back within an hour and the page content has not changed, the SEO impact is usually negligible. A prolonged outage (24+ hours) can cause ranking drops.

What is the difference between a PHP error and a WSOD?

A PHP error often shows text — like a warning or a fatal error message — before the page breaks. The WSOD is a complete failure: the PHP interpreter hits a fatal error before it can output anything, so the browser receives an empty document. Enabling WPDEBUG is the best way to see the underlying error.

Key takeaways