WordPress White Screen of Death: Fix It Fast (2026)

Quick Answer: The WordPress white screen of death is a completely blank page with no error text, almost always caused by a PHP memory limit, a plugin or theme conflict, or a corrupted .htaccess file. The fastest fix is to rename your /wp-content/plugins/ folder over FTP, which disables every plugin at once. If the site returns, reactivate plugins one at a time to find the culprit.

Quick Fix (try this first): Log in over FTP or your host's file manager, open /wp-content/, and rename the plugins folder to plugins-off. Reload your site. Page comes back? A plugin broke it. Rename the folder back to plugins, then deactivate plugins one by one until the white screen returns — that's your guilty plugin.

You loaded your site and got nothing. No error, no theme, no logo — just a flat white page staring back at you. That's the WordPress white screen of death, and the panic is real. But the fix usually takes under ten minutes once you know where to look, and your content is almost certainly fine.

We run the servers behind a lot of WordPress sites, so at Hostaccent this error lands in our support inbox most weeks. Here's the reassuring part: in the tickets our team handles, roughly 4 out of 5 white-screen cases trace back to just two causes — a misbehaving plugin or an exhausted PHP memory limit. Both are fixable without touching a single line of code you don't understand.

This guide ranks the causes by how often they actually happen, then gives you the exact file paths and steps for each. Work top to bottom and stop when your site comes back.

What the WordPress White Screen of Death Actually Means

A blank white page means PHP hit a fatal error and stopped executing before it could send any HTML to your browser. WordPress runs on PHP, so when the code crashes hard, there's literally nothing left to display — hence the empty screen.

Older WordPress versions hid the error completely. Newer ones (since the fatal error protection feature shipped) sometimes show "There has been a critical error on this website" instead, occasionally with an email to your admin address. A true blank page usually means error display is switched off on your server, which is the safe default for a live site.

Behind the scenes, the server is often returning an HTTP 500 status code — a generic "something broke" signal. The white screen is just what a 500 looks like when no error message is allowed through.

The important thing: a white screen is a display failure, not a data loss. Your posts, pages, images, and database are still sitting safely in MySQL. You're fixing the engine, not rebuilding the car.

Pro Tip: Before you change anything, note exactly what you did last — installed a plugin, ran an update, edited a theme file, switched PHP version. The action right before the screen went white is your number-one suspect, and it'll save you twenty minutes of guessing.

What Causes a WordPress Blank Page (Ranked by Frequency)

Most guides throw ten possible causes at you in no order. That's not helpful at 2 a.m. Here's how they actually break down, based on the support patterns we see day to day:

| Cause | How often we see it | Typical trigger | |---|---|---| | Plugin conflict or bad plugin | Most common | New plugin, plugin update, two plugins clashing | | PHP memory exhaustion | Very common | Heavy plugin, large import, low memory_limit | | Theme error | Common | Theme update, edited theme file, bad child theme | | Corrupted .htaccess | Occasional | Permalink change, plugin write, manual edit | | Failed core/PHP update | Occasional | WordPress or PHP version jump | | File permissions / disk full | Rarer | Migration, server move, full quota |

Notice nothing here says "you got hacked." A white screen is overwhelmingly a code or resource problem, not a security breach. If you're worried about that separately, run a scan — but fix the blank page first.

How to Fix the WordPress White Screen of Death: Step by Step

Go through these in order. Each one is independent, so if step 1 doesn't bring your site back, move to step 2.

1. Disable all plugins at once

This is the single highest-yield fix. If you can still reach /wp-admin, go to Plugins → Installed Plugins, select all, and choose "Deactivate."

No admin access? Use FTP or your control panel's file manager:

1. Navigate to /wp-content/.
2. Rename the plugins folder to plugins-off.
3. Reload your site.

If the page loads, a plugin is the cause. Rename the folder back to plugins (this re-lists them, all deactivated), then reactivate them one at a time, refreshing your site after each. The plugin that brings the white screen back is your culprit — delete or replace it.

2. Increase the PHP memory limit

If plugins aren't it, you've probably hit the wall on memory. WordPress needs at least 64MB to run, but a real-world site with a page builder and WooCommerce often needs 256MB or more. The default on cheap shared hosting is sometimes still 128M, which a heavy theme can blow through in seconds.

