How to Fix WordPress White Screen of Death

You open your WordPress site, ready to check on things, and instead of your blog… nothing. Just white. No error message. No explanation. No hint of what went wrong. Just a blank, empty page staring back at you.

If this is happening to you right now, take a breath. How to fix WordPress white screen of death is one of the most searched WordPress problems for a reason; it’s also one of the most common errors beginners run into, and it has an actual name: the White Screen of Death, or WSOD.

I know it looks terrifying. A blank screen where your website used to be feels like everything is gone. But here’s the truth: it rarely is. In most cases, this is fixable, and often in under 10 minutes. You don’t need to be a developer to sort this out. You just need to know where to look.

As a WordPress designer who has built and managed multiple sites, I understand exactly what’s happening behind that blank page and why it shows up in the first place. This guide walks you through every common cause, in plain English, step by step, so you can diagnose your specific issue and fix it, not just try random things and hope.

Before we go any further, here’s the reassurance you need most right now: your content is not deleted. Your site is not permanently broken. This is a display error, not data loss. Stay calm and work through the steps below in order.

If you’re still setting up your blog or you’re new to this whole process, it might help to first read how to start a blog from scratch, so you understand the moving parts of your WordPress site before troubleshooting one of them.

What Is the WordPress White Screen of Death?

The White Screen of Death is exactly what it sounds like: your WordPress site displays a completely blank white page. No error message, no content, nothing visible at all. It can affect your entire site, or just parts of it, like your dashboard while your homepage still loads, or the other way around. The WordPress community nicknamed it WSOD, borrowing from the infamous “Blue Screen of Death” that Windows computers are known for.

Here’s what it is not:

Your content is not deleted
Your site is not permanently broken
Your hosting account is not suspended
You do not need to rebuild your site from scratch

So why does it happen? Under the hood, PHP (the programming language WordPress runs on) hits a fatal error and can’t complete the process needed to load your page. Instead of showing you what went wrong, it just shows a blank page. There are several possible causes, which is exactly why diagnosis has to come before any fix; guessing wastes time.

There are also two types of WSOD worth knowing apart, because they change your starting point:

Frontend only — visitors see a white screen, but you can still log into your dashboard
Complete — both your frontend and your dashboard show white

Before You Start: Essential Preparation

Don’t jump straight into fixes. A few minutes of preparation now saves you a lot of confusion later.

Step 1: Identify which type you have. Try visiting yoursite.com/wp-admin. If it loads, you’re dealing with a frontend-only WSOD. If it doesn’t, you have a complete WSOD, and your approach will lean more on File Manager access.

Step 2: Back up if possible. If you can get into your hosting panel at all, trigger a manual backup before touching anything. On Hostinger hPanel, this is under Backups → Create Backup. It protects you in case anything goes sideways while you’re fixing the real issue.

Step 3: Stay calm. Most WSOD cases are resolved in 5 to 30 minutes. None of the fixes in this guide are irreversible; you can undo every single one of them. Work through this systematically. Randomly clicking things in a panic is how simple problems turn into complicated ones.

Step 4: Have your hosting access ready. Log into your hosting account (I use Hostinger’s hPanel for The Income Plug) before you start, since you’ll likely need File Manager access at some point. If you haven’t picked a host yet or you’re wondering whether yours is holding you back, I break down my experience in my Hostinger review.

The Most Common Causes (Know Yours Before Fixing)

Here are the causes behind almost every white screen, ranked from most to least common.

Cause 1: Plugin conflict (most common). A plugin update introduced a compatibility issue, a newly installed plugin clashes with an existing one, or two plugins are trying to do the same job at once. A telltale sign: the white screen appeared right after you installed or updated a plugin.

Cause 2: Theme conflict (very common). A theme update caused the issue; your new theme doesn’t play well with your plugins, or theme files got corrupted. Sign: The white screen showed up after a theme change or update.

Cause 3: PHP memory limit exhausted. WordPress ran out of the memory it was allocated, which is especially common on shared hosting plans with low default limits. Sometimes you’ll see a memory-related error flash briefly before it goes white.

Cause 4: PHP version incompatibility. Either your PHP version is too old for a plugin or theme, or PHP was recently updated, and something broke as a result. Sign: This happened right after a PHP update.

Cause 5: Corrupted WordPress core files. Usually, the result of a failed update leaving core files damaged. Sign: The white screen appeared after a WordPress update.

Cause 6: Syntax error in code. Custom code added to functions.php, or an error from a code snippet plugin. Sign: This started right after you added a code snippet.

Cause 7: File permission issues. WordPress files end up with incorrect permissions, often after a server migration. Sign: This began right after moving hosts.

How to Diagnose Your Specific Cause

Guessing wastes time. The fastest path to a fix is finding out exactly what’s causing your white screen, and that means enabling debug mode.

