Quickly Disable All WordPress Plugins via phpMyAdmin

WordPress | Updated 2026

If a WordPress plugin is causing your site to crash, show a white screen, or lock you out of the admin panel, you can disable all plugins at once through the database without needing to log into WordPress.

01. Step by Step

  1. Log into cPanel > Databases > phpMyAdmin
  2. Select your WordPress database from the left sidebar
  3. Click the "SQL" tab
  4. Run this query:
UPDATE wp_options SET option_value = 'a:0:{}' WHERE option_name = 'active_plugins';
  1. Visit your site - It should load now with all plugins deactivated
  2. Log into WordPress admin
  3. Go to Plugins and reactivate them one at a time, checking your site after each one
Finding the Problem Plugin

Reactivate plugins one by one, refreshing your site after each. When the site breaks again, the last plugin you activated is the culprit. Either update it, find an alternative, or contact the plugin developer. See Optimize WordPress Performance for identifying resource-heavy plugins.

Table Prefix

If your WordPress installation uses a custom table prefix (not the default wp_), replace wp_options with your actual prefix. Check wp-config.php for the $table_prefix value.

02. Alternative: Rename the Plugins Folder

If you prefer not to use SQL, you can rename the plugins directory via cPanel File Manager or FTP:

  1. Navigate to wp-content/
  2. Rename plugins to plugins_disabled
  3. Visit your site - WordPress automatically deactivates all plugins when it cannot find the folder
  4. Rename back to plugins
  5. Reactivate one at a time in WordPress admin

Site Still Down After Disabling Plugins?

If disabling all plugins does not fix the issue, the problem may be your theme, a corrupted core file, or a database issue. Open a ticket and we will investigate.

Open a Support Ticket

Quick Recap

  1. Run the SQL query in phpMyAdmin to deactivate all plugins at once
  2. Or rename the plugins folder via File Manager
  3. Reactivate one at a time to find the problem plugin
  4. Check your table prefix in wp-config.php if using a custom prefix
  5. Still broken? The issue may be the theme or WordPress core

WordPress emergency troubleshooting · Last updated March 2026 · Browse all WordPress articles

  • 185 Users Found This Useful

Was this answer helpful?

Related Articles

PCLZIP_ERR_MISSING_FILE WordPress Error

WordPress | Updated March 2026 The error "PCLZIP_ERR_MISSING_FILE (-4) : Missing archive...

Unable to create directory uploads/ Is its parent directory writable by the server?

Unable to create directory... Is its parent directory writable by the server? This error can be...

WordPress Security

🔒 WordPress Security Guide | Updated 2026 WordPress powers over 40% of the web,...

CloudFlare for WordPress

Cloudflare + Web Hosting Guide | Updated 2026 Cloudflare is a content delivery network (CDN)...

WordPress Response Body Too Large and Too Many Arguments Errors

WordPress | Updated March 2026 The "Response Body Too Large" and "Too Many Arguments in...



Save 30% on web hosting - Use coupon code Hosting30