Deactivate a WordPress Plugin Without Admin

What this problem looks like

Plugins load on every request, including wp-admin. A fatal error in plugin code prevents the Plugins list from rendering, so you cannot click Deactivate. File-level deactivation skips WordPress hooks entirely because PHP never loads that folder.

Step 1: Deactivate a single plugin via File Manager, SFTP, or FTP

Connect via File Manager, SFTP, or FTP.
Browse to wp-content/plugins/.
Find the plugin folder slug, for example woocommerce or contact-form-7.
Rename it by adding .off at the end: woocommerce.off.
Reload the site and wp-admin.

WordPress treats missing plugin folders as deactivated. The plugin row may show a “file not found” notice in admin until you delete or reinstall it. That is normal after manual deactivation.

Step 2: Deactivate all plugins at once

When you do not know which plugin failed, rename the whole plugins directory:

Go to wp-content/ in File Manager, SFTP, or FTP.
Rename plugins to plugins.disabled.
Reload the site and wp-admin.
If the site works, rename plugins.disabled back to plugins. WordPress will see the plugins again, but they should remain deactivated.
In wp-admin, activate plugins one at a time and reload the site after each activation.
When the fatal error returns, the plugin you just activated is the culprit.

Step 3: Deactivate with WP-CLI (SSH)

Only run these commands if you have SSH access to the server. WP-CLI updates the database active_plugins option directly without renaming folders:

bash

cd /path/to/wordpress
wp plugin list
wp plugin deactivate woocommerce
wp plugin deactivate --all

Step 4: Must-use plugins and drop-ins

Plugins in wp-content/mu-plugins/ load automatically and do not appear on the normal Plugins screen. Rename or remove the offending PHP file in mu-plugins if a must-use plugin is the cause.

Drop-ins like advanced-cache.php or object-cache.php sit in wp-content/ itself. Rename them only if you know which caching layer they belong to, or you may disable caching entirely.

Step 5: After the site is back

Update the plugin that caused the fatal, or replace it with a supported alternative.
Test checkout, forms, and cron-dependent features.
Re-enable auto-updates only on low-risk plugins.
Consider staging or a maintenance plan for future updates.

When to stop DIY and hire help

If the site still fatals after all plugins are off, the theme or core may be corrupt. BugShield diagnoses plugin conflicts at a confirmed fixed price without hourly billing surprises.

Questions answered

Deactivating WordPress plugins without wp-admin FAQs

Answers about using File Manager, SFTP, WP-CLI, and the database when a broken plugin blocks dashboard access.

Does renaming plugins delete settings?

No. Settings stay in the database. WordPress simply stops loading that plugin’s code until you rename the folder back or reinstall.

Can I deactivate plugins from the database?

Yes, by editing the active_plugins row in wp_options, but it is error-prone due to serialized PHP data. File Manager, SFTP, FTP, or WP-CLI is safer for most users.

What if only the front end is broken but admin works?

Deactivate the suspect plugin from wp-admin normally, or use a health check plugin to identify front-end-only fatals.

When should I hire BugShield instead?

If the site still fatals after all plugins are off, the theme or core may be corrupt. BugShield diagnoses plugin conflicts at a confirmed fixed price.

Where are WordPress plugin folders stored?

Standard plugins live under wp-content/plugins. Rename only the folder belonging to the suspected plugin when you want to deactivate it without wp-admin.

Should I rename one plugin folder or the entire plugins folder?

Rename one when the error log identifies it. Rename the whole directory only as a controlled test when the cause is unknown, then restore the name and isolate plugins individually.

Can WP-CLI deactivate a plugin without wp-admin?

Yes. With SSH access, use wp plugin deactivate plugin-slug. WP-CLI gives a clearer result than changing database values manually.

Why is the plugin still active after I rename its folder?

A cache may still show the error, the renamed folder may be on the wrong WordPress installation, or the code may be a must-use plugin under wp-content/mu-plugins.

How do I reactivate a plugin after restoring wp-admin?

Return the folder to its exact original name, open Plugins in wp-admin, update or replace the faulty code, then activate it while watching the site and logs.

Can deactivating a WordPress plugin break the site further?

It can remove functions the theme or another plugin expects. Take a backup, record the original folder name, and test important pages immediately after the change.

Keep troubleshooting

Learn how to deactivate a WordPress plugin without wp-admin.