Blog

A blank white WordPress site can make your stomach drop, but it usually does not mean your site is gone.

The WordPress White Screen of Death is almost always caused by a fatal PHP error, a plugin conflict, a theme issue, a memory limit problem, or a failed update. The trick is to slow down, avoid making the damage worse, and work through the likely causes in the right order.

This guide walks you through how to recover your site without deleting content, overwriting the wrong files, or guessing blindly.

What the WordPress White Screen of Death actually means

The White Screen of Death, often shortened to WSOD, is when your WordPress site loads as a completely blank white page. Sometimes it affects the public website. Sometimes it affects only the admin area. Sometimes both disappear.

It usually means WordPress hit an error so serious that it stopped loading before it could display the page. Depending on your server settings, that error may be hidden from visitors, which is why all you see is white space.

Common causes include:

• A plugin update that introduced a fatal error
• A theme conflict or broken theme file
• PHP memory being exhausted
• An incompatible PHP setting on the server
• A partial or interrupted WordPress update
• Corrupted files from a bad upload or failed migration
• Malware or suspicious code, less common but possible

If the issue started right after an update, start with plugins and themes. If it happened after a hosting change, migration, or PHP change, start with server logs and PHP settings.

First: do not start deleting things

When a site goes white, the worst move is panic-cleaning. Do not delete random plugins, remove your theme, reinstall WordPress over top of the site, or restore an old backup without checking what changed first.

Those actions can destroy useful clues and may create a second problem on top of the first one.

Before you touch anything: take a fresh backup of the broken site if your hosting control panel allows it. Even a broken copy is useful if you need to recover files, uploads, orders, form entries, or settings later.

If your site handles contact forms, appointment requests, client intake, or WooCommerce orders, be extra careful. Restoring an older backup can roll back recent submissions or orders, which may create business and privacy headaches.

For a deeper look at backup basics, read WordPress Backup Guide: What You Need to Know.

Check whether WordPress sent a recovery mode email

WordPress can sometimes detect a fatal error and send an email to the site administrator with a special recovery mode link. That link may let you log in and disable the plugin or theme causing the crash.

Check the inbox for the admin email address on the site. Also check spam, junk, and any mailbox forwarding rules.

If you receive a recovery mode email, read it carefully. It may name the plugin, theme, or file that triggered the problem. That is your best first clue.

If you do not get an email, that does not mean WordPress failed completely. It may mean the site email is not working, the fatal error happened too early, or the admin email address is outdated.

Figure out what part of the site is affected

Before troubleshooting, narrow the problem. Open the site in a private browser window and test a few different URLs.

• Does the homepage show white, but inner pages load?
• Does the public site load, but /wp-admin/ is white?
• Does the login page load?
• Does the problem happen only after logging in?
• Does it affect only one language, product page, form, or landing page?

This matters because a site-wide white screen usually points to a major plugin, theme, or PHP problem. A white screen on one page may be caused by a shortcode, page builder module, custom field, template, or a block that triggers an error only on that page.

If the white screen appeared immediately after a WordPress, plugin, or theme update, this related guide may help: WordPress Update Broke My Site: What to Do.

Look at the error logs before guessing

The fastest fix usually starts with the server error log. Most hosting control panels include some kind of error log viewer. If you are on cPanel, look for an Errors or Metrics section. Other hosts may place logs in a dashboard area.

You are looking for recent fatal errors around the time the white screen started. Common phrases include:

• PHP Fatal error
• Allowed memory size exhausted
• Uncaught Error
• Call to undefined function
• Cannot redeclare
• Failed opening required

The error may point to a plugin folder, a theme folder, or a core WordPress file. If the path includes wp-content/plugins/, the plugin name is usually in the next folder name. If it includes wp-content/themes/, the active theme may be involved.

Do not paste sensitive logs into public forums. Logs can contain server paths, usernames, IP addresses, and other details you may not want public.

Temporarily disable plugins safely

Plugin conflicts are one of the most common causes of a white screen. If you can still access WordPress admin, go to the Plugins screen and deactivate the plugin mentioned in the recovery email or error log.

If you cannot access admin, use your hosting file manager or SFTP. Go to wp-content and rename the plugins folder to something like plugins-disabled. This forces WordPress to deactivate all plugins without deleting them.

Then reload the site.

