Errors
The WordPress White Screen of Death: Every Cause and Fix
If your WordPress site is showing a blank white page, the most common causes are a fatal PHP error, a memory limit problem, a bad plugin or theme change, or a server-side issue like a broken cache or .htaccess rule. Start with the safest checks first: confirm whether the whole site is blank or just the admin, clear caches, then disable plugins and switch themes one step at a time.
Before you change files or settings, take a full backup if you can. If the site is down on a live store or business site and you need it back quickly, Mend can diagnose it for free and quote a flat price before any work starts.
What the white screen usually looks like
The classic “white screen of death” is exactly what it sounds like: WordPress loads to a blank white page with no visible error message. Sometimes it affects the entire front end, sometimes only /wp-admin, and sometimes only one page, post type, or device.
The tricky part is that the blank page is not one problem. It is a symptom. WordPress is failing before it can render the page, but the reason can be anywhere from PHP to the database to the active theme. That is why fixes that work for one site do nothing for another.
The fastest way to narrow it down
- Check whether the blank screen happens everywhere or only on one page.
- Open the site in a private browser window and clear any plugin, host, or CDN cache.
- If you can access files, look for a fatal error message in debug logs.
- Disable plugins, then test again.
- Switch to a default theme, then test again.
- Check memory, PHP version, and recent changes if the problem remains.
This order matters because it starts with the least invasive checks and moves toward deeper changes only when needed.
Cause 1: A fatal PHP error
This is one of the most common reasons for a white screen. A plugin, theme, or custom code snippet hits a fatal error, and WordPress stops execution before it can display content.
You may also see this after editing theme files, adding code to functions.php, or installing a plugin that is incompatible with your current PHP version or WordPress version.
How to fix it
- Enable debugging in
wp-config.phpif you can safely edit files. - Set
WP_DEBUGandWP_DEBUG_LOGto true. - Reload the broken page, then check
/wp-content/debug.log. - Remove or roll back the code, plugin, or theme file named in the error.
If the debug log is not available, many hosts also store PHP error logs in their control panel. The exact location depends on the host.
Cause 2: Memory exhausted
WordPress can also blank out when PHP runs out of memory. This often happens on larger sites, WooCommerce stores, media-heavy sites, or sites running several resource-hungry plugins.
A memory problem may not always show a clear message to visitors. Instead, you just get a white page because PHP fails before the output is sent.
How to fix it
- Check the logs for a message like “Allowed memory size exhausted.”
- Increase the WordPress memory limit if your host allows it.
- If the problem returns, reduce the load by disabling the heaviest plugin or removing unnecessary functionality.
- If you are already near the host’s limit, ask the host to raise the PHP memory cap or move to a plan with more resources.
Raising the limit is a workaround, not always the final answer. If the site repeatedly needs more memory, something on the site is inefficient or overbuilt.
Cause 3: A broken plugin
A single plugin update, conflict, or bad code path can take the whole site down. This is especially likely if the white screen started right after installing, updating, or activating a plugin.
How to fix it
- Rename the plugin folder through SFTP or your hosting file manager to disable it.
- Reload the site after each plugin is disabled, if you need to isolate the one causing the problem.
- Once you find the culprit, delete it or restore a known-good version.
- If it is essential, look for a compatible alternative or a patched update from the developer.
If you cannot reach the admin area, this file-level method is usually the safest way to test plugins. If you want a fuller recovery checklist, see How to Fix the WordPress White Screen of Death.
Cause 4: A broken theme or template file
Theme problems can produce a white screen if a template file has a syntax error, a function call fails, or a child theme depends on something that is missing in the parent theme.
This is especially common after editing theme files directly, which is risky because a tiny PHP mistake can break the entire page.
How to fix it
- Temporarily switch to a default WordPress theme such as Twenty Twenty-Four.
- If you cannot use the dashboard, rename the active theme folder via SFTP to force WordPress to fall back to another theme.
- Check the theme’s files for recent edits, missing includes, or syntax errors.
- Restore the last working version of the theme or child theme.
If the site returns when you switch themes, the problem is in the theme layer, not WordPress core.
Cause 5: WordPress core files are damaged
Core files can be damaged by an incomplete update, a bad manual file transfer, or a host-level issue. That is less common than plugin or theme problems, but it does happen.
In this case, the site may go white across the board, and plugin deactivation may not help.
How to fix it
- Back up the site first.
- Replace the WordPress core folders with a fresh copy from WordPress, but do not overwrite
wp-contentorwp-config.php. - After replacing core files, test the site again.
- Run an update only if the site is stable and the logs do not show another cause.
Cause 6: Cache is serving a broken page
Sometimes the site is not actually broken anymore, but a cache layer is serving the white page. This can happen in the browser, in a WordPress caching plugin, at the host, or on a CDN.
Because there can be multiple cache layers, clearing just one may not be enough.
How to fix it
- Clear the browser cache or test in a private window.
- Clear the WordPress cache plugin if one is active.
- Clear any host cache from the hosting dashboard.
- Clear CDN cache, if your site uses one.
If you want a clearer breakdown of where stale content can live, read WordPress Caching Explained: Which Layer Is Stale?
Cause 7: A bad .htaccess rule or server config issue
On Apache or LiteSpeed servers, a bad rewrite rule in .htaccess can send WordPress into a blank response. Server config problems, permissions issues, and PHP handler misconfiguration can do the same.
How to fix it
- Rename
.htaccessto something like.htaccess-old. - Reload the site.
- If the site works, regenerate permalinks by visiting Settings > Permalinks and saving changes.
- If it still fails, check file permissions and ask the host to review the web server error log and PHP handler.
This is one of those cases where the fix may sit outside WordPress itself. If the host needs to inspect server logs or tune PHP settings, a good engineer can save a lot of time.
Cause 8: Database trouble or missing content
A full database outage usually shows a different error, but partial database issues can still lead to a blank page. A bad query, a corrupted table, or a plugin that cannot read required data may leave the page empty.
How to fix it
- Check whether the database is reachable and the site can still load basic admin pages.
- Look for database errors in the logs.
- Repair corrupted tables if your host supports it, or restore from a clean backup.
- Disable the plugin that triggers the broken query.
If the issue is broader than a single plugin, it may be safer to restore from a known-good backup than to patch table-by-table on a live site.
Cause 9: Malware or injected code
Malware can cause a white screen by injecting broken PHP, hijacking requests, or disabling normal output. This is less obvious than a visible defacement, but it is still a security problem.
If the blank screen appeared after strange admin activity, unknown files, or unexplained redirects, treat it as a possible compromise.
How to fix it
- Scan the site with your host’s security tools or a trusted security plugin.
- Review recently changed files and unknown users.
- Replace core files, plugins, and themes from clean sources.
- Reset passwords and revoke suspicious sessions.
If you suspect compromise, use the safer cleanup approach in WordPress Site Hacked? Here's How to Clean It Up — Safely.
How to prevent the white screen from coming back
- Keep regular backups that you have actually tested by restoring.
- Update plugins, themes, and core in a controlled way, not all at once on a busy live site.
- Remove unused plugins and themes instead of just deactivating them.
- Avoid editing live theme files directly.
- Use a staging site for risky changes whenever possible.
- Monitor PHP errors so you can catch problems before visitors do.
A stable maintenance routine is often the difference between a quick fix and a midnight outage. If you want the bigger picture, see What a Good WordPress Maintenance Routine Looks Like.
When to call a professional
Call a professional when the site is live and revenue is at stake, when you cannot access files or logs, when the white screen returns after basic fixes, or when you suspect malware, core file corruption, or server misconfiguration. Those are the cases where guesswork gets expensive fast.
If you want someone to isolate the cause, fix it safely, and tell you exactly what changed, Mend’s Emergency Rescue is built for broken sites, and most fixes are completed the same day. For a smaller issue, a Quick Fix may be enough; every paid fix includes a plain-English report and a fixed-or-your-money-back guarantee.
To let an engineer get in securely without sharing passwords, you can use Mend Connect.
The White Screen of Death is frustrating because it hides the actual failure. But once you treat it as a symptom and check the most likely layers in order—logs, plugins, theme, memory, cache, server config—you can usually find the real cause without making the situation worse.
If you are stuck, back up what you can, stop guessing, and get the site diagnosed before the next change adds another problem on top.
Frequently asked questions
Is the white screen of death always caused by a plugin?
No. Plugins are common, but theme errors, PHP memory limits, broken core files, cache problems, .htaccess issues, and malware can all cause it.
Should I disable all plugins at once?
If you have no log access and the site is already down, disabling plugins is a reasonable first test. Do it carefully and one step at a time if you need to identify the exact culprit.
What if the white screen only happens on one page?
That usually points to a page-specific template issue, a shortcode or block problem, or code that only runs on that page. Check recent edits and the page’s related plugin or theme features.
Can I fix this without losing content?
Usually yes. The safest fixes target the broken code, plugin, theme, or server setting rather than content itself. Always back up first so you can restore if needed.