How to Fix the WordPress White Screen of Death

What the white screen of death actually is

The WordPress white screen of death is exactly what the name suggests: you open your site, or your admin dashboard, and instead of your pages you get a blank white page with nothing on it. No error message, no menu, no content, just white. It is one of the most unnerving problems a site owner can run into, because the site gives you no clue about what went wrong. It simply stops showing anything at all.

Behind that blank page, something has gone wrong badly enough that WordPress could not finish building the page. WordPress runs on PHP, the programming language that assembles each page when someone visits. When the PHP hits an error it cannot recover from, called a fatal error, it stops. On many servers the default setting is to hide error messages from visitors for security reasons, so instead of printing the error, the server sends back an empty page. That empty page is the white screen you are looking at.

So the white screen is not really a single problem with a single cause. It is a symptom, the visible result of a fatal error that has been hidden from you. The whole job of fixing it is to uncover what that hidden error is, and then deal with whatever caused it. Once you learn to reveal the real error, the white screen stops being a mystery and turns into an ordinary bug you can track down.

It helps to know that the white screen is common and almost always fixable. Sites do not usually break beyond repair. In most cases a plugin, a theme, a memory limit, or a small piece of broken code is behind it, and each of those has a known fix. This guide walks through every likely cause in a sensible order, so you can work from the quickest checks to the deeper ones without guessing.

Common causes of the white screen

Before you start changing things, it helps to know what usually causes the white screen of death, because that tells you where to look first. In our experience fixing WordPress sites, a handful of causes account for the large majority of cases. If you understand these, you can often guess the culprit from what you were doing right before the screen went blank.

The most frequent cause is a plugin conflict or a broken plugin. You update a plugin, or install a new one, and the site goes white. Plugins run their own code inside WordPress, and if that code has a bug, or it clashes with another plugin, the whole page can fail. The second most common cause is the theme, for the same reason: a theme is also code, and a bad update or a small edit to a theme file can bring everything down.

Running out of PHP memory is another big one. Every page WordPress builds needs a certain amount of memory, and if your site or a plugin tries to use more than the server allows, PHP stops with an out of memory error and you get a white page. This often shows up on heavier pages, or after you add a plugin that needs more resources than the ones before it.

Other causes include corrupted core files from a failed update, a broken .htaccess file, an outdated or misconfigured version of PHP on the server, and small syntax errors introduced when someone pastes a code snippet into a theme file. Each of these has its own fix, which the later sections cover. The chart below shows roughly how often we see each cause, based on the sites we work on. Treat it as illustrative rather than exact, since every site is different.

Before you start: back up and stay calm

When your site goes white, the first instinct is to start changing things fast to get it back. Resist that. A calm, ordered approach fixes the white screen faster than frantic clicking, and it stops you from turning one problem into three. The screen is blank, but your content, your settings, and your files are almost always still there and intact. Nothing has been deleted just because the page will not display.

The single most important step before you touch anything is to make a backup, if you can. If your admin dashboard still loads, use your backup plugin or your host's backup tool to save a copy of the site as it is right now. If the dashboard is also white, your host almost certainly keeps recent backups you can restore from, and many hosts can roll a site back to a point before it broke with a single click. Knowing you have that safety net makes the rest of the work far less stressful.

It also helps to write down what you were doing right before the site broke. Did you update a plugin? Activate a new theme? Paste a snippet of code into a file? Change a setting? The answer usually points straight at the cause and saves you a lot of time. If several people manage the site, ask them too, since someone may have made a change you do not know about.

Finally, decide where you will work. Some fixes need access to your files, which you reach through your host's file manager or an FTP program, or through the hosting control panel. If you have never used those, do not worry, the steps below explain what to open and what to change. If at any point you feel out of your depth, that is a fine time to reach out for help rather than risk making things worse. There is no shame in handing a broken site to someone who fixes them every day.

Turn on debug mode to see the real error

This is the most important step in the whole guide, because it changes the white screen from a mystery into a plain message that tells you what broke. Remember that the white screen appears because the real error is being hidden. WordPress has a built in debug mode that reveals that hidden error, and turning it on often solves the problem in minutes by pointing you straight at the guilty file or plugin.

To turn it on, you edit a file called wp-config.php, which sits in the main folder of your WordPress install. You reach it through your host's file manager or an FTP program. Open the file and look for a line that says define('WP_DEBUG', false);. Change false to true. It is also worth adding a couple of lines so the errors get written to a log file instead of shown to every visitor, which keeps things tidy and private while you work.

