Black Friday: Kinsta 50% off for 3 months · WPX first month $1.80 · InMotion up to 73% off — See the 4 hosting deals →
WORDPRESS GUIDE

WordPress white screen of death: how to fix it in 2026

A blank WordPress page means a PHP fatal error with the error message hidden. This guide finds the real error — Recovery Mode, the debug log, plugins, theme, memory — and fixes it in order, from the five-minute checks to reinstalling the core files.

Published November 19, 202626 min readBy Sharjeel Tahir
WordPress white screen of death: a blank browser window with a warning sign

What the white screen of death actually is

You open your WordPress site and get nothing. No error message, no broken layout, no half-loaded page — just a blank white browser window. The admin area may be blank too, or it may load fine while the front of the site shows nothing. Either way, the site is down, and WordPress is not telling you why.

The white screen of death is not a specific error. It is what a PHP fatal error looks like when the error message is hidden. WordPress runs on PHP, and every page load executes PHP code from the WordPress core, the active theme and every active plugin. When one of those files hits a problem PHP cannot recover from — a call to a function that does not exist, a file that cannot be found, a memory limit that has run out — PHP stops executing the page on the spot. If nothing has been sent to the browser yet, the visitor sees a blank page.

The reason you see white instead of an error is a server setting. On most production hosts, PHP is configured not to display errors on the page, because error messages can leak file paths and code details to anyone who triggers them. WordPress's own debugging documentation describes the same behaviour: with errors off, hitting a fatal error gives you a white screen.

Since WordPress 5.2, WordPress catches many fatal errors itself and shows visitors "There has been a critical error on this website" instead of a blank page, and emails the site administrator a Recovery Mode link. A truly blank page still happens when an error occurs before that safety net loads, or a caching plugin serves a blank page stored during the failure. Either way, the fix is the same: make the hidden error visible, read it, and remove the cause.

The most common causes are a faulty plugin (usually right after an update), a faulty theme (after an update or a bad edit), an exhausted PHP memory limit, a PHP version a theme or plugin no longer supports, and damaged core files after a failed update. A database problem can also produce a blank page, though WordPress usually shows its own database-connection error for that instead.

The good news is that the white screen almost never means your content is gone. Posts, pages, images and settings live in the database and the uploads folder, and a PHP error does not touch them. The fix is about code, not content. Most white screens are fixed by disabling one plugin or one theme, and this guide works through the fixes in that order.

First, work out which screen you are seeing

Before changing anything, establish exactly what is broken, because the answer decides which fix to try first. Open the front page in a private browser window — this rules out your own browser cache showing a stale blank page — then try the admin area at yoursite.com/wp-admin.

There are four situations, and each points somewhere different. If the front of the site is blank but wp-admin loads normally, the problem is almost certainly a plugin or the theme, and you can fix it from the dashboard without touching any files. If wp-admin is blank too, the fault is deeper — a plugin that loads in the admin area, the theme, the memory limit, or the core files — and you will need file access through your host's file manager or FTP. If the front page shows "There has been a critical error on this website" instead of a blank page, WordPress caught the error for you, and the Recovery Mode email described in the next section is the fastest way back in. And if the site shows "Briefly unavailable for scheduled maintenance. Check back in a minute." for more than a few minutes, that is a different problem with a one-minute fix, covered in the section on the stuck .maintenance file.

Also note when the white screen started, because the timing usually names the culprit: right after a plugin update points at that plugin, after a theme change points at the theme, after editing a file — functions.php is the usual suspect — points at that edit, and with no change made at all points at the host, such as a PHP version change or a memory limit the site has outgrown. Write down what changed most recently; you will need it in the next steps.

One more check: try a second page, such as a single post or yoursite.com/wp-login.php. If the homepage is blank but a single post loads, the problem is likely in the homepage template or a widget there; if every page is blank, the fault is in something that loads on every page — a plugin, the theme, or the core files.

