If your WordPress site shows a blank white page after an update, the problem is usually caused by a PHP error, an incompatible plugin or theme, a memory limit issue, or a failed update process. In a hosting environment, this is often referred to as the WordPress White Screen of Death. The good news is that it is usually recoverable without losing content, especially if you have file access, a database backup, and a control panel such as Plesk or a similar hosting panel.
This guide explains how to identify the cause, restore access safely, and reduce the chance of the issue happening again after future updates.
What causes the WordPress white screen after an update?
The white screen usually appears when WordPress cannot finish loading the page. Instead of showing an error message, it returns a blank page because of a fatal PHP error or a configuration conflict. After an update, the most common triggers are:
- A plugin conflict caused by a new WordPress, plugin, or PHP version.
- A theme error if the active theme is not fully compatible with the updated WordPress core.
- PHP memory exhaustion when the site needs more resources than the current limit allows.
- Corrupted update files if the update was interrupted.
- Outdated PHP version on the hosting account.
- Fatal errors in custom code added through functions.php, mu-plugins, or custom snippets.
On managed hosting platforms, the issue is often easier to diagnose because you can use logs, file manager access, and PHP version tools from the control panel.
First checks before you change anything
Before making changes, confirm whether the problem affects the whole site or only part of it. Check the homepage, a post page, and the WordPress admin area. If the white screen appears only in the frontend, the issue is often theme-related. If both frontend and admin are affected, the problem may be broader, such as a plugin conflict or a PHP fatal error.
Also verify whether:
- the domain is resolving correctly;
- the hosting account is active and not resource-limited;
- you recently changed the PHP version, plugin list, or theme;
- the issue started right after a WordPress core update, plugin update, or theme update.
If possible, take a backup of the current site state before you begin troubleshooting. Even if the site is broken, preserving the current files and database can help if you need to compare versions or restore specific content later.
How to fix the WordPress white screen step by step
1. Clear browser and site cache
Sometimes the white screen is caused by cached content rather than a live error. Start with the simplest checks:
- Refresh the page with a hard reload.
- Clear your browser cache.
- If you use a caching plugin, clear its cache.
- If your hosting platform has server-side cache, purge it from the control panel.
- If you use a CDN, clear the CDN cache as well.
If the site comes back after cache clearing, the issue may have been temporary or limited to cached assets.
2. Enable WordPress debug logging
If the screen remains blank, the next step is to identify the error. WordPress can log PHP errors when debug mode is enabled. In a hosting control panel or file manager, open the wp-config.php file and ensure debugging is configured so errors are written to a log file rather than displayed publicly.
Useful settings include enabling WP_DEBUG and WP_DEBUG_LOG while keeping WP_DEBUG_DISPLAY disabled on a live site. This lets you review errors in a log file without exposing technical details to visitors.
After saving the change, reload the broken page and check the debug log for the exact plugin, theme, or file that is failing.
3. Check the error logs in your hosting panel
Hosting error logs often give the fastest answer. In a Plesk or similar control panel, open the domain’s logs and look for recent PHP errors, fatal errors, or memory exhaustion messages. Common log entries may mention:
- Allowed memory size exhausted
- Call to undefined function
- Parse error
- Class not found
- Fatal error in plugin or theme file
The timestamp is important. Focus on errors that appeared immediately after the update.
4. Disable all plugins
Plugin conflicts are one of the most frequent reasons for a white screen after an update. If you cannot access the WordPress dashboard, disable plugins at file level:
- Open the site files through the hosting file manager or via FTP.
- Go to the wp-content folder.
- Rename the plugins folder to something like plugins-disabled.
This temporarily disables all plugins. Then reload the site.
If the site starts working again, the issue is plugin-related. Rename the folder back to plugins, then reactivate plugins one by one from the WordPress admin area until the problem returns. The last plugin enabled is likely the cause.
If you use managed hosting, this step is often quick because file access is usually available without using SSH.
5. Switch to a default theme
If disabling plugins does not fix the issue, the active theme may be the problem. This is especially common after a WordPress core update when the theme contains outdated template code or custom functions.
To test the theme:
- Open wp-content/themes in the file manager.
- Rename the current theme folder.
- WordPress should fall back to a default theme if one is installed, such as Twenty Twenty-Four.
If the site loads after this, the original theme contains the error. Check the theme logs, update the theme, or restore a previous version from backup. If it is a custom theme, review any recent code changes.
6. Increase the PHP memory limit
A white screen after an update can happen when WordPress runs out of memory during page generation. This is common on busy sites, image-heavy pages, or sites with several plugins.
Possible ways to increase memory include:
- Editing wp-config.php to raise the WordPress memory limit.
- Adjusting PHP settings in the hosting control panel.
- Changing the memory_limit value in PHP configuration if your hosting plan allows it.
In a managed hosting environment, it is often better to increase memory through the panel rather than using multiple overlapping configuration files. If you are unsure which limit applies, check the active PHP settings in the control panel and compare them with the WordPress configuration.
If the logs show memory exhaustion, increasing the limit may resolve the issue immediately. If not, the problem may still be a plugin or theme that is consuming too many resources.
7. Verify the PHP version
After an update, some sites fail because the hosting account is running a PHP version that no longer matches plugin or theme requirements. Older code may break on newer PHP versions, while newer WordPress components may not perform well on outdated versions.
From the control panel, check the active PHP version for the domain. If the issue started after a PHP switch, try a supported alternative version recommended by the theme or plugin developer.
Keep in mind:
- Upgrading PHP can improve performance and security.
- Changing PHP too aggressively can expose compatibility issues.
- Test after each change, rather than adjusting multiple variables at once.
8. Reinstall WordPress core files
If the update was interrupted or core files were corrupted, reinstalling WordPress core can repair missing files without affecting your content, plugins, or themes.
Use the following approach:
- Back up your files first.
- Download a fresh copy of the same WordPress version or the latest stable version.
- Replace only the wp-admin and wp-includes folders, and the root WordPress files, while keeping wp-content and wp-config.php intact.
This is a useful step when the white screen follows a failed core update or if the site breaks immediately after a partial file transfer.
9. Review custom code and must-use plugins
Some sites use custom snippets, mu-plugins, or code added to functions.php for redirects, security rules, or custom behavior. A single syntax error in one of these files can cause a blank screen.
Check:
- functions.php in the active theme;
- must-use plugins in wp-content/mu-plugins;
- custom snippets added through a site-specific plugin;
- recent changes made during deployment or maintenance.
If you recently added code, compare it against a known working backup. Even a missing semicolon or incompatible function call can break the site after an update.
10. Restore from a clean backup if needed
If the issue cannot be isolated quickly, restoring a recent backup may be the most efficient fix. This is especially practical in managed hosting or Plesk environments where automated backups are available.
Before restoring, confirm the backup date. Choose a backup from before the update that caused the white screen. If possible, restore files and database selectively rather than replacing everything blindly.
After restoration, update one component at a time and test the site after each change.
How to use logs to find the exact cause
Logs are one of the most valuable troubleshooting tools on a hosting platform. They help you move from guesswork to a specific error message.
Look for these patterns:
- Fatal error in a plugin file — usually means that plugin needs an update, rollback, or replacement.
- Fatal error in theme functions — often means the active theme or a child theme has incompatible code.
- Memory exhausted — increase memory or reduce plugin load.
- Parse error — a code syntax issue, often from custom edits.
- Missing file — a failed update or incomplete deployment.
If your hosting provider offers PHP error logs separately from access logs, check both. Access logs show what was requested, while error logs show why the request failed.
When the white screen affects only the admin area
Sometimes the public site loads, but /wp-admin is blank. This usually points to an admin-specific plugin issue, a permissions problem, or a fatal error triggered only in the dashboard.
In that case, test:
- plugin deactivation;
- theme fallback;
- PHP version compatibility;
- browser cache and cookies;
- file permissions in the hosting account.
If you use security plugins, they may also interfere with admin loading after an update. Check whether the login page or dashboard is blocked by a rule that needs adjustment.
How to prevent the white screen after future updates
Prevention is much easier than recovery. For WordPress sites hosted in Europe on shared or managed hosting, a stable maintenance routine can reduce downtime significantly.
Use a staging site
Test major updates on a staging copy before applying them to production. This is especially important for sites with custom themes, e-commerce functionality, multilingual plugins, or membership features.
A staging site lets you verify:
- plugin compatibility;
- theme behavior;
- PHP version changes;
- layout issues after core updates.
Keep regular backups
Automated backups are essential. Make sure you have both file and database backups, and know how to restore them from the control panel.
Good backup practice includes:
- daily backups for active sites;
- off-site or separate storage copies;
- retention of several restore points;
- testing restore procedures before an emergency.
Update one component at a time
Avoid updating WordPress core, plugins, and themes all at once if the site is business-critical. Update in stages and test after each change. This makes it much easier to identify the cause if something breaks.
Monitor PHP compatibility
Keep track of the PHP version recommended by your theme and major plugins. Before switching to a newer version, confirm that all extensions and custom code are compatible.
Limit risky custom changes
If possible, place custom functionality in a child theme or site-specific plugin rather than editing core or theme files directly. This reduces the chance that an update will overwrite your changes.
Best practices for hosting and control panel users
If your site is hosted in a managed environment, the control panel can simplify recovery. In Plesk or similar panels, you can usually:
- open file manager access to rename plugin or theme folders;
- review domain error logs;
- change PHP versions per domain;
- adjust memory and execution settings;
- restore from backup snapshots;
- enable maintenance tools for safe troubleshooting.
When working with an Apache-based hosting stack, remember that the issue may involve both application code and server-side settings. A configuration mismatch in .htaccess, PHP handlers, or caching rules can sometimes mimic a WordPress problem.
If you manage several sites in the same hosting account, check whether the issue is isolated to one installation or shared across multiple domains. A single site-specific failure is usually application-related, while a wider issue may point to account-level configuration or resource limits.
FAQ
Why does WordPress show a white screen after an update instead of an error?
WordPress often hides fatal errors from visitors on live sites to avoid exposing technical details. The blank page usually means the page generation process failed, and the real cause is visible in the debug log or hosting error log.
Will I lose content if I fix the white screen by disabling plugins?
No, disabling plugins does not remove content. It only turns off plugin functionality. However, some plugin-generated features may disappear temporarily until the plugin is re-enabled.
What if I cannot access the WordPress dashboard at all?
You can still troubleshoot through the hosting control panel, file manager, FTP, and logs. Renaming the plugins folder or switching the theme at file level are common recovery steps when wp-admin is unavailable.
Should I change the PHP version first or disable plugins first?
In most cases, disable plugins first because that is the most common cause after updates. If that does not help, check the theme, logs, and PHP version. Change only one variable at a time so you can identify the real cause.
Can a failed automatic update cause a white screen?
Yes. If the update process is interrupted, core files may be left incomplete or corrupted. Reinstalling WordPress core files from a clean package often fixes this.
How do I know if it is a theme issue?
If the site works after switching to a default theme, the active theme is likely the problem. Theme-related issues are especially common after core updates or when a custom theme contains outdated code.
Conclusion
The WordPress white screen after an update is usually fixable with a structured approach: check logs, disable plugins, test the theme, confirm PHP compatibility, and restore core files if needed. In a hosting environment with a control panel, these steps can often be completed without data loss and without full server-level intervention.
The best long-term protection is a combination of regular backups, staged updates, compatibility checks, and careful use of custom code. If you maintain WordPress sites for clients or business use, building these checks into your update routine will save time and reduce downtime after future releases.