How to Fix WordPress White Screen of Death (10 Ways)

The WordPress white screen of death is a blank page caused by a hidden PHP fatal error, usually from a plugin, theme, memory limit or PHP version problem. Fix it by checking where the page is blank, turning on WP_DEBUG_LOG to reveal the error, and fixing that cause. WPOptimizers can repair the site if the steps below don’t work.

The blank screen is frustrating because it tells you nothing. There is no message, no error code, and sometimes no way into the dashboard.

This guide changes that. You will learn how to make the hidden error visible, how to read it, and which fix matches each cause, including cases most guides skip, like a blank editor, a white screen after migration, and a site that stays blank after it’s been fixed.

How Do You Fix The WordPress White Screen Of Death?

Fix the WordPress white screen of death by first noting where the page is blank, then enabling debug logging to see the real error. Disable the plugin or theme it names, raise the memory limit or adjust PHP if needed, repair .htaccess or core files, and clear every cache. WPOptimizers follows this order on client sites.

Here are the 10 fixes covered in this guide, in the order to try them:

1. Use the Recovery Mode email if WordPress sent one
2. Turn on WP_DEBUG_LOG and read debug.log
3. Disable plugins to find a conflict
4. Switch to a default theme
5. Raise the PHP memory limit
6. Check the PHP version and missing extensions
7. Reset a broken .htaccess file
8. Finish a failed update and reinstall core files
9. Fix file permissions and free up disk space
10. Clear page, object, OPcache and CDN caches

Work from the top. Each step either finds the cause or rules one out, so you never change more than you need to.

What Is The WordPress White Screen Of Death?

The WordPress white screen of death (WSOD) is a completely blank white page that appears when PHP hits a fatal error and the error is hidden from view. It can affect the whole site, only the admin dashboard, or a single page. The site isn’t deleted; it just can’t finish loading.

Live sites hide PHP errors by default, which is correct for security but unhelpful when something breaks. The result looks the same whatever the cause: a broken plugin, a bad theme edit or exhausted memory all produce the same empty page.

That’s why the real first step is not to guess at a fix. It is to make the error visible.

WPOptimizers sees the WSOD most often right after plugin updates, PHP upgrades and site migrations.

Why Do You See A Blank Page Instead Of The Critical Error Message?

Since WordPress 5.2, released in May 2019, most fatal errors show “There has been a critical error on this website” and trigger a recovery email. A pure blank page usually means that protection did not run: the error happened too early, the handler was disabled, or the server stopped output first.

Common reasons the friendlier message doesn’t appear:

• The error happens before WordPress loads its error handler, for example in wp-config.php, a must-use plugin or a drop-in file.
• A developer disabled the handler with WP_DISABLE_FATAL_ERROR_HANDLER set to true.
• The server stops output, for example when memory or execution time runs out at server level.
• A blank cached page is being served from an earlier failure.

Whichever applies, the diagnosis is the same: read the logs. WPOptimizers checks the WordPress debug log and the server error log together.

What Causes The WordPress White Screen Of Death?

The most common causes are a plugin conflict, a theme error, PHP memory exhaustion, an incompatible PHP version, a broken .htaccess file, corrupted core files after a failed update, wrong file permissions, and a full disk. Where the blank page appears is the fastest clue to which one you’re facing.

Where The Page Is Blank	Most Likely Cause	Try First
Whole site and wp-admin	Plugin, memory or PHP version	Debug log, then rename plugins folder
Front end only, wp-admin works	Theme or front-end plugin	Switch to a default theme
wp-admin only, front end works	Admin-only plugin or theme functions	Rename recently updated plugins
One page or post	Page template, shortcode or block plugin	Check that page’s template and shortcodes
Block editor or page builder only	Editor add-on, memory or a JavaScript conflict	Disable editor add-ons, raise memory
Right after migration	PHP version, missing extensions, URLs or permissions	Compare server settings with the old host
Only for visitors, fine when logged in	Cache serving a blank page	Clear all cache layers

Note what changed most recently. An update an hour ago is a far stronger lead than any general list.

What Should You Check Before Changing Any Files?

Before changing files, back up wp-config.php and .htaccess, check your admin email for a recovery link, and confirm the site is blank for everyone, not just your browser. Also note recent updates or edits. These checks take minutes and often point straight to the cause.