Before you change anything: back up the site

Every fix in this guide changes files or settings, and every change carries a small risk of making things worse. So the first step, before any troubleshooting, is a backup — even though the site is down. A backup is your undo button: if a fix goes wrong, you restore the backup and you are back where you started instead of further down the hole.

If wp-admin still loads, take the backup from the dashboard: a backup plugin such as UpdraftPlus can create a full backup — database plus files — and send it to remote storage such as Google Drive. If wp-admin is blank too, use your host's file manager or control panel: most hosts offer a one-click backup, or you can download the files and export the database yourself. Our WordPress backup guide walks through both routes, including restoring a backup when the dashboard is unreachable.

At minimum, before editing any file, download a copy of that file first. Editing wp-config.php without a copy of the original is how a five-minute fix turns into a lost afternoon: one wrong character in that file takes the whole site down, and without the original you have nothing to restore. The same applies to the theme's functions.php and to .htaccess. Download first, edit second, every time.

If you cannot back up at all — no dashboard, no file manager access — stop and contact your host before changing anything. A host can usually take a snapshot or restore a server-side backup, which is far safer than editing files blind.

Fix 1: Use the Recovery Mode email

The fastest fix, when it is available, takes five minutes and needs no file access at all. When WordPress catches a fatal error, it sends an email to the site's administrator address — the address set under Settings, then General — with the subject line "[Your Site Name] Your Site is Experiencing a Technical Issue". The email names the plugin or theme WordPress believes caused the error, includes the error itself, and contains a special link that opens the dashboard in Recovery Mode.

Check that inbox first, including the spam folder — the email usually arrives within minutes of the error and is easy to miss. Click the Recovery Mode link and log in as normal: you will land in the dashboard with a notice saying which plugin or theme is paused and what the error was. The pause applies only to your session, but inside Recovery Mode you can deactivate the named plugin from the Plugins screen, or switch away from the named theme from Appearance, then Themes.

Once the faulty plugin or theme is deactivated, click "Exit Recovery Mode" in the admin bar at the top, then reload the front of the site. If it loads, the white screen is fixed: the cause was the thing you just deactivated. Leave it deactivated, and decide afterwards whether to update it, replace it, or restore an earlier version of it — do not simply switch it back on and hope.

Two limitations: the Recovery Mode link expires after about a day, and WordPress sends at most one of these emails a day, so an expired link or a missing email will not be replaced straight away. The email can also fail outright if the site cannot send mail, or the administrator address is an inbox nobody monitors. If there is no email in the inbox or spam folder, do not wait — move on to the next fix, which finds the same error a different way.

Fix 2: Turn on debug logging and read the error

If there is no Recovery Mode email, make the hidden error visible — not on the page, where visitors could see it, but in a private log file only you can read. WordPress has built-in debugging tools for exactly this, documented on the official WordPress developer site, and they turn a blank page into a named file and line number.

Open wp-config.php in the host's file manager or over FTP — it sits in the root folder, next to wp-admin, wp-content and wp-includes. Before editing it, download a copy: this file holds the database credentials, and a mistake here takes the site down. Then find the line that reads /* That's all, stop editing! Happy publishing. */ and add these three lines directly above it:

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

These three constants do three different jobs. WP_DEBUG switches debugging on. WP_DEBUG_LOG writes every error to a file called debug.log inside the wp-content folder. WP_DEBUG_DISPLAY set to false keeps the errors off the public page, so visitors still see the blank page while you read the real error in private. The official documentation is explicit that these lines must go above the "stop editing" line, and that WP_DEBUG_LOG does nothing unless WP_DEBUG is enabled first. Save the file, then reload the broken page once.

