WordPress White Screen: How to Troubleshoot a Blank Website

A WordPress white screen can be a PHP fatal error, a failed update or a problem limited to one template. Preserve a backup and the error evidence before disabling components. If the whole site will not load, start with our WordPress website not loading guide; the quickest safe route depends on whether the dashboard still opens.

Establish the scope of the WordPress white screen

Test the homepage, an inner page and wp-admin. Note whether you see a blank screen, a critical-error notice or a server error. Check another browser only to rule out a local display problem. Record the time and any recent theme, plugin or PHP update. A problem limited to one page may involve its builder or template.

Look for a recovery message

WordPress may email the administrator a recovery-mode link when it detects a fatal error. If available, use that link to access the dashboard and identify a paused plugin or theme. Keep the email private and avoid forwarding the link publicly. Recovery mode is a diagnostic aid, not proof that the underlying conflict is fixed.

Use logs to diagnose a WordPress white screen

The hosting PHP error log can point to the failing file and line near the outage time. A warning from a different time may be unrelated. If a developer enables diagnostic logging, keep logs away from public access and prevent public error display throughout the investigation. Record the exact component and version involved before changing anything.

Isolate the suspected component

If a specific plugin was just updated and the dashboard is unavailable, a hosting file manager or SFTP can temporarily rename that plugin directory to test the cause. Record its original name. Do not disable every plugin at once unless there is no narrower path, and check functionality when restoring components. Avoid making the site’s configuration less secure for a prolonged test.

Verify recovery from a WordPress white screen

A known-good backup can recover the site, but restoring a full database may overwrite recent leads or orders. Prefer the smallest repair that addresses the error. Test important pages, forms, login and any payment or OTP step after the site returns. Confirm the original fatal error no longer appears in logs.

Related: WordPress emergency support and post-update troubleshooting.

Prepare a useful support handover

The WordPress troubleshooting reference covers common failure and recovery paths. When seeking help, provide the affected URL, error time, recent component changes and whether the dashboard opens. Share only the relevant redacted log lines, not a full database or credentials. This makes it easier to test a specific cause while protecting customer information and avoiding unnecessary disruption.