Edit wp-config.php (in your site root) and add this line just above the /* That's all, stop editing! */ comment:

bashCopy
define('WP_MEMORY_LIMIT', '256M');

If that doesn't hold, the cap is set at the server level. You can raise PHP's memory_limit in php.ini or a .user.ini file:

bashCopy
memory_limit = 256M

On managed plans, support can bump this in seconds. On our Nginx → Apache and NVMe SSD stack, we set generous PHP memory headroom by default precisely because memory-exhaustion white screens are so common — it's cheaper to prevent than to debug.

Insider Insight: A site that goes white only on the editor or a specific heavy page (not the whole front end) is almost always a memory problem, not a plugin one. That single clue lets you skip straight to step 2.

3. Switch to a default theme

A broken theme — usually after an update or a botched edit to functions.php — produces a clean white screen too.

Rename your active theme's folder under /wp-content/themes/ (for example astra to astra-off). WordPress falls back to a default theme like Twenty Twenty-Four if it's installed. If your site reappears, the theme was the problem. Restore from a backup of that theme or reinstall a fresh copy — never edit core theme files directly without a child theme.

4. Regenerate the .htaccess file

A corrupted .htaccess (often after a permalink change or a plugin writing rewrite rules) can take the whole site down.

Rename the existing .htaccess in your site root to .htaccess-old. Reload the site. If it works, log into /wp-admin, go to Settings → Permalinks, and click "Save Changes" — WordPress writes a fresh, clean file automatically. The rules WordPress generates follow the standard Apache documentation, so a regenerated file is almost always correct.

5. Turn on WP_DEBUG to see the real error

Still stuck? Stop guessing and make WordPress tell you what's wrong. Open wp-config.php and set:

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

Reload your site. The error now logs to /wp-content/debug.log. Open that file and read the last few lines — it'll name the exact file and line number, usually pointing at a specific plugin or theme. The official WordPress debugging documentation explains each constant if you want the full detail. Switch WP_DEBUG back to false once you're done — never leave debug display on for a live site.

6. Check file permissions and disk space

Less common, but worth a 60-second check. Folders should be 755 and files 644. Wrong permissions after a migration can block PHP from reading files, producing a blank page.

Also confirm you're not out of disk space — a full quota stops WordPress from writing sessions and cache, and the symptom is often a silent white screen. Your control panel shows usage at a glance.

7. Roll back a bad core or PHP update

If the screen went white right after a PHP version jump (say 7.4 to 8.2) or a WordPress core update, an old plugin may be incompatible with the new version. Switch PHP back to the previous version in your control panel as a temporary measure, get the site live, then update the offending plugin before moving forward again.

How to Tell Which Fix You Actually Need

Don't run all seven steps blindly. Use this shortcut:

• The whole front end is white → start with plugins (step 1), then memory (step 2).
• Only the admin or a specific heavy page is white → memory limit (step 2).
• It broke right after a theme update or edit → theme (step 3).
• It broke right after changing permalinks → .htaccess (step 4).
• It broke right after a core or PHP update → debug log first (step 5), then roll back (step 7).
• No idea what changed → enable WP_DEBUG (step 5) and let the log tell you.

If you've worked through all of this and the site is still down — or it keeps coming back — the problem may be lower in the stack. Our WordPress Site Slow: Complete Diagnosis and Fix Guide (2026) and our breakdown of how to fix high TTFB in WordPress cover the server-side causes that a plugin swap won't touch.

How to Confirm the Fix and Stop It Coming Back

Once your site loads, don't just walk away. Confirm it properly:

1. Hard-refresh your browser and clear any caching plugin or CDN cache. A cached white page can fool you into thinking the fix failed when it actually worked. (Here's a plain-English explainer on what a CDN cache does if that's new to you.)
2. Visit the front page, a post, an admin page, and the editor — the white screen sometimes hides on just one of these.
3. Re-check wp-config.php and make sure WP_DEBUG is back to false.

Then prevent the repeat:

• Keep memory headroom. Set WP_MEMORY_LIMIT to 256M and don't run a dozen heavy plugins on a 128M cap.
• Update on a staging site first. Test plugin and core updates somewhere safe before they touch your live site.
• Take backups before every change. A 30-second restore beats an hour of debugging.
• Stay on a current, supported PHP version (PHP 8.2 or 8.3 as of 2026) and keep plugins updated to match.

