How to Find the Plugin Causing a WordPress Critical Error

Transform Your Business with ZalmiRank!

Take your digital marketing to the next level with data-driven strategies and innovative solutions. Let’s create something amazing together!

Quick answer: To find the plugin causing a WordPress critical error, first check the site admin email for “Your Site is Experiencing a Technical Issue”, which names the plugin. If there is no email, turn on the debug log and read wp-content/debug.log: the folder name after wp-content/plugins/ in the fatal error line is the plugin. If the log is empty, disable plugins in halves until the error disappears.

You updated a plugin, or maybe you did nothing at all, and now your site shows “There has been a critical error on this website.” The good news: in most cases one plugin is to blame, and you can find it in minutes without losing any content.

This guide shows six ways to find it, from the fastest to the most thorough. Start with Method 1 and stop as soon as you have your answer.

Before you start: take a backup

If your host offers one-click backups, take one now. None of the steps below delete content, but a backup means you can always get back to where you are.

Method 1: Read the recovery mode email

Since WordPress 5.2, when a plugin or theme crashes the site, WordPress emails the site admin a message titled “Your Site is Experiencing a Technical Issue”. It usually names the plugin or theme that failed and includes a recovery mode link.

  1. Search your inbox and spam folder for that subject line.
  2. Click the recovery mode link and log in.
  3. Go to Plugins. WordPress shows which plugin was paused. Deactivate it.

No email? It goes to the address in Settings › General › Administration Email Address, which may be an old address or your developer’s. Some servers also cannot send email at all. Move on to Method 2.

Method 2: Read the debug log

The debug log tells you the exact file that failed. Open wp-config.php in your hosting file manager and add these lines above the line that says “That’s all, stop editing”:

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

Reload your site once, then open wp-content/debug.log. Look for a line that starts with PHP Fatal error. It will look something like this:

PHP Fatal error: Uncaught Error: Call to undefined function example_function()
in /home/user/public_html/wp-content/plugins/example-plugin/includes/class-main.php:142

The folder name straight after wp-content/plugins/, here example-plugin, is the plugin causing the error. If the path shows wp-content/themes/ instead, it is your theme.

Important: when you are done, set WP_DEBUG back to false and delete debug.log. Leaving it on can expose file paths and error details to anyone.

Method 3: Check your hosting error log

Even with WordPress debug off, most hosts keep a PHP error log. In cPanel, look under Metrics › Errors or open the error_log file in your site folder. On Hostinger, use the error logs section of your website dashboard. Read it the same way as Method 2.

Method 4: Use the Health Check troubleshooting mode

If you can still reach wp-admin, install the free Health Check & Troubleshooting plugin from WordPress.org. Its troubleshooting mode turns off all plugins and switches to a default theme for your login only, so visitors see no change.

  1. Go to Tools › Site Health › Troubleshooting and enable troubleshooting mode.
  2. Turn plugins back on one at a time from the admin bar.
  3. When the error appears, the last plugin you enabled is the cause.

Method 5: Disable plugins in halves (the fastest manual method)

If there is no email and the log is empty, test plugins in groups instead of one by one. With 20 plugins, testing one at a time can take 20 rounds. Splitting them in half takes at most 5.

  1. In your file manager, open wp-content/plugins.
  2. Rename half of the plugin folders by adding -off to the end, for example contact-form-7-off.
  3. Reload the site. If the error is gone, the cause is in the half you turned off. If it is still there, it is in the other half.
  4. Rename the innocent half back, then split the guilty half again.
  5. Repeat until one plugin is left. That is your cause.

Renaming a folder only deactivates the plugin. Its settings stay in the database, so nothing is lost when you rename it back.

Method 6: Use WP-CLI (for developers)

If your host gives you SSH access with WP-CLI, you can test plugins without touching wp-admin:

wp plugin list --status=active
wp plugin deactivate example-plugin
wp --skip-plugins option get home

If wp --skip-plugins works but normal commands fail, a plugin is the cause. Deactivate plugins one at a time until normal commands work again.

Not a plugin? Check these next

  • Your theme: rename the active theme folder in wp-content/themes so WordPress falls back to a default theme.
  • Must-use plugins: files in wp-content/mu-plugins load automatically and do not appear in the normal plugin list.
  • Drop-ins: files such as object-cache.php or advanced-cache.php in wp-content, often left by caching plugins.
  • PHP version: if your host recently upgraded PHP, an older plugin or theme may not support it.
  • Memory limit: “Allowed memory size exhausted” in the log means you need a higher limit or a lighter plugin.
  • Hacked files: unknown files or admin users mean the error may be caused by malware.

You found the plugin. Now what?

  • Update it if an update is available. Many crashes are fixed in the next release.
  • Roll back to the previous version if the crash started after an update.
  • Check compatibility with your PHP and WordPress versions on the plugin’s WordPress.org page.
  • Report it to the plugin developer with the exact error line from your log.
  • Replace it with a maintained alternative if it has not been updated in a long time.

Frequently asked questions

How do I know which plugin caused the WordPress critical error?

Check the admin email for “Your Site is Experiencing a Technical Issue”, which names the plugin. If there is no email, turn on WP_DEBUG_LOG and read wp-content/debug.log: the folder name after wp-content/plugins/ in the fatal error line is the plugin.

Can I find the plugin without access to wp-admin?

Yes. Use your hosting error log or debug.log, or rename plugin folders through your hosting file manager or SFTP. None of these need wp-admin.

Will deactivating plugins delete my data?

No. Deactivating or renaming a plugin folder does not delete its settings or your content. Only deleting a plugin through wp-admin can remove its data.

What if no plugin is the cause?

Check the theme, must-use plugins in wp-content/mu-plugins, drop-in files such as object-cache.php, your PHP version and the memory limit. Hacked files can also cause critical errors.

Still stuck? ZalmiRank fixes WordPress critical errors for $49, within 24 hours of access or your money back, with a full backup first. See our WordPress critical error fix service or book a free call.

Written by Shahab Ali, founder of ZalmiRank, a WordPress specialist with 10+ years of experience fixing and growing business websites. Last updated November 13, 2026.