The official documentation on debugging in WordPress lists the exact lines to use, but the common set looks like this: set WP_DEBUG to true, set WP_DEBUG_LOG to true so errors are saved to a file, and set WP_DEBUG_DISPLAY to false so they are not printed on the page for visitors to see. Once those are in place, reload the broken page.

Now, instead of a blank screen, you will either see an error message on the page, or you will find one written into a file called debug.log inside the wp-content folder. That message usually names the exact file and line where the error happened, and very often it names the plugin or theme responsible. A line mentioning a plugin folder tells you which plugin to disable. A message about memory tells you to raise the memory limit. This single step points you at the right fix more often than anything else, so do not skip it.

When you have finished fixing the site, remember to set WP_DEBUG back to false. You do not want debug logging running on a live site long term, both for privacy and for tidiness. Debug mode is a tool you switch on to investigate and switch off when you are done.

Rule out plugins

Plugins are the number one cause of the white screen, so if debug mode has not already named the culprit, plugins are the first thing to test. The idea is simple: turn all your plugins off, see if the site comes back, and if it does, turn them on one at a time until the site breaks again. The plugin that breaks it is your problem.

If your admin dashboard still loads, this is easy. Go to the plugins page, select all your plugins, and deactivate them in one go. Check your site. If the white screen is gone, you have confirmed a plugin is the cause. Now reactivate them one by one, checking the site after each, until the screen goes white again. The last one you turned on is the offender. You can then leave it off, look for an update that fixes it, or replace it with a better alternative.

If the dashboard is also white, you cannot use that page, but you can still deactivate plugins through your files. Open your file manager or FTP, go to the wp-content folder, and find the folder named plugins. Rename it to something like plugins-off. This instantly deactivates every plugin at once, because WordPress can no longer find them where it expects. Check your site. If it loads, a plugin was the cause.

To find which one, rename the folder back to plugins, then go inside it and rename individual plugin folders one at a time, testing the site after each, until you find the plugin that brings the screen back when present. It is a little tedious, but it reliably finds the guilty plugin even when you have no dashboard access. The steps for this are covered in the official WordPress configuration and troubleshooting resources, and they are safe as long as you only rename folders rather than delete them.

Once you find the plugin, you have choices. Check whether the developer has released an update that fixes the bug. Check whether two plugins are clashing, which you spot when the site only breaks with both active. If a plugin is abandoned and broken, the safest path is to replace it with a maintained alternative that does the same job. Plugin conflicts are common and usually straightforward to resolve once you know which plugin is involved.

Switch to a default theme

If turning off every plugin did not fix the site, the theme is the next suspect. Your theme is code too, and a broken theme, a bad theme update, or a small mistake in a theme file can cause the white screen just as a plugin can. The way to test this is to temporarily switch to one of the default WordPress themes, which are known to be clean and reliable.

If your dashboard works, go to the appearance section and activate one of the default themes, the ones named after a year. If the white screen disappears once you switch, your theme was the cause. That does not always mean your theme is bad, it may just need an update, or a recent edit to it needs to be undone, but you have confirmed where the problem lives.

If the dashboard is white, you switch themes through your files, similar to the plugin trick. Go to wp-content and open the themes folder. Find the folder for your active theme and rename it. When WordPress cannot find the active theme, it falls back to a default theme if one is present, which should bring the site back. This is why it is wise to always keep one default theme installed even if you do not use it, so there is something to fall back to.

Once you know the theme is the cause, think about what changed. Did the theme update recently? Did someone edit a theme file, perhaps adding a code snippet to functions.php? A single misplaced character in that file, like a missing bracket or semicolon, is enough to white screen the whole site. If you or a developer made a recent edit, undoing it often fixes things instantly. If the theme itself is broken, updating it or contacting the theme's support are the next moves. And if you rely on a heavily customized theme with no backup of the original, that is a strong reason to keep proper backups going forward.

Increase the PHP memory limit

If the error you found in debug mode mentions memory, or you have ruled out plugins and the theme, the next likely cause is that your site is running out of PHP memory. Every page WordPress builds needs a slice of the server's memory to work with. If a page needs more than the limit set for your site, PHP stops partway through with an out of memory error, and you get a white screen. This is common on resource heavy sites, on pages with many plugins active, or after adding a plugin that is hungrier than the rest.

The fix is to raise the memory limit, and there are a few ways to do it. The simplest is to add a line to your wp-config.php file that sets a higher limit for WordPress. The line looks like define('WP_MEMORY_LIMIT', '256M');, which raises the limit to a comfortable level for most sites. Add it above the line that says to stop editing, save the file, and reload your site. If memory was the problem, the white screen clears.