• If the site comes back, one of the plugins is the likely cause.
• Rename the folder back to plugins.
• Reactivate plugins one by one from WordPress admin.
• After each activation, test the site in a private browser window.

When the white screen returns, the last plugin you activated is probably involved. It may not be the only cause, but it is the first place to investigate.

When not to reactivate everything

Do not blindly reactivate every plugin if your site takes payments, bookings, memberships, or form submissions. Test business-critical functions first.

For WooCommerce, test cart, checkout, payment gateway behaviour, tax display, shipping options, and order emails before assuming the store is healthy. A site can “look fixed” while checkout is still broken.

Switch to a default theme temporarily

If disabling plugins does not fix the white screen, the active theme may be the issue. This is especially likely after editing theme files, updating a theme, changing PHP settings, or moving the site to a new host.

If you can access the admin area, switch to a default WordPress theme from Appearance. If you cannot access admin, use your hosting file manager or SFTP and rename the active theme folder inside wp-content/themes/.

WordPress will try to fall back to another installed theme. If no other usable theme exists, you may need to install one through your hosting tools or restore the theme from backup.

If the site works after switching themes, do not immediately reinstall the same theme and hope for the best. Check the theme error, recent changes, custom code snippets, and any child theme modifications.

Increase PHP memory only if the error points that way

A white screen can happen when WordPress runs out of PHP memory. The error log often says something like “Allowed memory size exhausted.”

If you see that, increasing memory may help, but treat it as a clue, not a cure. A site that suddenly needs much more memory may have a plugin loop, a bloated page builder layout, a huge query, or a background task gone wrong.

Depending on your host, you may be able to adjust PHP memory in the hosting control panel. Some sites also define memory limits in wp-config.php. If you are not comfortable editing that file, ask your host or developer, because one typo can bring the site down further.

When memory fixes the white screen, still investigate why memory was exhausted. Otherwise the same problem may return during traffic spikes, imports, backups, or WooCommerce tasks.

Check PHP compatibility

If the white screen started after your host changed the PHP version, a plugin or theme may not be compatible with the current server environment.

The error log usually points to the file causing the problem. Look for older plugins, abandoned themes, custom code, or premium plugins that have not been updated recently.

You can temporarily switch PHP settings back if your host allows it, but that should be a short-term recovery step. Long term, the better fix is updating or replacing incompatible code.

Do not keep an outdated PHP setup forever just because one old plugin requires it. That can create security and performance problems later.

Clear caches after each major change

Caching can make troubleshooting confusing. Your site may be fixed, but the browser, WordPress cache plugin, server cache, or CDN may still be serving the broken page.

After disabling plugins, switching themes, or restoring files, clear:

• Your browser cache, or test in a private window
• Any WordPress caching plugin cache
• Server-level cache if your host provides it
• CDN cache if your site uses one

Do not change five things and then clear cache. Change one thing, clear cache, test, and write down the result. That way you know what actually fixed the issue.

Restore from backup only when it makes sense

A backup restore can be the fastest route back online, but it is not always the safest.

Restoring makes sense when:

• The problem started after a known bad update
• You have a clean backup from shortly before the issue
• The site is mostly static, with no recent orders or form entries to preserve
• You understand what data will be overwritten

Restoring is risky when:

• You run WooCommerce and may lose recent orders
• You collect appointment requests, legal intake forms, healthcare forms, or quote requests
• You do not know whether the backup is clean
• The white screen may be caused by malware or a server issue

If you restore a backup, note the exact restore point and test the site afterward. Also update the plugin, theme, or setting that caused the issue, but do it carefully. Otherwise you may restore the site and immediately break it again.

Use a staging site for risky fixes

If your site is still partly working, or if it handles transactions and leads, use a staging copy before making big changes. A staging site lets you troubleshoot without experimenting on the live site.

On staging, you can safely test plugin deactivation, theme changes, PHP settings, and updates. Once you know the fix, apply the smallest necessary change to the live site.

This is especially helpful for WooCommerce stores, membership sites, booking sites, and agency-managed client sites. For more background, see WordPress Staging Environments Explained.

Ambrite’s Canadian cloud hosting includes WordPress staging on every hosting plan, which is useful when you want a safer place to test before touching the live site.

Check for malware if the fix does not hold

Most white screens are not hacks. They are usually boring technical failures: updates, conflicts, memory, or server settings.