1. Download copies of wp-config.php and .htaccess from the root folder, usually public_html. In File Manager, turn on “Show Hidden Files” to see .htaccess.
2. Check your admin inbox and spam folder for an email titled “Your Site is Experiencing a Technical Issue.”
3. Test in another browser, a private window, or on mobile data to rule out a local cache problem.
4. Check whether other sites on the same hosting account work. If they’re all blank, the server is the likely problem.
5. List recent changes: updates, new plugins, code snippets, PHP upgrades or a host move.

If you received a recovery email, click the link, log in, and deactivate the plugin or theme it names. Then exit Recovery Mode and reload the site. WPOptimizers always starts here when the email exists.

How Do You Make The Hidden Error Visible With WP_DEBUG?

Make the hidden error visible by enabling WP_DEBUG and WP_DEBUG_LOG in wp-config.php, keeping WP_DEBUG_DISPLAY off. Reload the blank page, then open wp-content/debug.log and read the newest “PHP Fatal error” line. It names the exact file, which usually points to the plugin or theme at fault.

Open wp-config.php with FTP (such as FileZilla) or your hosting File Manager. Add these lines above “That’s all, stop editing!” or replace any existing WP_DEBUG line:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

A typical log entry looks like this:

PHP Fatal error: Uncaught Error: Call to undefined function example_function()
in /wp-content/plugins/example-plugin/example-plugin.php:212

The path tells you where to look. A path in /wp-content/plugins/ points to that plugin, and one in /wp-content/themes/ points to your theme.

Keep WP_DEBUG_DISPLAY off so visitors never see file paths. When the site works again, set WP_DEBUG back to false and delete debug.log, as it can expose sensitive details.

If debug.log stays empty, check your host’s PHP error log in cPanel, hPanel or Plesk. WPOptimizers reads both before changing anything.

How Do You Fix A Plugin Conflict That Causes A White Screen?

Fix a plugin conflict by deactivating all plugins, confirming the site returns, then reactivating them one by one until the blank page reappears. If you can’t reach wp-admin, rename the plugins folder through FTP or File Manager. Then update, roll back or replace the faulty plugin.

If wp-admin works:

1. Go to Plugins → Installed Plugins.
2. Select all, choose Deactivate from Bulk actions, and click Apply.
3. Reload the site, then reactivate plugins one at a time.

If wp-admin is blank too:

1. Open /wp-content/ and rename plugins to plugins-off.
2. Reload the site. If it loads, a plugin is responsible.
3. Rename the folder back to plugins. All plugins stay installed but deactivated.
4. Reactivate them one by one, or rename individual plugin folders to isolate the culprit faster.

Sometimes two plugins conflict only when both are active, so test pairs if single plugins seem fine.

Before updating again, read the changelog and test on staging. This safe plugin update process prevents repeats, and WPOptimizers uses the same approach on maintained sites.

How Do You Fix A Theme That Causes A White Screen?

Fix a theme-caused white screen by switching to a default WordPress theme such as Twenty Twenty-Five. If wp-admin is blank, rename your active theme’s folder so WordPress falls back to a default theme, or change the theme in phpMyAdmin. Then repair or replace the faulty theme file.

1. In /wp-content/themes/, confirm a default theme is installed. If not, upload one by FTP.
2. Rename your active theme’s folder, for example my-theme to my-theme-off.
3. Reload the site. If it loads, the theme is the cause.

Alternatively, in phpMyAdmin, open the wp_options table and set both template and stylesheet to the default theme’s folder name. Back up the database first.

A common hidden cause is a stray space, blank line or invisible BOM character before <?php or after a closing ?> in functions.php. This can break page output and leave a blank screen. Remove the closing ?> at the end of PHP-only files to avoid it.

Make future edits in a WordPress child theme so a mistake only affects the child, never the parent. WPOptimizers builds client customizations this way.

How Do You Fix Memory Exhaustion That Causes A White Screen?

If debug.log shows “Allowed memory size of … bytes exhausted,” raise WP_MEMORY_LIMIT to 256M and WP_MAX_MEMORY_LIMIT to 512M in wp-config.php. If nothing changes, your host caps memory at server level, so raise memory_limit in your hosting panel or ask support. Then find what’s using so much memory.

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