Now open wp-content/debug.log — if the file does not exist yet, reload the broken page once more, since the log is only created when an error happens. Look for the most recent line beginning with "PHP Fatal error": it names the file and line where the failure happened, and the path names the culprit — wp-content/plugins/some-plugin/ points at that plugin, wp-content/themes/ at the theme, wp-includes or wp-admin at the core files. A typical memory error reads "PHP Fatal error: Allowed memory size of 41943040 bytes exhausted", which points at the memory limit fix below.

Read the last fatal error line, not the first. A debug log also collects harmless warnings and notices, so the top of the file may be full of them. The fatal error is the one that stopped the page, and it is usually the last entry — if the log is long, search for "Fatal error" and read the most recent match.

Two clean-up rules. First, when the site is fixed, turn debugging back off: change WP_DEBUG back to false and remove the WP_DEBUG_LOG and WP_DEBUG_DISPLAY lines. These tools are meant for local and staging installs, not live sites, and leaving debug mode on slows the site and fills the log indefinitely. Second, delete debug.log: it sits inside the public web folder, so on many hosts anyone can read it at yoursite.com/wp-content/debug.log, and it contains file paths and error details that do not belong in public.

Fix 3: Disable the plugins

Plugins cause the majority of white screens, so disabling them resolves the most cases. If the dashboard works, this takes two minutes: go to Plugins, select all, choose Deactivate from the bulk actions menu, and apply it. Reload the front of the site — if it loads, one of the plugins was the cause, proved without touching a file.

If wp-admin is blank too, disable the plugins from the file system: open the host's file manager or FTP client, go into wp-content, and rename the plugins folder to plugins-old. That single rename deactivates every plugin at once. Reload the site: if it loads, a plugin was the cause. Rename the folder back to plugins, then reactivate the plugins one by one from the dashboard, reloading the front page after each one — when the white screen returns, the plugin you just reactivated is the faulty one. Leave it deactivated.

There is a faster variant when the debug log already named a plugin: rename just that one plugin's folder inside wp-content/plugins — some-plugin to some-plugin-off, for example. WordPress treats a plugin whose folder it cannot find as deactivated, so the site should come back immediately while every other plugin keeps working.

Once you have identified the faulty plugin, decide what to do with it. If it broke after an update, the plugin's page on WordPress.org lists earlier versions under its Advanced view, so you can download and install the previous one. If the plugin is essential, check the author's support forum for a known conflict before reinstalling. And if it is one you barely use, delete it: every plugin is code that can break, and one that earns its keep only occasionally is not worth a white screen. Our WordPress security guide covers keeping the plugin list short and updated.

A note on caching: after deactivating plugins, clear any cache before judging the result. A caching plugin — or the host's server cache — may keep serving the blank page it stored during the failure, so the site can look broken after the fix has worked. Clear the cache from the host control panel, and check the site in a private browser window.

Fix 4: Switch to a default theme

If disabling every plugin does not bring the site back, the theme is the next suspect. The theme controls how every page is rendered, so a broken theme file — usually functions.php, which runs on every page load — produces a blank page across the whole site. Theme faults usually follow a theme update, a bad edit to the theme files, or a theme that has not been updated for the current WordPress or PHP version.

If wp-admin loads, go to Appearance, then Themes, and activate one of WordPress's bundled default themes — the Twenty Twenty series that ships with WordPress. Reload the front of the site: if it loads with the default theme, the active theme is the cause, and the site is back up — plain-looking, but up.

If wp-admin is blank, switch themes from the file system. Open the file manager or FTP, go into wp-content/themes, and rename the active theme's folder — for example, rename my-theme to my-theme-off. WordPress cannot load a theme whose folder is missing, so it falls back to a default theme automatically, provided one is installed. Reload the site: if it loads, the theme was the cause.

Two things to know. First, this only works if a default theme is installed — WordPress ships with one, but some hosts or site builders remove it, and a site with only one theme has nothing to fall back to. If renaming produces a missing-theme error, upload a fresh default theme from the WordPress theme directory, or ask the host to. Second, switching themes deletes nothing: content, menus and widgets live in the database, and renaming the folder back restores the theme exactly as it was. But do not rename it back and hope — a theme that produced a white screen will produce it again. Update it, replace it, or have its author look at the error the debug log recorded.

