WordPress

How to Fix the WordPress White Screen of Death Without Losing Content

WordPress November 5, 2026 17 min read
How to Fix the WordPress White Screen of Death Without Losing Content

You open your website, and there is nothing there. No menu, no text, no error. Just a blank white page.

This is the WordPress white screen of death, often called the WSOD. It is one of the most frightening problems that a site owner can see, because it gives you no clue about the cause. Your site seems to have vanished.

The reassuring truth is that your content is almost always safe. Your posts, pages, and images are stored in your database and your uploads folder, and a white screen does not delete them. It means that PHP stopped before it could finish building the page, so the browser received nothing to show.

Advertisement

In this guide, we’ll explain what causes the white screen of death and how to fix it, step by step, without losing content. We’ll start with the safest checks, move to the fixes that work on most sites, and finish with ways to prevent it in the future.

What Is the White Screen of Death?

The white screen of death is a blank page with no information. According to the official WordPress common errors page, it can be caused by PHP or database errors.

In plain terms, a part of your site’s code hit an error so serious that PHP stopped, and the error message is hidden for security. On a live site, WordPress is set to hide errors from visitors, so you see a white page.

You may also see it in a few forms.

  • A completely blank page, on the front end, the dashboard, or both.
  • A page that is blank only on one post, one page, or one template.
  • A dashboard that works while the front end is blank, or the opposite.
  • A short message saying that the site has a technical problem, which comes from the built-in fatal error handler.

Where the blank appears tells you something. A blank front end with a working dashboard often points to the theme. A blank dashboard with a working front end often points to an admin-side plugin. A blank everything points to a plugin, a core problem, or a server limit.

Is My Content Lost?

Almost never.

  • Posts, pages, comments, and settings are stored in the database.
  • Images and files are stored in the uploads folder.
  • A white screen does not delete either of these.
  • Even if you cannot log in, the content is still there.

The one thing to avoid is panic. Do not restore an old backup or delete folders in a hurry. Fix the cause, and the content comes back with the site. Before you try any fix, make a copy of the current state. Our review of UpdraftPlus shows how to keep backups, and if you can only reach the files, download a copy of your site folder and a database export from your host.

Common Causes of the White Screen

CauseHow oftenTypical trigger
A plugin with a PHP errorVery commonA new plugin, an update, or a conflict
A theme errorCommonA theme update, or a code edit in functions.php
PHP memory limit reachedCommonA heavy plugin or page builder
A PHP version problemCommonA host changed the PHP version
A syntax error in edited codeCommonA snippet added to a theme file
A stuck update or maintenance fileLess commonAn interrupted update
Corrupted core filesLess commonA failed update or a bad upload
A damaged .htaccess fileLess commonA plugin or a manual edit
Wrong file permissionsLess commonA server move or a restore
A database problemLess commonA server issue or a damaged table

Most white screens come from the first five rows.

Before You Start

  1. Do not panic, and do not delete anything yet.
  2. Write down what you did just before it happened: an update, a new plugin, a code edit, or a host change.
  3. Take a copy of your files and database, if you can reach them.
  4. Have your hosting login and an FTP or file manager ready.
  5. Check your email for a message from WordPress about a fatal error. It may contain a recovery link.

Fix 1: Use the Recovery Mode Email

Since version 5.2, WordPress has a feature that catches many fatal errors and sends an email to the site’s administrator address. The email explains which plugin or theme caused the error, and includes a link to recovery mode.

  1. Check the inbox for the admin email, and the spam folder.
  2. Open the link in the message.
  3. Log in. In recovery mode, WordPress pauses the plugin or theme that caused the error.
  4. Deactivate or update the plugin, or switch the theme.
  5. Exit recovery mode, and test the site.

If you have no email, or the white screen has no message, move on to the next fixes.

Fix 2: Turn On the Debug Log

The fastest way to find the cause is to read the error. Turn on the debug log, as explained in the official WordPress debugging guide.

  1. Use your host’s file manager or an FTP client to open the wp-config.php file in your site’s root folder.
  2. Find the line that says that is all and to stop editing. Above it, add or change these lines:

– define( ‘WP_DEBUG’, true );

– define( ‘WP_DEBUG_LOG’, true );

– define( ‘WP_DEBUG_DISPLAY’, false );

  1. Save the file, and reload the blank page.
  2. Open the wp-content folder, and find the debug.log file.
  3. Read the newest lines. A line such as “PHP Fatal error” names a file path and a line number.

