WordPress White Screen of Death: How to Fix It in 2026 (Step-by-Step)

You open your site and there’s nothing there. No error, no logo, no text — just a blank white page. This is the WordPress White Screen of Death (WSOD), and it’s one of the most common WordPress errors there is.

The good news: a white screen almost never means your content is gone. It usually means a script hit a wall — a plugin conflict, a theme error, or a memory limit — and WordPress, for security reasons, hides the actual error message from visitors instead of showing it.

This guide is a complete WordPress WSOD troubleshooting guide for 2026. It covers what causes the white screen, how to fix WordPress white screen of death whether or not you can still log into wp-admin, and how to stop it from coming back.

What Is the WordPress White Screen of Death (and Why Does It Happen)?

The white screen of death happens when PHP — the language WordPress runs on — hits a fatal error partway through loading a page. WordPress stops executing right there. Because production sites are configured not to display raw PHP errors to visitors, the browser just gets an empty response instead of a helpful message.

Since WordPress 5.2, this doesn’t always show up as a totally blank page. You might instead see the message:

“There has been a critical error on this website.”

That’s the same underlying problem as the classic white screen — WordPress just added a layer (called fatal error protection) that catches some of these crashes and shows a message instead of nothing at all. So if you searched for a WordPress critical error and landed here, you’re in the right place; the causes and fixes below apply to both.

Common causes include:

• A plugin or theme that was just installed or updated
• A PHP version that’s no longer compatible with your theme or plugins
• The PHP memory limit being exhausted
• A syntax error in functions.php or another theme/plugin file
• Corrupted or incomplete WordPress core files
• A caching or CDN issue showing you an old, broken version of the page
• File permission problems
• A hosting-side outage or resource limit

Step 0: Figure Out Which Kind of White Screen You Have

Before you start fixing anything, narrow down the problem. This determines which steps below actually apply to you.

Check these things:

1. Is it the whole site, just the frontend, or just wp-admin? Visit yourdomain.com/wp-admin directly. If the dashboard loads but the homepage doesn’t (or vice versa), that narrows things down a lot — a caching plugin, for example, usually only breaks the public-facing site while the dashboard stays fine.
2. Did it start right after a change? A wordpress white screen after plugin update or a white screen after installing a new theme is one of the most common patterns, and it points straight at that plugin or theme as the likely cause.
3. Are other sites on the same hosting account also affected? If every site on your account is showing a blank page, the problem is more likely with your hosting server than with any single WordPress install.
4. Try a private/incognito window. This rules out a stale browser cache before you touch any files.

Once you know whether you still have wp-admin access or not, jump to the matching steps below.

If You Can Still Access wp-admin

Step 1: Clear Your Cache

This is the fastest possible fix, and it’s worth trying first even though it feels almost too simple. If your admin area works fine but the frontend shows a white screen, caching is a very likely suspect.

• Clear your browser cache, or just open the site in a private window.
• If you use a caching plugin (WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, etc.), open its settings from the dashboard and clear/purge the cache.
• If you use a CDN like Cloudflare, clear the CDN cache separately — plugin-level cache clearing doesn’t always reach it.
• If your host provides server-side caching (common with managed WordPress hosting), clear that from your hosting dashboard too.

This is the core of any WordPress WSOD cache clearing tutorial: clear browser cache, then plugin cache, then CDN cache, then host-level cache, retesting after each one.

Step 2: Use WordPress Recovery Mode

If the error was caused by a plugin or theme, WordPress’s built-in fatal error protection may have already caught it. Check your site admin’s inbox for an email with the subject “Your Site is Experiencing a Technical Issue.” It identifies the plugin or theme that triggered the error and includes a one-time link into WordPress Recovery Mode, where you can deactivate just that plugin without touching anything else.

If you don’t have that email, or the link has expired, move on to the manual steps below.

Step 3: Increase the PHP Memory Limit

A large share of white screens happen because a script simply ran out of memory. Increase PHP memory limit WordPress WSOD fixes by editing your wp-config.php file (found in your WordPress root folder) and adding these two lines just above the line that says /* That's all, stop editing! Happy blogging. */:

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

WP_MEMORY_LIMIT raises the limit for the public-facing site; WP_MAX_MEMORY_LIMIT raises it specifically for the admin area, which often needs more headroom. If the white screen persists after this, your hosting provider may be capping PHP memory at the server level — in that case, contact their support and ask them to raise it.

Step 4: Disable All Plugins, Then Re-Enable One at a Time

This is the single most reliable way to catch a WordPress white screen of death plugin conflict. From Plugins → Installed Plugins, select all plugins and choose Deactivate from the Bulk Actions dropdown.

If the site comes back, reactivate your plugins one at a time, reloading the site after each one. The plugin that brings the white screen back is your culprit — you can then update it, replace it, or contact its developer.

Step 5: Switch to a Default WordPress Theme

If disabling plugins didn’t fix it, the WordPress white screen of death theme conflict is likely your active theme. Go to Appearance → Themes and activate a default theme (Twenty Twenty-Four, Twenty Twenty-Five, or similar). If the site loads normally, the problem is in your theme’s code — often in functions.php.

Step 6: Turn On Debug Mode

If none of the above found the cause, it’s time to make WordPress show you what’s actually happening. This is what a WordPress debug mode white screen of death fix looks like in practice. Add these three lines to wp-config.php:

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

Here’s what each one does:

