How to Fix the WordPress White Screen of Death

Overview

If your WordPress site suddenly shows a blank page, a fully white screen, or an incomplete page with no obvious error message, you are usually dealing with a fatal PHP error, a memory issue, a plugin conflict, a theme problem, or a server-side configuration issue. In practical terms, WordPress started to load, something broke before output finished, and the browser was left with very little to display.

The good news is that most blank page cases can be narrowed down quickly if you work in the right order. The wrong order creates extra risk: clearing useful logs too early, deactivating too many things at once, or making changes without a backup. The right order keeps the site recoverable and helps you identify the actual trigger.

Use this workflow when:

• The entire site is blank
• Only the admin area is blank
• Only one page type is blank, such as blog posts or product pages
• A white screen appeared after a plugin, theme, PHP, or WordPress update
• The site works for some users but not for others because of cache or CDN issues

Before you change anything, note three details:

1. What changed recently? A new plugin, a theme edit, a PHP version change, a migration, or a bulk update often points to the cause.
2. Where does the problem happen? Front end, admin area, specific URLs, or only logged-in users.
3. Do you have access? WordPress admin, hosting panel, file manager, SFTP, SSH, or database access.

Those details will shape the fastest path to a fix.

Step-by-step workflow

Follow these steps in order. The goal is to restore access first, then isolate the cause, then make the fix durable.

1. Confirm whether it is a real blank page or a cache problem

Start with the least invasive checks. Open the affected page in a private browser window. Try a second browser and a mobile device. If you use a caching plugin, server cache, or CDN, purge those layers. A stale or broken cached page can look like a white screen even when the site is already fixed underneath.

If only one user sees the problem, clear the browser cache. If everyone sees it, continue.

2. Check whether WordPress recovery mode email was sent

Modern WordPress installations may send an administrator email when a plugin or theme causes a fatal error. That message can include a recovery link and mention the component involved. If you have it, use it. Recovery mode can let you log in and disable the offending plugin or theme without guessing.

If no email arrived, do not stop there. Email delivery may not be working, especially on fresh sites or servers without reliable mail configuration. If you need to improve that later, your broader setup may also benefit from a review of business email setup with your domain.

3. Make a backup before deeper changes

If you still have hosting access, create a backup of files and database. Many hosts include snapshots or one-click backups in the control panel. If not, download the site files and export the database. Even if the site is already broken, a backup preserves logs, the current state, and any custom code you might need to review.

This matters because some troubleshooting steps are destructive by nature, especially bulk deactivation and replacing core files.

4. Turn on debugging the safe way

The next job is to expose the hidden error without displaying sensitive details to visitors. In wp-config.php, enable logging and keep front-end display off. A common approach is to set WordPress debugging on, log errors to a file, and disable on-screen error output. Then reload the broken page and inspect the generated debug log.

Look for patterns such as:

• Fatal error pointing to a plugin file
• Memory exhausted messages
• Function redeclaration or missing class errors
• Theme template failures
• PHP compatibility warnings that escalate into failures

If you use managed WordPress hosting, you may also find PHP error logs in the hosting dashboard. On traditional shared hosting, error logs may live in cPanel, Plesk, or a raw log file in your account.

5. Deactivate plugins if the admin area is inaccessible

Plugin conflicts are one of the most common causes of the WordPress white screen of death. If you cannot reach wp-admin, deactivate plugins from the file system by renaming the wp-content/plugins folder temporarily. WordPress will treat the plugins as unavailable and deactivate them.

If the site starts working again, the issue is almost certainly plugin-related. Rename the folder back, then reactivate plugins one by one until the failure returns. This takes longer than random guessing, but it gives you a clean answer.

As you test, record:

• The exact plugin that triggers the failure
• Its version
• Any dependency, such as WooCommerce, a page builder, or PHP version
• Whether the error happens only when combined with another plugin

Once the site is stable again, review your plugin stack against practical guidance like Best WordPress Plugins for New Websites and remove anything redundant.

6. Switch to a default theme

If deactivating plugins does not fix the issue, test the theme. Rename the active theme folder in wp-content/themes. If a default WordPress theme is installed, WordPress will usually fall back to it automatically. If the site loads after the switch, your theme or child theme is likely responsible.

This is especially common after:

• Theme updates with changed template logic
• Manual edits to functions.php
• Outdated page builder integrations
• Custom snippets copied from older tutorials

If the active theme is the problem, compare it against a clean copy or restore the last known working version. If you are considering a cleaner long-term setup, see Best WordPress Themes for Small Business Websites.

7. Raise the PHP memory limit if logs suggest exhaustion

A memory limit issue often appears after installing heavier plugins, importing content, generating thumbnails, or running several admin tasks at once. The log may mention allowed memory size exhausted. In that case, increasing the PHP memory limit may solve the blank page, but treat that as a symptom check, not the final diagnosis.

If the site only works after raising memory, ask why usage spiked. Heavy plugins, oversized images, bad loops in code, or a weak hosting environment may be contributing. If performance is part of the problem, follow up with How to Speed Up a WordPress Site.

8. Check PHP version compatibility

A plugin or theme that worked on one PHP version may fail on another. This often happens after hosting providers update PHP or when a site is migrated. In your hosting panel, note the current PHP version and compare it against the requirements of WordPress core, your active theme, and critical plugins.

