How to Fix the WordPress White Screen of Death (6 Fixes)

Few sights panic a website owner like this: you open your site — or worse, your WordPress dashboard — and see nothing. A blank white page. No error message, no clues, just emptiness. This is the famous White Screen of Death (WSoD), and despite the dramatic name, it’s one of the most fixable WordPress problems. It almost always means a PHP error stopped WordPress before it could draw the page — usually a plugin, a theme, or a memory limit.

This guide works through the fixes in the right order, from the two-minute checks to the deeper ones, explaining how to find the real cause instead of guessing.

Quick Answer

The WordPress white screen of death is usually caused by a faulty plugin, a broken theme update, or your site hitting its PHP memory limit. Fix it by: enabling debug mode to reveal the error, deactivating all plugins (via FTP or your hosting file manager by renaming the plugins folder), switching to a default theme, and increasing the memory limit in wp-config.php. If you can still access the dashboard, deactivate plugins one at a time until the site returns — the last one you turned off is the culprit.

First: Work Out How Bad It Is

• Only the front end is white, dashboard works: Usually a theme or front-end plugin problem. This is the easy case.
• Both site and wp-admin are white: A plugin, theme functions file, or a fatal PHP error. You’ll need FTP or your host’s file manager.
• It happened right after an update or install: That plugin/theme update is suspect number one.
• It happened “for no reason”: Often an automatic update, a memory limit, or a hosting-side PHP change.

You’ll need access to your site’s files: either an FTP program (like FileZilla) with credentials from your host, or the File Manager in your hosting control panel. Both let you rename folders, which is the key trick below.

Fix 1: Turn On Debug Mode to See the Real Error

1. Open your site’s wp-config.php file (in the main WordPress folder) via FTP or file manager.
2. Find the line define( 'WP_DEBUG', false ); and change false to true. If the line doesn’t exist, add it above the “That’s all, stop editing!” comment.
3. Reload the white page. Instead of blankness, you’ll usually see a PHP error naming the exact file and plugin/theme responsible.
4. Note the culprit, fix it using the steps below, then set WP_DEBUG back to false — never leave debug mode on a live site, because errors can expose server details to visitors.

The official WordPress troubleshooting FAQ walks through debug mode and the other standard recovery steps in the project’s own words — a good page to keep open while you work.

Fix 2: Deactivate All Plugins at Once

1. Connect via FTP or file manager and open the wp-content folder.
2. Rename the plugins folder to plugins_off. This deactivates every plugin instantly, without needing the dashboard.
3. Reload your site. If it loads, a plugin was the cause.
4. Rename the folder back to plugins, then in the WordPress dashboard activate plugins one at a time, reloading the site after each. When the white screen returns, you’ve found the bad plugin — delete it or contact its developer, and check for a fixed update.

Fix 3: Switch to a Default Theme

1. In wp-content/themes, note your current theme’s folder name.
2. Rename that folder (e.g. add “_off” to the name). WordPress will automatically fall back to a default theme like Twenty Twenty-Five if one is installed.
3. If no default theme exists, download one free from WordPress.org and upload its folder into wp-content/themes.
4. Reload the site. If it works, your theme (or its latest update, or a child-theme edit) caused the crash. Reinstall a fresh copy of the theme rather than trusting the broken one.

Fix 4: Increase the PHP Memory Limit

A white screen can simply mean WordPress ran out of memory mid-task — common after adding heavy plugins or during updates.

1. Open wp-config.php and add this line above “That’s all, stop editing!”: define( 'WP_MEMORY_LIMIT', '256M' );
2. Save and reload. If the site returns, memory was the issue.
3. If your host caps memory below this, they can raise it for you — or it may be a sign you’ve outgrown the plan.

Fix 5: Check for Corrupted Core Files and Permalink Issues

• Reinstall WordPress core: If you can reach the dashboard, go to Dashboard → Updates → Reinstall Now. It replaces core files without touching your content, themes, or plugins. If you can’t reach the dashboard, upload a fresh copy of WordPress via FTP, overwriting everything except the wp-content folder and wp-config.php.
• Clear your cache: If you use a caching plugin or server cache, purge it — sometimes the “white screen” is a corrupted cached page. Try viewing the site in an incognito window too, to rule out your own browser.
• Reset permalinks (for white screens on inner pages only): In Settings → Permalinks, just click Save Changes to regenerate the rules. If .htaccess is corrupted, this repairs it.
• Check PHP version: An ancient plugin may break on new PHP, and a very new plugin may need newer PHP. Site Health (Tools → Site Health) shows your version; hosts let you switch it in the control panel.

When All Else Fails: Restore a Backup

If the error appeared suddenly and you can’t isolate it, restoring yesterday’s backup is a legitimate, professional move — sites run businesses, and uptime matters. Restore from your host’s backup system or your backup plugin, then update plugins and themes one at a time to find what triggered the crash. This is exactly the disaster that a proper backup routine exists for; if you don’t have one yet, set it up the moment your site is back using our guide on backing up your WordPress website safely.

Common Mistakes to Avoid

• Deleting random files in panic: Renaming is reversible; deleting is not. Diagnose first.
• Leaving WP_DEBUG on: It can display file paths and database details publicly. Turn it off when you’re done.
• Reactivating everything at once after the plugins-folder trick: you’ll never learn which plugin was guilty, and it’ll strike again.
• Restoring a backup before noting the error: Spend two minutes with debug mode first — the fix is often one plugin, not a full rollback.
• Editing theme files directly to “fix” the code if you’re not a developer: a fresh reinstall of the theme is safer.

Conclusion

The white screen of death looks catastrophic but is usually one plugin, one theme, or one memory setting away from fixed. Turn on debug mode to see the real error, deactivate plugins by renaming their folder, fall back to a default theme, raise the memory limit, and reinstall core files if needed. Work through the steps calmly and in order — and once your site is back, take the backup and update habits seriously so the next incident is a five-minute job, not a five-hour one.

Frequently Asked Questions

What causes the WordPress white screen of death?

A PHP fatal error that stops WordPress loading — most often a buggy plugin or theme (especially after an update), an exhausted PHP memory limit, or a corrupted file. Debug mode reveals the exact cause.

Can the white screen of death delete my content?

No. Your posts, pages, and media live in the database and uploads folder, which a white screen doesn’t touch. Once you fix the faulty plugin, theme, or setting, everything reappears exactly as it was.

How do I fix a white screen if I can’t access wp-admin?

Use FTP or your hosting file manager. Rename the wp-content/plugins folder to deactivate all plugins, or rename your active theme’s folder to force the default theme. Both work without dashboard access.

Why did the white screen appear after updating a plugin?

The new plugin version likely conflicts with your theme, another plugin, or your PHP version. Deactivate it via FTP, and either roll back to the previous version or wait for the developer’s fix before updating again.

How can I prevent the white screen of death in future?

Keep everything updated, back up before major updates, update plugins one at a time, use a staging site for big changes, and avoid abandoned plugins that haven’t been updated in years.