Troubleshooting
How to Uninstall Broken Plugins on WordPress: Causes and Fixes

Short answer
If you can still log in, deactivate the plugin and delete it from the Plugins screen. If the site is down, rename or delete the plugin's folder inside wp-content and then plugins, using FTP or your host's File Manager, then clean up leftover settings.
Key takeaways
- Deleting from the dashboard runs the plugin's own uninstall routine.
- Renaming the folder by FTP is the safest fix when the site is down.
- Recovery mode emails let you log in with the faulty plugin paused.
- WP-CLI with --skip-plugins can remove plugins that crash WordPress.
- Check mu-plugins, drop-ins, wp-config and .htaccess for leftovers.
How do you uninstall a broken plugin on WordPress?
If the dashboard still loads, deactivate and delete the plugin from Plugins > Installed Plugins; if the site is down, rename or delete the plugin's folder in wp-content/plugins using FTP or your host's File Manager.
A broken plugin can crash the whole site, lock you out of the admin area or simply refuse to delete. Each case has a different route, but they all end with the plugin's folder removed from the server.
Before you start, take a backup if you can. Even a broken site is worth saving, because a wrong deletion can make things worse.
| Situation | Best method | Removes plugin data? |
|---|---|---|
| Dashboard works | Deactivate, then Delete in Plugins screen | Usually, if the plugin has an uninstall routine |
| Critical error with recovery email | Use the recovery mode link, then delete | Usually |
| Site or admin down | Rename or delete the folder via FTP or File Manager | No, leftovers stay |
| You have SSH | WP-CLI plugin deactivate and delete | Usually |
| Plugin keeps coming back | Check mu-plugins and drop-in files | Manual cleanup needed |
What makes a plugin broken?
A plugin breaks when its code clashes with your PHP version, WordPress version, theme or another plugin, or when an update fails halfway and leaves files missing.
Typical signs include a There has been a critical error message, a blank white screen, a 500 error, or an admin area that loads without styles.
Failed automatic updates sometimes leave a .maintenance file in the site root, which shows a maintenance message to everyone. Delete that file by FTP to bring the site back.
If you are not sure which plugin is at fault, our guide on finding the plugin causing a problem explains how to narrow it down.
Fix 1: Delete it from the Plugins screen
When you can still log in, go to Plugins > Installed Plugins, click Deactivate under the broken plugin, then click Delete and confirm.
WordPress only shows the Delete link for inactive plugins. Deleting through the dashboard also runs the plugin's own uninstall routine, if it has one, which can remove its settings and database tables.
The plugin handbook on uninstall methods explains how plugins clean up after themselves. Not every plugin does, so some data may remain.
If deletion fails with a permissions error, the server may not let WordPress remove files. Use FTP instead, or fix file ownership with your host.
Fix 2: Use the recovery mode link
When WordPress catches a fatal error, it emails the site admin a special login link that opens the dashboard in recovery mode with the faulty plugin paused.
This feature arrived in WordPress 5.2. The announcement on Make WordPress Core describes how it works.
Click the link in the email, log in, and you will see a notice naming the plugin that caused the error. Deactivate it, then delete it from the Plugins screen.
If the email never arrives, your site may not be sending mail. Our guide on the critical error message covers what to do without the email.
Fix 3: Rename or delete the folder with FTP
Connect with FTP or SFTP, open wp-content/plugins, and rename the broken plugin's folder; WordPress will deactivate it on the next page load, and you can then delete the folder.
Renaming first is safer than deleting. If you picked the wrong folder, rename it back and nothing is lost.
If you cannot tell which plugin broke the site, rename the whole plugins folder to plugins-off. That disables every plugin at once. Then rename it back and switch folders off one at a time to find the culprit.
Add something like -off to the name, such as contact-plugin-off. Reload your site. If it works again, you found the culprit.
Need login details? Our guide on getting FTP access to WordPress explains where to find them in your hosting panel.
Deleting the folder this way removes the code but skips the plugin's uninstall routine. Its settings and tables stay in the database until you clean them up.
Fix 4: Use your host's File Manager
If you do not have an FTP client, open the File Manager in cPanel, Plesk or your host's dashboard and rename or delete the plugin folder the same way.
The File Manager works in your browser. Navigate to your site's root folder, then wp-content, then plugins.
Most File Managers have a Rename and Delete option on right-click or in a toolbar. Some move deleted files to a trash folder in your hosting account, which you may need to empty.
Fix 5: Use WP-CLI over SSH
With SSH access, run wp plugin deactivate followed by the plugin's folder name, then wp plugin delete, and WordPress removes it cleanly.
The commands look like this:
wp plugin deactivate broken-plugin --skip-plugins
wp plugin delete broken-plugin
The --skip-plugins flag stops plugins from loading while the command runs, which helps when the broken plugin also crashes WP-CLI. The wp plugin delete documentation lists the options.
Use wp plugin list first to see the exact folder names. They do not always match the plugin's display name.
Fix 6: Deactivate it in the database
As a last resort, open phpMyAdmin, find the active_plugins row in the options table and remove the plugin's entry, or reset the value to deactivate all plugins.
This is delicate. The value is a serialized PHP array, and one wrong character can break it. Back up the database before you touch it.
Resetting the whole value to a:0:{} deactivates every plugin at once. Our guide on deactivating all plugins without admin access walks through this method step by step.
What if the plugin keeps coming back?
A plugin that reappears is usually a must-use plugin, a drop-in file, part of your theme, or being reinstalled by your host or a management tool.
Check the wp-content/mu-plugins folder. Files there load automatically and do not show the usual Deactivate link. Hosts often place their own tools here.
Caching and security plugins may leave drop-in files such as advanced-cache.php or object-cache.php directly in wp-content. Delete those only if the plugin that created them is gone.
Some hosts and management dashboards reinstall plugins they rely on. Check your hosting panel or management service settings if a plugin returns overnight.
How do you clean up after removing a broken plugin?
Remove leftover database tables and options, extra lines in wp-config.php and .htaccess, and scheduled tasks the plugin created.
Cache plugins often add a WP_CACHE line to wp-config.php and rewrite rules to .htaccess. Remove those lines once the plugin is gone. Our guide on editing .htaccess shows how to do it safely.
Leftover database tables usually share a prefix with the plugin's name. Drop them only if you are sure no other plugin uses them.
The free Health Check & Troubleshooting plugin can help confirm the site runs cleanly afterwards, by testing with plugins switched off for your session only.
How do you stop it happening again?
Test updates on a staging site, keep backups before every update, and remove plugins you no longer use, since fewer plugins means fewer chances of a clash.
Check that your PHP version matches what your plugins support. Major PHP upgrades are a common trigger for old plugins breaking.
The PHP supported versions page shows which releases still get security fixes. Plugins that have not been updated for newer PHP versions are a warning sign.
Before a PHP upgrade, check each plugin's page for a Tested up to note and recent updates. Replace abandoned plugins first, so the upgrade does not break the site.
Our guide on removing unused plugins and themes safely covers a regular cleanup routine.
Frequently asked questions
Why can't I delete a plugin in WordPress?
The Delete link only appears for deactivated plugins. If it still fails, the server may not allow WordPress to remove files due to permissions. Rename or delete the folder with FTP or the File Manager, or ask your host to fix file ownership.
Does deleting a plugin folder by FTP remove its data?
No. Deleting the folder removes the code but skips the plugin's uninstall routine, so settings, database tables and scheduled tasks stay behind. Clean them up manually or reinstall and delete the plugin from the dashboard.
How do I find which plugin broke my site?
Check the recovery mode email, the error message or the PHP error log, which often names the plugin folder. Otherwise rename plugin folders one at a time and reload the site until it works again.
Is it safe to delete files in the mu-plugins folder?
Only if you know what they do. Hosts often place their own management or caching tools there. Removing them can break features or support access, so check with your host before deleting anything you did not add.
What does the .maintenance file do?
WordPress creates it during updates to show a maintenance message. If an update fails, the file can stay behind and lock visitors out. Deleting it from the site root by FTP restores normal access.
Sources
- Uninstall Methods WordPress Plugin Handbook
- Fatal Error Recovery Mode in 5.2 Make WordPress Core
- wp plugin delete WP-CLI Commands
- Health Check & Troubleshooting WordPress.org Plugins
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


