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

You load your WordPress site. Nothing comes back. No error message. No layout. Just a completely blank white page staring at you.

This is the WordPress White Screen of Death (WSOD). It is one of the most searched WordPress errors in 2026, and for good reason. It gives you zero clues about what went wrong.

The good news: the WSOD is almost always fixable within 15 to 30 minutes without data loss. This guide walks you through every proven fix in the exact order most likely to resolve your specific situation.

What Is the WordPress White Screen of Death?

The WordPress White Screen of Death is a blank browser page that appears when PHP encounters a fatal error. WordPress stops executing before it renders any content. Because PHP error reporting is turned off on most live sites for security, nothing shows on screen except white.

In WordPress 5.2 and later, you sometimes see “There has been a critical error on this website” instead of pure white. Both messages have the same root causes and the same fixes.

According to Kinsta, the WSOD is almost always caused by PHP code errors or memory limit exhaustion. A faulty plugin or theme is the root cause in the majority of cases.

Before You Start: Diagnose Which Version You Have

Not all WSoDs are the same. Your fix depends on where the blank screen appears.

Check your site and your /wp-admin URL separately before proceeding. Knowing which scenario you have cuts your fix time in half.

Step 1: Check Your Recovery Mode Email

WordPress 5.2 and later automatically sends a recovery mode email to your admin address when a fatal error occurs during an update.

What to do:

1. Check the inbox for your WordPress admin email address.
2. Look for a subject line: “Your Site is Experiencing a Technical Issue.”
3. Click the recovery link inside the email.
4. This gives you temporary access to your dashboard even with the WSOD active.
5. From there, deactivate the plugin or theme WordPress identifies as the problem.

If you received this email, the fix is already pointed out for you. If you did not receive it, move to Step 2.

Step 2: Enable WordPress Debug Mode

Debug mode shows you the actual PHP error instead of a blank screen. This is the fastest way to identify the exact cause.

How to enable debug mode:

1. Log in to your hosting control panel (cPanel, Plesk, or your host’s dashboard).
2. Open the File Manager and navigate to your WordPress root directory (usually public_html).
3. Find wp-config.php and open it for editing.
4. Find this line:

define( 'WP_DEBUG', false );

5. Replace it with these three lines:

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

6. Save the file and reload your site.

Now check /wp-content/debug.log in your file manager. The log shows the exact file and line number causing the error.

Common error messages you might see:

Once you know the error type, jump to the fix for that specific issue below. If debug mode shows nothing or you prefer to work through the fixes in order, continue to Step 3.

Step 3: Deactivate All Plugins

Plugins cause the WSOD in the majority of cases, according to multiple sources including Codeable and SpinupWP.

If you can access your WordPress dashboard:

1. Go to Plugins > Installed Plugins.
2. Select all plugins using the checkbox at the top.
3. Choose “Deactivate” from the Bulk Actions dropdown.
4. Click Apply.
5. Reload your site.

If you cannot access your dashboard (Scenario C from the table above):

1. Log in to your hosting File Manager or connect via FTP.
2. Navigate to wp-content/.
3. Find the folder named plugins.
4. Rename it to plugins_deactivated.
5. Reload your site.

If the white screen disappears, a plugin was the cause. Rename the folder back to plugins. Then reactivate plugins one at a time, reloading the site after each activation. When the white screen returns, the last plugin you activated is the problem plugin. Keep it deactivated and contact its developer or find an alternative.

If deactivating plugins did not fix the white screen, move to Step 4.

Step 4: Switch to a Default WordPress Theme

If the problem is not a plugin, your active theme is the next most likely cause. A syntax error or incompatible function in functions.php produces a white screen in exactly the same way a bad plugin does.

If you can access your dashboard:

1. Go to Appearance > Themes.
2. Activate a default WordPress theme such as Twenty Twenty-Five.
3. Reload your site.

If you cannot access your dashboard:

1. Open your hosting File Manager or FTP client.
2. Navigate to wp-content/themes/.
3. Rename your active theme folder. For example, rename mytheme to mytheme_old.
4. WordPress automatically falls back to the next available theme.
5. Reload your site.

If the white screen disappears after switching themes, the problem is in your original theme. Check functions.php for recent changes, or contact your theme developer.

If neither plugins nor themes fixed the issue, move to Step 5.

Step 5: Increase the PHP Memory Limit

WordPress requires a minimum of 64MB of PHP memory. Complex sites with page builders like Elementor or Divi, multiple plugins, and heavy themes regularly exceed 128MB or 256MB. When PHP runs out of memory, the WSOD is the result.

According to GigaPress, the recommended memory limit in 2026 is at least 256MB. Managed WordPress hosts like Kinsta set 256MB by default.

Method 1: Edit wp-config.php (fastest)

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

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

Method 2: Edit .htaccess (Apache servers only)

Add this line to the top of your .htaccess file in the WordPress root directory:

php_value memory_limit 256M

Method 3: Edit php.ini

If your host gives you access to a php.ini file, add or update this line:

memory_limit = 256M

Method 4: Through your hosting dashboard

Most managed hosts (SiteGround, Kinsta, WP Engine, Cloudways) let you change the PHP memory limit directly from your control panel without editing any files.

After increasing the memory limit, clear your site cache and reload your site.

Step 6: Check and Fix the .htaccess File

A corrupted .htaccess file stops Apache from processing requests before WordPress or PHP even loads. This produces an instant white screen.

How to fix it:

1. Open your hosting File Manager or FTP client.
2. Navigate to your WordPress root directory.
3. Find .htaccess (enable hidden files if you do not see it).
4. Rename it to .htaccess_old.
5. Reload your site.