Sometimes the WordPress setting alone is not enough because the server itself caps memory at a lower level. In that case the limit has to be raised at the server, which you can sometimes do through a php.ini file or through your hosting control panel's PHP settings. On managed hosting the limit is often already generous, and if it is not, your host's support can raise it for you quickly. It is worth asking them rather than fighting with server files if you are not comfortable there.

A word of judgement here. Raising the memory limit is the right fix when a site genuinely needs a bit more room, but if you find yourself needing to raise it very high just to load a page, that can be a sign of a deeper problem, such as a badly built plugin that leaks memory or a theme doing far too much work on every page. Raising the limit gets you running again, but if it keeps happening, it is worth having someone look at why the site is so hungry in the first place.

Repair corrupted core files

Sometimes the white screen comes from a damaged WordPress core file. Core files are the main program files that make WordPress run, separate from your plugins, theme, and content. They can become corrupted when an update fails halfway, when a file transfer is interrupted, or, in worse cases, when a site is hacked and files are tampered with. If a core file is broken, WordPress cannot run properly and you get a blank page.

The good news is that core files are the same on every WordPress site, so replacing them with fresh copies is safe and does not touch your content or settings. Your posts, pages, images, and options live in the database and the uploads folder, not in the core files, so swapping the core files out does not risk your content as long as you replace the right folders only.

To do this, download a fresh copy of WordPress from the official WordPress.org download page, matching the version you run if you can. Unzip it on your computer. Then, using your file manager or FTP, upload the fresh wp-admin and wp-includes folders over the ones on your site, replacing the existing files. These two folders hold the core program and contain nothing of yours, so overwriting them is the standard, safe way to repair a damaged install.

Do not overwrite the wp-content folder, since that holds your themes, plugins, and uploaded files, and do not overwrite your wp-config.php, since that holds your unique settings and database connection. As long as you only replace wp-admin and wp-includes, this fix is low risk. After uploading, reload your site. If a corrupted core file was the cause, the fresh copies bring it back to life. If you suspect the corruption came from a hack rather than a failed update, treat that as a security incident and read our guide on how to secure a WordPress website once the site is back up.

Fix the .htaccess file and permalinks

On many WordPress sites there is a hidden file called .htaccess in the main folder that controls how web addresses work, along with some redirects and rules. If this file becomes corrupted, often after a plugin change or a botched edit, it can cause errors that show up as a white screen or as broken links across the site. Because it is a small file with a big influence, it is worth checking when the usual suspects come up empty.

The fix is to regenerate a clean version of the file. First, find the existing .htaccess in your main WordPress folder using your file manager. You may need to turn on the option to show hidden files, since names beginning with a dot are hidden by default. Rename the existing file to something like .htaccess-old rather than deleting it, so you keep a copy in case you need to look back at any custom rules it held.

With the old file renamed, WordPress will run without it, though your nice looking links may temporarily break. To rebuild the file cleanly, log into your dashboard if you can, go to the permalinks settings, and simply click save without changing anything. That action tells WordPress to write a fresh, correct .htaccess file. If your dashboard is not available yet, removing the corrupted file alone is often enough to clear the white screen, and you can regenerate the links once you are back in.

If your site sits on a different type of server that uses its own configuration instead of .htaccess, this particular fix will not apply, and the cause is more likely to be one of the others in this guide. But on the common setup that most shared and managed WordPress hosts use, a broken .htaccess is a real and easily fixed cause of a blank page, so it belongs on your checklist.

Check wp-config and PHP settings

The wp-config.php file is the heart of your WordPress settings. It holds the details WordPress needs to connect to its database and a set of other important options. Because it is so central, a mistake in this file can bring the whole site down with a white screen. This often happens when someone edits the file to add a setting and accidentally introduces a typo, a stray character, or an extra closing tag.

If you recently edited wp-config.php, that edit is the first thing to check. Open the file and look carefully at any lines you added. A common mistake is text placed after the final PHP closing tag, or a missing quote or semicolon on a line you pasted in. Even one wrong character can stop the file from running. If you are not sure, comparing against a fresh copy of the sample config that ships with WordPress helps you spot anything out of place.

The database details in this file matter too. If the database name, username, password, or host in wp-config.php are wrong, WordPress cannot reach your content and may show a blank page or a database error instead. These details usually only change if you moved the site to a new server or your host changed them, so if the site broke right after a move, this is a prime suspect. Your host can confirm the correct values.

