Troubleshooting · Guide
How to Deactivate All Plugins Without wp-admin
Short answer
Rename the wp-content/plugins folder to plugins_old over FTP or File Manager, or run wp plugin deactivate --all in WP-CLI. Try WordPress Recovery Mode first if the fatal error email arrived. Turn plugins back on one at a time to find the one that broke the site.
Key takeaways
- Renaming wp-content/plugins to plugins_old deactivates every plugin without deleting files.
- Recovery Mode, from WordPress 5.2, pauses the faulty plugin for your session only.
- wp plugin deactivate --all turns every plugin off from the command line.
- Setting active_plugins to a:0:{} in phpMyAdmin deactivates all plugins from the database.
- Turn plugins back on one at a time, since bulk activation hides which one breaks the site.
What does deactivating all plugins do?
Deactivating all plugins stops every plugin file from loading, while leaving the plugin files and their settings in place on your server.
WordPress loads plugin code before it loads the admin screen. A single broken plugin file can therefore crash the whole dashboard before you ever reach the Deactivate button. Turning all plugins off from outside WordPress breaks that loop and lets you log in again.
Deactivating is not deleting. The plugin folders stay in wp-content/plugins/, and the settings stay in the database. You can turn plugins back on one at a time after the site loads, which is how you find the one that broke it.
This guide covers the case where wp-admin will not load at all. If you can still open wp-admin, use Plugins > Installed Plugins instead, tick the boxes, pick Deactivate from the bulk menu, and click Apply. The steps below are only for a locked-out site.
| Method | What you need | Best when |
|---|---|---|
| Recovery Mode | Admin email inbox | A fatal error email arrived |
| FTP or File Manager | File access | No email, no command line |
| WP-CLI | SSH access | You want the fastest route |
| phpMyAdmin | Database access | File access is not available |
What do you need before you start?
You need file or database access to your site, and a backup made before you change anything.
File access means SFTP, FTP, or the file manager in your hosting panel. Database access means phpMyAdmin or a similar tool in your hosting panel. SSH access with WP-CLI is the fastest route if your host offers it.
Take a full backup of files and database first. If wp-admin is down, use your host backup tool, not a WordPress plugin, since the plugin route needs the admin area that is broken. A backup turns a wrong rename or a wrong database edit from a disaster into a restore.
Write down which plugins were active before you start. If you cannot open wp-admin, check the active_plugins row in the wp_options table in phpMyAdmin, or copy the plugin folder names from wp-content/plugins/. That list tells you what to turn back on later.
Plan on 10 to 30 minutes for the whole job. The deactivation itself takes about 5 minutes. Finding the faulty plugin by turning them back on one at a time takes the rest.
How do you try Recovery Mode first?
You try Recovery Mode first, because it is the only route that needs no file or database access at all.
Recovery Mode is a built-in WordPress feature that arrived in version 5.2. When a plugin or theme causes a fatal error, WordPress sends an email to the site admin address with a special link.
The WordPress.org Recovery Mode docs state that the mode may help you regain access when a fatal error occurs, without FTP or code edits.
Open the inbox for the admin email address, which is the address under Settings > General when the site works. Look for a message titled “Your Site is Experiencing a Technical Issue” and check the spam folder too. The email names the plugin or theme that failed and holds the recovery link.
Click the link and log in. WordPress pauses the faulty plugin or theme for your session only, so wp-admin loads and you can deactivate the culprit from Plugins > Installed Plugins. Visitors still see the error until you deactivate it, since the pause applies to your browser session alone.
The recovery link expires, so use it promptly. If it expires, WordPress sends a new link when the error happens again. If no email arrived at all, move on to the file methods below, since some errors never trigger the email.
Our guide on fixing the critical error message covers what each version of that message means.
How do you deactivate all plugins with FTP or File Manager?
You deactivate all plugins by renaming the plugins folder, which makes WordPress unable to find any plugin file.
This is the most reliable locked-out method, and it needs no command line or database work. WordPress looks for each active plugin inside wp-content/plugins/. If that folder has a different name, WordPress drops every plugin from the load list and loads the site without them.
Follow these steps:
- Connect to your site with an SFTP client such as FileZilla, or open File Manager in your hosting panel.
- Open the
wp-contentfolder in your site root, which is usuallypublic_html. - Right-click the
pluginsfolder and choose Rename. - Rename it to
plugins_oldand save. - Try to open wp-admin again.
If the fault was a plugin, wp-admin should load now. The Kinsta guide to disabling plugins gives the same three steps: connect by FTP or SFTP, open the wp-content folder, and rename plugins to plugins_old.
Do not delete the folder. Renaming only hides it from WordPress, and the files stay on the server.
If wp-admin still will not load after the rename, the fault is not a plugin. Switch to the theme next, or read the error log for the real cause.
To restore the folder, rename plugins_old back to plugins. The plugins stay deactivated after the rename back, so you must turn them on by hand in Plugins > Installed Plugins. That is the safe result: nothing turns itself back on without your say.
The WordPress.org Recovery Mode docs confirm this route too. They state that you may temporarily deactivate one or several plugins by renaming their folder names when FTP or a file handler is at hand.
How do you deactivate all plugins with WP-CLI?
You deactivate all plugins with one WP-CLI command, and this is the fastest route when you have SSH access.
WP-CLI is the command-line tool for WordPress. It runs from the server, so it works even when wp-admin is down. Open SSH, move to your WordPress root folder, and run:
wp plugin deactivate --all
The WP-CLI command docs state that the --all flag deactivates all plugins, and that --exclude takes a comma-separated list of plugin slugs to skip. For example, wp plugin deactivate --all --exclude=hello,wordpress-seo leaves those two plugins on and turns the rest off.
List your plugins first if you are unsure of the slugs:
wp plugin list
The plugin slug is the folder name in wp-content/plugins/. The list shows each plugin with its status and version, so you can note which ones were active before you turn them off.
If WP-CLI itself errors out, the broken plugin may be crashing the command too. Add flags that skip plugin and theme code, as the WP Engine SSH Gateway guide shows:
wp plugin deactivate --all --skip-plugins --skip-themes
The Make WordPress Hosting handbook gives the same pair of commands for a broken dashboard: wp plugin deactivate --all, then wp plugin activate your-plugin-slug to turn one back on (Make WordPress Hosting: WP-CLI).
Turn plugins back on one at a time with wp plugin activate your-plugin-slug, and load the site after each one. When the site breaks again, the last plugin you turned on is the cause.
How do you deactivate all plugins with phpMyAdmin?
You deactivate all plugins in phpMyAdmin by emptying the active_plugins value in the wp_options table.
Use this route only when FTP, File Manager, and WP-CLI are all out of reach. A wrong edit in the database can break the site further, so back up the database first and follow the steps exactly.
Follow these steps:
- Open phpMyAdmin from your hosting panel, under the Databases section.
- Click your WordPress database name in the left sidebar.
- Click the
wp_optionstable. Your table prefix may differ fromwp_if the installer used another prefix. - Find the row where
option_nameisactive_pluginsand click Edit. - Replace the whole
option_valuefield witha:0:{}and click Go.
The value a:0:{} is a serialized empty array, which tells WordPress that no plugins are active. The GreenGeeks tutorial gives the same steps: open phpMyAdmin, open wp_options, find active_plugins, and edit its value.
Do not change any other row. The wp_options table holds the site URL, the admin email, and other settings that break the site if edited. Change only the active_plugins row, and only its value field.
After the edit, open wp-admin and check Plugins > Installed Plugins. Every plugin should show as inactive. Turn them back on one at a time, as in the section below.
How do you find the plugin that broke the site?
You find the faulty plugin by turning plugins back on one at a time and loading the site after each one.
Start with the site loading and all plugins off. Open Plugins > Installed Plugins in wp-admin. The list shows every plugin as inactive, with an Activate link under each name.
Turn on one plugin, then load the home page and one admin page. If both load, that plugin is fine, so turn on the next plugin and check again. Repeat until the site breaks, and the plugin you just turned on is the cause.
Turn that plugin off again right away, and leave it off. Then turn on the rest of the plugins one at a time to confirm no second plugin is also broken. A site can have two faulty plugins, and stopping at the first one leaves the second in place.
If the site breaks the moment you turn on a plugin, check the error log for the exact file. The fatal error line names the plugin folder in its path. Our guide on fixing a plugin conflict covers the same one-at-a-time method in more detail.
If every plugin turns back on without breaking the site, the fault may have been a bad update or a cached file. Clear the cache, check for plugin updates, and watch the site for a day before you call it fixed.
How do you reactivate plugins safely?
You reactivate plugins one at a time, in a safe order, and you check the site after each one.
Start with the plugins the site needs most, such as the security plugin and the backup plugin. Then turn on the rest in any order, one at a time. Do not use the bulk Activate action to turn them all on at once, since that hides which one breaks the site.
Check the home page and wp-admin after each activation. A plugin can break only the admin area or only the front end, so check both. If a plugin breaks the site, turn it off and note its name and version.
Update the faulty plugin before you give up on it. An update may hold the fix for the crash. If no update exists, delete the plugin from Plugins > Installed Plugins and find a replacement, or ask the plugin author for support with the error message from the log.
Keep a short note of the order you used and the result for each plugin. If the fault returns later, that note tells you which plugin to check first. If you are locked out again, our guide on fixing a lockout covers the other ways back in.
What mistakes should you avoid?
The most common mistakes in this job turn a quick fix into a longer outage.
First, do not delete the plugins folder or any plugin folder. Deleting removes files and can remove data that deactivation would have kept. Rename the folder instead, and delete only a single faulty plugin from wp-admin after you know which one it is.
Second, do not turn all plugins back on at once. Bulk activation hides the faulty plugin, and the site breaks again with no clue which plugin did it. One at a time is slower, but it names the cause.
Third, do not edit the database without a backup. The phpMyAdmin route changes live settings, and a typo in wp_options can break the site URL or the admin email. Back up the database first, and change only the active_plugins row.
Fourth, do not skip the backup step because the site is already down. A broken site can still get worse. A bad rename or a wrong database edit can turn a plugin fault into a lost site, while a backup makes every step reversible.
Fifth, do not assume the plugin you found is the only fault. A white screen can have two causes at once, such as a plugin fault and a theme fault.
If the site still shows a blank page after all plugins are off, read our guide on fixing the white screen of death for the theme and memory checks that come next.
Frequently asked questions
Does deactivating a plugin delete its data?
No. Deactivation stops the code from running but leaves the files and settings in place. Deleting removes the files. Rename the folder instead of deleting it, and delete only the single faulty plugin from wp-admin once you know which one it is.
What if I have no FTP access and no recovery email?
Try Recovery Mode first, since it needs no file access. If no email arrived, use FTP or your host file manager to rename the plugins folder, or use WP-CLI if you have SSH access.
Do plugins turn back on when I rename the folder back?
Yes, that is expected. Renaming the folder back restores the list but leaves every plugin inactive. Turn them back on one at a time from Plugins and Installed Plugins, checking the site after each one.
What does setting active_plugins to a:0:{} do?
It sets active_plugins to an empty list, which tells WordPress that no plugins are active. Back up the database first and change only that one row, since other rows in wp_options hold the site URL and admin email.
What should I do with the plugin that broke the site?
Update it first, since the update may hold the fix. If no update exists, delete it from wp-admin and find a replacement, or ask the plugin author for support and include the fatal error line from the log.
Sources
- Recovery Mode WordPress.org
- wp plugin deactivate WordPress Developer Resources
- How to disable WordPress plugins (no access to WP-Admin) Kinsta
- WP-CLI Make WordPress Hosting
- Troubleshoot Site with SSH Gateway WP Engine Support
- How to Turn Off Plugins without WP Admin Access GreenGeeks
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.