WP_MEMORY_LIMIT covers normal front-end requests. WP_MAX_MEMORY_LIMIT covers heavier admin tasks such as image processing, imports and backups.

WordPress uses a low front-end limit of 40M by default, which page builders and large WooCommerce stores can exceed. Very high values rarely help and can hide a memory leak.

If memory keeps running out, a plugin or slow database query is usually to blame. A tool like Query Monitor shows which queries and plugins use the most resources.

Hosting matters too. Compare the best WordPress hosting for speed or see this guide to increasing the WordPress memory limit. WPOptimizers checks memory use during every speed audit.

Can The PHP Version Or Missing Extensions Cause A White Screen?

Yes. An outdated PHP version can break modern plugins, while a brand-new version can break older code that uses removed functions. After a PHP switch or host move, missing extensions such as mysqli, mbstring, curl or intl can also stop WordPress loading and leave a blank page.

Check your PHP version in Tools → Site Health → Info → Server, or in your hosting panel (for example MultiPHP Manager in cPanel).

If the white screen started right after a PHP upgrade, switch back to the previous version to restore the site. Then update the plugin or theme that failed before upgrading again.

Use the PHP version WordPress currently recommends on its official requirements page, and confirm your plugins and theme support it.

Site Health also flags missing required and recommended PHP modules. Ask your host to enable any that are missing.

WPOptimizers tests PHP upgrades on staging first, so a version change never lands on a live site untested.

How Do You Fix A Broken .htaccess File?

Fix a broken .htaccess file by renaming it to .htaccess-old and reloading the site. If the page returns, go to Settings → Permalinks and click Save Changes to generate a fresh file. Then re-add any custom rules from your backup copy, such as redirects or security settings.

Plugins that write caching, security or redirect rules can leave .htaccess in a broken state. That can cause a blank page, a redirect loop or a 500 error.

Keep your backup copy. Re-saving permalinks only restores the standard WordPress block, not custom rules you or your plugins added.

On Nginx servers there is no .htaccess, so check the server configuration with your host instead.

WPOptimizers reviews .htaccess rules during WordPress maintenance so conflicting plugin rules are caught early.

How Do You Fix A White Screen After A Failed WordPress Update?

After a failed update, check the site root for a hidden .maintenance file and delete it. If the site is still blank, reinstall WordPress core by replacing only the wp-admin and wp-includes folders and root files with a fresh copy. Never overwrite wp-content or wp-config.php.

1. In File Manager or FTP, show hidden files and delete .maintenance from the root folder if it exists.
2. Reload the site. If it loads, the update finished but the cleanup file stayed behind.
3. If it’s still blank, download a fresh copy of the same WordPress version.
4. Upload wp-admin, wp-includes and the root PHP files, overwriting the old ones.
5. Leave wp-content, wp-config.php and .htaccess untouched.

If wp-admin works, use Dashboard → Updates → “Re-install version x.x” instead. Over SSH, WP-CLI’s wp core download --skip-content --force does the same.

Take a backup before reinstalling. WPOptimizers keeps daily backups on maintained sites so this step is always reversible.

Can File Permissions Or A Full Disk Cause A White Screen?

Yes. Wrong file permissions can stop the server from reading WordPress files, and a full disk can stop PHP from writing sessions, cache and logs. Both can leave a blank page. Set files to 644 and folders to 755, never 777, and check storage use in your hosting panel.

Permission problems often follow a migration or a manual upload. Most FTP clients can apply 755 to folders and 644 to files recursively. See this WordPress file permissions guide for details.

Avoid 777. It lets anyone on the server write to your files, which is a serious security risk.

A full disk is easy to miss. Old backups, large log files and unused media often fill storage quietly. Delete or move them, then reload the site.

WPOptimizers monitors disk usage on managed sites, so storage never fills up without warning.

Why Is Only The Editor Or One Page Blank?

When only the block editor, a page builder editor or one page is blank, the cause is usually local to that area: an editor add-on, a shortcode from a deactivated plugin, a custom template, or a browser script conflict. Reproduce the problem, check debug.log, and test that area with add-ons disabled.