The folder name in the path tells you the cause. A path with /plugins/plugin-name/ points to that plugin. A path with /themes/theme-name/ points to that theme. A message about memory points to the memory limit.

When you finish, set WP_DEBUG back to false, and delete the log if it holds private information. Do not leave debug mode on a live site.

Fix 3: Deactivate Plugins Without the Dashboard

If the log names a plugin, or if you suspect one, turn it off from outside WordPress.

Turn off one plugin

  1. Open your host’s file manager, or connect with FTP.
  2. Go to wp-content, then plugins.
  3. Rename the folder of the suspect plugin, for example by adding -off to its name.
  4. Reload your site. WordPress cannot find the plugin, so it turns it off.

Turn off all plugins

If you do not know which plugin, rename the whole plugins folder to plugins-off. Reload the site. If the white screen is gone, a plugin is the cause.

  1. Rename the folder back to plugins.
  2. Log in to the dashboard. All plugins are inactive.
  3. Activate them one at a time, and test the site after each one.
  4. When the white screen returns, the last plugin that you activated is the cause.

For larger sites, a binary search is faster. Our guide on how to find which plugin is breaking your site shows the method, and other safe tests.

Fix 4: Switch the Theme

If turning off plugins does not help, or the log names a theme file, test the theme.

  1. In wp-content, open the themes folder.
  2. Rename the folder of your active theme, for example by adding -off.
  3. Reload the site. WordPress falls back to a default theme, if one is installed.
  4. If the site works, the theme is the cause.

If you have no default theme installed, upload one through FTP, and then rename your active theme again.

If you edited functions.php

A syntax error in a code edit is a classic cause. A missing bracket, a missing semicolon, or a stray character can stop the whole site.

  1. Open the functions.php file of your theme through FTP or the file manager.
  2. Remove or comment out the code that you added last.
  3. Save, and reload.

To avoid this in the future, use a code snippet plugin, test on a staging site, and edit files with a code editor, not in the dashboard.

Fix 5: Increase the PHP Memory Limit

If the log says that the allowed memory size was exhausted, your site needs more memory. The common errors page lists this as a cause, and suggests raising the limit in wp-config.php, in php.ini if you have access, or through your host.

  1. Open wp-config.php.
  2. Above the line that says to stop editing, add: define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
  3. Save, and reload.

If the limit does not change, your host may enforce a lower value. Raise it in your hosting panel, or ask your host to do it. A limit of 256 MB suits most sites that use a page builder.

If a large process stops by timeout, the same page mentions that the maximum execution time can also be raised in the server settings.

Fix 6: Check the PHP Version

A change in PHP version can cause a white screen, because old code may not run on a newer version, and new code may not run on an older one.

  • Check whether your host changed the version recently.
  • In your hosting panel, change the PHP version back to the one that worked, and reload.
  • After the site works, update the plugin or theme that is not compatible, and then move to a supported PHP version.
  • If a plugin is no longer maintained, replace it.

Fix 7: Delete the .maintenance File

If the white screen or a maintenance message appeared during an update, a file named .maintenance may be stuck in your root folder.

  1. Open the root folder through FTP or the file manager.
  2. Turn on the option to show hidden files, since the name starts with a dot.
  3. Delete the .maintenance file.
  4. Reload your site.

Then go to the dashboard, and check whether the update needs to be run again.

Fix 8: Reset the .htaccess File

A damaged .htaccess file can cause errors on servers that use it. The common errors page suggests renaming the file and resetting permalinks.

  1. Rename .htaccess to .htaccess_old.
  2. Reload the site.
  3. If it works, log in, go to Settings, then Permalinks, and click Save Changes. WordPress creates a fresh file.

Fix 9: Replace Core Files

If a failed update left damaged core files, replace them with fresh copies.

  1. Download a fresh copy of the same WordPress version from WordPress.org, and unzip it on your computer.
  2. Upload the wp-admin and wp-includes folders, replacing the old ones.
  3. Upload the loose files from the root folder, except wp-config.php.
  4. Do not overwrite the wp-content folder, because it holds your plugins, themes, and uploads.
  5. Reload the site, and run any database update that WordPress asks for.

Fix 10: Check File Permissions and the Database

If nothing else works, the cause may be on the server.

