You open your site on a Monday morning, coffee in hand, and see… nothing. No error message. No homepage. Just a blank white page staring back at you.
Don’t panic — your site is almost certainly not gone. Learning how to fix WordPress white screen of death problems is one of the most useful skills any site owner can have, because the blank page is almost always fixable in minutes, and your content is usually sitting safely in the database, untouched.
The key takeaway: a white screen is not a deleted site — it’s a hidden error message.
What the White Screen Actually Is
The WordPress white screen of death (WSOD) happens when a PHP fatal error crashes your site while error display is turned off. WordPress stops mid-page, produces no output, and your browser shows a blank page instead of an explanation.
Think of it this way: the error exists, but WordPress is hiding it from you.
The usual triggers are a conflicting plugin or theme update, a PHP memory limit being hit, a corrupted file, or a PHP version your code can’t run on. For example, a business owner updates three plugins on a Monday morning and finds the site blank — one incompatible plugin is almost always the whole problem.
Quick Checks First
Before touching any files, spend 60 seconds on these:
- Hard-refresh your browser (Ctrl+Shift+R or Cmd+Shift+R) and try a private window — a stale cache can mimic a broken site.
- Check wp-admin separately. If the homepage is blank but yoursite.com/wp-admin/ loads, the problem is narrower, often a theme or front-end plugin.
- Check another device and your host’s status page to rule out a local issue or an outage.
If the white screen survives all of these, find the real error.
How to Fix WordPress White Screen of Death With WP_DEBUG
The fastest WordPress white screen of death fix starts with error logging, so WordPress tells you exactly what broke.
Safety warning: never display errors on a live site. Public errors leak file paths and server details. Log errors to a file instead, and always back up wp-config.php before editing it.
To enable safe logging with WP_DEBUG WordPress settings, connect via FTP or your host’s file manager, open wp-config.php, and just above the line “That’s all, stop editing! Happy publishing.”, add: define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_LOG’, true ); define( ‘WP_DEBUG_DISPLAY’, false );
Save, reload the blank page, then open wp-content/debug.log. The last few lines will usually name the exact plugin, theme, or file that crashed.
Turn debug mode OFF when you’re done. Set WP_DEBUG back to false, or logging will keep filling your disk and could expose sensitive paths.
WordPress Critical Error Fix: Use Recovery Mode
Since WordPress 5.2, a fatal error often triggers a WordPress critical error fix pathway called Recovery Mode — and many site owners never notice it.
When a plugin or theme causes a fatal error, WordPress may email the administrator a Recovery Mode link. It opens a protected admin session where you can deactivate the faulty plugin or switch themes while the site is down.
Check the admin inbox (including spam) for “Your site is experiencing a technical issue.” If you find it, use its link before digging into FTP.
Disable WordPress Plugins via FTP
If the debug log points at a plugin — or you updated plugins right before the white screen — disable WordPress plugins via FTP. This deletes nothing and erases no settings.
- Open the wp-content folder via FTP or your host’s file manager.
- Rename the plugins folder to plugins-disabled and reload. If the site returns, a plugin was the culprit.
- Rename the folder back to plugins, then rename plugin folders one at a time, reloading after each, until the white screen returns. The last one renamed is the offender.
- Leave that plugin deactivated, check for an update or replacement, and contact its developer if needed.
Your plugin settings stay intact. Deactivation only stops code from running; your data stays in the database.
Switch to a Default Theme
If plugins aren’t the problem, the theme is next — especially after a theme update. In wp-admin or Recovery Mode, switch to a default theme like Twenty Twenty-Four. If you can’t reach wp-admin, rename your active theme’s folder inside wp-content/themes/ via FTP and WordPress will fall back to a default theme.
WordPress Memory Limit Fix
If your debug log says “Allowed memory size exhausted,” you need a WordPress memory limit fix. WordPress defaults to 40M on single sites and 64M on multisite, which heavy plugins can exhaust. Add this to wp-config.php above the “stop editing” line: define( ‘WP_MEMORY_LIMIT’, ‘256M’ ); If the error persists, ask your host to raise the PHP memory_limit as well — WordPress can only raise the limit, never lower it, and it cannot exceed the server’s ceiling.
Fix a Corrupt .htaccess or Core Files
A damaged .htaccess file can also blank your site. Back it up, then replace it with a fresh default WordPress .htaccess. If core files are corrupt, reinstall WordPress core from Dashboard, Updates — this replaces core files without touching your content, themes, or plugins. Keep a full backup before either step.
Check the PHP Version
Plugins built for a newer PHP version can crash on an old one, and vice versa. In your hosting panel, check the PHP version your site runs and compare it with your theme and plugins’ requirements. Change it one step at a time and reload after each change. If a recent PHP upgrade caused the blank page, rolling back one version often restores the site while you update the offending plugin.
When to Call Your Host
Call your host if the debug log is empty, the error names wp-includes or wp-admin files, or the site blanks on every page including wp-admin. Those point to a server or core problem, not a single plugin. Give them the exact error line from debug.log — it saves hours of guessing.
Need help with a site that will not load? See our services or contact us — and for related fixes, read how to speed up a WordPress site and how to check if your WordPress site is hacked. Further reading: DevDiggers WSOD guide, OpenReplay WSOD guide, AHosting WSOD guide.
Frequently Asked Questions
What causes the WordPress white screen of death? Almost always a PHP fatal error: a plugin or theme conflict, an exhausted memory limit, a corrupt file, or a PHP version mismatch — with error display turned off, so the page renders blank.
How do I fix it if I cannot access wp-admin? Use the Recovery Mode email link if one was sent, or fix it at file level: enable WP_DEBUG logging, rename plugin folders via FTP or your host’s file manager, and switch themes by renaming the theme folder.
Does raising the memory limit fix it? Only if the error is memory exhaustion (“Allowed memory size exhausted”). It will not fix a plugin conflict or a corrupt file — read debug.log first so you fix the real cause.
Will deactivating plugins delete my data? No. Deactivation stops the code from running; settings and data stay in the database until you actually delete the plugin.
Conclusion: How to Fix WordPress White Screen of Death, in One Pass
Learning how to fix WordPress white screen of death problems comes down to one habit: find the error before you guess at fixes. Check Recovery Mode, log the error with WP_DEBUG, isolate the plugin or theme, fix the memory limit if that is the cause, and turn debug mode off when you are done. Most blank sites are back within 15 to 30 minutes — and your content was never gone in the first place.