• Block editor blank: disable block add-on plugins one at a time, then check the browser console (F12) for JavaScript errors.
• Page builder won’t load: raise memory, update the builder and its add-ons, and test with other plugins disabled.
• One page blank: switch that page to the default template, remove shortcodes one by one, and check for a missing plugin.
• WooCommerce checkout blank: test payment and shipping plugins first, since a broken checkout stops sales while the rest of the store looks fine.

Clearing your browser cache also helps, because editors load many scripts that can be cached in a broken state.

WPOptimizers tests checkout, forms and key pages after every fix, not just the homepage.

Why Does The White Screen Appear After A Site Migration?

A white screen after migration usually comes from a different PHP version or missing extensions on the new server, wrong database details in wp-config.php, incorrect siteurl and home values, wrong file permissions, or a damaged search-and-replace of URLs. Compare the new server with the old one first.

• Match the PHP version used on the old host, then upgrade later on staging.
• Confirm DB_NAME, DB_USER, DB_PASSWORD and DB_HOST in wp-config.php.
• Check siteurl and home in the wp_options table.
• Reset permissions to 644 for files and 755 for folders.
• Use a serialization-safe search-and-replace tool when changing domains, as plain text replacement can break stored settings.

If you’re choosing a new host, compare managed vs shared hosting or browse cloud hosting providers in the USA.

WPOptimizers handles migrations with a full checklist, so the new site matches the old one before DNS changes.

Why Does The Site Still Look Blank After You Fixed It?

A site can look blank after a successful fix because a cache is still serving the old empty page. Clear your caching plugin, hosting cache, object cache such as Redis or Memcached, PHP OPcache and your CDN, then test in a private window before assuming the fix failed.

This catches many people out. They undo a correct fix because a cached blank page made it look like nothing changed.

Clear caches in this order: caching plugin, hosting cache, object cache, then CDN.

If you use Redis or Memcached, flush it from the plugin or hosting panel.

WPOptimizers purges every cache layer as a standard final step after any repair.

Still Staring At A Blank Page?

If the fixes above haven’t worked, or you’d rather not edit files on a live site, WPOptimizers WordPress developers can find the hidden error, repair your site, and check that forms, checkout and key pages work.

Get WordPress Help

How Is The White Screen Of Death Different From The Critical Error And A 500 Error?

All three can come from fatal problems, but they look and behave differently. The white screen of death is a fully blank page with no message. The critical error shows a message and usually sends a recovery email. A 500 internal server error shows a server error page and often comes from server configuration.

Error	What Visitors See	Typical Cause	Best First Step
White screen of death	Completely blank page	Hidden PHP fatal error, memory or output issue	Enable WP_DEBUG_LOG
Critical error	“There has been a critical error on this website”	Fatal PHP error caught by WordPress	Recovery email and debug.log
500 internal server error	“500 Internal Server Error” page	Server config, .htaccess, PHP limits	Server error log and .htaccess

Treating them as the same error wastes time. A 500 error often needs server-level checks, while the other two usually point to code.

WPOptimizers diagnoses all three from the logs first, then fixes the specific cause.

When Should You Restore A Backup Instead Of Fixing The Error?

Restore a backup when you can’t find or fix the cause, when files are badly damaged, or when the site may be hacked. Otherwise, fix the cause first, because restoring can erase recent posts, form entries and WooCommerce orders made after the backup was taken.

Before restoring, export any recent orders or form entries if you can reach the database.

Choose the most recent backup from before the white screen started, then repeat the update or change more carefully on staging.

Know how to restore WordPress from backup before you need it. A restore you have never tested is a risk.

WPOptimizers keeps offsite backups for maintained sites, so a clean restore point is always available.

How Do You Stop The White Screen Of Death From Coming Back?

Stop the white screen of death from returning by testing updates on staging, keeping automatic offsite backups, updating plugins one at a time, keeping PHP on a supported version, watching disk space and error logs, and using uptime monitoring. A WordPress maintenance plan handles these tasks for you.

• Use staging for plugin, theme and PHP updates.
• Back up daily and store copies offsite.
• Update one plugin at a time and read changelogs first.
• Remove unused plugins and themes to reduce conflicts.
• Watch disk space and logs so warnings are caught before a fatal error.
• Monitor uptime so you hear about downtime within minutes.
• Keep the site secure, because injected code can also cause a blank page. See how to secure a WordPress site.

