Every WordPress troubleshooting guide eventually says "deactivate all your plugins". If you are reading this, you have probably just noticed the problem with that instruction: you cannot reach the screen where the Deactivate buttons live.
There is a way to switch every plugin off without logging in, it takes about two minutes, and it is reversible. It also has one behavior that surprises people afterwards, so that part is covered too.
What you are about to do, and why it works
WordPress looks for active plugins in wp-content/plugins. Each plugin lives in its own folder inside it. When WordPress starts up, it checks its list of active plugins against what is actually on disk, and any plugin whose files are missing is quietly dropped from the list.
Renaming the folder makes every plugin missing at once. WordPress starts up with no plugins running, which is exactly the state you want for diagnosis.
Nothing is deleted. The files are all still there under a different name. This is the safest destructive-looking action in WordPress troubleshooting, which is why it is the standard recovery move.
Before you start
Take a backup if you can reach one. If your host makes backups, note the most recent one before you touch anything. You are not going to need it for this specific action, and having it is the difference between a calm session and a tense one.
Write down what is active, if you can see it. Frequently you cannot, which is why you are here. If you happen to have a recent screenshot, an old email, or a staging copy, that list saves you time later.
Know which of your plugins matter. Turning off a security plugin, a firewall or a maintenance-mode plugin changes what your site exposes to the public for as long as the test runs. Keep the window short.
Getting to the files
Two normal routes, and either is fine.
Your host's File Manager. Log into the hosting control panel and look for a file browser. It will open at your account's root, and your WordPress installation is usually in a folder called public_html, httpdocs, www, or the domain name itself. You will know you are in the right place when you see wp-admin, wp-content, wp-includes and wp-config.php side by side.
An FTP or SFTP client. Your host supplies the address, username and password, usually in the control panel under FTP accounts. The folder layout is identical.
Control panel designs differ between hosts and change over time, so treat the wording above as a description of what to look for rather than a click path. If you cannot find the file manager, your host's support can point at it in one message.
The rename
Open wp-content. You will see folders including plugins, themes and uploads.
Rename plugins to something obvious and temporary. plugins-off is a good choice, because in a month you will still know what it means.
Do not use plugins.old, and do not move it outside wp-content. Both work, and both are easier to forget about or to lose. A name you will recognize, in the place you found it, is the version that gets undone properly.
Now load your site. Three outcomes.
The site works. A plugin was the cause. Good, and now you need to find which one.
The site is still broken. Plugins are not the cause. Rename the folder back immediately, and look at the theme, at core files, or at the server.
The site changes but is still wrong. Expected, and not alarming. With every plugin off, forms, galleries, shopping carts and shortcodes stop working, so the page will look wrong regardless. You are checking whether the specific fault is gone, not whether the site looks right.
Finding the specific plugin
Rename plugins-off back to plugins. Every plugin's files are now visible again.
Here is the behavior that catches people out. WordPress does not automatically reactivate the plugins that were dropped from its active list. In practice most people find the site comes back with all plugins deactivated rather than restored to how they were. That is normal, it is not damage, and it is why the list you wrote down earlier is worth having.
If you can now reach the admin, you are in the best possible position: the site is running, every plugin is off, and you can reactivate them one group at a time from the Plugins screen, checking after each group. Half of them, then half of the guilty half, and so on. That is the conflict test and it is far faster than one at a time.
If you still cannot reach the admin, work at the file level instead. Rename individual plugin folders one at a time rather than the whole plugins folder, starting with anything you updated, installed or changed recently. If your debug log or the error message on screen named a file path, start with the plugin in that path. Our critical error after an update walkthrough sets out the order for the after-an-update case specifically.
Doing the same to a theme
The same trick works on the active theme's folder inside wp-content/themes, with one important condition. WordPress falls back to a default theme, so a default theme must be installed for this to help. If the only theme on the site is the one you rename, you will replace a broken site with a differently broken site.
Check the themes folder first. If you see a twenty-something theme sitting there unused, you have a fallback and the rename is safe to try.
Cleaning up
When you are finished, make sure wp-content/plugins is named exactly that, with no leftover plugins-off folder beside it. Two plugin folders is not dangerous, but it is confusing for whoever looks next, including you.
Then reactivate what you need, deliberately, one at a time, and write down what you turned back on. A site that came back with sixteen plugins off is also a site where you get to ask whether all sixteen earn their place.
What this does not fix
Renaming the plugins folder addresses plugin faults and nothing else. A database connection failure, a server error, an expired certificate, a disk that is full, a corrupted core file, or a host outage will all survive it untouched. If the site is unchanged after the rename, put the folder name back straight away rather than leaving the site in a modified state while you look elsewhere.
Version context. Written against WordPress 7.1, released 2026-08-19, the current major release on our record. The folder-based deactivation behavior described here is long-standing and is not specific to 7.x. Hosting control panels are a moving target and the file-manager descriptions above are generic by design. Release dates come from our own dated record of the WordPress.org release page, last read 2026-08-19.