One common special case: a syntax error in the theme's functions.php, often from pasting a code snippet found online. A single missing semicolon or bracket there breaks every page, because the file runs on every load. If the white screen started right after you edited functions.php, restore the copy you downloaded before editing, or remove the snippet you added.

Fix 5: Raise the PHP memory limit

If the debug log says "Allowed memory size exhausted", or if the white screen appears on media-heavy pages, during imports, or when saving large posts, the cause is memory, not a faulty plugin or theme. Every PHP request gets a fixed amount of memory, and when WordPress asks for more than the limit allows, PHP stops the request — which the visitor sees as a blank page.

WordPress sets its own memory request through two constants: WP_MEMORY_LIMIT for normal front-end requests, defaulting to 40M on a single site and 64M on multisite, and WP_MAX_MEMORY_LIMIT for admin screens, defaulting to 256M. These are requests, not guarantees — the PHP memory_limit setting on the server is the real ceiling, and if the server allows only 128M, asking WordPress for 256M changes nothing.

To raise the limit, open wp-config.php — again, above the "That's all, stop editing!" line — and add:

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

Save the file and reload the broken page. If the white screen clears, memory was the cause. Do not set these values absurdly high — 1024M on a small site does not make it faster, it just lets a runaway script consume more memory before failing — and if the new value has no effect at all, the host has locked the PHP memory setting, and only the host can raise it.

To confirm what the site is actually running, check Tools, then Site Health, then Info, and open the Server section: it shows the PHP memory limit WordPress resolved, alongside the PHP version. If the number does not change after your edit, the server is enforcing its own ceiling. Some hosts let you raise the limit from the control panel instead — look for a PHP settings section — and if neither route works, ask support to raise it.

Memory exhaustion is also a symptom worth reading. A site that ran fine for a year and suddenly exhausts its memory has usually gained something hungry: a new plugin, a badly coded feature, or a traffic spike. Raising the limit fixes the white screen today; finding the hungry plugin — the debug log often names it — stops it coming back. Our WordPress speed optimisation guide covers keeping a site's resource use under control.

Fix 6: Delete a stuck .maintenance file

This fix takes one minute and applies to one specific symptom: instead of a blank page, the site shows the message "Briefly unavailable for scheduled maintenance. Check back in a minute." — and it has been showing it for much longer than a minute.

WordPress creates a small file called .maintenance in the root folder every time it runs a core update, and deletes it when the update finishes. If the update is interrupted — the connection drops, the server times out, the tab closes mid-update — the file stays behind, and WordPress keeps showing the maintenance message indefinitely.

The fix is to delete the file. Open the file manager or FTP, go to the root folder of the WordPress installation, and look for .maintenance. Note the dot at the start of the name: files beginning with a dot are hidden in many file managers, so you may need to turn on "show hidden files" before it appears. Delete it — only that file, nothing else — and reload the site. It should come back immediately.

Before deleting it, check whether an update is genuinely still running: if you started one two minutes ago, wait for it to finish. But if the message has been there for ten minutes or more, the update is not coming back, and the file is safe to remove. Afterwards, check Dashboard, then Updates, and confirm no update is pending — if the update only half-applied, run it again without closing the tab.

Fix 7: Check the PHP version

WordPress and its plugins are written for particular PHP versions, and a site running on old PHP — or a plugin that demands newer PHP than the server provides — can fail with a white screen. This is the most common cause of a white screen that appears with no change to the site itself: the host updates the PHP version on the server, a plugin that was written for the new version starts failing, or the reverse — the host leaves the site on an old PHP version while a plugin update assumes a newer one.

