White Screen of Death on WordPress: What to Do Now

VenbitThe Venbit TeamJuly 24, 20264 min read

The short answer

The WordPress white screen of death is a blank page with no error message, and it's almost always caused by a plugin conflict, a theme error, or your site running out of PHP memory. The fastest fixes are deactivating plugins, switching to a default theme, and raising the memory limit. Turning on debug mode reveals the exact culprit.

Key takeaways

  • A blank white page usually means a fatal PHP error, not a lost site.
  • Plugin conflicts and bad updates are the most common cause.
  • You can deactivate plugins by FTP even when the admin won't load.
  • Turning on WP_DEBUG shows the real error behind the blank screen.
  • Restoring a recent backup is the cleanest fix when you have one.

The white screen of death is a totally blank page where your WordPress site or dashboard should be, with no error message to explain it. It looks alarming, but it usually means one specific thing: a fatal PHP error stopped the page from finishing. The cause is almost always a plugin conflict, a theme problem, or your site hitting its memory limit. Your content is still there. You just need to clear whatever is choking the page.

CauseHow commonThe tell
Plugin conflict or bad updateMost commonIt went blank right after updating or activating a plugin
Theme errorCommonStarted after a theme update or edit; only some pages are blank
PHP memory limit exhaustedCommonBlank on heavy pages; error log mentions 'allowed memory size'
Corrupted core file or bad code editOccasionalFollowed a manual edit to a .php file or a failed update
What's behind a WordPress white screen

If you can, take a backup of your files and database before you start. If the site is too broken to back up through a plugin, your host can often make a snapshot from their control panel. Then work through the fixes below in order.

Turn on debug mode to see the real error

The blank screen hides the actual error, so the smartest first move is to reveal it. Using your host's file manager or FTP, open wp-config.php and change the line define('WP_DEBUG', false); to true. Reload the page and, instead of a blank screen, you'll usually see the exact file and line causing the problem, often naming a specific plugin or theme. That tells you precisely where to aim. Set WP_DEBUG back to false when you're done, since you don't want errors showing to visitors.

Deactivate your plugins

Because plugins are the usual culprit, this is the highest-odds fix. If you can still reach your dashboard, deactivate all plugins at once, then reactivate them one by one, reloading the site after each, until the white screen returns. The last one you turned on is the offender.

If the dashboard itself is blank, you can still do this by FTP or your host's file manager. Find the folder wp-content/plugins and rename it to something like plugins-off. That deactivates every plugin at once. If your site comes back, rename it back to plugins, then disable each plugin individually inside the folder to isolate the bad one. It's the same idea that helps when the whole site is down: undo the last thing that changed.

Switch to a default theme

If disabling plugins didn't help, suspect the theme. In your dashboard, switch to a default WordPress theme like Twenty Twenty-Four. No dashboard access? By FTP, rename your active theme's folder inside wp-content/themes. WordPress will fall back to a default theme automatically. If the site returns, your theme, or a recent edit to it, was the problem, and it needs a fix or a fresh copy.

Raise the PHP memory limit

If the debug log mentioned "allowed memory size exhausted," your site ran out of memory. In wp-config.php, add this line above the "stop editing" comment: define('WP_MEMORY_LIMIT', '256M'); That raises the ceiling. Some hosts cap memory at the server level, so if this doesn't stick, ask your host to increase the PHP memory limit for your account. A site that regularly hits its memory limit is often carrying too many heavy plugins, which is worth trimming.

The point where you should call for backup

Editing wp-config.php, renaming folders, and toggling plugins are all reasonable for a careful owner, and they solve most white screens. But if debug mode points at a core file, or you've worked through all of the above and the screen is still blank, you may be looking at corrupted WordPress files, a bad code edit, or a deeper server issue. Editing core PHP without knowing what you're doing can turn a recoverable problem into a rebuild. If you have a recent backup, restoring it is the clean way out. If not, that's the moment to get a developer involved.

How we stop the white screen before it happens

Almost every white screen we get called about traces back to an untested update. On our maintenance plans, starting at $99 a month, we test plugin and theme updates on a staging copy before they ever touch your live site, so a bad update gets caught in a safe environment instead of on your homepage. We also keep off-site backups, which turn a fatal error into a quick restore rather than a crisis. We're a Seattle-area studio that's been doing this since 2011, and we handle fixes within one business day.

More website answers

Every question in this series, from Website Problems, Solved.

Symptoms & emergencies19
What happens if...9
Cost & pricing7
Plans & hiring10
Ownership & switching9
Platform-specific7
Seattle & local2
Venbit

The Venbit Team

Web design & SEO, Seattle

Venbit is a Seattle-area web design, SEO, and digital marketing studio. Since 2011 we've designed, built, and ranked small-business websites for clients across the Puget Sound and around the country, so the numbers and advice here come from real projects, not a content mill.

Common questions

Questions, answered straight.

Straight answers about website fixes for your business. If yours isn't here, ask us directly and we'll give it to you straight.

Ask the team

Almost certainly not. The white screen is a page that failed to finish rendering because of a fatal error, not a sign your content was deleted. Your posts, pages, images, and settings are still safely in your database and files. Once you clear the error causing the blank page, everything reappears exactly as it was.

Use FTP or your host's file manager, which work independently of the WordPress admin. From there you can rename the plugins folder to deactivate all plugins, rename your theme folder to force a default theme, or turn on debug mode in wp-config.php to see the real error. Those file-level actions let you fix the site without ever reaching the dashboard.

When some pages load and others are blank, the error is usually tied to something specific to the broken pages, often a theme template or a plugin that only runs on certain pages, like the admin area or a single post type. Turning on debug mode on a blank page will point you to the exact file responsible.

Indirectly, yes. Each active plugin uses memory, and a site loaded with heavy plugins can exhaust its PHP memory limit and go blank, especially on cheaper hosting. Raising the memory limit helps in the short term, but trimming plugins you don't need is the healthier long-term fix and reduces the chance of conflicts too.

Free 30-minute strategy call

Let's talk about your project.

Tell us what you need and we'll give you an honest read on the project, the timeline, and what it takes, before you spend a dollar. Based in Seattle, working across the Puget Sound.

4.8 on Google 5.0 on Yelp