Enable WordPress debug mode via File Manager:

Log into hPanel
Go to File Manager → public_html
Find and open wp-config.php by clicking Edit
Locate this line: define('WP_DEBUG', false);
Change it to:

   define('WP_DEBUG', true);
   define('WP_DEBUG_DISPLAY', true);
   define('WP_DEBUG_LOG', true);

Save the file
Refresh your white-screen page
An error message should now appear where the blank page was
Read the error; it will usually point directly to the plugin, theme, or file causing the problem

Here’s how to interpret what you see:

“Fatal error in /plugins/[name]/” → plugin conflict (jump to Fix 1)
“Fatal error in /themes/[name]/” → theme conflict (jump to Fix 2)
“Allowed memory size exhausted” → memory limit issue (jump to Fix 3)
“Parse error: syntax error” → code error (jump to Fix 6)

Important: once you’ve identified and fixed the issue, go back into wp-config.php and change WP_DEBUG back to false. Leaving debug mode on publicly exposes error details you don’t want visible to visitors.

The Fixes: Step by Step for Each Cause On: How to fix WordPress white screen of death

Fix 1: Plugin Conflict

Method A: Via WordPress Dashboard (if you can still access it):

Go to Plugins in your dashboard
Select all plugins using the checkbox at the top
Choose Bulk Action → Deactivate
All plugins are now deactivated
Refresh your site — does it load now?
If yes, a plugin was the cause
Reactivate plugins one at a time, checking your site after each one
When the white screen returns, you’ve found your problem plugin
Keep it deactivated and contact the plugin developer, or look for an alternative

Method B: Via File Manager (if the dashboard is also white)

Log into Hostinger hPanel
Go to File Manager → public_html → wp-content
Find the “plugins” folder
Rename it to “plugins_disabled” this deactivates every plugin at once
Refresh your site
If it loads, a plugin was the cause
Rename the folder back to “plugins.”
Go inside the folder and rename individual plugin folders one at a time to isolate the problem plugin
Once found, delete or replace that plugin

Fix 2: Theme Conflict

Method A — via Dashboard:

Go to Appearance → Themes
Activate a default WordPress theme, like Twenty Twenty-Four
Check whether your site loads now
If yes, your theme was the cause
Contact your theme developer or switch to a different theme

Method B — via File Manager:

Go to File Manager → public_html → wp-content → themes
Find your active theme’s folder
Rename it, adding “_disabled” to the end
WordPress will automatically switch to a default theme
Check if your site loads. If it does, the theme was the cause

Fix 3: PHP Memory Limit

Via wp-config.php:

Open File Manager → public_html
Find wp-config.php and click Edit
Add this line just before “That’s all, stop editing!”: define('WP_MEMORY_LIMIT', '256M');
Save the file and refresh your site

Via Hostinger hPanel:

Go to hPanel → Advanced → PHP Configuration
Find the memory_limit setting
Increase it to 256M or 512M
Save your changes

Via .htaccess file:

Open File Manager → public_html
Find and edit .htaccess
Add this line: php_value memory_limit 256M
Save and refresh

Fix 4: PHP Version Issue

Go to hPanel → Advanced → PHP Configuration
Check your current PHP version
If it’s below 8.0, update to 8.1 or 8.2
Save your changes and check your site immediately
If the site breaks further, revert to the previous version
Check whether your plugins and theme are actually compatible with the newer PHP version before updating again

Fix 5: Corrupted WordPress Core Files

Download a fresh copy of WordPress from wordpress.org
Extract the zip file
Delete the wp-admin and wp-includes folders from the fresh download, keeping everything else
Upload the remaining files via File Manager into public_html, overwriting the existing ones
This replaces corrupted core files without touching your content, plugins, or theme
Refresh your site

Fix 6: Syntax Error in Code

If the code is in functions.php:

Go to File Manager → public_html → wp-content → themes → your active theme
Open functions.php for editing
Find any code you recently added
Remove it carefully
Save and refresh

If you used a code snippet plugin:

Rename the plugins folder as described in Fix 1 to deactivate it
Your site should load again
Reactivate the plugin carefully and remove the specific snippet that caused the issue

What to Do If Nothing Works

If you’ve worked through the causes above and you’re still stuck, you have a few solid options left.

Option 1: Restore from backup. In Hostinger hPanel, go to Backups and restore to your last working version. This is the most reliable fix when the exact cause is unclear.

Option 2: Contact hosting support. Hostinger offers 24/7 live chat. Tell them your WordPress site is showing a white screen and give them your domain name — they have server-level access that can catch issues you can’t see from the dashboard. This is often the fastest route for deeper, server-side problems.

Option 3: Hire a WordPress developer. For complicated database-level issues, platforms like Upwork or Fiverr can connect you with affordable help. Describe the issue clearly, and it’s usually resolved within hours.