WordPress.org currently recommends PHP 8.3 or greater, with MySQL 8.0 or MariaDB 10.11 or greater and HTTPS support. WordPress still runs on older PHP versions, but WordPress.org notes that those versions have reached end of life and may expose a site to security vulnerabilities. The practical rule: a site in 2026 should run PHP 8.3 or newer, and any plugin demanding newer PHP than the server provides needs a PHP upgrade or a different plugin.

To find the PHP version, go to Tools, then Site Health, then Info and open the Server section — it lists the PHP version alongside the memory limit. If wp-admin is blank, the host's control panel usually shows the PHP version, or support can tell you in one message. If the version is below 8.3, raise it: most hosts let you change the PHP version from the control panel, and the change takes effect immediately.

Two warnings before changing it. First, test the change: a jump from a very old PHP version can break old plugins written for it, so switch, reload the site, and check the main pages before calling it done — if something breaks, switch back, update the offending plugin, and try again. Second, keep a backup from before the change: a PHP version change is a server change, and it affects every site on the account.

Fix 8: Reinstall the WordPress core files

If no plugin, no theme, no memory limit and no PHP version explains the white screen, the WordPress core files themselves may be damaged — usually after an update that was interrupted, or after a malware infection that modified core files. The symptom is a white screen with nothing in the debug log pointing at a plugin or a theme, or a fatal error whose file path sits in wp-admin or wp-includes.

If wp-admin loads, the easy route is built in: go to Dashboard, then Updates, and click the "Re-install Now" button. WordPress downloads a fresh copy of itself and replaces the core files, leaving your content, themes, plugins and settings untouched. It takes a minute or two, and it is the safest way to do this, because WordPress itself controls what gets replaced.

If wp-admin is blank, do the same job by hand: download a fresh copy of WordPress from wordpress.org, unzip it, and upload only the wp-admin and wp-includes folders, replacing the ones already there. Do not touch wp-content — themes, plugins and uploads live there — and do not touch wp-config.php, which holds the database credentials.

After reinstalling, reload the site and check the main pages. If it loads, the core files were the problem. Then run the updates: Dashboard, then Updates — make sure WordPress, every plugin and the theme are current, because an interrupted update is the usual cause. If the damage was malware rather than a failed update, reinstalling core is only half the job: the infection may also have touched the theme, plugins or database. Our WordPress malware removal guide covers the full clean-up.

Fix 9: When to contact your host

Some white screens are not fixable from inside WordPress at all, because the cause sits on the server. If you have worked through the fixes above and the site is still blank — or you cannot reach the files or the database — contact the host's support team, and give them something useful to work with.

Contact the host when any of these apply: the debug log is empty even with logging turned on, which suggests the error happens before WordPress loads; the site shows a server error alongside the blank page, such as a 500 or 503 status; the white screen started right after a server-side change the host made; the host's control panel itself is unreachable; or the file manager and FTP both refuse access. These are server problems, and only the host can see the server's own error logs.

When you contact support, include four things: the exact address that shows the blank page, when it started and what changed just before it, the last fatal error line from wp-content/debug.log, and what you have already tried. "The site is down" gets a generic reply; "the front page went blank after a plugin update, the log says PHP Fatal error in wp-content/plugins/example-plugin/file.php on line 42, and deactivating the plugin did not help" gets an engineer looking at the right thing. Paste the log line exactly — the file path and line number are the most useful part.

If the cause is still unclear, ask three questions: what does the server error log show for the time the page went blank, what PHP version and memory limit is the account running, and is a server-side cache or security rule serving a blank page. The server log often holds the answer WordPress could not show you, because it records errors from before WordPress loads. A good host will also restore a server-side backup if you ask — most keep daily backups for a few days — which is a legitimate fix when the site needs to be back up now.

How to stop it happening again

A white screen fixed is a lesson learned — if the habits that caused it change. Most white screens are preventable, and the prevention is routine maintenance rather than technical skill. The five habits below cover nearly every cause in this guide.

