How to Fix the WordPress White Screen of Death in 10 Minutes (Without Deleting Anything)

You refreshed your site and got nothing. A blank white page. No error message, no clue what broke. This is the WordPress White Screen of Death (WSOD), and it happens to nearly every site owner at some point. The good news: in most cases, you can fix it in under 10 minutes without deleting a single file.

This guide walks through every common cause, from plugin conflicts to memory limits to PHP errors, and gives you exact steps to fix each one. No FTP expertise required. No developer needed.

---

What Causes the WordPress White Screen of Death?

The WSOD has five main causes. All of them are fixable without deleting your content or reinstalling WordPress:

• Plugin conflict – a newly activated or updated plugin throws a fatal PHP error
• Theme conflict – your active theme has a bug or is incompatible with your PHP version
• Memory limit exhausted – WordPress runs out of PHP memory mid-load
• PHP fatal error – bad code in a plugin, theme, or custom snippet kills the page
• Corrupted .htaccess file – a malformed rewrite rule sends every request to a blank response

The approach below goes through the fastest checks first. Work through them in order.

---

Step 1: Check If the White Screen Is Site-Wide or Admin-Only

Before touching any files, narrow down the scope.

1. Visit your homepage (e.g. https://yourdomain.com)
2. Try your wp-admin login page: https://yourdomain.com/wp-admin
3. Try a single post URL

What you see	Likely cause
White screen everywhere, including wp-admin	Plugin, theme, or PHP fatal error
White screen only on the front end	Theme issue or .htaccess
White screen only in wp-admin	Admin-specific plugin or memory limit

---

Step 2: Enable WordPress Debug Mode

WordPress hides errors by default. Turning on debug mode reveals the exact PHP error causing the white screen.

How to edit wp-config.php

Find wp-config.php in the root of your WordPress install (same folder as wp-admin and wp-content). You can edit it via:

• cPanel File Manager – log in to cPanel, open File Manager, navigate to public_html
• FTP client – connect with FileZilla and open the file in your editor
• SSH – run nano wp-config.php

Find this line in wp-config.php:

define( 'WP_DEBUG', false );

Replace it with these three lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Save the file. Now reload your site. WordPress will write all PHP errors to wp-content/debug.log instead of showing them on screen.

Reading the debug log

Open wp-content/debug.log in File Manager or FTP. Look for lines starting with PHP Fatal error. The error message will tell you exactly which file and line number is broken. Example:

PHP Fatal error: Uncaught Error: Call to undefined function acme_plugin_init()
in /home/user/public_html/wp-content/plugins/acme-plugin/acme-plugin.php on line 42

That tells you acme-plugin is the problem. You can now target it directly.

---

Step 3: Disable All Plugins Without Logging In

If you cannot access wp-admin, you can disable every plugin by renaming the plugins folder. WordPress will deactivate all plugins automatically when the folder name changes.

1. Open your file manager or connect via FTP
2. Navigate to wp-content/
3. Rename the folder plugins to plugins-disabled
4. Reload your site

If the white screen goes away, a plugin is the culprit. To find which one:

1. Rename plugins-disabled back to plugins
2. Inside the plugins folder, rename each plugin subfolder one at a time (add -off to the name)
3. Reload your site after each rename until the white screen disappears
4. The last plugin you renamed is the one causing the issue

If you can access wp-admin, go to Plugins and deactivate all plugins from there. Then reactivate them one by one to find the bad one.

---

Step 4: Switch to a Default Theme

If disabling plugins did not fix it, your active theme may be broken. Switch to a default WordPress theme (Twenty Twenty-Four or Twenty Twenty-Three).

Option A: If you can access wp-admin

Go to Appearance > Themes and activate any default theme.

Option B: Via FTP or File Manager

1. Navigate to wp-content/themes/
2. Rename your active theme folder (e.g. mytheme to mytheme-disabled)
3. WordPress will automatically fall back to a default theme if one is installed

Option C: Via phpMyAdmin

In phpMyAdmin, open your WordPress database, go to the wp_options table, and find the row where option_name is stylesheet. Change its option_value to twentytwentyfour. Do the same for template.

---

Step 5: Increase the PHP Memory Limit

A low memory limit (32M is a common default on budget hosting) can cause a white screen when WordPress tries to load a heavy page or run a resource-intensive plugin. The fix is a one-line addition to wp-config.php.

Open wp-config.php and add this line just above /* That's all, stop editing! */:

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

Save and reload your site. If memory was the cause, the white screen disappears immediately. If your host’s PHP limit is set below 256M, you may also need to update .htaccess. Add this line to .htaccess in your WordPress root:

php_value memory_limit 256M

---

Step 6: Regenerate Your .htaccess File

A corrupted or malformed .htaccess file can block every page request and cause the white screen. Here is how to reset it safely:

1. Connect via FTP or File Manager and open .htaccess in your WordPress root (it may be hidden – enable “show hidden files” in your file manager settings)
2. Rename it to .htaccess-backup
3. Create a new file called .htaccess with this standard WordPress content:

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

Reload your site. If this fixes the white screen, your old .htaccess had an invalid rule. You can delete the backup once confirmed.

---

Step 7: Roll Back a Recent Update

If the white screen appeared right after a plugin or theme update, rolling back is faster than debugging the cause.

Using WP Rollback plugin

1. Install and activate the WP Rollback plugin (if you can access wp-admin)
2. Go to Plugins and find the plugin that was just updated
3. Click “Rollback” and choose the previous version

Via FTP when you cannot access wp-admin

1. Download the old version from wordpress.org/plugins/[plugin-name]/advanced
2. Unzip it on your computer
3. Upload the files via FTP to overwrite wp-content/plugins/[plugin-name]/

---

Step 8: Check Your PHP Version

WordPress 6.x requires PHP 7.4 or higher. If your host recently changed the PHP version for your account, it can break plugins or themes that relied on older PHP syntax.

Check your PHP version in cPanel under “MultiPHP Manager” or “PHP Version.” If it was recently changed, switch it back to your previous version and test. Then upgrade plugins and themes to PHP 8.x-compatible versions before upgrading again.

---

Step 9: Check Your Host’s Error Logs

If none of the above steps reveal the cause, check the server-level error log. This captures PHP fatal errors even when WordPress debug mode is off.

• cPanel hosts: cPanel > Metrics > Errors (shows the last 300 lines of your error log)
• SSH: run tail -100 /var/log/apache2/error.log or ask your host for the exact path
• Managed hosting (Kinsta, WP Engine, Flywheel): each has a log viewer in their dashboard

Look for Fatal error or Allowed memory size exhausted. The file path in the error points you directly to the problem.

---

Step 10: Increase the Maximum Execution Time

A timeout during a long database query or file import can also produce a blank screen. The default PHP max_execution_time is 30 seconds, which some operations (large imports, WooCommerce updates) can exceed.

Add this to your wp-config.php just above /* That's all, stop editing! */:

set_time_limit(300);

Or add this to your .htaccess:

php_value max_execution_time 300

This gives PHP up to 5 minutes to complete a request, which covers most long-running operations. If you only see the white screen during specific admin tasks (like a bulk import), this is likely your fix.

---

Common Mistakes When Fixing the WSOD

A few missteps can make the white screen problem worse or cause you to lose time. Watch out for these:

• Deleting wp-content/plugins entirely – renaming is safe; deleting removes your plugin files permanently. Always rename, not delete.
• Editing wp-config.php with smart quotes – if you copy-paste from a Word doc or email, curved quotation marks break PHP. Use a plain text editor like Notepad (Windows) or TextEdit in plain text mode (Mac).
• Leaving WP_DEBUG on after fixing – debug mode exposes your file paths and error details publicly. Always turn it off once the issue is resolved.
• Reinstalling WordPress unnecessarily – you do not need to reinstall WordPress to fix a WSOD. The problem is almost always in a plugin or theme, not WordPress core itself. If you want to verify your core files, WordPress > Dashboard > Updates > Re-install version X is safer than a full reinstall.
• Contacting your host before checking debug.log – most hosts will ask for the error message anyway. Read your debug.log first and you will get a faster resolution.

If your site is a WooCommerce store and you are seeing blank screens on checkout or cart pages, the same steps apply but start with WooCommerce-specific plugins first. The WordPress error troubleshooting guide covers WooCommerce-specific scenarios in more detail.

---

Quick Reference: WSOD Fixes by Symptom

Symptom	Fix
White screen after plugin update	Disable plugins via FTP (Step 3)
White screen after theme change	Switch theme via FTP or phpMyAdmin (Step 4)
White screen after content import	Increase memory limit (Step 5)
White screen after adding redirect rules	Reset .htaccess (Step 6)
White screen on all pages including admin	Enable debug, check debug.log (Step 2)
White screen only on front end	Theme issue or .htaccess (Steps 4 and 6)
White screen during bulk admin actions	Increase max execution time (Step 10)

---

After Fixing: Clean Up and Prevent Future WSOD

Once your site is back, do these five things before closing your file manager:

1. Turn debug mode back off in wp-config.php – set WP_DEBUG back to false
2. Delete wp-content/debug.log – it may contain sensitive server path information
3. Update or replace the plugin or theme that caused the problem
4. Set up automatic daily backups with a plugin like UpdraftPlus or BackWPup
5. Consider a staging environment – test plugin and theme updates there before applying to your live site

For a full list of common WordPress errors and how to fix them, see 10 Most Common WordPress Errors and How to Fix Them. If your site was taken down by a bad update, you can also restore from a backup in 15 minutes as an alternative path to recovery.

---

Frequently Asked Questions

Will fixing the WSOD delete my content?

No. Every fix in this guide works at the file level only. Your posts, pages, and database are not touched. Renaming the plugins folder or changing your theme does not delete anything – all data stays in your database.

What if I still see the white screen after all these steps?

Contact your host’s support team and share the exact error from your debug.log or server error log. Most shared hosts can identify server-level PHP errors quickly. If you are on a managed WordPress host, use their live chat – they have direct server access and can pinpoint the problem in minutes.

Is the WSOD the same as a 500 Internal Server Error?

Sometimes. A 500 error shows a browser error code, while the WSOD shows nothing at all. The causes often overlap – PHP fatal errors and .htaccess issues can produce either one. The fixes in this guide work for both.

How do I prevent the WSOD from happening again?

Three habits prevent most future WSOD incidents: keep a daily backup with UpdraftPlus, test updates on a staging site before applying them to production, and keep your PHP version current. Most shared hosts offer one-click staging through cPanel. WP Engine, Kinsta, and Flywheel include staging on all plans at no extra cost.

---

You’ve Got This

The WordPress White Screen of Death looks terrifying but it almost always has a simple cause. Plugins, themes, memory.htaccess – each one has a clear fix that does not involve deleting your content or reinstalling WordPress. Work through the steps above in order, check your debug log, and your site will be back in minutes.

Got your site back? Take 5 minutes to set up automatic backups so a future problem like this does not become a crisis. UpdraftPlus is free and backs up to Google Drive or Dropbox with no coding needed.

Beginner WordPress Tips White Screen of Death WordPress Error Fix WordPress Errors WordPress Troubleshooting

Last modified: April 24, 2026