Black FridayCyber Monday 2026
14Days
15Hrs
34Mins
46Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress Critical Error: Recover Your Website Safely

A WordPress critical error means a fatal PHP error stopped the page. Use the recovery email and recovery mode, read a redacted log, isolate the plugin or theme, or restore a known-good backup.

wpallsolution Updated 8 min read

WordPress critical error is the message “There has been a critical error on this website” that WordPress shows when a fatal PHP error stops the page from loading. It usually comes from a plugin, a theme or custom code, often right after an update. The good news is that WordPress has a built-in recovery mode that is designed for this situation. This guide starts with recovery, so the site works again, and only then looks for the cause.

Quick answer

Check the inbox of the site’s administrator email for a message from WordPress about a technical issue. It contains a secret link to recovery mode, which pauses the plugin or theme that caused the fatal error so you can log in. In the admin area, deactivate or fix that extension. If you receive no email or cannot log in, deactivate plugins from the file manager or WP-CLI, switch to a default theme if a theme change caused it, or restore a known-good backup. Read the error details before you change anything, and never post an unredacted log publicly.

How this guide was prepared: the steps follow the WordPress documentation listed under Sources, read on October 19, 2026. We did not reproduce your exact error, so the steps are research-based. The right fix depends on the error message, your host and your plugins, and a host’s file manager and backup tools differ.

Before you change anything

  • Take a backup of files and database first, even of a broken site, so you can undo your changes. The WordPress handbook says to back up your database regularly and always before an upgrade. See Is your WordPress backup really safe?
  • Note what changed. Which update, install or edit happened just before the error?
  • Do not edit live code in a hurry. One wrong character in a PHP file can make things worse.
  • Protect secrets. Logs and wp-config.php can contain database passwords, keys and personal data. Redact them before sharing.

WordPress critical error: the decision tree

WordPress critical error flowchart: five questions covering the recovery email, recovery mode, plugin deactivation, theme switching and backup restore
Five questions, asked in order, lead from the error screen back to a working site.
  1. Did you receive a recovery email at the admin address? If yes, use the recovery link (Step 1).
  2. Can you log in through recovery mode? Then pause or deactivate the named extension (Steps 2 and 3).
  3. No email and no login? Deactivate plugins by file manager or WP-CLI (Step 4).
  4. Did it start after a theme change? Switch to a default theme (Step 5).
  5. Is nothing working? Restore a known-good backup (Step 6).

Symptoms and likely causes

What you seeLikely causeStart with
“Critical error” message on the siteA fatal PHP error in a plugin, theme or codeSteps 1 and 2
Blank white screenA PHP or database error with no displaySteps 3 and 4
Error right after a plugin updatePlugin incompatible with PHP or another pluginSteps 3 and 4
Error right after a theme change or editTheme or edited file with an errorStep 5
No recovery email receivedEmail not delivered, or the admin address is wrongStep 4
Admin works, front end does notTheme or a front-end pluginSteps 3 and 5

6 steps to recover from a WordPress critical error

Step 1: Use the recovery email

The WordPress core team describes recovery mode, added in WordPress 5.2: when a fatal error occurs, a user-facing screen says the site is experiencing technical difficulties, and an email is sent to the administrator (and super admin) address with a secret link to recovery mode. Check the spam folder too. Open the link in the same browser you will use to log in, because recovery mode is tied to a cookie on that client, not to a specific user.

Step 2: Log in and read what was paused

In recovery mode, WordPress pauses the plugins and themes that caused a fatal error for your browser session, so you can log in as usual. After login, an admin notice says recovery mode is on and lists the paused extensions and the exact errors. Write down the extension’s name, the file and the line from the message. That is the best clue you will get. You can also use the Site Health screen under Tools for a summary of your site’s status.

Step 3: Deactivate, update or replace the culprit

The core team lists the options: completely deactivate the extension (usually a temporary fix that restores service at once), fix the problem if you have the technical ability, or contact the extension’s author with the exact error. When you leave recovery mode with the exit button in the admin bar, all extensions run normally again, and if one is still broken, the fatal error returns. So deactivate or replace it before you exit. If the cause is a recent update, see WordPress 500 internal server error after a plugin update for rolling back safely.

Step 4: Deactivate plugins without the admin area

If you cannot log in, the WordPress troubleshooting FAQ describes two methods. In a file manager or FTP, open wp-content and rename the plugins folder (for example to plugins.hold), log in, rename it back, and reactivate plugins one at a time. This keeps settings but disables everything. The second method edits the active_plugins option in the database to a:0:{}, which is best done with your host’s help. With WP-CLI, wp plugin deactivate can deactivate a named plugin or, with the --all flag, all plugins. Our guide How to find the plugin that broke your site explains how to find the culprit afterwards.

Step 5: Rule out the theme and recent edits

The WordPress handbook says a theme can cause the white screen, especially after you have just activated a new theme, and suggests activating a default WordPress theme. If you cannot reach the admin, rename the active theme’s folder in wp-content/themes so WordPress falls back to a default theme (one must be installed). If you edited functions.php or added a code snippet, undo that edit first.

Step 6: Read a redacted debug log, or restore a backup

The error message names a file and line. If it does not, WordPress documents debug logging: with WP_DEBUG and WP_DEBUG_LOG set to true and WP_DEBUG_DISPLAY set to false, errors go to wp-content/debug.log instead of the page. The handbook says debug tools are meant for local testing and staging, not live sites, so switch them off afterwards and delete the log, because it can contain sensitive paths and data. Never publish the log without redacting paths, usernames and keys. If you cannot find or fix the cause, restore the most recent backup that you know was good (files and database together), then reapply updates one at a time on staging.

Version and hosting differences

  • Recovery mode needs WordPress 5.2 or later, and the email depends on working mail on your site. Your host may offer its own recovery tools.
  • Some hosts add a maintenance page, a firewall or a PHP version switch that changes what you see. Ask your host for the PHP error log.
  • Managed hosts often provide one-click restores and staging. Use them.
  • A PHP version change is a common trigger. Check what your host recently changed.

How to verify the fix

  • The front end and the admin area load without errors, logged in and logged out.
  • Forms, checkout and other key features work. See WooCommerce checkout not working if you sell online.
  • The Site Health screen shows no new critical issues, and debug display is switched off.
  • You removed any debug log you created.

How to prevent it from happening again

  • Update on staging first, one plugin at a time, as in how to update WordPress plugins safely.
  • Keep a tested, recent backup and a way to restore it.
  • Make sure the administrator email is a real inbox, so the recovery email can reach you.
  • Follow a regular maintenance routine and remove plugins you do not use.

Frequently asked questions

Is my site hacked?

Not necessarily. Most critical errors come from plugin, theme or PHP compatibility problems, but check for unexpected files and users if you see anything suspicious.

I got no recovery email. What now?

Check the spam folder and the administrator address, then deactivate plugins from the file manager (Step 4).

Can I fix it by turning on WP_DEBUG?

Debug mode only shows or logs errors. It does not fix them, and the handbook recommends it for staging.

Should I delete the broken plugin?

What to do next

Recover access, note the extension named in the error and change one thing at a time. If the WordPress critical error is still there, send your host or the plugin author the exact error text, your PHP and WordPress versions and what changed, with secrets removed. If you would like a person to look, wpallsolution offers emergency WordPress fixes and independent plugin support. We cannot promise a fix without seeing your setup.

Sources and official documentation

Last reviewed: October 19, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation or Automattic.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us