How to Fix the WordPress White Screen of Death

A completely blank WordPress page can be alarming, especially when the WordPress dashboard is unavailable too. This problem is commonly called the White Screen of Death (WSOD). The good news is that a blank screen usually has a specific underlying cause, such as a PHP fatal error, a plugin or theme conflict, exhausted memory, or a failed update.

This guide shows a practical recovery process that starts with the least disruptive checks and moves toward deeper debugging only when necessary.

What causes a WordPress white screen?

WordPress can stop rendering a page when PHP encounters a fatal error or when a server-side resource is exhausted. Common causes include:

• A recently updated or incompatible plugin
• A theme change or theme code error
• A PHP version or compatibility problem
• A failed WordPress, plugin, or theme update
• Memory exhaustion
• Corrupted or incomplete files
• A fatal error caused by custom code

Before changing anything, identify what changed

Think about the last action performed before the blank screen appeared. Did you update a plugin, change the theme, edit PHP code, change the PHP version, or install something new? A recent change is one of the most useful clues and can save you from making unrelated changes.

1. Check whether the problem affects the whole site

Open the homepage, a few individual posts, and /wp-admin/. If only one page is blank, the problem may be specific to that page, its content, or a feature used there. If the front end and dashboard are both affected, investigate server-side errors, plugins, themes, PHP, and memory first.

2. Try WordPress Recovery Mode

Modern WordPress can detect certain fatal errors and send the site administrator a recovery-mode email. If you receive one, use the recovery link and review the plugin or theme identified in the message. Recovery Mode can allow you to access the dashboard while the problematic component is paused for your administrator session.

If you do not receive a recovery email, do not assume that no error exists. Email delivery can fail independently of the underlying WordPress problem.

3. Disable the suspected plugin

If the problem started immediately after a plugin update or installation, temporarily disable that plugin and test again. If you can access the dashboard, deactivate it normally.

If you cannot access the dashboard, you may need to use your hosting file manager or SFTP. In the wp-content/plugins/ directory, temporarily rename the suspected plugin’s folder. WordPress will no longer find it under its original name, which can effectively disable it. Restore the original folder name after testing if the plugin was not responsible.

Do not rename or delete random plugin folders one by one without recording what you changed. A controlled test makes it much easier to identify the cause and return the site to its previous state.

4. Test the active theme

If a theme was recently changed or updated, temporarily switch to a current default WordPress theme if you can access the dashboard.

If the dashboard is unavailable, a developer or site administrator can change the active theme through the database or another controlled recovery method. Because database edits can cause additional problems when performed incorrectly, use a backup and your host’s documentation before making direct database changes.

5. Check the PHP error log

A PHP error log can turn a blank page into a specific diagnosis. Look for entries generated at the time the problem started. Messages mentioning a fatal error, an undefined function, an incompatible method, a memory limit, or a particular plugin/theme file can point directly to the component that needs attention.

If you are not comfortable reading PHP errors, copy the relevant error message and ask your developer or hosting provider to interpret it. Avoid posting sensitive configuration details publicly.

6. Enable WordPress debugging when necessary

For a development or staging site, WordPress debugging can provide more information about PHP problems. On a production site, be careful: displaying PHP errors publicly can expose technical information to visitors.

If you need debugging on a live site, log errors rather than displaying them to visitors and turn debugging back off after troubleshooting. Make changes carefully in wp-config.php and keep a backup of the file before editing it.

7. Check memory and PHP compatibility

A white screen can occur when a request runs out of available PHP memory or when code is incompatible with the server’s PHP version. Check the site’s PHP version and relevant memory limits through your hosting panel or WordPress Site Health.

If a recent PHP upgrade triggered the problem, check whether the active theme and plugins support the new version before changing the server back. Downgrading PHP can sometimes restore a site temporarily, but it should be treated as a compatibility workaround rather than the final solution.

8. If an update failed, restore safely

A failed update can leave incomplete files or an inconsistent state. If the problem began during an update, check whether the update actually completed and whether the affected component has a known compatibility issue.

Do not restore an old backup as your first response unless you understand what data will be lost. A backup may contain older posts, orders, settings, uploads, or database changes. If a restore is necessary, take a fresh backup of the current state first when possible.

9. Check for custom code

If you recently added PHP to a theme’s functions.php, a custom plugin, a code-snippets tool, or another PHP file, temporarily undo the most recent change. A missing bracket, undefined function, incompatible hook, or syntax error can stop PHP execution before WordPress can render the page.

10. Clear caches only after fixing the cause

Page caches, object caches, CDN caches, and browser caches can make troubleshooting confusing, but clearing every cache will not repair a PHP fatal error. First fix the underlying problem, then clear the relevant caches so visitors can receive the corrected response.

When to contact your hosting provider or developer

Get professional help if you cannot identify the failing component, the server returns 500 errors, database errors appear, files are missing, or the site contains important transactions or customer data. A developer can inspect server logs and make controlled changes without guessing.

How to prevent another WordPress white screen

• Keep WordPress, plugins, themes, and PHP reasonably current.
• Use reliable backups and test that restores are possible.
• Test significant updates on a staging site when practical.
• Change one component at a time when troubleshooting.
• Keep a record of custom code and configuration changes.
• Monitor Site Health and server error logs.

Quick recovery checklist

1. Identify what changed immediately before the problem.
2. Check whether the dashboard and front end are both affected.
3. Look for a WordPress Recovery Mode email.
4. Temporarily disable the suspected plugin or theme.
5. Review the PHP/server error log.
6. Check PHP compatibility and memory limits.
7. Review recent custom code or failed updates.
8. Restore from backup only when appropriate.
9. After fixing the cause, clear relevant caches and test the site again.

A WordPress white screen is frustrating, but it is usually easier to solve when you work from the most recent change and use the available error information instead of making many changes at once. A controlled troubleshooting process reduces the risk of turning one problem into several.