Advertisement
  • Wrong file permissions after a move or a restore can stop WordPress from reading files. Ask your host to check ownership and permissions.
  • A damaged database table can cause errors. Your host can often repair it, and WordPress has a repair tool that you can turn on with a line in wp-config.php. Turn it off after use, and back up the database first.
  • Check your hosting panel for notices about outages or resource limits.

If you are still stuck, send your host the time of the problem and the lines from the debug log. They can read server logs that you cannot.

A Quick Troubleshooting Order

StepActionResult to look for
1Back up the current stateA safe copy
2Check email for recovery modeA link to a paused plugin or theme
3Turn on the debug logA file name and line number
4Rename the suspect plugin folderSite loads
5Rename the plugins folderSite loads, which proves a plugin cause
6Rename the theme folderSite loads, which proves a theme cause
7Raise the memory limitA memory error goes away
8Check the PHP versionThe site works on a different version
9Delete .maintenanceThe maintenance state ends
10Reset .htaccessA route problem is solved
11Replace core filesA core file problem is solved
12Ask your hostServer logs reveal the cause

After the Site Is Back

  1. Turn off debug mode.
  2. Clear all caches: plugin, host, CDN, and browser.
  3. Check your key pages, your forms, and your checkout, if you have one.
  4. Update the plugin or theme that caused the problem, or replace it.
  5. Take a fresh backup.
  6. Write down what happened, and what fixed it.

If the white screen came after an update, our guide on what to do when your WordPress website breaks after an update covers rollbacks and a safe update routine.

How to Prevent the White Screen of Death

  • Take a backup before every update, and keep copies away from your server.
  • Test updates on a staging site first.
  • Update one item at a time.
  • Do not edit theme files in the dashboard.
  • Use a code snippet plugin, or a child theme, for custom code.
  • Keep your PHP version supported, and your memory limit generous.
  • Delete plugins and themes that you do not use.
  • Use plugins that are updated often and tested with your WordPress version.
  • Keep the admin email address current, so that you receive recovery mode messages.
  • Use an uptime monitor, so that you learn about a blank site from an alert, not from a customer.

Reading the Debug Log: Common Messages

The debug log is full of text, but a few message types appear again and again. Here is what they usually mean.

Message in the logWhat it usually meansWhat to do
Allowed memory size exhaustedA script used more memory than the limitRaise the memory limit, or remove a heavy plugin
Maximum execution time exceededA process ran too longRaise the time limit, or find the slow plugin
Call to undefined functionCode needs a function that is missingA plugin is incompatible, or a file is missing
Cannot redeclare functionThe same function exists twiceTwo plugins, or a snippet and a plugin, clash
Parse error, or syntax errorA typing mistake in codeFix or remove the last code edit
Uncaught Error in a plugin fileA plugin failedDeactivate or update that plugin
Cannot modify header informationStray output before headersCheck for spaces or characters before PHP tags in edited files
Class not foundA needed library is missingReinstall the plugin, or check for a conflict

Always read the file path in the message. It points to the exact plugin, theme, or core file that failed.

What If There Is No Debug Log?

Sometimes the log stays empty. Check these points.

  • The wp-content folder must be writable by the server. If it is not, WordPress cannot create debug.log.
  • Check that you placed the debug lines above the line that says to stop editing, and not below it.
  • Check that you edited the right wp-config.php, since some servers keep one file above the root folder.
  • Check your host’s own error log in the hosting panel. Many hosts keep a separate PHP error log.
  • If the site does not run any PHP at all, the problem may be at the server level, such as a stopped service, and you should contact your host.

White Screen vs Other Common Errors

It helps to know what you are looking at, because each error has a different fix.

What you seeWhat it isFirst step
Blank white pageWhite screen of deathDebug log, plugins, theme
Message that the site has a technical problemFatal error caught by WordPressRecovery mode email
500 internal server errorServer-side failureServer error log, .htaccess, memory
Error establishing a database connectionWordPress cannot reach the databaseCheck wp-config.php details, ask host
Briefly unavailable for scheduled maintenanceStuck updateDelete .maintenance
404 on every page except homePermalink problemSave permalinks, reset .htaccess
503 service unavailableServer busy or downCheck resource use, ask host

A white screen is one of several errors that look alike. If you see a message, use it. The message is a clue that a plain white page does not give you.

Cache and Browser Checks

