WordPress White Screen of Death

WordPress Errors

A blank page that refuses to say what went wrong.

datacram.com/fix/wordpress-white-screen-of-death
Likely causes, ranked
WordPress White Screen of Death
A plugin fatal errormost likely
A theme errorcommon
Exhausted PHP memorycommon
A PHP version changepossible
Fix steps in this guide5
the causes explained below, most likely first
What you’re seeing

Nothing. A completely white page — no design, no error message, no status code you can see. Sometimes the front end is white and the admin still works, sometimes both are gone.

What it actually means

PHP hit a fatal error and stopped mid-page. Because production sites are configured not to display errors to visitors, there is nothing left to show — the script died before it printed anything, and you get the empty page that remained.

So the white screen is not a specific fault. It is the absence of a message about one. Every minute spent guessing is wasted; the entire job is persuading WordPress to tell you what it already knows.

Which parts are white narrows it fast. Front end white but admin fine points at the theme. Both white points at a plugin or core. One admin page white points at whatever runs on that screen.

What usually causes it

Most likely first.

  1. 1

    A plugin fatal error

    The most common cause by a wide margin. An update called a function that no longer exists, or two plugins collided.

  2. 2

    A theme error

    Usually after a theme update or an edit to functions.php. A stray character in that file is enough to blank the whole site.

  3. 3

    Exhausted PHP memory

    The script ran out of memory and was killed. Often shows up on one heavy page — an import, a media library, a builder screen.

  4. 4

    A PHP version change

    The host upgraded PHP and code written for an older version no longer parses. Common on older sites and abandoned plugins.

  5. 5

    Corrupted core files

    An interrupted update or a failed migration leaving WordPress itself incomplete.

How to fix it

Work through these in order. Take a backup before you change anything.

  1. Step 1Turn on error logging first

    In wp-config.php set WP_DEBUG and WP_DEBUG_LOG to true, and WP_DEBUG_DISPLAY to false. Reload, then read wp-content/debug.log. The fatal error is named there with a file and line number. Do this before changing anything else.

  2. Step 2Check Recovery Mode email

    Modern WordPress emails the admin address with a recovery link when a plugin or theme causes a fatal error. That email often names the culprit outright.

  3. Step 3Disable all plugins at once

    Over SFTP, rename wp-content/plugins to plugins-off. If the site returns, rename it back and re-enable plugins one at a time until the white screen reappears.

  4. Step 4Switch to a default theme

    If plugins are not the cause, rename your theme's folder. WordPress falls back to a default theme, which isolates the fault to your theme's code.

  5. Step 5Raise the memory limit

    Add a memory limit of 256M in wp-config.php. If the white screen only affects one heavy page, this is frequently the whole fix.

When to stop and call someone

Call someone if the debug log points at WordPress core rather than a plugin or theme, if the site is a store losing orders, or if you have no SFTP access and are locked out of the admin — that combination leaves you with no way in without help.

Frequently asked

It is a completely blank page shown when PHP hits a fatal error and production settings suppress the error message. Nothing is displayed because the script stopped before rendering anything. The cause is recorded in the error log, not on the page.

Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php, keeping WP_DEBUG_DISPLAY off so visitors never see errors. Reload the page, then read wp-content/debug.log — the fatal error is named there with the exact file and line responsible.

That split almost always points at the theme, since the admin does not load your theme's front-end templates. Renaming the theme folder forces WordPress onto a default theme and confirms it within a minute.

Connect over SFTP and rename wp-content/plugins to something else. WordPress cannot find them, so all plugins deactivate at once. Rename the folder back and re-enable them individually to identify the one at fault.

No. Your posts, pages, and settings live in the database, and none of these steps touch it. Disabling plugins, switching themes, and reading logs are all reversible and leave your content untouched.

Free · AI-powered · Emailed to you

See exactly what’s holding your website back.

Get a free audit of your site — speed, SEO, mobile, and security — with the fixes that matter most, delivered as a PDF to your inbox.

Get my free audit
CallGet a quote