One more thing worth repeating: never delete your entire WordPress installation before trying every fix above. Your database, where your actual content lives, is separate from your WordPress files. Even a complete WordPress reinstall does not touch your content.

While you’re thinking about site stability, it’s also worth looking at your best WordPress security plugins setup, since some security tools can interact with the same files involved in a white screen.

How to Prevent the White Screen of Death

Prevention is always easier than the cure.

Always back up before major changes. Before updating plugins, themes, or WordPress core and before adding custom code, back up first. UpdraftPlus is a solid free plugin for this, and Hostinger’s automatic backups add another layer of protection.

Update plugins carefully. Don’t update everything at once. Update one plugin at a time, check your site after each update, and read the changelog beforehand. If something breaks, you’ll know exactly which update caused it.

Use a staging site for testing. Test changes on staging before pushing them live. Hostinger’s business plan includes staging, which lets you confirm plugin and theme updates work before your visitors ever see them.

Keep PHP updated. Outdated PHP versions carry more vulnerabilities. Check hPanel → PHP Configuration and aim to keep PHP at 8.1 or 8.2 minimum after confirming your plugins are compatible.

Use quality plugins only. Check for 4+ star ratings, confirm the plugin was updated within the last year, and verify WordPress compatibility. Fewer, better plugins mean fewer conflicts, quality over quantity, every time.

Choose reliable hosting. Good hosting means better server stability and adequate memory limits from the start. This is honestly one of the biggest factors in preventing server-level causes of WSOD. I use Hostinger’s Premium plan for The Income Plug, and it’s given me a solid, stable foundation to build on.

For more on tightening up your site’s technical setup, take a look at Rank Math vs Yoast SEO to make sure your SEO plugin choice isn’t adding unnecessary weight either.

Frequently Asked Questions

Will I lose my content if I get the white screen of death? No. The white screen is a display error caused by a PHP fatal error, not a data loss event. Your posts, pages, images, and settings live in your database, which is separate from the files causing the crash. Even a full WordPress core reinstall won’t touch that content.

How long does the white screen of death take to fix? Most cases resolve in 5 to 30 minutes once you’ve identified the cause. Plugin and theme conflicts, the most common causes, are usually the fastest to fix, often within 10 minutes of enabling debug mode.

Can bad hosting cause WordPress white screen of death? Yes. Low memory limits, outdated PHP versions, and unstable servers are all hosting-related factors that can trigger a white screen. This is why choosing reliable hosting with adequate resources matters; it removes an entire category of potential causes before they happen.

What’s the difference between white screen and a 500 error? A white screen shows nothing at all, no message, just blank. A 500 internal server error shows an actual error page with that message displayed. Both can stem from similar causes, like plugin conflicts or memory issues, but a 500 error at least tells you something went wrong immediately, while WSOD requires you to enable debug mode to see anything.

Can I fix white screen without FTP or file manager access? If you can still access your WordPress dashboard, yes, deactivating plugins and switching themes through the dashboard doesn’t require FTP or File Manager. If your dashboard is also white, File Manager access through your hosting panel becomes necessary for most fixes.

Why does white screen happen after a WordPress update? This usually points to either a plugin or theme that hasn’t been updated to work with the new WordPress version or a failed update that left core files incomplete. Enabling debug mode right after an update will typically show you which one it is.

How do I know which plugin caused the white screen? Enable WP_DEBUG and refresh your site; the error message will often name the exact plugin folder involved. If it doesn’t, deactivating all plugins and reactivating them one by one, checking your site after each one, will isolate the culprit.

Final Thoughts

The WordPress white screen of death sounds terrifying, but in practice, it rarely is. In most cases, you’re dealing with a plugin or theme conflict, and it’s fixed in under 15 minutes once you know where to look.

The systematic approach is what makes the difference: diagnose first, then fix. Debug mode exists specifically to tell you what’s wrong, so use it before you try anything else. And prevention, as always, is far simpler than the cure.

As a WordPress designer, the biggest thing I can tell you is this: stay calm, work through the causes systematically, and never randomly delete things out of panic. Back up before any major change, and choose hosting that gives you a stable foundation from the start.

Bookmark this guide now, before you ever need it. The worst time to search for a fix is while you’re panicking over a blank screen. Having these steps ready means you’ll handle it with confidence when it eventually happens.

Have you experienced the white screen of death on your own site? Drop a comment below and let me know what caused yours.

If you’re working on speeding up your site in general, I’ve also put together a guide on how to speed up WordPress, and if security is on your mind after reading this, check out my best WordPress security plugins roundup.

How to fix WordPress white screen of death

What Is the WordPress White Screen of Death?

Before You Start: Essential Preparation

The Most Common Causes (Know Yours Before Fixing)

How to Diagnose Your Specific Cause

Enable WordPress debug mode via File Manager: