How to Deactivate WordPress Plugins Without Admin Access

Introduction

An incompatible or buggy plugin can block access to WordPress, cause a white screen, a 500 error, or a critical failure.

Even if you can’t get into /wp-admin, you can deactivate plugins from the file manager, FTP, the database, or WP-CLI. Before making changes, back up if possible, note which plugin or update may have caused the problem, and change one thing at a time.

Method 1: rename a plugin’s folder

The simplest method when you suspect a specific plugin.

1. Access the DirectAdmin or cPanel file manager, or connect via FTP/SFTP.
2. Go into wp-content/plugins/.
3. Find the plugin’s folder and rename it, for example from problem-plugin to problem-plugin-disabled.
4. Reload the site and try /wp-admin.

WordPress won’t find the plugin’s main file and will mark it as deactivated. Renaming the folder usually doesn’t delete the settings stored in the database.

Once you regain access, go to Plugins > Installed Plugins, confirm it shows as deactivated, check for an update, and review the error log before reactivating it.

Method 2: deactivate all plugins from files

Use this method when you don’t know which plugin is responsible.

1. Open wp-content.
2. Rename the plugins folder to plugins-disabled.
3. Check the site. If it works again, the problem is related to one or more plugins.

To find them, restore the folder’s name to plugins and rename the folders inside one at a time, reactivating plugins individually from WordPress and checking the site after each activation.

Method 3: deactivate plugins with WP-CLI

You need SSH access and WP-CLI available (see managing WordPress with WP-CLI).

wp plugin list
wp plugin deactivate plugin-name
wp plugin deactivate --all
wp plugin deactivate --all --exclude=plugin-name

If a plugin prevents WP-CLI from loading WordPress:

wp plugin deactivate plugin-name --skip-plugins --skip-themes

On Multisite, check whether the plugin is network-activated — you may need to run the command with the corresponding network options and superadmin permissions.

Method 4: deactivate all plugins from phpMyAdmin

Use this method carefully, and only after exporting the database.

1. Log in to phpMyAdmin and select the WordPress database.
2. Open the options table (usually wp_options, though the prefix can differ).
3. Find the row whose option_name is active_plugins.
4. Edit option_value and replace its content with a:0:{}.
5. Save the changes.

This empties the main site’s active plugins list. Don’t edit other rows or change serialized data manually — one wrong character can damage the configuration.

On WordPress Multisite, network-wide active plugins can appear in an option like active_sitewide_plugins inside the network metadata table. Don’t modify these values by hand if you don’t understand the network structure — use WP-CLI or get technical help.

Plugins these methods won’t deactivate

MU-plugins, in wp-content/mu-plugins/, load automatically and don’t show up as normal plugins. Some setups also use special drop-ins inside wp-content, such as advanced-cache.php, object-cache.php, or db.php, which can keep running even after you deactivate normal plugins — don’t delete them without knowing which service created them.

If the failure might be in the theme’s code, try a default theme temporarily (see WordPress 500 error and white screen).

How to identify the responsible plugin

Once you regain access, activate a default theme if the error continues, reactivate plugins one by one while reproducing the action that caused the failure, and check wp-content/debug.log (see how to turn on debug mode).

On a site with many plugins, you can use a binary search: activate half of them, and if it fails, the culprit is in that group; split it again and repeat until you find it.

Common issues

I renamed plugins, but the site still fails

Check the theme, MU-plugins, drop-ins, PHP memory, core files, and server logs.

The plugin reactivates itself

There may be an external management tool, an automatic restore, a scheduled task, or network activation on Multisite.

I can’t find wp_options

The table prefix is different. Check $table_prefix in wp-config.php.

Settings are missing after reactivating

Most plugins keep their settings when deactivated. If they’re lost, check whether an uninstall or a restore ran.

Frequently asked questions

Does renaming a folder delete the plugin?

No. It just stops WordPress from finding its files.

Does deactivating a plugin delete its data?

Usually not. Deleting or uninstalling can trigger cleanup routines, depending on the plugin.

Can I deactivate just one plugin from phpMyAdmin?

It’s possible, but it involves editing serialized data and isn’t recommended. Rename the folder or use WP-CLI instead.

What do I do if the plugin is essential?

Keep the site stable with the plugin deactivated, look for a compatible version, contact the developer, or consider an alternative.

Conclusion

The safest way to deactivate a plugin without admin access is renaming its folder. For several plugins, rename wp-content/plugins or use WP-CLI.

phpMyAdmin should be reserved for situations where you have no file or console access. Once the site is back up, review the logs and compatibility before reactivating the responsible plugin.