First, keep everything updated — but at the right time. Update WordPress core, the theme and every plugin when updates are available, because updates close the bugs and security holes that cause white screens. Do them when you have time to check the site afterwards, not five minutes before leaving the house, and never update everything at once on a site with no backup. Update, check the site, then move on. Our WordPress security guide covers the update routine, including automatic updates for minor releases.

Second, keep the plugin list short. Every active plugin is code that runs on every page load, and any one of them can produce a white screen. Audit the list twice a year: deactivate and delete anything the site no longer uses, and never install two plugins that do the same job. A site with eight maintained plugins is dramatically safer than one with thirty, five of which were abandoned years ago.

Third, back up on a schedule, not on a hope. A backup plugin set to run daily and store copies off-site — on Google Drive, for example — means the next white screen costs minutes instead of hours. Test the restore occasionally: a backup you have never restored is a hope, not a backup. The backup guide shows how to set the schedule up and test it.

Fourth, test changes on a staging copy before making them live. Most managed hosts offer one-click staging: a private copy where updates and new plugins can be tried safely. A plugin update that would have white-screened the live site white-screens the staging copy instead, where nobody sees it.

Fifth, watch the basics: the PHP version, the memory limit, and the Site Health screen. Site Health — Tools, then Site Health — flags an outdated PHP version, a low memory limit and other problems before they become a white screen. Checking it once a month takes two minutes and catches the slow drift — PHP getting older, plugins piling up — that eventually breaks a site out of nowhere.

Frequently asked questions

What causes the WordPress white screen of death?

A PHP fatal error that stops the page before any HTML is sent, while the server hides the error message — so the visitor sees a blank page instead of an explanation. The usual causes are a faulty plugin, a faulty theme, an exhausted PHP memory limit, an unsupported PHP version, or damaged WordPress core files after a failed update.

Can I fix the white screen of death without losing my content?

Yes. Posts, pages, images and settings live in the database and the uploads folder, and a PHP fatal error does not touch them. Every fix in this guide changes code — plugins, themes, settings or core files — not content. Back up before you start, and your content is safe even if a fix goes wrong.

How do I find which plugin caused the white screen?

Turn on debug logging in wp-config.php, reload the broken page once, and read the last line starting with "PHP Fatal error" in wp-content/debug.log — the file path names the plugin. Without the log, rename the wp-content/plugins folder to plugins-old to disable all plugins, then reactivate them one by one until the white screen returns.

Why is my WordPress site blank only on some pages?

Because the fault is in something only those pages use: a template file, a widget on one page, a shortcode in one post, or a plugin that only runs on certain page types. If the homepage is blank but single posts load, look at the homepage template and its widgets; if every page is blank, the fault loads everywhere — a plugin, the theme, or the core files.

How do I turn off debug mode after fixing the white screen?

Open wp-config.php, change WP_DEBUG back to false, and remove the WP_DEBUG_LOG and WP_DEBUG_DISPLAY lines you added. Then delete wp-content/debug.log, because the log sits in a publicly reachable folder and contains file paths and error details. Debug mode is a diagnostic tool, not a permanent setting — WordPress documents it for local and staging use, not for live sites.

When should I contact my hosting provider about a white screen?

Contact your host when the debug log stays empty with logging on, when the blank page comes with a 500 or 503 server error, when the white screen followed a server-side change, or when you cannot reach the files or the database. Send the failing address, when it started, the last fatal error line from debug.log, and what you have already tried.

Back up WordPress before the next white screen

A daily off-site backup turns the next white screen into a ten-minute restore instead of a lost afternoon — set it up once, and it runs itself.

Read the WordPress backup guide ↗
Portrait of Sharjeel Tahir
About the author

By Sharjeel Tahir

He builds free online tools at sharjeeltahir.com and writes WordPress, SEO and hosting guides for site owners everywhere. (The steps in this guide were checked against the official WordPress documentation on 19 November 2026.)

Published: 2026-11-19