Guide

Disable plugins in WordPress without admin access

Disable WordPress plugins through files or database access when wp-admin is unavailable because of a 500, 502, or database error.

When to use this guide

Use this when WordPress admin is unavailable and a plugin update, security plugin, cache plugin, page builder, or custom plugin may be causing a 500 error, white screen, or gateway failure.

Steps

  1. Back up first. Copy the current wp-content/plugins folder name list and take a database backup if you will edit the database.
  2. Disable all plugins from the filesystem. Rename wp-content/plugins to plugins.disabled. WordPress will deactivate plugins when it cannot find the folder.
  3. Test the site. If the site loads, rename the folder back to plugins and disable individual plugin folders until the failing plugin is isolated.
  4. Use the database only if needed. If filesystem access is unavailable, update the active_plugins option to an empty serialized array after taking a backup.
  5. Clear cache layers. Purge object cache, page cache, and CDN cache after disabling cache or optimization plugins.

Verify

The public site and /wp-admin/ should load. Re-enable plugins one at a time and test the failing URL after each change.

Rollback or escalate

Restore the original folder names or database option if disabling plugins does not help. Escalate with the plugin changed most recently, PHP error log lines, and the exact URL that fails.

Review notes

Last reviewed
2026-05-05
Reviewed by
FaultForge Editorial Team, Web operations reviewer
Tested on

HTTP status checks, access and error log review, server response headers, recent deployment review, and safe rollback verification.

Sources