How to Fix the WordPress White Screen of Death: 8 Proven Fixes (2026)

You open your site and see nothing. No error message, no layout, no content — just a blank white page where your website used to be. That is the wordpress white screen of death, one of the most stressful errors a site owner can face, because it gives you no clue about what went wrong.

The good news: the wordpress white screen of death is almost always fixable, usually in under thirty minutes. A PHP fatal error stopped WordPress before it could send any HTML, while your server hid the error message. This guide follows the sequence professionals use: find the real error first, then test the likely culprits one at a time.

In this guide

  • What Is the WordPress White Screen of Death?
  • What Causes the WordPress White Screen of Death?
  • Before You Start: Back Up First
  • Fix 1: Check for the Recovery-Mode Email
  • Fix 2: Turn On Debug Logging and Read the Error
  • Fix 3: Deactivate All Plugins
  • Fix 4: Switch to a Default Theme
  • Fix 5: Raise the PHP Memory Limit
  • Fix 6: Check and Update Your PHP Version
  • Fix 7: Replace a Corrupted .htaccess File
  • Fix 8: Restore a Backup or Reinstall WordPress Core
  • Which Fix Should You Try First?
  • How to Prevent the White Screen of Death
  • Frequently Asked Questions

What Is the WordPress White Screen of Death?

The wordpress white screen of death is a completely blank page that appears instead of your WordPress site or dashboard. It is not a specific bug, but a symptom: a PHP fatal error stopped the page from loading, and the server hid the error text.

It can hit the front of your site, the admin area, or both. When only the front is blank but wp-admin works, the problem is usually your theme or a front-end plugin. When both are blank, the cause is more often a plugin that loads everywhere, a memory limit, or a broken core file.

Since WordPress 5.2, many fatal errors show “There has been a critical error on this website” instead of a blank page, and the fixes below work for that message too. Your content is safe: the wordpress white screen of death only stops WordPress from displaying your posts and pages.

What Causes the WordPress White Screen of Death?

A plugin conflict is the most common cause. A plugin update can clash with another plugin, your theme, or a newer PHP version. One line of bad code in a single plugin can kill every page, because WordPress loads active plugins before it renders anything.

A theme problem is the second most common cause. A theme update, a bad edit to functions.php, or a theme that is not compatible with your WordPress version can produce the same blank result. Memory exhaustion is third: WordPress asks for 40 MB by default on a single site, and 64 MB on multisite. A heavy page builder or a traffic spike can push a request past that limit.

Other causes include a PHP version your plugins were not ready for, a corrupted .htaccess file, and a failed core update. The wordpress white screen of death can also appear after a hosting move; our guide to migrate a WordPress site to a new host shows how to avoid that.

Before You Start: Back Up First

Before you change anything, back up what you have. A backup is your undo button if a fix makes things worse. If you can reach the dashboard, take a full backup with your backup plugin now. If the dashboard is blank too, use your hosting control panel or FTP to download wp-config.php and the wp-content folder, and export the database from phpMyAdmin.

Also download a copy of wp-config.php before you edit it: one missing quote or semicolon can break the site further. If you have never made a backup, read our WordPress backup guide for the 3-2-1 setup that actually restores. You will need dashboard access or file access (host file manager or a free FTP client such as FileZilla) for most fixes below.

How to Fix the WordPress White Screen of Death

Work through these eight fixes in order, reloading the blank page after each one. Stop as soon as the site returns. The wordpress white screen of death usually surrenders at Fix 2 or Fix 3.

Fix 1: Check for the Recovery-Mode Email

Since WordPress 5.2, when a plugin or theme causes a fatal error, WordPress emails the site administrator. The subject is usually “Your Site is Experiencing a Technical Issue.” The email names the faulty plugin or theme and includes a link that opens your admin area in recovery mode, with that plugin or theme paused.

Check the inbox of the address listed under Settings, then General — and check spam too. If the email is there, click the link, log in, and deactivate or delete the named plugin or theme. If there is no email, move on: some hosts block WordPress emails, and some errors happen too early for recovery mode to catch.

Fix 2: Turn On Debug Logging and Read the Error

If Fix 1 did not solve it, stop guessing and read the actual error. WordPress can write every PHP error to a log file. The official Debugging in WordPress documentation explains the three constants you need. Add them to wp-config.php, above the line that reads “That’s all, stop editing! Happy blogging.”


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

