Learn what causes the WordPress white screen of death, including plugin conflicts, theme errors, PHP issues, memory limits and failed updates.
Learn what causes the WordPress white screen of death, including plugin conflicts, theme errors, PHP issues, memory limits and failed updates.
The WordPress white screen of death usually means WordPress has hit a fatal error and cannot finish loading the page. In many cases, the cause is a plugin conflict, theme error, PHP memory issue, failed update or incompatible PHP version.
The important thing is not to delete files at random. Work through the likely causes in order, check error logs where possible and make one change at a time.
If the site is live or business-critical, take a backup before making changes. A calm recovery process is safer than guessing.
Start with recent changes, plugins, themes, PHP memory, PHP version and error logs. Most white screen issues come from a fatal WordPress or PHP error.
The WordPress white screen of death is a blank page that appears when WordPress cannot complete the request. Sometimes there is no visible error message, which makes the problem feel more serious than it actually is.
In most cases, the white screen is caused by a PHP fatal error. This can come from a plugin, theme, update, memory limit, missing file, incompatible PHP version or custom code.
The site may be blank on the front end, the admin area, or both. Noting where the white screen appears helps narrow down the cause.
Most white screen issues come from a small group of WordPress and PHP problems. Check these areas before restoring backups or reinstalling WordPress.
A plugin update, conflict or fatal error can stop WordPress loading.
A theme file, function or update can trigger a fatal PHP error.
WordPress may hit the available PHP memory limit and fail before rendering the page.
Interrupted WordPress, plugin or theme updates can leave files incomplete.
A PHP fatal error can stop the request and show a blank screen.
Debug logs can reveal the file or plugin causing the error.
Start by asking what changed recently. A plugin update, theme edit, WordPress core update, PHP version change or new custom code is often the clue.
If you can access the WordPress admin area, disable recently changed plugins first. If the admin area is also blank, use the hosting file manager or FTP to rename the plugins folder temporarily.
Next, check the active theme, PHP memory limit and error logs. Error logs are especially useful because they often identify the exact file causing the fatal error.
| Problem | What It Usually Means | What To Check |
|---|---|---|
| White screen after plugin update | A plugin conflict or fatal error. | Disable recent plugins and check error logs. |
| White screen after theme change | The active theme may be broken. | Switch to a default WordPress theme. |
| White screen on admin only | Admin-specific plugin or PHP issue. | Check admin plugins and server logs. |
| White screen on whole site | Fatal error affecting WordPress loading. | Disable plugins, check theme and review logs. |
| Error after PHP change | Plugin or theme may be incompatible. | Review PHP version and compatibility. |
| Blank page after failed update | Files may be incomplete. | Restore from backup or re-upload clean files carefully. |
If the admin area still works, disable recently updated plugins one at a time and test the site after each change.
If the admin area is blank, rename the plugins folder through file manager or FTP. This disables plugins without deleting them. If the site loads again, rename the folder back and reactivate plugins carefully.
A theme can cause the white screen if a template file, function or update introduces a fatal error. Switching temporarily to a default WordPress theme can confirm whether the active theme is involved.
Avoid editing theme files blindly. If a custom theme is in use, check recent edits and error logs before making changes.
Error logs are often the fastest way to identify the cause. They may show the exact plugin, theme file or PHP error responsible for the white screen.
WordPress debug mode can also help, but it should be used carefully on live websites because visible errors may reveal technical details to visitors.
The biggest mistake is deleting plugins, themes or WordPress files without a backup. This can turn a recoverable error into a much bigger problem.
Visitors see a blank page and usually have no way to know what went wrong. For a business website, that can mean missed enquiries, failed orders and loss of trust.
If the admin area is still accessible, add a temporary maintenance message while the issue is being fixed. If the whole site is blank, focus on restoring access quickly and safely.
Keep regular backups, update plugins carefully and avoid making several major changes at the same time.
Test important updates on a staging copy where possible, especially for WooCommerce, membership sites and business-critical WordPress websites.
Keep plugin use under control and remove anything no longer needed. Fewer moving parts usually means fewer conflicts.
A plugin update introduces a fatal error and the front end becomes blank.
A theme function causes a fatal error after a theme edit or update.
WordPress runs out of available PHP memory and cannot finish loading.
Avoid random fixes. Work from the most likely causes first: recent plugin changes, theme changes, PHP settings and logs.
Before restoring backups or reinstalling WordPress, check recent plugin updates, theme changes, PHP version changes and error logs.
Most white screen issues can be traced back to a recent change or fatal PHP error.
It is a blank page caused when WordPress cannot complete loading, often because of a fatal PHP error.
Common causes include plugin conflicts, theme errors, PHP memory limits, failed updates and incompatible PHP versions.
Yes. A plugin conflict or faulty update is one of the most common causes.
Yes. Theme files, functions or updates can trigger fatal errors.
Use file manager or FTP to rename the plugins folder temporarily.
Only after checking recent changes and logs, unless the site needs urgent rollback.
Yes. If WordPress runs out of PHP memory, it may fail before rendering the page.
Yes. Older plugins or themes may not be compatible with newer PHP versions.
Check hosting error logs, WordPress debug logs and recent plugin or theme changes.
Keep backups, update carefully, test major changes and avoid unnecessary plugins.
If the white screen is still showing, collect the exact symptoms: whether the front end, admin area or both are blank, what changed recently and whether any error logs mention a plugin, theme or PHP file.
Work through plugins, theme, PHP memory, PHP version and failed updates in order. If the website is business-critical, use a backup or staging copy before making larger changes.
When the cause is found, update carefully and remove any unnecessary plugins or custom code that could cause the same issue again.
WordPress hosting links
Useful WordPress hosting, VPS and maintenance pages without adding a heavy extra section.
Install for quick access to hosting, tools, billing and support.