WordPress White Screen of Death & Common Errors: Fix Guide (2026)

The white screen of death is the most alarming and usually the least serious WordPress error. Your site isn't gone — PHP just crashed before it could print anything. I've fixed hundreds of these. The sequence below is the exact order I try things, because order matters: each step either fixes it or tells you where to look next.

Before anything: don't panic-delete

Your content is in the database. A white screen almost never means data loss. The people who lose data are the ones who start deleting plugins and themes in a panic. Breathe. Follow the sequence.

Step 1: Enable debugging (2 minutes)

Add to wp-config.php, just above "That's all, stop editing!":

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Reload the page, then check wp-content/debug.log. Nine times out of ten, the log names the exact plugin file and line number that crashed. This one step turns a mystery into a to-do item. Turn debugging back off when you're done — debug output on a live site is a security issue.

Step 2: The plugin test (5 minutes)

If you have FTP/file access: rename the wp-content/plugins folder to plugins-old. WordPress deactivates everything at once. If the site comes back, it's a plugin — rename the folder back, then reactivate plugins one by one until it breaks again. That's your culprit.

No file access? Most hosts have a file manager in cPanel. Same process.

Step 3: The theme test

Still white? Switch to a default theme (Twenty Twenty-Four). Via FTP, rename your active theme's folder — WordPress falls back to a default theme automatically. If the site loads, your theme (or its latest update) is the problem.

Step 4: Memory limit

If the log shows "Allowed memory size exhausted," add to wp-config.php:

define('WP_MEMORY_LIMIT', '256M');

If your host caps it lower, that's a hosting conversation. Page builders and WooCommerce on 128M is asking for exactly this error.

Other errors, same logic

"There has been a critical error on this website" — WordPress 5.2+ catches the crash and emails the admin. Same sequence: debug log, plugin test, theme test. The email sometimes names the culprit directly.

500 Internal Server Error — often a corrupted .htaccess. Rename it, reload; WordPress regenerates a clean one. Then re-save your permalink settings.

Stuck in "Briefly unavailable for scheduled maintenance" — a failed update left .maintenance in the root. Delete that one file via FTP. Done.

Error establishing database connection — check wp-config.php credentials first (did anything change?), then ask your host if MySQL is down. This one is rarely your code.

When to stop DIY-ing and call someone

• The debug log points somewhere you don't understand
• It's WooCommerce and orders are involved — don't experiment on revenue
• The error returns after you "fixed" it (there's a deeper cause)
• You've spent 2 hours and the site is still down (your time has a price)

A developer fixes most of these in under an hour because we've seen the pattern before. That's the whole trick — pattern recognition from hundreds of cases.

Get it fixed now

Site down = money and trust leaking every hour. I fix WordPress errors fast — most resolved same-day.

• WhatsApp me now (fastest): Chat on WhatsApp
• Share your project brief: fysalyaqoob.com/contact#contact-form
• Prevent the next one: WordPress maintenance plan — $100/mo