The version of PHP your server runs is another setting worth checking, though you change it in your hosting control panel rather than in this file. WordPress needs a reasonably current version of PHP, and running a very old one, or switching to a version your theme or plugins do not support, can trigger fatal errors and a white screen. Most hosts let you pick the PHP version with a couple of clicks. If a recent PHP change lines up with when the site broke, switching back to a supported version can fix it at once. The official notes on editing wp-config.php are a good reference if you want to double check any line before you save.

White screen on admin only vs the whole site

A useful clue for narrowing down the cause is where the white screen appears. There is a real difference between your public site going white, your admin dashboard going white, or both going white together, and that difference points you toward different causes. Paying attention to it saves you from testing things that could not be the problem.

If your public site is white but your admin dashboard still loads, that is actually the easier situation, because you can use the dashboard to do all your testing. It also suggests the problem is with something that runs on the front of the site, such as your theme or a plugin that only acts on public pages. You can deactivate plugins and switch themes right from the dashboard, following the steps above, and the fix is usually quick.

If the admin dashboard is white but the public site still loads, the cause is more likely something that runs specifically in the admin area, which can include certain plugins or a problem with the admin core files. Since you cannot use the dashboard, you fall back to the file based methods: rename the plugins folder, rename the theme folder, and if needed replace the wp-admin core folder with a fresh copy. Because the front of the site still works, you can be more relaxed while you fix the back end.

If both the site and the dashboard are white, the cause is usually something more fundamental, such as a memory limit that affects everything, a corrupted core file, a broken wp-config.php, or a server level issue. In that case you work entirely through your files and your host, starting with debug mode to reveal the error, then memory, then core files. The table below sums up which symptom tends to point to which cause, so you can start in the right place.

White screen after an update or on one page

Timing is one of your best clues. If the site went white immediately after you updated something, that update is almost certainly the cause, and you can skip much of the guessing. Updates to plugins, themes, or WordPress itself occasionally introduce a bug or a conflict, and the fix is usually to undo or replace whatever you just updated.

If a plugin update broke the site, deactivate that plugin using the methods above, then either wait for the developer to release a fix or roll back to the previous version, which some tools and hosts let you do. If a theme update broke it, switch to a default theme and contact the theme's support. If a WordPress core update failed and left the site white, replacing the core files with a fresh copy of the same version, as described earlier, usually sets it right. The pattern is the same each time: identify what changed, and reverse or repair it.

A different and gentler version of the white screen is when only one page goes blank while the rest of the site works fine. This narrows the cause enormously, because it has to be something specific to that page. Often it is a shortcode from a plugin you removed, a block that is not rendering, an embedded element, or a plugin that only runs on that type of page. Since the rest of the site is healthy, you are not in an emergency, and you can investigate calmly.

To fix a single blank page, edit it and look at what it contains, especially anything added recently. Try removing the most recent additions one at a time, or switching a problem block back to plain text, and preview after each change. If the page uses a shortcode from a plugin, check that the plugin is still active and working. A single blank page is usually the quickest kind of white screen to solve, because the cause is boxed into one place rather than spread across the whole site.

Server and hosting causes

Not every white screen comes from your own plugins or theme. Sometimes the cause sits at the server level, in the hosting that runs your site. When you have worked through plugins, theme, memory, and files without luck, the server becomes the prime suspect, and this is where your host's support becomes your best ally.

One server side cause is the PHP version, mentioned earlier. Hosts update the versions of PHP they offer, and sometimes an automatic change, or one you made without realizing the effect, moves your site to a version your theme or plugins do not fully support, which can white screen the site. Checking and adjusting the PHP version in your hosting control panel, or asking your host to do it, is a quick thing to try.

Another cause is resource limits beyond memory. Hosts set limits on how much processing time and how many resources a site can use, especially on shared plans. If your site regularly bumps into those limits, pages can fail and go blank, particularly under traffic. This shows up as a site that is fine most of the time but goes white when it is busy or when a heavy task runs. If that sounds like your situation, the fix is often better hosting with more headroom, which also helps your site speed at the same time.

There are also plain outages and server faults, where the problem is entirely on the host's side and nothing you changed. In those cases the fastest path is simply to contact your host, tell them your site is showing a blank page, and ask them to check the server logs. Hosts can see errors in their logs that you cannot, and a good support team will often spot the cause in minutes. Never feel you have to solve a server problem alone when the people running the server are one message away. If your host is slow or unhelpful when your site is down, that itself is a sign it may be time to move to hosting built for WordPress.

Recovery mode and fatal error emails

Modern versions of WordPress include a helpful safety feature that can make the white screen much less scary, and many site owners do not know it exists. When a fatal error happens, WordPress tries to detect it, and rather than leaving you with a pure blank screen, it can send an email to the site administrator explaining what went wrong and offering a way back in. It is worth knowing about because it can hand you the answer without any digging.

