WordPress "Critical Error on This Website": Find the Plugin

“There has been a critical error on this website” means WordPress hit a fatal PHP error and stopped loading the page. In almost every case the cause is a plugin or theme that was just installed, updated or edited. The fix is to find out which one, using the recovery-mode email or the debug log, and then disable it from wp-admin or by renaming its folder over FTP or your host’s file manager.

Key Takeaways

• The message is WordPress’s generic way of saying a fatal PHP error occurred. It is not a hack.
• Check the admin email address for a “Your Site is Experiencing a Technical Issue” message first. It names the plugin or theme at fault.
• If there is no email, turn on WP_DEBUG_LOG and read wp-content/debug.log.
• Disabling a plugin is as simple as renaming its folder in wp-content/plugins.
• Take a backup before you edit or delete anything.

A site that was fine this morning and now shows only a short grey message is alarming, but this error is one of the more fixable ones. WordPress is telling you something specific broke. Your job is to find out what.

What Does “There Has Been a Critical Error on This Website” Mean?

It is the friendly wrapper WordPress (version 5.2 and later) shows when PHP throws a fatal error that stops the page from finishing. Before 5.2 you would have seen a blank page instead, which is the white screen of death. The two are close relatives. The critical error screen is simply the more helpful version.

WordPress also tries to protect you. When it catches a fatal error it can enter recovery mode, which pauses the broken plugin or theme just for your login session and emails you a special link to get in.

What Causes the Critical Error?

The error message does not tell you the cause, but the usual suspects are well known:

• A plugin or theme update that is incompatible with your PHP version, your WordPress version or another plugin.
• A newly installed plugin that conflicts with something already on the site.
• A syntax mistake in a file you edited by hand, such as functions.php.
• A PHP version change made by your host, which breaks older code.
• Running out of memory, which has its own fix in the white screen guide.
• A corrupted or incomplete update, often after an interrupted download.

How Do You Fix the Critical Error?

Work through these steps in order. Stop as soon as the site loads again. Before you start, take a backup of the site files and database, or ask your host to take a snapshot.

1. Check your email for the recovery-mode message

WordPress sends an email to the site’s administration email address (the one under Settings > General) with the subject “Your Site is Experiencing a Technical Issue”. It names the plugin or theme that caused the error and includes a recovery link.

Click the link, log in, and WordPress will show a notice that recovery mode is active. Go to Plugins (or Appearance > Themes), and deactivate the item it named. Then exit recovery mode from the admin bar. The link expires after a day, so use it promptly. Check your spam folder too.

2. Read the error log if no email arrived

If the email never came, or the site cannot send mail, turn on logging. Connect by FTP, SFTP or your host’s file manager and open wp-config.php in the site root. Find the line that says “That’s all, stop editing” and add these lines above it:

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

Reload the broken page once, then open wp-content/debug.log. Look for the most recent line beginning “PHP Fatal error”. The file path in that line tells you the culprit, for example:

PHP Fatal error: Uncaught Error: Call to undefined function ... in /wp-content/plugins/example-plugin/main.php:42

Here the folder name example-plugin is the plugin to disable. If the path points into wp-content/themes/, the theme is at fault.

3. Disable the plugin over FTP or file manager

Go to wp-content/plugins/ and rename the offending folder, for instance from example-plugin to example-plugin-disabled. WordPress cannot find it, so it deactivates the plugin automatically. Reload the site. If it comes back, log in, and decide whether to update, replace or remove the plugin.

If you cannot tell which plugin it is, rename the whole plugins folder to plugins-off. If the site loads, rename it back and then rename plugin folders one at a time until the error returns.

4. Switch to a default theme if the theme is at fault

If the log points to your theme, go to wp-content/themes/ and rename the active theme’s folder. WordPress will fall back to a default theme such as Twenty Twenty-Five, as long as one is installed. If none is installed, upload one from wordpress.org first.

5. Undo your last edit or update

If you edited a file by hand just before the error, revert that change. If an update triggered it, reinstall the previous version of the plugin from your backup or from the plugin’s page on wordpress.org (look under Advanced View for older versions).

6. Turn debugging off again

Once you are fixed, set WP_DEBUG to false or remove those lines, and delete debug.log, which can contain details you do not want public.

What If the Error Is Still There?

If renaming every plugin and the theme made no difference, the problem may sit in WordPress core files or the PHP version itself. Re-upload a fresh copy of WordPress (everything except wp-content and wp-config.php), and ask your host which PHP version is active. If the log mentions memory, raise the limit as described in the white screen of death guide. If your visitors see a generic server message instead, read about the 500 Internal Server Error.

How Do You Stop It Happening Again?

• Update with a safety net. Take a backup first, update one plugin at a time, and check the site after each. Our guide on whether a plugin update is safe covers the pre-checks.
• Use a staging copy for big changes.
• Keep PHP and WordPress reasonably current, and remove plugins you no longer use.
• Never edit theme files live. Use a child theme and test elsewhere.
• Monitor the site. WordPress monitoring means you find out in minutes, not when a customer emails.

TalkToWP checks every site every 5 minutes on every plan, Free included. When a critical error appears, it tells you which plugin or update caused it and gives you the fix in plain English, so you skip the log-reading. The free plan covers one site, and you can start here.

Frequently Asked Questions

Is the critical error a sign my site was hacked?

Usually not. It is most often a plugin or theme conflict or a coding mistake. That said, a compromised file can also trigger a fatal error, so if you did not change anything and the log shows an unfamiliar file, run a security scan and change your passwords.

I never received the recovery-mode email. What now?

Check spam, then confirm the administration email under Settings > General is one you can read. If you cannot log in to check, enable WP_DEBUG_LOG and read wp-content/debug.log instead. Mail from some hosts fails silently, so the log is the more reliable route.

Will I lose my content when I rename a plugin folder?

No. Posts and pages live in the database, not in the plugin folder. Renaming the folder only deactivates the plugin. Some plugin settings may reset if you delete the plugin, so rename rather than delete until you are sure.

Can I get the site back without FTP access?

Yes, if the recovery email arrived, because recovery mode lets you deactivate the plugin from wp-admin. Otherwise most hosts offer a file manager in their control panel (cPanel, Plesk and similar) that does the same job as FTP.

How is this different from the white screen of death?

The two are the same kind of fatal error. The critical error message is what WordPress 5.2 and later show when it can catch the failure, while the white screen appears when it cannot. The fixes overlap almost completely.