If the white screen appeared right after a PHP change, temporarily switching back to the previous stable version can confirm the cause. That is a useful test even if it is not the permanent solution. The durable fix is to update or replace incompatible code.

9. Replace core WordPress files if corruption is suspected

If plugin and theme tests fail, and logs do not clearly point elsewhere, replace the WordPress core files with fresh copies of the same version, excluding wp-content and preserving wp-config.php. Corrupted core files are less common than plugin issues, but they do happen during failed updates, interrupted transfers, or bad permissions changes.

This step should be done carefully. Do not overwrite custom content directories by accident.

10. Review .htaccess and server rules

A broken rewrite rule or malformed server directive can create blank responses or error loops that present like a white screen. Check the .htaccess file for recent changes, especially after security plugin adjustments, redirects, caching changes, or manual edits. Save a copy, then regenerate a clean version by resaving permalinks once admin access returns.

If your hosting stack uses Nginx, reverse proxies, or additional firewall layers, the relevant rules may live outside WordPress.

11. Check file permissions and ownership

Incorrect file permissions can block PHP from reading or executing files correctly. This is more common after migrations, manual uploads, or mixed deployment methods. Review permissions for WordPress files and folders and confirm ownership is consistent with your hosting environment. If you are not sure what values are normal for your stack, use your host's defaults rather than guessing.

12. Test the database only if other steps fail

The database is not the first suspect for a pure white screen, but corrupted options, failed migrations, or broken serialized data can contribute. If the issue started after a site move, plugin import, or URL replacement, inspect key settings such as site URL, home URL, and any recently changed options.

Migration-related blank pages often sit alongside domain or DNS changes, so if the issue appeared during a move, review your environment with How to Connect a Domain to Web Hosting Step by Step and DNS Records Explained to rule out edge-case misconfiguration.

13. Escalate with evidence, not just symptoms

If you need help from your hosting provider or a developer, send a compact handoff:

• When the issue started
• What changed just before it happened
• Whether front end, admin, or both are affected
• The exact plugin or theme tests already performed
• Any fatal error lines from logs
• PHP version, WordPress version, and active theme name

This turns a vague “site is blank” ticket into a useful incident report.

Tools and handoffs

You do not need every tool to fix a wordpress blank page, but you do need enough access to observe the problem and reverse one change at a time. The best tool set depends on how your site is hosted.

Useful tools

• Hosting file manager: Fastest way to rename plugin or theme folders when wp-admin is down.
• SFTP or SSH: Better for repeatable changes, log review, and safer file handling.
• Hosting error logs: Often easier to read than guessing from the browser.
• WordPress debug log: Best for tracing plugin and theme fatal errors.
• Backup snapshots: Essential if you need to roll back quickly.
• Staging site: Ideal for reproducing the error without risking the live site.

Who handles what

Some fixes belong to the site owner, some to hosting support, and some to a developer:

• Site owner or admin: cache clearing, backup creation, plugin isolation, theme switch, checking recent changes
• Hosting support: PHP version changes, server logs, memory settings, permissions, firewall or cache layers
• Developer: custom code review, child theme errors, fatal stack traces, compatibility patches

If your site is still early in its lifecycle, it may help to review your setup against How to Start a WordPress Website for Beginners so small misconfigurations do not become repeat outages later.

Quality checks

Once the site loads again, do not stop at “the homepage works.” A real fix should survive normal use.

Run this checklist:

1. Visit critical pages: home, blog, contact, landing pages, checkout or lead forms if applicable.
2. Log in and test wp-admin: dashboard, plugins, themes, media library, updates, editor screens.
3. Trigger the original failing action: if the site broke during an update or after activating a plugin, reproduce the scenario carefully on staging first.
4. Review logs again: confirm the fatal error is gone, not just hidden.
5. Check scheduled tasks: backup jobs, cron events, form notifications, and email sending.
6. Verify caching behavior: purge caches and make sure visitors see the repaired version.
7. Test performance: a site that barely loads after a memory increase may still be unstable.

Then document the cause and the fix. A short internal note can save time the next time you face wordpress troubleshooting under pressure.

For longer-term stability, pair this article with a routine maintenance habit. The guide WordPress Maintenance Checklist for Small Business Websites is a good next step.

When to revisit

This workflow is worth revisiting whenever your WordPress environment changes, because the white screen of death is often triggered by change rather than by age alone.

Re-run or refresh your process when:

• You change hosting providers or move from shared hosting to managed WordPress hosting
• You update PHP versions
• You replace your theme or page builder
• You install a performance, security, or caching plugin
• You add custom code snippets
• You migrate domains or adjust DNS and CDN settings
• You notice repeated memory errors, partial page loads, or failed updates

A practical habit is to keep your own incident checklist in a document or password manager note. Include your hosting login path, where error logs live, how to access files, which plugins are mission-critical, and what your last stable PHP version was. That turns a future outage into a routine recovery instead of a scramble.

If you want the simplest action plan, use this condensed version:

1. Confirm it is not just cache.
2. Check for recovery mode email.
3. Create a backup.
4. Enable logging safely.
5. Disable plugins and test.
6. Switch to a default theme and test.
7. Review memory and PHP version.
8. Inspect core files, rules, and permissions.
9. Validate the fix across front end and admin.
10. Document what caused it.

That process will solve most cases of the wordpress white screen of death without unnecessary guesswork. And when it does not, it gives you the evidence needed for a faster handoff to hosting support or a developer.