But malware becomes more likely if the site keeps breaking after you fix it, unknown admin users appear, files come back after deletion, visitors are redirected, or Google shows warnings.

If you suspect compromise, stop trying random repairs and preserve evidence. Change passwords for WordPress, hosting, SFTP, database users, and administrator email accounts. Then have the site scanned properly.

Ambrite provides WordPress hack cleanup and malware removal for compromised sites, including identifying backdoors, removing malicious code, patching the vulnerability, and hardening the site after cleanup. One-time cleanup starts at $499 CAD depending on severity, and hack cleanup is included on the Complete maintenance plan.

Common mistakes that make a white screen worse

The first repair attempt matters. A careful fix is usually faster than cleaning up after a rushed one.

• Deleting plugins instead of disabling them: this can remove settings or make rollback harder.
• Restoring an old database without checking recent activity: this can erase orders, form submissions, and content edits.
• Editing live PHP files in the WordPress editor: one syntax error can lock you out.
• Updating everything at once: if something breaks again, you will not know which update caused it.
• Ignoring logs: logs often tell you the exact file or plugin involved.
• Assuming the homepage represents the whole site: test forms, checkout, search, menus, login, and key landing pages.

A practical recovery checklist

If you want a clean order of operations, use this checklist:

1. Take a fresh backup of the current broken site if possible.
2. Check for a WordPress recovery mode email.
3. Test whether the issue affects the public site, admin area, or only certain pages.
4. Review server error logs for recent fatal errors.
5. Disable the plugin named in the error, or temporarily disable all plugins if needed.
6. If plugins are not the issue, switch to a default theme temporarily.
7. Check PHP memory only if logs suggest memory exhaustion.
8. Review recent PHP version or hosting changes.
9. Clear browser, plugin, server, and CDN caches after each major change.
10. Restore from backup only after checking what data may be lost.
11. Test important site functions before calling the issue fixed.

What to test after the white screen is gone

Getting the page to load is only step one. You still need to make sure the site works.

Test these areas:

• Homepage and main service pages
• Contact forms and notification emails
• Navigation menus on desktop and mobile
• Login and admin dashboard access
• Search, filters, or directories if your site uses them
• WooCommerce cart, checkout, taxes, shipping, payments, and order emails
• Booking forms, intake forms, quote request forms, and newsletter signups

For Canadian businesses, also think about personal information. If a restore affected contact form entries, customer records, or order history, document what changed. If your site collects personal information, you should already have privacy and retention practices that fit your obligations under Canadian privacy law.

How to reduce the chance of it happening again

You cannot prevent every WordPress problem, but you can make white screens less likely and easier to recover from.

• Keep WordPress core, themes, and plugins updated.
• Remove plugins you no longer use.
• Use reputable plugins that are actively maintained.
• Keep automatic backups and test that they can be restored.
• Use staging for risky updates.
• Monitor uptime so you know when the site fails.
• Document custom code, special plugin settings, and critical integrations.

Ambrite’s WordPress maintenance and security plans include daily updates, daily backups kept for 90 days, uptime monitoring, malware scanning, CDN protection, daily speed checks, and support by email and ticket from a Canadian WordPress professional. Plans are month-to-month and start at $49 CAD/month.

Maintenance is not magic, and no service can guarantee a site will never break. The value is that updates, backups, monitoring, and recovery planning are handled before something goes wrong, not during a panic.

When to stop troubleshooting and ask for help

DIY troubleshooting is fine if you have a recent backup, a simple brochure site, and a clear error pointing to one plugin. It is not the best choice when the site is business-critical or the cause is unclear.

Get professional help if:

• You cannot access WordPress admin or hosting backups
• The site processes payments or bookings
• You may lose recent orders, leads, or form entries
• The error log points to custom code you do not understand
• The white screen keeps coming back
• You see signs of malware, redirects, unknown users, or Google warnings

A blank screen feels dramatic, but the fix is usually found by working methodically: preserve the site, read the logs, isolate plugins and themes, check server settings, and restore only when you understand the tradeoff.

If you would rather not troubleshoot it yourself, you can contact Ambrite with your site URL and a short description of what changed before the white screen appeared. Support is handled by email and ticket, so the details stay written down while the issue is investigated.

This article was written with the help of AI and reviewed by Ambrite. Pricing, features, and technical details may change, so always verify with official sources before making decisions.

Photo by Polina Zimmerman on Pexels