Skip to content

Home  /  Blog  /  Repairs and errors

WordPress White Screen of Death: 7 Causes and How to Diagnose Them

The WordPress white screen of death is a blank page caused when a fatal error stops WordPress finishing its work. The usual causes are a plugin or theme fault, a PHP memory limit, an incompatible PHP version, a corrupted file or a server problem. Your content is almost always still safe in the database.

6 min readRepairs and errorsWritten by WP Mate, Warrnambool VIC
WP Mate koala mascot beside a laptop, representing Australian WordPress support
01

Why a blank screen happens

WordPress builds each page by running PHP code from the core software, your theme and your plugins. If any of that code produces an error it cannot recover from, the page stops being built. When error display is switched off, which is normal on a live site, the visitor sees nothing at all, hence the white screen.

02

Seven common causes

  • A plugin fault. Often straight after an update or a new install.
  • A theme fault. Especially after editing theme files or updating a customised theme.
  • PHP memory exhausted. A heavy page, import or plugin runs past the limit.
  • PHP version mismatch. The host upgrades PHP and older code stops working.
  • A corrupted or incomplete update. Files are partly written or missing.
  • A broken .htaccess or server rule. The server cannot route the request.
  • A hosting or database fault. The environment, not WordPress, is failing.

Not sure what is going on with your website?

Tell us what you are seeing and we will outline the next step before any chargeable work.

03

Reading the pattern

What you seeWhat it suggests
Whole site blank, dashboard blankA fatal error in core, the theme or a plugin that loads everywhere
Public pages blank, dashboard worksA theme or front-end plugin problem
Dashboard blank, public pages workAn admin-side plugin or memory issue
One page blankA shortcode, page builder block or plugin used only on that page
Critical error message instead of blankWordPress caught the error; check the admin email for details
04

Diagnosing without guessing

The reliable route is the error log. It records the file and line where PHP stopped. Reading it points directly at the failing plugin or theme, which can then be tested in isolation. Turning on debug logging temporarily, from a backup, is a standard technique used by developers.

05

What to avoid

  • Do not restore an old backup over the only working copy until you know what would be lost
  • Do not delete plugin folders at random on a live website
  • Do not leave debug output switched on for visitors to see
  • Do not email passwords to get help
06

A closer look at memory limits

PHP gives each request a memory allowance. Heavy plugins, large image processing, big imports and complicated page builders can all exceed it, and when they do, PHP stops and WordPress shows a blank page. Raising the limit is a legitimate fix when a site simply needs more, but it can also mask a plugin that is leaking memory or running far more work than it should. Good diagnosis asks what consumed the memory, not only how to give it more.

07

Updates that never finished

If an update stalls partway, WordPress core, a plugin or a theme can be left with a mixture of old and new files. The mismatch can cause a fatal error on the next page load. Completing or repairing the update, from a backup, restores consistency. This is one reason updates should be applied one at a time, with a way back, and not by clicking update on everything while the host is under load.

08

Recovery mode and staging

Modern WordPress can email an administrator a recovery mode link when it detects a fatal error, which lets you log in and deactivate the problem plugin without editing files. For anything riskier, a staging copy lets a developer reproduce the issue, test a fix and apply it to the live site only once proven. If you would rather hand this over, see our white screen fix service.

09

Why content is usually still safe

Because the white screen is a display failure, your posts, pages, products and users normally remain untouched in the database. That is reassuring, but it also means the recovery should avoid anything that rewrites data unnecessarily. Replacing a failing plugin file, or switching to a default theme for diagnosis, leaves content alone. Restoring a database from an old backup, by contrast, rewrites everything and can erase recent work. Understanding the difference keeps a frightening problem in proportion and guides you toward the least risky fix.

10

Handling a white screen on a busy website

If the site takes orders or enquiries, the priority is to stop the loss while the diagnosis continues. Consider a temporary holding page or pausing paid traffic, record when the problem began so you know which orders might be affected, and keep a copy of the current state. Then work through the cause with logs, not guesses. For websites that cannot afford downtime, planned updates on a staging copy, uptime monitoring and tested backups are the realistic protection. Our urgent WordPress support service exists for exactly this situation.

11

How professionals diagnose it

A developer typically starts by checking the error logs for the most recent fatal error, then reviews what changed in the hours before the failure: updates, edits or hosting changes. Next they confirm the PHP version and memory settings, then isolate the failing component on a copy, by switching to a default theme and disabling suspect plugins in sequence. Once the cause is identified, they repair or replace it, test the site and document what happened. The process is methodical rather than clever, and that is exactly why it works. Clear notes also make recurrence easier to handle.

12

Fixing it properly

A proper fix identifies the component, repairs or replaces it, tests the website and explains the cause. If this is happening now, see our white screen fix service, or urgent WordPress support if enquiries or orders are being lost.

Want this looked after for you?

WP Mate maintenance plans cover managed updates, daily offsite backups, security scanning and 24/7 uptime monitoring.

Staring at a blank screen? We can help get it back.

How we can help

Services related to this guide

White screen fix

Blank page? We find the cause and restore the site.Get White Screen Help →

WordPress repair

Broken website? We investigate the cause and fix it safely.Get a Repair Quote →

Talk to WP Mate

Not sure which service fits? Ask us and we will point you the right way.Contact us →

Frequently asked questions

Almost never. The content lives in the database. The white screen means WordPress cannot display it, not that it has been deleted.

An admin-side plugin, a memory limit or a theme function used in the dashboard is usually responsible.

Yes. Resource limits, PHP version changes and server faults can all produce it.

Ready to get your website sorted?

Based in Warrnambool, Victoria, helping Australian businesses online. Tell us what is happening.

Get WordPress help

Tell your mate what's going wrong.

Send us a few details and we’ll work out the next step. Please don’t include passwords or payment details.

  • Australian support in plain English
  • Clear scope and next steps before chargeable work
  • Backup and recovery plan before live changes

Please don't include passwords, payment card numbers or private customer data. If we need access, we'll arrange a secure way to share it.