A blank white page usually hides a PHP or database error, and a plugin or your theme is the quickest thing to rule out. Deactivate every plugin, or rename the plugins folder to plugins_old over FTP if you can't log in. Still blank? Switch to a default theme, then turn on WP_DEBUG so you can read the error itself.
WordPress shows PHP errors and database errors the same way: a blank screen with no message, no menu and no clue about what went wrong. That's why fixing it is a process of elimination. You switch things off until the page comes back, and whatever you switched off last is your suspect.
For the first pass you need either the admin screens or FTP access, and the patience to reload the site after every change.
The quick route back from a blank page
Work through these in order and reload the site after each one. Stop as soon as the page loads again.
- Take a backup or set up a staging copy first. The official debugging guidance asks for one or the other before you change anything, and our walkthrough on how to back up your site covers the first option.
- If the admin screens still open, deactivate all of your plugins in one go.
- Reload the site. If it's back, reactivate the plugins one by one, reloading after each, until the white screen returns.
- If you can't reach the admin screens, connect by FTP, open the wp-content folder and rename the plugins folder to plugins_old. That deactivates every plugin at once.
- If the blank page appeared right after you activated a new theme, switch to a default theme such as Twenty Twenty-One.
- Locked out? Over FTP, go to wp-content/themes and rename the active theme's folder.
- Still white? Add WP_DEBUG and WP_DEBUG_LOG to wp-config.php so errors are written to a debug.log file in wp-content.
- Read the newest entries in debug.log, then switch debugging off again.
Notice the order. Plugins come first because switching them all off is the quickest test you can run, and the theme comes second unless the screen went white straight after a theme change. Debugging is the last resort for when neither of those brings the page back.
Admin access or FTP only: where each fix lives
Which route you take depends on one question: do the admin screens still load? Here's where each fix sits in both situations.
| Fix | If the admin screens load | If you're locked out |
|---|---|---|
| Turn off plugins | Deactivate all plugins, then reactivate one at a time | Rename wp-content/plugins to plugins_old over FTP |
| Rule out the theme | Activate a default theme such as Twenty Twenty-One | Rename the active theme's folder in wp-content/themes |
| See the real error | Same either way: edit wp-config.php over FTP | Same either way: edit wp-config.php over FTP |
| Read the log | Same either way: download debug.log from wp-content over FTP | Same either way: download debug.log from wp-content over FTP |
Renaming a folder is the blunt version of the same fix. Nothing gets deleted: the files sit there under a new name, and the site simply can't load them. Once the page is back, rename the folder to plugins again and reactivate each plugin from the admin, one at a time, so you can see exactly which one breaks it.
The theme folder works the same way. Rename it back once you know the theme was the problem, and only reactivate it when you've dealt with whatever it was choking on. If you're about to try a fresh one instead, our guide to installing a new theme goes through it step by step.
What to check when the screen stays white
If neither plugins nor the theme brings the page back, the blank screen is hiding an error you haven't seen yet. The WP_DEBUG feature often gives you the extra information you're missing. With WP_DEBUG_LOG switched on as well, every error, notice and warning is written to debug.log in wp-content, so you're no longer guessing.
- Did you rename the right folder? It's the plugins folder inside wp-content, renamed to plugins_old.
- Did the trouble start straight after a theme change? Then try the theme step before the plugins.
- Is debug.log missing? Check that both WP_DEBUG and WP_DEBUG_LOG went into wp-config.php, not just one of them.
- Did you reload after each change? Testing three changes at once tells you nothing about which one mattered.
- Are you editing the live site? Stop and move the testing to a staging copy before you go further.
Remember what you're hunting for. The white screen is often a PHP error or a database error, and the log is how you find out which. That answer decides whether you're looking at a plugin, a theme file or the database next.
The catch: debug mode doesn't belong on a live site
The official debugging guidance is clear on this point: it doesn't recommend WP_DEBUG or the other debug tools on live sites. That's the step people forget. They turn debugging on to find the problem, fix it, and leave it running long after the page is back.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Treat it like a torch, not a light you leave on. Turn it on, read debug.log, turn it off. Better still, do your detective work on a copy of the site. A staging plugin gives you somewhere to break things without your visitors seeing a blank page while you test.
The same goes for the backup. It's the step everyone wants to skip when the site is down and the pressure is on, and it's the one that means a wrong rename or a bad edit to wp-config.php takes minutes to undo instead of costing you the site.
As of Nov 2026, WordPress's own documentation on this error is the page to keep open while you work through the list.
Frequently asked questions
Can a database error cause a blank white page?
Yes. Both PHP errors and database errors can appear as a blank screen with no information, which is why reading the debug log matters.
My screen went white after a theme change. Where do I start?
Go to the theme before anything else. Swap in Twenty Twenty-One from the dashboard, or give the current theme's folder a new name if you're shut out.
What should I do before I start changing things?
Make sure you can roll back. Copy the whole site somewhere safe, or test on a separate staging site, so any mistake can be reversed.
Should I keep WP_DEBUG switched on to catch future errors?
No. It isn't recommended on live sites, so turn it off as soon as you've read what you needed.
Do I need FTP if I can still log in?
Not for the plugin and theme steps, which you can do from the admin screens. You'll still need file access to edit wp-config.php for debugging.