Pro Tip: Schedule plugin and theme updates for a low-traffic window — and never run them all at once. Update one, check the site, move to the next. If a white screen appears, you instantly know which update caused it. This one habit prevents most repeat incidents we see.

When a Blank Page Is Really a Hosting Problem

Here's the honest part most articles skip: sometimes you do everything right and the white screen keeps returning. When we migrate customer sites onto our stack, we repeatedly see the same root cause — a previous host with a low PHP memory ceiling, slow shared CPU, or aggressive process limits that kill PHP mid-request. No amount of plugin juggling fixes a server that's starving your site of resources.

The tell is a white screen that comes back under traffic, during a backup, or whenever the site gets busy — that's resource exhaustion, not code. If that sounds like your situation, the fix is infrastructure, not plugins. Our guide to the best hosting for high traffic WordPress sites in 2026 walks through exactly what to look for, and if you're seeing related timeouts, our 504 gateway timeout fix guide covers that cousin of the white screen.

Get WordPress Hosting Built to Prevent This

If you'd rather not babysit memory limits and PHP versions yourself, that's exactly what managed hosting is for. Hostaccent's WordPress Hosting runs on a Cloudflare → Nginx → Apache stack with NVMe SSD storage and generous PHP memory headroom set by default — the configuration that quietly prevents most white-screen incidents before they happen. The Basic plan starts at $22.99/yr, includes UK-based human support that can raise a memory limit or roll back a PHP version in minutes, and comes with the staging and backup tools that turn a scary white screen into a one-click restore. One honest caveat: if your site is genuinely huge or runs custom server software, you may outgrow a shared WordPress plan and want a VPS instead — we'll tell you straight if that's you. For most WordPress owners, though, reliable hosting is the cheapest insurance against ever seeing the WordPress white screen of death again. If your current site is just sluggish rather than down, start with our guide to diagnosing a slow WordPress site in 30 minutes.

Three takeaways to leave with:

• The WordPress white screen of death is a PHP crash, not data loss — your content is safe.
• 80% of cases are a plugin conflict or a low PHP memory limit; check those two first.
• Enable WP_DEBUG when you're stuck, and prevent repeats with staging, backups, and proper memory headroom.

Frequently Asked Questions

What is the WordPress white screen of death?

It's a completely blank white page shown when PHP hits a fatal error and stops before sending any HTML. WordPress runs on PHP, so a hard crash leaves nothing to display. It usually points to a plugin conflict, an exhausted memory limit, a theme error, or a corrupted .htaccess file — not a hack or data loss.

How do I fix a WordPress white screen with no admin access?

Use FTP or your host's file manager. Rename /wp-content/plugins/ to plugins-off to disable every plugin at once. If the site returns, a plugin was the cause. If not, try renaming your active theme folder, then regenerating .htaccess. These file-level fixes work even when /wp-admin is unreachable.

Why does my WordPress site go white after an update?

An update changed something a plugin or theme depended on. A plugin update can clash with another plugin; a core or PHP version jump can break an outdated plugin. Enable WP_DEBUG, read /wp-content/debug.log to find the exact file, then update or remove the incompatible component.

Does the white screen of death mean I lost my data?

No. A white screen is a display failure, not data loss. Your posts, pages, media, and settings stay safe in the MySQL database and the file system. You're fixing the code that renders the site, not the content itself — once the crash is resolved, everything reappears exactly as it was.

How much PHP memory does WordPress need?

WordPress runs on 64MB minimum, but a real site with a page builder, WooCommerce, or many plugins usually needs 256MB or more. Set WP_MEMORY_LIMIT to 256M in wp-config.php; if that's ignored, the cap is server-side and needs raising in php.ini or by your host.

Can bad hosting cause the white screen of death?

Yes. A low server-side memory limit, strict process caps, or starved CPU can crash PHP under load, producing repeat white screens no plugin swap will fix. A managed setup like Hostaccent's, with generous memory headroom on an NVMe stack, removes that whole category of cause — the screen that returns under traffic is almost always a resource problem.

Written and reviewed by The Hostaccent Team — Hostaccent Limited, a UK-registered host running WordPress infrastructure for customers worldwide. Last updated 2026.