Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

WordPress white screen: how to troubleshoot safely

Published August 2026 · 8 min read

A blank WordPress page gives you almost no information in the browser, which is why the next useful place to look is the server-side error path. The goal is to find the first failing component without turning one outage into several changes at once.

Check the HTTP status and error logs

A blank page with HTTP 500 points toward a server-side application failure. Review PHP and web-server logs at the exact request time. A successful HTTP response with no content suggests a different application path than a hard server error.

Look at the last change

Plugin updates, theme changes, PHP version changes, edited code, deployments, and exhausted disk space are common starting points. If the site failed immediately after a known change, test or roll back that change before touching unrelated settings.

Disable components methodically when needed

If logs point toward a plugin or theme and the dashboard is unavailable, use a safe control-panel or filesystem method to isolate one component at a time. Keep notes so you can reverse each diagnostic change.

Do not leave debugging output exposed

Detailed errors can reveal paths, configuration, or other information to visitors. Use server logs for diagnosis and return production error display to a safe state after the incident.

Next step

A WordPress white screen often means a hidden PHP failure, exhausted resource, plugin conflict, or theme problem. Collect evidence before randomly disabling components.

Get WordPress hosting help

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move