The WordPress white screen of death is almost always a PHP fatal error, and it's fixable — usually in under 30 minutes. The fastest path: don't guess. Identify what changed last, disable it, and restore access. Here's the calm version of that process, from someone who has fixed this on a lot of sites.
First: what the white screen actually is
A blank white page means PHP hit a fatal error and stopped before your theme could render anything. WordPress hides the error message from visitors on purpose (good for security, terrible for your blood pressure). The error is still there — it's just written to a log you haven't met yet instead of the screen.
The recovery checklist, in order
- Check your inbox. Since WordPress 5.2, the site often emails the admin a "your site is having a technical issue" message with a recovery-mode link that names the failing plugin. That email solves half of all white screens by itself.
- Ask what changed in the last hour. An update, a new plugin, a settings change, an edit to functions.php. White screens are almost never spontaneous — something changed.
- Try the admin. If
/wp-adminloads, deactivate the suspect and you're done. If it doesn't, keep going. - Read the error log. Your host's control panel has a PHP error log; the last "Fatal error" line names the exact file. The folder that file lives in is your culprit.
- Disable the culprit without the admin. Over your host's file manager or FTP, rename that one plugin's folder (e.g.
bad-plugin→bad-plugin-off). Site comes back; the rest of your plugins stay active. - Restore from backup only if the above fails. A backup restore is the sledgehammer — it works, but you'll lose whatever changed since. Use it last, not first.
Why is renaming the whole plugins folder bad advice?
The classic tip — rename wp-content/plugins and reactivate one by one — works, but it deactivates everything, loses widget and integration state on some setups, and on a store or membership site it takes real functionality down while you experiment. Renaming just the failing plugin's folder is surgical; the log (or the recovery email) tells you which one it is. Only fall back to the whole-folder trick when nothing names the offender.
How do I stop playing detective entirely?
This exact 30-minute ritual is why I built Culprit. It catches the fatal error at the moment it happens, names the plugin or theme responsible, and shows what changed right before. Full disclosure: it's my plugin — but it was built by someone who has done the FTP-and-oven-mitts routine more times than any human should.
Frequently asked questions
Can a white screen fix itself?
If it comes and goes, you're likely hitting a memory limit or a conflict that only triggers on certain pages. Intermittent white screens are still fatal errors — check the log before it becomes permanent.
Is it ever the theme?
Yes — especially after editing functions.php or updating a theme whose child theme overrides old code. The log will point at a theme file instead of a plugin folder; the fix is the same rename trick with the theme folder, which forces a default theme.
Should I be scared of PHP updates?
No, but stage them. A PHP version bump is the one change that can white-screen a site with no plugin update involved, because old plugin code stops being valid. Test on staging, or at minimum know your host's one-click PHP rollback before you bump.