If the white screen disappears, the .htaccess file was the cause. Regenerate a clean one by going to Settings > Permalinks in your WordPress dashboard and clicking Save Changes. WordPress writes a fresh .htaccess file automatically.

Step 7: Check File Permissions

Incorrect file permissions prevent the server from reading WordPress files. This is less common but produces a white screen when it occurs.

The correct WordPress file permission settings are:

If you have SSH access, run these commands from your WordPress root directory:

find . -type f -exec chmod 644 {} +
find . -type d -exec chmod 755 {} +
chmod 640 wp-config.php

If you do not have SSH access, use your hosting control panel’s file permission tool to check and correct these values.

Step 8: Re-upload WordPress Core Files

If every other step failed, your WordPress core files are corrupted. A failed or interrupted update often causes this.

How to fix it:

1. Download the latest version of WordPress from wordpress.org.
2. Extract the ZIP file on your computer.
3. Delete the wp-content folder from the extracted files. Do not upload this folder. It contains your themes, plugins, and uploads.
4. Connect to your site via FTP or File Manager.
5. Upload the remaining WordPress files to your root directory, overwriting existing files.

This replaces all core WordPress files without touching your content, themes, or plugins.

Step 9: Upgrade Your PHP Version

Outdated PHP versions produce compatibility errors with current WordPress versions. WordPress 6.7 requires PHP 7.4 or higher. PHP 8.2 and 8.3 are the recommended versions in 2026.

How to check your PHP version:

1. Go to Tools > Site Health in your WordPress dashboard.
2. Click Info, then expand the Server section.
3. Find “PHP version.”

How to update PHP:

Most hosting control panels (cPanel, Plesk, SiteGround, WP Engine) let you switch PHP versions from a dropdown menu under PHP settings. If yours does not, contact your host and ask them to update PHP to 8.2 or 8.3.

After updating PHP, always test your plugins and theme for compatibility. Some older plugins do not support PHP 8.x.

Quick-Reference Troubleshooting Table

Use this table to jump directly to the right fix based on what triggered your white screen.

How to Prevent the WordPress White Screen of Death

Fixing the WSOD once is enough. These practices stop it from happening again.

Always test updates on a staging site first. Never update plugins, themes, or WordPress core directly on your live site. Most managed hosts including WP Engine, Kinsta, and SiteGround provide one-click staging environments.

Keep daily backups. A working backup from 24 hours ago fixes any WSOD in minutes. Use UpdraftPlus or Jetpack VaultPress Backup for automated daily backups.

Keep PHP on a supported version. Run PHP 8.2 or 8.3 in 2026. Outdated PHP versions are both slower and more prone to compatibility errors.

Set PHP memory at 256MB minimum. Do this proactively before a memory-related white screen forces you to.

Remove unused plugins and themes. Every inactive plugin is a security risk and a potential source of conflict. Delete anything you are not actively using.

Update one plugin at a time. Bulk-updating all plugins at once makes it impossible to identify which update caused a problem. Update individually and check your site after each one.

Our website maintenance services handle all of these tasks on a fixed monthly schedule so you never deal with the WSOD again.

When to Call a Developer

Handle the WSOD yourself when:

• The error appeared right after a plugin or theme update.
• You have FTP access or hosting file manager access.
• You can follow the steps above in order.

Call a developer when:

• You have worked through all nine steps and the white screen remains.
• The debug log shows a database error or corrupted table.
• The fix requires editing PHP code in a plugin or theme file.
• Your site is an ecommerce store actively losing orders.
• You do not have FTP or file manager access.

Our WordPress development team resolves WordPress errors including WSOD, 500 errors, and plugin conflicts. We also provide a full website maintenance service that includes proactive monitoring so these errors get caught before your visitors see them.

Frequently Asked Questions

What causes the WordPress White Screen of Death?

The WSOD is caused by a fatal PHP error that stops WordPress from rendering any output. The most common causes are plugin conflicts, PHP memory exhaustion, faulty theme code, corrupted .htaccess files, incorrect file permissions, and outdated PHP versions. Plugin conflicts account for the majority of cases.

How do I fix the WordPress white screen without FTP?

Use your hosting control panel’s built-in File Manager. Most hosts including SiteGround, Bluehost, Hostinger, and cPanel-based hosts include a File Manager that gives you the same file access as FTP through a browser interface. You can rename plugin folders, edit wp-config.php, and fix .htaccess from there without any FTP client.

Why is only my admin showing the white screen?

If your front end loads but /wp-admin shows white, the issue is isolated to the admin area. This typically means a plugin or a code error in your theme’s functions.php is affecting only the admin interface. Deactivate all plugins through FTP and rename your theme folder to isolate the cause.

How do I enable debug mode in WordPress?

Open wp-config.php in your File Manager, find define( 'WP_DEBUG', false ), and change false to true. Add define( 'WP_DEBUG_LOG', true ) on the next line. Check /wp-content/debug.log for the error details. Turn debug mode off after you resolve the issue by setting WP_DEBUG back to false.

Will I lose data fixing the WordPress white screen?

No. The WSOD is a display error, not a data loss event. Your WordPress database, content, media, and settings remain intact throughout all the troubleshooting steps above. The only step that modifies data is restoring from a backup, and you control when and whether you do that.

How long does it take to fix the WordPress White Screen of Death?

Most WSoDs resolve in 10 to 30 minutes by following the steps above in order. If a plugin update caused the issue, Step 3 alone fixes it in under 5 minutes. Memory limit issues (Step 5) take about 2 minutes once you locate the right file. Complex cases involving corrupted core files or database errors take 30 to 60 minutes.