Table of contents13
Direct answer: if WordPress shows a blank white screen, it is usually a fatal PHP error caused by a plugin, a theme, or a memory limit. Back up first, then turn on WP_DEBUG, deactivate your plugins, switch to a default theme, and check the memory limit — testing your site after each step until the screen returns to normal.
You open your site and there is nothing. No error message, no layout, just white. That blank screen is called the WordPress white screen of death, and it is frightening because it looks as if the whole site has gone. In most cases the content is still there in the database. Something is stopping WordPress from finishing the page, and the job is to find that something without making the problem worse.
This guide works through diagnosis before repair. You will not be asked to guess, to reinstall everything, or to edit files blindly. Each step changes one thing, then you test. When the site comes back, you know what caused it, and you can fix that one thing properly instead of starting again.
What this guide will help you do
- Understand what a white screen means — and what it does not mean
- Take the safe first steps before you change anything
- Read the clues and narrow down the cause
- Fix the cause step by step, with a test after each change
- Stop the same white screen from happening again
- Answer the questions most site owners ask about this error
What the white screen of death actually is
The white screen of death is a blank page where a WordPress page should be. Sometimes it appears on the whole site, sometimes only in the dashboard, and sometimes only on one page. That pattern matters, because it points to where the fault lies. A site-wide blank screen usually points to a plugin, a theme, or a server limit. A blank dashboard with a working front page points more narrowly to something loaded in the dashboard. A single blank page can point to that page’s content or to a feature used only on that page.
Behind the blank screen there is usually a PHP error that WordPress is not displaying. Many hosts hide PHP errors from visitors for security, so you see white instead of a useful message. That is why the first diagnostic step in this guide is to make the error visible to you, in a private log, rather than guessing at the cause.
A white screen does not, on its own, mean your content is lost, that you have been hacked, or that you need a new site. Those things are possible in other situations, but a blank screen after an update, after installing a plugin, or after changing a theme is far more often a straightforward conflict or limit. Stay calm, work in order, and keep a note of every change you make.
Before you change anything: back up and get access
Do not start by editing files or deleting plugins. First, make sure you can get back to where you started. If your host offers a backup, take one now, even if the site looks blank. If you can reach the dashboard, export what you can. If you cannot reach the dashboard, a backup from your hosting account is the safety net that lets you try the steps below with confidence.
You will also need a way into your files. That is usually your hosting file manager or an FTP or SFTP connection. If you do not have those details, ask your host for help before you go further, and do not share your login details in public forums while you look for help. File access is what lets you rename a plugin folder, switch a theme, or edit the configuration file when the dashboard is unavailable. The steps below explain each of those actions in plain language.
Finally, note when the problem started and what changed just before it. Did you update a plugin, install a new theme, change a setting, or move hosts? That timing is often the best clue you have, and it tells you where to test first. Write it down, because it is easy to forget once you have tried several fixes.
Diagnose it: what you see, what it usually means, and what to check first
Use this table to narrow down the cause before you change anything. It does not prove the cause, but it tells you which test to run first, and that saves time and avoids unnecessary changes.
| What you see | Likely cause | First check |
|---|---|---|
| Whole site blank, including the dashboard | A plugin, theme, or memory limit stopping pages from loading | Enable WP_DEBUG and check the error log |
| Front page works, dashboard is blank | A dashboard-only plugin or a dashboard setting | Deactivate plugins and test the dashboard again |
| Blank screen straight after an update | The updated plugin or theme, or a conflict with another plugin | Roll back that one change if you can, then test |
| Blank screen on one page only | Content or a feature used only on that page | Check that page in the editor or a draft copy |
| Blank screen after a host move | A file, database, or server setting that did not move cleanly | Check the configuration file and file permissions with your host |
Now turn on error logging so you are working from evidence, not guesses. In your site’s configuration file, wp-config.php, the WP_DEBUG setting controls whether WordPress shows and records PHP errors. For diagnosis, enable WP_DEBUG and WP_DEBUG_LOG, and keep WP_DEBUG_DISPLAY off, so errors go to a log file instead of appearing on the live site. The log is usually saved as wp-content/debug.log. Open it after you reload the blank page, and look for the most recent fatal error. It will often name a plugin or theme folder, which tells you where to look next. When you have finished diagnosing, turn debugging off again, because a log left running can grow and can expose details you would rather keep private.
If you are not comfortable editing wp-config.php, ask your host to enable error logging for you, or use the plugin and theme tests below first. You can still make progress without a log, but the log makes the job much faster and much less of a guessing game. For a careful, ordered approach to updates in general, see The Safe WordPress Update Checklist.
Fix it step by step: one change, then one test
Work through this checklist in order, and test the site after each step. Stop as soon as the site returns, because the last change you made is the one that matters. Do not make several changes at once, or you will not know which one fixed it.
- Back up, then enable WP_DEBUG and WP_DEBUG_LOG. Reload the blank page, then read wp-content/debug.log for the latest fatal error. Note any plugin or theme folder it names.
- Deactivate all plugins. Using file access, rename the plugins folder to plugins-old, then create a new empty plugins folder, or rename each plugin folder one by one if you prefer. Reload the site. If it returns, a plugin is involved. For safe plugin habits in future, see How to Install WordPress Plugins Safely.
- Reactivate plugins one at a time. Restore the original folder name, then reactivate each plugin in turn, testing after each one. When the white screen returns, you have found the problem plugin. Keep it deactivated, and check for an update, a replacement, or advice from its author. Run the same careful checks described in 10 Checks to Run Before Activating Any Plugin before you reactivate anything else.
- Switch to a default theme. If plugins are not the cause, rename your active theme folder so WordPress falls back to a default theme, then reload. If the site returns, the theme, or a feature in it, is involved. Check the theme for an update, and test any custom code in a child theme or staging site before you put it back.
- Check the memory limit. A site can run out of PHP memory when a plugin or theme asks for more than the server allows. Your host can raise the limit, or you can raise it in wp-config.php if you are comfortable doing so, following your host’s guidance. Raise it only as far as needed, then test again.
- Check for a damaged file or an incomplete update. If the white screen followed an update, a file may not have copied completely. Reinstalling WordPress core files, without touching your content or your theme and plugin settings, can repair that. Ask your host to help if you are unsure, and keep your backup close.
- Restore from backup only if you must. If none of the steps above works, restoring a recent backup from before the problem started is a reasonable next step. After the restore, repeat the update or change that caused the problem, one step at a time, so you do not restore the fault along with the site. For moving or rebuilding after a restore, Migrate WordPress to a New Host With Zero Downtime explains the careful order to follow.
While you work, keep your notes up to date. Write down each change, each test result, and the exact error from the log. If you later ask your host or a developer for help, those notes turn a long investigation into a short one, and they stop you from repeating a step that already failed.
Prevent the next white screen
Most white screens follow a change, so the best prevention is a calm change routine. Update one thing at a time, and test the site after each update. Keep regular backups, and test a restore now and again on a staging site, so a backup is not a surprise when you need it. Keep plugins and themes to those you actually use, and remove the rest, because every extra plugin is another possible conflict.
Use a staging site for major changes, such as a theme change or a set of updates together. A staging copy lets you see the white screen, if it happens, without your visitors seeing it. When a change works on staging, you can repeat it on the live site with confidence. If you build pages in the editor, The Complete Guide to the WordPress Block Editor will help you work in a way that is easier to undo, because blocks and patterns are easier to change than custom code pasted into a live theme.
Finally, turn WP_DEBUG off when you have finished. Leave debugging on only while you are diagnosing a problem. A debug log left running can grow large, and it can record details that are better kept private.
Frequently asked questions
How can I fix the white screen of death?
Back up first, enable WP_DEBUG logging, then deactivate plugins, switch theme, and check the memory limit, testing after each step. The step that brings the site back points to the cause, which you can then update, replace, or repair.
Why is my website displaying a white screen?
Usually because a PHP error is stopping WordPress from finishing the page, and your host is hiding that error from visitors. A plugin, a theme, or a memory limit is the most common trigger, especially straight after an update or a new installation.
Why am I getting a blank white screen?
A blank screen means the page started to load but stopped before any content could be shown. Check the error log first, then isolate plugins and the theme, as described above, rather than guessing at the cause.
Is a white screen caused by a plugin or by a theme?
It can be either. Deactivating all plugins and testing will tell you if a plugin is involved. If the site stays blank with plugins off, switching theme will tell you if the theme is involved. Test one at a time so the result is clear.
Will I lose my content if my site shows a white screen?
Not usually. A white screen normally means pages cannot be displayed, not that posts, pages, or media have been deleted. That is why a backup, and a calm step-by-step test, are the right first moves before any repair.
What is WP_DEBUG, and is it safe to use?
WP_DEBUG is a WordPress setting that records PHP errors so you can see what went wrong. Use it with logging on and on-screen display off, so errors go to a private log file, and turn it off again when you have finished diagnosing.
Ready to make your next change safely? Read How to Customize WordPress Without Breaking It next, and use its staging, child-theme, and rollback routine before you change a live site again.