Buying new plugins during sales? Check them on staging first, even when they come from the best WordPress Black Friday deals.

WordPress maintenance plans from WPOptimizers start at $49 per month and keep updates, backups and site health under control.

Frequently Asked Questions About The WordPress White Screen Of Death

These answers cover the questions site owners ask most often about the WordPress white screen of death, from data safety and fix time to SEO, Multisite and hosting support, based on the fixes WPOptimizers uses when repairing client websites.

Will I Lose My Content Because Of The White Screen Of Death?

No. The white screen of death stops pages from loading, but your posts, pages, media and database stay in place. Content is only at risk if you delete folders, overwrite wp-content, or restore an old backup carelessly. Rename folders instead of deleting them, and back up before editing files.

Why Is My Site Blank For Visitors But Fine When I’m Logged In?

This usually means a cache is serving a blank page to logged-out visitors, while logged-in users bypass the cache. Clear your caching plugin, hosting cache, object cache and CDN. If the problem returns, a front-end plugin or the theme may be failing only on cached or public requests.

How Long Does It Take To Fix The White Screen Of Death?

Most white screens caused by one plugin, theme or memory limit can be fixed within an hour once debug.log shows the cause. Problems linked to PHP versions, migrations, the server or a hacked site take longer and may need your host or a WordPress developer.

Can Malware Cause The White Screen Of Death?

Yes. Injected PHP code or modified core files can trigger fatal errors and leave a blank page. Warning signs include unknown files, new admin users, and redirects to spam sites. Scan the site, remove infected files, change all passwords, and update every plugin and theme.

Does The White Screen Of Death Hurt SEO?

A short outage usually has little lasting SEO impact, because search engines retry pages later. Long or repeated downtime can cause pages to drop from results and lose traffic. Fix the error quickly and use uptime monitoring to protect rankings. Some ranking drops have other causes, as covered in this guide to rankings that fluctuate without a Google update.

What Memory Limit Should A WordPress Site Use?

Most WordPress sites run well with WP_MEMORY_LIMIT set to 256M and WP_MAX_MEMORY_LIMIT set to 512M for admin tasks. Your host’s server limit must be equal or higher for these to work. If you still run out of memory, find the plugin or query using it.

Can The White Screen Of Death Affect WordPress Multisite?

Yes. On Multisite, a network-activated plugin or a shared theme can blank every site in the network at once. Disable network plugins by renaming their folders, check the network admin email for recovery notices, and test each site after the fix.

Can My Hosting Provider Fix The White Screen Of Death?

Your host can confirm server status, share PHP error logs, raise memory limits, change PHP versions and enable missing extensions. Many hosts won’t fix plugin or theme code. For those issues, a WordPress developer or maintenance provider such as WPOptimizers can complete the repair.

What Should You Remember The Next Time Your Screen Goes White?

Remember that a white screen is a hidden error, not a deleted site. Note where the page is blank, make the error visible with debug.log, fix the named cause, and clear every cache. WPOptimizers recommends reviewing your update process afterward, because that is what prevents the next one.

• Your content is safe, so don’t delete anything in a panic.
• Check where the page is blank: whole site, admin, editor or one page.
• Back up wp-config.php and .htaccess before editing.
• Use WP_DEBUG_LOG with display turned off to find the cause.
• Rename plugin and theme folders instead of deleting them.
• Set memory to 256M and keep PHP on a supported version.
• Clear page, object, OPcache and CDN caches after fixing.
• Prevent repeats with staging, offsite backups and uptime monitoring.

What Is The Fastest Way To Fix A WordPress White Screen?

The fastest route is the Recovery Mode email, if WordPress sent one. If not, enable WP_DEBUG_LOG, read debug.log, and rename the plugin or theme it names. Most sites come back within minutes once the error is visible, and WPOptimizers can step in when it isn’t.

Afterward, write down what caused the problem and when. Patterns, such as one plugin breaking after every update, show what to replace or test more carefully.

Keep Your WordPress Site Up And Running

WPOptimizers WordPress maintenance plans start at $49 per month, with managed updates, backups and site monitoring, so problems are caught early and fixed before your visitors see a blank page.

View Maintenance Plans