The email goes to the administrator address set in your WordPress settings, so the first thing to do when your site breaks is check that inbox, including the spam folder. The message often names the exact plugin or theme that caused the error, which tells you immediately where to look. That alone can turn a stressful outage into a two minute fix, because you no longer have to test everything to find the culprit.

The email also usually contains a special link into what WordPress calls recovery mode. This is a protected version of your dashboard that loads even when the front of the site is broken, with the offending plugin or theme paused so you can get in. Once inside recovery mode, you can deactivate or update the problem plugin or theme through the normal dashboard, then leave recovery mode and check that the site is back. It is designed for exactly this situation and is much friendlier than editing files.

For the fatal error email to reach you, your site needs to be able to send email and your administrator address needs to be one you actually check. This is one more reason to keep that address current. If you never receive these emails, it can mean your site is not set up to send mail reliably, which is a common WordPress issue worth fixing on its own, and something a maintenance plan usually takes care of. When recovery mode is available to you, it is often the quickest route out of the white screen, so check for that email before you start renaming folders.

How to prevent the white screen in future

Fixing the white screen once is good, but not having it happen again is better. Most white screen incidents are preventable with a few sensible habits, and putting them in place protects you from the stress of a sudden outage. The goal is to catch problems before they reach your live site and to always have a fast way back if something does slip through.

The most valuable habit is keeping current backups. If you always have a recent backup, a white screen stops being a crisis, because in the worst case you restore and you are back in minutes. Set up automatic backups, either through your host or a reliable plugin, and make sure they are stored somewhere off the site itself. A backup you cannot reach because the site is down is not much use, so keep copies you can restore from independently.

Testing updates before they hit your live site is the next big one. Many white screens come from an update that clashed with something. A staging site, which is a private copy of your live site, lets you apply updates there first and check that everything still works before you repeat them on the real site. Many good hosts offer one click staging. It turns risky updates into safe, checked ones, and it is one of the strongest defenses against surprise outages.

Beyond those two, the everyday habits matter: keep WordPress, your theme, and your plugins updated so bugs and security holes get patched, but do it carefully and one thing at a time so you can tell what caused any problem. Remove plugins and themes you do not use, since idle code is still code that can break. Avoid pasting snippets you do not understand into important files. And keep an eye on the site with monitoring that tells you the moment it goes down, so you find out before your customers do. The table below lines up each common cause with the habit that prevents it.

If keeping up with backups, staging, updates, and monitoring sounds like more than you want to manage, that is exactly what a WordPress maintenance service is for. It puts all of these protections on autopilot so the white screen, and problems like it, become far less likely and far easier to recover from when they do occur.

When to call a developer

Most of the fixes in this guide are within reach of a determined site owner, and working through them in order solves the large majority of white screens. But there is no prize for struggling alone, and there are clear moments when bringing in a developer is the smart, cost effective choice rather than a last resort. Knowing when to make that call saves you time and protects your site.

If you have worked through debug mode, plugins, theme, memory, and core files and the site is still white, that is a fair sign the cause is deeper than the common ones, and a developer who reads server logs every day will find it faster than continued trial and error. The same is true if the error message you found mentions parts of the code you do not recognize, or if the fix would mean editing code you are not confident changing. A wrong edit to a core file or to wp-config.php can make things worse, so caution here is wise.

You should also lean on a professional when the site is a business you cannot afford to have down, when the white screen may be linked to a hack, or when it keeps coming back after you fix it. A recurring white screen usually means the underlying cause was patched over rather than solved, and finding the root of it is exactly the kind of work a developer is good at. If security is even a possibility, treat it seriously and get expert eyes on it quickly.

At WP Developer, getting a broken WordPress site back up is routine work, and we can usually pin down a white screen quickly because we have seen every version of it. Whether you want a one time fix to get running again, or an ongoing plan so you are never caught out like this, we can help. Take a look at what we offer on our services page, and when you are ready, request a free quote and tell us what happened. There is no obligation, and even if you decide to fix it yourself, a quick conversation can point you in the right direction.

The white screen of death looks alarming, but it is one of the most solvable problems in WordPress. Behind that blank page is almost always an ordinary, fixable cause: a plugin, a theme, a memory limit, a file. Reveal the real error with debug mode, work through the suspects in order, and keep good habits like backups and staging so it rarely happens again. Do that, and a white screen becomes a minor bump rather than a disaster. And whenever you would rather hand it to someone who does this every day, get in touch and we will take it from here.