- Checked
- 2026-11-14
WordPress shows a white screen or a critical error
Both mean the same thing: PHP hit a fatal error while building the page. Newer WordPress says 'There has been a critical error on this website', some setups show nothing at all. The error itself is written down somewhere. Find it before you change anything.
Check the admin inbox first
When a plugin or theme causes a fatal error, WordPress emails the site's admin address with the name of the culprit and a link that opens the admin in recovery mode, with that plugin or theme paused. If the mail came, use the link, then update or deactivate what it names.
Find the error
Turn on the debug log in wp-config.php, above the line that says to stop editing:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Load the page again and read wp-content/debug.log. The last PHP Fatal error names a file, and its path names the plugin or theme. Turn debugging off afterwards and delete the log: anyone can download it from the web.
If WordPress could not write its own log, the web server or PHP-FPM error log has the same line: tail -n 50 /var/log/nginx/error.log.
Switch off the plugin or theme behind it
- With WP-CLI:
wp plugin deactivate plugin-name --skip-plugins --skip-themes. The two flags keep the broken code from loading while WP-CLI runs. Use--allin place of the name if you cannot tell which plugin it is. - Without WP-CLI: rename
wp-content/pluginstoplugins_old. WordPress deactivates every plugin it can no longer find. Rename the folder back and turn the plugins on one at a time to find the one that breaks. - If the error points at the theme, rename the active theme's folder in wp-content/themes. WordPress falls back to a default theme if one is installed.
- If the site broke right after an update, the plugin's changelog or support forum often already has the report and a fixed version.
Allowed memory size exhausted
If the error says Allowed memory size of 134217728 bytes exhausted, PHP hit its memory limit, 128 MB in that example. A plugin that suddenly needs far more is often the real problem, but raising the limit is a fair first step.
define( 'WP_MEMORY_LIMIT', '256M' ); in wp-config.php raises what WordPress asks for; by default it asks for 40 MB on a single site and 64 MB on multisite. Some hosts block the change. If the error stays, raise memory_limit in the php.ini PHP-FPM reads, and reload PHP-FPM.
What not to do
- Do not delete plugin folders. Renaming does the same job and can be undone.
- Do not leave
WP_DEBUG_DISPLAYon for a live site. Visitors then see file paths and error details. - Do not update everything at once while the site is down. Find the one change that broke it first.
When to stop and hand it over
Stop if the log names WordPress core files, if the error stays with every plugin off, or if the site is a shop and orders are waiting. Our Server Rescue is one incident at a fixed $69, with a same-day start listed at $109, and nothing to pay if we cannot fix it. You get the cause and every step taken, in order.
Questions people ask
- What causes the WordPress white screen of death?
- A PHP fatal error, most often from a plugin or theme update, a PHP upgrade the code was not ready for, or the memory limit.
- Why did the recovery email never arrive?
- The admin address may be old, or mail from the server lands in spam or is never sent. The debug log works without it.
- Did I lose my content?
- No. Content lives in the database, and the error comes from code. Deactivating a plugin keeps its settings.
- What does fixing it cost?
- With us, Server Rescue at $69 for the incident, or $109 for a same-day start. If we cannot fix it, you pay nothing.
Where each statement comes from
Checked against the sources on .
- WordPress: common errors (developer.wordpress.org)
- WordPress: debugging in WordPress (developer.wordpress.org)
- WordPress: editing wp-config.php (developer.wordpress.org)
- WP-CLI: wp plugin deactivate (developer.wordpress.org)
- WordPress core: fatal error recovery mode in 5.2 (make.wordpress.org)
More server help
- Error establishing a database connection
- 502 Bad Gateway on nginx
- Website hacked: the first steps
- Email from the server going to spam
- Server down: what to check first
- 504 Gateway Timeout
- Too many redirects
- 403 Forbidden on nginx or Apache
- Disk full: no space left on device
- SSL certificate expired: the fix
- Renewing a Let's Encrypt certificate
- DNS not resolving or still on the old server
- Moving a site to a new server
- Linux server hardening checklist
- All server help guides