WP_DEBUG turns debug mode on; it is assumed to be false by default. WP_DEBUG_LOG saves errors to debug.log in the wp-content folder, usually at wp-content/debug.log. WP_DEBUG_DISPLAY set to false hides errors from visitors while you read the log in private. Use debug mode briefly on a live site and turn it off when you finish.

Reload the blank page once, then open wp-content/debug.log and check the last lines for “Fatal error” or “Parse error.” The line names the failed file, and the path usually names the culprit: /wp-content/plugins/ points at a plugin, /wp-content/themes/ at your theme. That one line turns the wordpress white screen of death from a mystery into a named culprit. If the log is empty, ask your host to check the PHP error log.

Magnifying glass over a WordPress debug log file showing the error that caused the blank screen

Fix 3: Deactivate All Plugins

If the log names a plugin, deactivate that one first. If it names nothing, deactivate all plugins at once. This is the single most effective fix for the wordpress white screen of death, because plugins cause it more often than anything else.

In the dashboard, go to Plugins, then Installed Plugins, select all, choose Deactivate from the bulk menu, and apply. If the dashboard is blank, use file access: open wp-content and rename the plugins folder to plugins-old. WordPress then treats every plugin as deactivated. Reload the site.

If the site returns, a plugin is the problem. Rename the folder back to plugins, then rename each plugin folder one at a time, reloading after each. When the site breaks again, the last plugin you restored is the culprit — leave it deactivated or replace it.

Fix 4: Switch to a Default Theme

If plugins are not the cause, suspect your theme — especially if the log named a theme file, or the white screen started after a theme update or an edit to functions.php.

In the dashboard, go to Appearance, then Themes, and activate a default theme such as Twenty Twenty-Five. If the dashboard is blank, use file access: open wp-content/themes and rename your active theme’s folder by adding -old to its name. WordPress falls back to a default theme automatically if one is installed. Reload the site.

If the site returns, your theme is the cause. Reinstall a fresh copy from its original source to overwrite corrupted or badly edited files. Never edit theme files on a live site again — use a child theme or a code-snippets plugin. Our guide on how to start a WordPress website explains the safer setup.

Fix 5: Raise the PHP Memory Limit

If the debug log says “Allowed memory size of 41943040 bytes exhausted,” WordPress ran out of memory. Open wp-config.php and add this line above the “That’s all, stop editing!” line:


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

This raises the limit from the 40 MB default to 256 MB, enough for most small and medium sites. Reload the site. If it returns, the memory limit was your problem — but treat it as a warning, not a cure. A site needing far more than 256 MB may have a plugin leaking memory, and raising the limit again only hides the real cause.

If 256 MB is not enough, ask your host to raise the server-level PHP memory limit, which is set separately and sometimes capped on shared plans. Deactivate heavy plugins you do not need; our guide to speed up WordPress shows how trimming plugins helps speed and stability.

Fix 6: Check and Update Your PHP Version

A PHP upgrade on your server can break plugins and themes written for older PHP, and that break often appears as the wordpress white screen of death. Running ancient PHP can break newer plugins just as easily.

WordPress 7.1 requires PHP 7.4 or later. WordPress.org recommends PHP 8.3 or greater, and the WordPress Hosting Handbook recommends PHP 8.4 or later for production. PHP 8.2 loses security support on 31 December 2026, so it is a poor long-term baseline. As of 19 November 2026, the current WordPress version is 7.1.5, a security release from 18 November 2026 fixing 20 issues — take that update once the site is back.

Check your PHP version in your hosting control panel, or under Tools, then Site Health, then Info, then Server. Below 7.4, ask your host to move you to PHP 8.3 or 8.4. If the white screen started right after a PHP upgrade, switch back temporarily, then update or replace the plugin or theme that cannot handle the new version. Test PHP changes on staging first: PHP 8 turns many old warnings into fatal errors.

Fix 7: Replace a Corrupted .htaccess File

On Apache servers, a corrupted .htaccess file can blank a site, often after a security plugin writes bad rules to it or a failed edit leaves it half-finished. This fix costs nothing and takes two minutes.

Using file access, find .htaccess in your site’s root folder — the same folder that holds wp-config.php. If your file manager hides dotfiles, turn on “show hidden files.” Download a copy as a backup, then delete it from the server. Reload the site.

If the site returns, the file was corrupt. Log in, go to Settings, then Permalinks, and click Save Changes without changing anything. WordPress generates a fresh, correct .htaccess for you. If the site is still blank, restore the backup and move to Fix 8. This fix only applies to Apache and LiteSpeed servers; Nginx hosts have no .htaccess file.

Fix 8: Restore a Backup or Reinstall WordPress Core