Before you spend an hour on fixes, rule out a cached blank page.

  1. Open the site in a private window, or another browser.
  2. Clear your browser cache.
  3. Clear your caching plugin and your host’s cache, if you can log in.
  4. Clear your CDN cache.
  5. Test from your phone on mobile data.

If the site loads for one device and not another, the blank page may be a cached copy. A white screen that persists on all devices after clearing caches is a real server-side error.

Hosting Problems That Look Like a White Screen

Sometimes the cause is the server, not your site.

  • Your hosting account may be suspended, or over its resource limits.
  • The server may have restarted, and PHP may not be running.
  • A new PHP version may have been set by the host.
  • A security rule on the server may block your own requests.
  • Disk space may be full, so WordPress cannot write files or sessions.

Check your hosting panel for notices and resource graphs. If you suspect a server cause, contact support, and send the time of the problem, your site address, and any lines from the debug log. A good host can often tell you the cause in minutes.

Fixing the White Screen on a Single Page or Post

If only one page is blank, the whole site is fine, and the cause is in that page.

  • Open the page in the editor, if you can, and look for a recently added block, shortcode, or widget.
  • Remove the last item that you added, and save.
  • If you use a page builder, check for a widget that needs a plugin that is no longer active.
  • Check whether the page uses a custom template, and test with the default template.
  • Check the debug log while you load only that page.
  • If a shortcode is the cause, deactivate the plugin that provides it, and test.

If the editor is blank too, try the recovery steps above, and use a revision from the revision list to go back to an earlier version.

Working With Your Host

When you contact your host, a clear message gets a faster answer. Include:

  • Your site address and the time that the problem started.
  • What you changed just before it, such as an update or a new plugin.
  • The exact lines from your debug log.
  • What you already tried, such as renaming the plugin folder.
  • Your PHP version and memory limit, if you know them.
  • A request to check the server error log for that time.

Ask your host about backups too. Many hosts keep daily copies that they can restore for you, which gives you a second safety net beside your own backups.

Staying Calm: A Short Recovery Checklist

  1. Do not delete anything yet.
  2. Take a copy of the files and database.
  3. Check your email for a recovery link.
  4. Turn on the debug log, and read it.
  5. Rename the plugin or theme folder named in the log.
  6. Raise the memory limit if the log mentions memory.
  7. Delete .maintenance if an update was in progress.
  8. Reset .htaccess if routes fail.
  9. Replace core files if the log names core.
  10. Ask your host if you are still stuck.
  11. After the fix, clear caches, test key pages, and take a new backup.

Frequently Asked Questions (FAQs)

What causes the WordPress white screen of death?

Usually a PHP error from a plugin, a theme, a code edit, or a memory limit. A stuck update, a damaged file, or a PHP version change can also cause it.

Will I lose my content?

No, in almost all cases. Your content is in the database and the uploads folder. Fix the cause, and it returns.

How do I fix it if I cannot log in?

Use the recovery mode email, or work through FTP or your host’s file manager. Rename the plugin or theme folder, and read the debug log.

How do I find which plugin caused it?

Read the debug log for a plugin path, or rename the plugins folder and turn plugins on one at a time.

Can a memory limit cause a white screen?

Yes. A heavy plugin or page builder can use more memory than your limit. Raise the limit to 256 MB, or ask your host.

Why is only my dashboard blank?

Often a plugin that runs in the admin area. Turn off plugins, and test.

Why is only my front end blank?

Often the theme. Switch to a default theme, and check functions.php for a recent edit.

Should I restore a backup?

Only if the simple fixes fail. A restore removes content added after the backup date, so save a copy of the current state first.

Is the white screen a sign that my site was hacked?

It can be, but it is usually a code error. If you see unknown files or users, scan the site and ask for help.

Can someone fix it for me?

Yes. If you prefer an experienced person to find the cause and restore your site, you can get WordPress management help through this Fiverr gig.

Final Thoughts

The white screen of death looks like a disaster, but it is a signal that one piece of code failed. Your content is safe, and the cause is usually a plugin, a theme, a code edit, or a memory limit.

Work in a safe order: back up, check for the recovery email, read the debug log, and then test plugins, the theme, and memory. Change one thing at a time, and write down what you did. Once your site works again, update your routine so that the next update, or the next code edit, is tested first.

Advertisement
Mindful reading

Better ideas, delivered thoughtfully.

Receive useful articles, thoughtful perspectives and practical knowledge from Mindful Tomorrow without unnecessary noise.

Scroll to Top