The WordPress white screen of death (WSOD) is exactly what it sounds like: visitors and admins see a blank page, sometimes with a vague “critical error” message, and nothing else. No header, no footer, no clue. For Nigerian businesses that take orders, bookings, or leads through WordPress, every minute of blankness is lost trust.
This guide walks through safe recovery steps you can try yourself, what usually causes the blank page, and when it is smarter to use WordPress bug fixing or move to managed WordPress hosting so the next update does not end the same way.
Before you change anything
Do not keep refreshing and installing more plugins. First:
- Confirm scope: Is only the front end blank, only
/wp-admin, or both? - Note the last change: Plugin update, theme update, PHP version change, new security rule, or a migration?
- Secure a backup: If you have a recent backup (hosting panel, plugin, or HostPawa website backup), know how to restore before you experiment.
- Stay calm on DNS: A white screen is almost never “the domain expired” if the site still resolves; it is application-level failure.
Most common causes
- Plugin conflict after an update (very common with page builders, security, and cache plugins)
- Theme functions.php error or incompatible child theme code
- PHP memory exhausted on a heavy page or admin screen
- Incompatible PHP version after the host upgraded (for example PHP 7.4 → 8.x)
- Corrupted core file or incomplete upload after a failed update
- Bad must-use (mu-plugin) or object cache drop-in left behind after a migration
Step 1: Turn on debugging (safely)
If you can still reach files via File Manager or SFTP, open wp-config.php and temporarily enable debugging so WordPress logs the real error instead of a blank page:
- Set
WP_DEBUGto true - Set
WP_DEBUG_LOGto true - Keep
WP_DEBUG_DISPLAYfalse so visitors do not see raw errors
Then check wp-content/debug.log. The last fatal error line usually names the plugin or theme file responsible. Turn display debugging off again after you finish.
Step 2: Disable plugins without the dashboard
If wp-admin is also white, rename the plugins folder via File Manager or SFTP:
- Go to
wp-content/ - Rename
pluginstoplugins-disabled - Reload the site
If the site returns, a plugin caused the crash. Create a new empty plugins folder and move plugins back one at a time (or in small batches) until the white screen returns. Leave the offender disabled and update or replace it.
Security note: while plugins are off, your site may be temporarily less protected—work quickly and avoid publicising the outage window.
Step 3: Switch to a default theme
If plugins are not the cause, rename the active theme folder under wp-content/themes/. WordPress should fall back to a default theme (Twenty Twenty-Four, etc.). If the site recovers, repair or replace the broken theme—especially custom code in functions.php.
Step 4: Raise PHP memory (when logs say so)
If the log shows memory exhausted, increase the PHP memory limit for WordPress (hosting panel PHP settings, or a careful WP_MEMORY_LIMIT in wp-config.php within what your plan allows). Memory fixes help overloaded admin pages; they do not fix a fatal syntax error in a plugin.
Step 5: Check PHP version compatibility
After a host-side PHP upgrade, older plugins can fatal on modern PHP. Temporarily select a supported older PHP version in the control panel only long enough to regain access, update plugins/themes, then return to a current secure PHP version. Do not stay on end-of-life PHP as a permanent “fix.”
Step 6: Restore from backup if needed
If you cannot isolate the change, restore the last known good backup of files + database. Then update in a controlled way. HostPawa customers can use website backup options and ask support to confirm restore points before a risky update window.
Step 7: Clear caches carefully
After a fix, clear any page cache, CDN cache, and browser cache. A fixed site can still look blank if an edge cache stored an empty error response. If you use a caching plugin, purge it after plugins are stable again.
What not to do
- Do not delete the entire
wp-contentfolder “to start fresh” - Do not install random “WSOD fixer” plugins while the site is already fataling
- Do not paste unknown code snippets from comment sections into
functions.php - Do not ignore database backups—file-only restores often leave a half-broken site
When to get expert help
Call for help when:
- Both front end and admin stay white after plugin/theme isolation
- You see database connection errors mixed with blank pages
- The site broke after a migration or SSL/DNS change and you are unsure what rolled back
- It is a production store and every hour matters more than DIY learning
HostPawa offers WordPress bug fixing for conflicts and white screens, and managed WordPress hosting for teams that want fewer of these incidents after updates. If you need a human quickly, contact support with the approximate break time, last changes, and whether you have a backup.
Prevent the next white screen
- Update plugins on staging or during low traffic when possible
- Keep a recent, tested backup—not only an untested nightly file
- Limit admin users and remove abandoned plugins
- Prefer hosts that understand WordPress tickets, not only disk quotas
- After major PHP upgrades, update WordPress, themes, and plugins in the same maintenance window
Bottom line
A WordPress white screen is almost always a PHP fatal error or resource failure, not a mysterious “hack” by default. Isolate plugins, switch themes, read the debug log, restore if needed, then harden your update process. If the site pays the bills, pair recovery with managed care so the next update is boring—in the best way.