If nothing else worked, use one of two last resorts. First, restore a backup from before the white screen appeared. A full backup restores files and database together, fixing corrupted core files, bad updates and most database damage in one move. Restore on a staging copy first if your host offers one.

If you have no backup, reinstall WordPress core files. Download a fresh copy of WordPress 7.1.5 from wordpress.org, unzip it, and upload everything except the wp-content folder and wp-config.php, overwriting the existing files. This replaces damaged core files while leaving your content, themes, plugins and settings untouched. Never delete wp-content or wp-config.php during this process.

If even a fresh core install leaves a blank page, the problem is at server or database level. Contact hosting support with the debug log: give them the exact fatal error line and what you already tried.

Checklist, wrench and restored website window showing the steps to fix a WordPress white screen

Which Fix Should You Try First?

Use this table to pick your starting point. The fixes are ordered by how often they solve the problem, not by difficulty.

Fix Try it first when Difficulty Typical time
Recovery-mode email You got the “technical issue” email from WordPress Easy 2 minutes
Debug logging You do not know the cause yet Easy 5 minutes
Deactivate all plugins The log names a plugin, or the screen went blank after a plugin update Easy 5–10 minutes
Switch to a default theme The log names a theme, or the screen went blank after a theme change Easy 5 minutes
Raise the memory limit The log says “allowed memory size exhausted” Easy 2 minutes
Check the PHP version The screen went blank after a server or PHP change Medium 10–15 minutes
Replace .htaccess You use Apache and a security plugin recently edited rules Easy 2 minutes
Restore a backup / reinstall core Nothing else worked Medium 15–30 minutes

In practice, most site owners find the answer with the debug log plus the plugin test. Those two steps alone resolve the large majority of cases, and they cost $0.

How to Prevent the White Screen of Death

Update one thing at a time: update a plugin, check the site, then update the next. Bulk-updating ten plugins at once means you cannot tell which one broke the site. The same applies to themes and core updates — take them one at a time, and take a backup first.

Use a staging site for updates: test there and push live only when staging still loads. Keep PHP, WordPress, themes and plugins up to date together, since an old plugin on new PHP — or a new plugin on old PHP — is the classic recipe for a fatal error. Check the Site Health screen monthly.

Limit your plugin count and delete what you do not use; every active plugin is code that runs on every page load. Keep automatic backups running and follow our WordPress security checklist. Together, these habits make a repeat of the wordpress white screen of death far less likely.

Frequently Asked Questions

What is the WordPress white screen of death?

The wordpress white screen of death is a blank white page that appears instead of your WordPress site when a PHP fatal error stops the page before any HTML is sent to the browser. The server hides the error message, so you see nothing. It is usually caused by a plugin conflict, a theme problem, or a memory limit, and your content in the database is almost always safe.

How do I fix the WordPress white screen of death if I cannot access wp-admin?

Use file access from your hosting control panel or an FTP client. Rename the wp-content/plugins folder to deactivate all plugins, or rename your active theme’s folder to force a default theme. You can also edit wp-config.php to turn on debug logging, which writes the real error to wp-content/debug.log. If you have no file access, ask your host.

Will the white screen of death delete my content?

No. The wordpress white screen of death stops WordPress from displaying your content, but it does not delete it. Your posts, pages and images live in the database and the wp-content/uploads folder, and they survive the error. A backup restore or a plugin fix brings everything back exactly as it was.

How long does it take to fix the white screen of death?

Most cases take 10 to 30 minutes. The recovery-mode email can fix it in two minutes, and reading the debug log plus deactivating the faulty plugin usually takes under ten. Only a corrupted database or a server-level problem stretches the fix past an hour, and hosting support can usually resolve that the same day.

Should I turn off WP_DEBUG after fixing the site?

Yes. Set WP_DEBUG back to false in wp-config.php and delete the wp-content/debug.log file when you finish. The debug log sits in a publicly reachable folder, and leaving it there can expose server paths and error details. Debug mode is a diagnostic tool, not a permanent setting.

Conclusion

The wordpress white screen of death looks catastrophic, but it is one of the most fixable errors in WordPress. A blank page means a PHP fatal error stopped the page early — and once you read that error in the debug log, the fix is usually a single plugin, theme, or memory setting.

Start with the recovery-mode email, then turn on debug logging and let the log name the culprit. Deactivate plugins, test the theme, raise the memory limit, and check your PHP version. Work in order, back up before you change anything, and turn debug mode off when you are done.

Leave a Comment