• WP_DEBUG turns on WordPress’s debugging system.
• WP_DEBUG_LOG writes every error, warning, and notice to a file instead of (or in addition to) showing them.
• WP_DEBUG_DISPLAY set to false keeps those messages out of the browser, so visitors still see a clean site while you diagnose the issue.

After adding this, reload the page that’s showing the white screen, then check wp-content/debug.log for the most recent entries. The last fatal error listed is almost always your answer — it will usually name the exact file and line number. This is the heart of any solid WordPress WSOD error logging tutorial: reproduce the error, then read the newest lines in debug.log.

Important: once you’ve found and fixed the issue, set WP_DEBUG back to false. Leaving debug mode on a live site is a security risk.

If You Can’t Access wp-admin at All

This is the scenario people usually mean when they search for “white screen of death with no dashboard” — the front end, the login page, and the dashboard are all blank. You’ll need to work through your hosting File Manager or an FTP/SFTP client (like FileZilla) instead of the WordPress admin screens. This is the wordpress white screen of death without wp-admin access situation, and it’s more common than people expect after a bad plugin or theme update.

Connect via FTP/SFTP or File Manager

Log into your hosting account’s File Manager, or connect with an FTP client using the credentials from your host. Either way, you’ll navigate to your site’s root folder and then into wp-content.

Disable All Plugins by Renaming the Folder

This is the WordPress WSOD FTP solution most hosts and developers recommend first:

1. Inside wp-content, find the plugins folder.
2. Rename it to something like plugins-disabled.
3. Reload your site. WordPress can’t find a folder named plugins, so it treats every plugin as deactivated.

If the site comes back, rename the folder back to plugins, then rename the folders of individual plugins one at a time (inside the plugins directory) to find the specific one causing the problem. When you rename the broken plugin’s folder back to disable it and the rest stay active, you’ve confirmed the culprit.

If your host’s control panel doesn’t give you direct file access, contact support — most hosts can rename a plugin folder for you within minutes, or can point you to phpMyAdmin so you can remove the plugin from the active_plugins entry in the wp_options database table.

Switch Themes via FTP

If plugins weren’t the cause, go to wp-content/themes/, back up your current theme folder locally, then rename it (adding _old to the end works fine). WordPress will fall back to a default theme automatically. If you don’t have one installed, download a current default theme from WordPress.org and upload it into the themes folder via FTP.

Check the Server Error Logs

Most hosting control panels (cPanel, Plesk, or your host’s custom dashboard) include a PHP error log or “Error Log” section separate from WordPress’s own debug.log. This can reveal fatal errors even if you haven’t been able to enable WP_DEBUG yet, and it’s especially useful when you can’t reach wp-config.php easily.

Check File Permissions

Incorrect file permissions can also produce a white screen, especially after a migration to new hosting. A WordPress WSOD file permissions fix generally means:

• Folders: 755
• Files: 644
• wp-config.php: 440 or 600 (more restrictive, since it holds your database credentials)

If you see permissions set to 777, that’s a security risk and can sometimes trigger hosting-level blocks that show up as a white screen — change those back down.

Other Situations Worth Knowing About

White Screen Only on One Long Post or Page

If everything else on your site works but one very long post or page shows the white screen of death, it’s likely hitting PHP’s regex processing limits rather than memory. A WordPress white screen of death long post fix involves raising the recursion and backtrack limits in wp-config.php:

ini_set( 'pcre.recursion_limit', 20000000 );
ini_set( 'pcre.backtrack_limit', 10000000 );

Restore From a Backup

If you’ve worked through the steps above and the site is still down, or if the fix would take longer than restoring, a WordPress white screen of death backup restore is a completely reasonable move. Restore your most recent known-good backup through your backup plugin, your host’s backup tool, or by manually re-uploading files and importing a database export via phpMyAdmin.

Still Stuck? Contact Your Host

If you’ve cleared caches, checked plugins and themes, raised the memory limit, and checked the error logs — and it’s still blank — it’s time to open a support ticket with your hosting provider. Server-level issues (corrupted core files, a bad server update, resource limits you can’t see from your dashboard) are sometimes only fixable on their end, and most hosts can check this quickly.

How to Stop the White Screen From Happening Again

• Use a staging site for updates. Most hosts now offer one-click staging. Test plugin and theme updates there first, then push to your live site.
• Turn off automatic updates on production for major plugins, and update them manually during low-traffic hours so you can catch a problem immediately.
• Keep a recent, tested backup at all times. A white screen is far less stressful when you know you can restore in minutes.
• Update PHP, WordPress core, and plugins/themes regularly in small batches, rather than letting a large number of updates pile up and land all at once.

FAQ

Internal Link Opportunities

• Anchor text: “how to back up your WordPress site” → Recommended destination/topic: a guide on backing up WordPress (manual and plugin-based methods)
• Anchor text: “increase PHP memory limit” → Recommended destination/topic: a dedicated deep-dive on the WordPress memory exhausted error
• Anchor text: “using FTP to connect to your WordPress site” → Recommended destination/topic: a beginner’s guide to FTP/SFTP for WordPress
• Anchor text: “WordPress critical error” → Recommended destination/topic: a dedicated article on the “There has been a critical error” message
• Anchor text: “choosing a WordPress host” → Recommended destination/topic: a hosting comparison or “how to choose WordPress hosting” guide
• Anchor text: “staging site” → Recommended destination/topic: a guide on setting up and using a WordPress staging environment