Deactivate a WordPress plugin without accessing the dashboard

Plugins are normally deactivated from Plugins > Installed Plugins. If a critical error prevents you from accessing the dashboard, first check the administration email: WordPress may have sent a link to enter its recovery mode. That session can skip the affected component so you can manage the site; afterwards, check whether you have actually deactivated it for all visitors.

If you cannot use that mode:

1. Go in through the File Manager or FTP.
2. Open wp-content/plugins and find the problematic plugin's directory.
3. Rename it temporarily, for example from nombre-plugin to nombre-plugin.desactivado. Do not delete it.
4. Check the website and go to Plugins so WordPress records the deactivation.
5. Give the directory back its original name. The plugin will stay deactivated until you decide to update, replace or activate it again.

If you do not know which plugin is causing the error, you can temporarily rename wp-content/plugins, check access and then restore its original name. Visit Plugins so WordPress detects the missing files before restoring the name. Check the state of the list and selectively reactivate only what you have tested.

Renaming preserves the files and lets you revert the test. Deleting the directory does not run the plugin's uninstall procedure and can make you lose files needed to diagnose or recover its configuration.

Scope and checks

Run the test on a clone or during controlled maintenance if the plugin handles payments, permissions, forms or security. Deactivating it can restore access while leaving an essential feature out of service. Keep the error and the time before changing several components.

The wp-content/plugins directory does not cover every case: mu-plugins, drop-in files such as object-cache.php and network-activated plugins in a Multisite network each need their specific scope reviewed. Do not rename files at random if the error persists.

Renaming a folder stops WordPress finding the plugin through its usual path, but it does not turn its files into a private quarantine. If you suspect an intrusion, keep evidence outside the public root and follow the clean-up procedure; do not leave compromised code reachable under another name.

Before reactivating it, update or fix the cause in the test environment and check that it works. Restoring the original name before WordPress has recorded the deactivation can make it load again.