How to Find Which WordPress Plugin Is Breaking Your Website
Your website breaks. A feature disappears. The admin dashboard locks up. Forms stop working. Or everything just gets slower.
Your first thought: which plugin did it?
You have 20 plugins active. Maybe 30. Testing each one manually sounds like it'll take hours. So you either guess (usually wrong) or give up and pay someone $200 to figure it out.
You don't have to guess. There's a systematic process. It takes 15-30 minutes. And it works every time.
Symptoms: How to Know It's a Plugin Conflict
First, confirm it's actually a plugin issue (and not something else).
Common plugin conflict symptoms:
- White screen of death (WSOD): Completely blank white page, no error message
- Broken layout: Styling disappears, elements misaligned, page looks wrong
- Functionality breaks: Forms don't submit, buttons don't work, features disappear
- Admin issues: Dashboard is slow, plugins page won't load, editing breaks
- Slow performance: Site suddenly loads slowly (after recent plugin update or install)
- Error messages: PHP errors, JavaScript errors, or cryptic messages
- Missing features: Something that worked yesterday doesn't today
- Emails don't send: Forms submit but confirmation emails don't arrive
BUT: These symptoms can also be caused by:
- Theme conflicts (not plugin)
- PHP version incompatibility
- Cache problems (clear browser cache first)
- Server-level issues (hosting firewall, mod_security, etc.)
- Malware
- Database corruption
So before assuming it's a plugin:
- Clear your browser cache (Ctrl+Shift+Delete or Cmd+Shift+Delete)
- Open the site in an Incognito/Private window (bypasses all caching)
- If the issue is gone in Incognito, it was cache. Problem solved.
- If the issue persists, it's a plugin, theme, or server issue. Continue below.
Method 1: Health Check & Troubleshooting (Safest, Recommended)
This is the gold standard for finding plugin conflicts.
Health Check & Troubleshooting is the gold standard for safe conflict testing. Its troubleshooting mode creates an isolated session where all plugins are temporarily disabled without affecting visitors.
Why this method is best:
- ā Visitors don't see any changes (only you see disabled plugins)
- ā Safe on live sites (no risk of breaking things for customers)
- ā You can test during business hours without impact
- ā Built-in error logging and debugging tools
- ā Free and officially maintained by WordPress community
Step 1: Install Health Check & Troubleshooting
- Go to WordPress > Plugins > Add New
- Search for "Health Check & Troubleshooting"
- Click "Install Now" > "Activate"
Step 2: Enable Troubleshooting Mode
- Go to WordPress > Tools > Site Health
- Click the "Troubleshooting" tab
- Click "Enable Troubleshooting Mode"
- This will deactivate all plugins and switch to the default theme for your session only.
Step 3: Test Your Site
- Open your website in a new tab (NOT in incognito, so your logged-in session stays active)
- Check if the problem is gone
If the problem is gone: A plugin OR the theme is the cause. Continue to Step 4A.
If the problem persists: It's a server-level issue or WordPress core issue, not a plugin. Contact your host or see "Server-Level Issues" section below.
Step 4A: Find the Problematic Plugin (If Problem Was Gone)
- Go to WordPress > Plugins (you'll see them all marked "Inactive" because Troubleshooting Mode disabled them)
- Activate plugins one at a time, starting with the one you updated/installed most recently
- After activating each plugin, reload your site in the other tab and check if the problem appears
- When the problem returns, you've found the conflicting plugin
- Write down the plugin name
Step 4B: Find the Theme Issue (If Problem Was Gone)
If all plugins are deactivated but problem persists, test the theme:
- Still in Troubleshooting Mode, go to WordPress > Appearance > Themes
- Switch to "Twenty Twenty-Four" (default WordPress theme)
- Check if the problem is gone
If problem is gone: Your current theme is the issue. Switch back to your theme and contact the theme developer.
If problem persists: It's a server-level issue. See "Server-Level Issues" section.
Step 5: Disable Troubleshooting Mode
- Go to Tools > Site Health > Troubleshooting
- Click "Disable Troubleshooting Mode"
- All plugins reactivate, theme switches back
- Your site returns to normal (for visitors and you)
Expected result: You've identified the problematic plugin. Now you know what to fix.
Method 2: Conflict Finder Plugin (Fastest Automated Tool)
Similar to Health Check, but with more automated features.
Conflict Finder allows you to: Enable and manage WP_DEBUG without manually editing files, view and clear the WordPress debug log, temporarily disable plugins to identify conflicts, switch themes to test theme-related issues, and test WordPress email delivery.
Step 1: Install Conflict Finder
- Go to Plugins > Add New
- Search for "Conflict Finder ā WP Fix It"
- Install and Activate
Step 2: Open Troubleshooting Tools
- Go to WordPress > Tools > Troubleshoot (you'll see the Conflict Finder menu)
- Click on any troubleshooting option
Step 3: Disable Plugins & Test
- Check "Disable All Plugins" option
- Save/apply changes
- Visit your site in another tab
- If problem is gone, re-enable plugins one-by-one as described in Method 1 Step 4A
Advantage over Health Check: Conflict Finder has additional tools like debug log viewer and email testing. But both methods accomplish the same goal.
Method 3: Plugin Detective (Most Guided Approach)
For people who want step-by-step guidance without guessing.
Plugin Detective walks you through solving your case one step at a time, all from one single screen. Open a case and tell Detective Otto where you're seeing the problem.
Step 1: Install Plugin Detective
- Go to Plugins > Add New
- Search for "Plugin Detective"
- Install and Activate
Step 2: Create a Case
- Go to WordPress > Tools > Plugin Detective
- Click "Open a Case"
- Describe the problem (e.g., "White screen after updating WooCommerce")
- Tell it where the problem appears (admin, frontend, specific page, etc.)
Step 3: Follow the Wizard
- Plugin Detective provides a guided troubleshooting flow
- Follow each step, testing after each action
- The plugin narrows down the cause (plugin vs theme vs server)
- Once identified, the plugin tells you the next steps
Advantage: Most hand-holding. Good if you're not comfortable with technical troubleshooting.
Method 4: Manual Plugin Deactivation (No Plugin Needed)
If you can't access WordPress admin, or you want the most direct control.
Option A: Manual Deactivation via FTP/SFTP (If Admin is Broken)
Scenario: You can't log in to WordPress admin (white screen, login page broken, etc.)
- Connect to your site via FTP or SFTP (File Manager in cPanel/Plesk)
- Navigate to /wp-content/plugins/
- You'll see folders for each plugin (e.g., woocommerce/, elementor/, wordfence/, etc.)
- Rename ALL plugin folders by adding "-disabled" to the end:
- woocommerce ā woocommerce-disabled
- elementor ā elementor-disabled
- wordfence ā wordfence-disabled
- etc. for all plugins
- Visit your site in a browser ā is the problem gone?
If problem is gone: A plugin caused it. Now rename folders back ONE AT A TIME, testing between each:
- Rename woocommerce-disabled ā woocommerce
- Test site
- If problem returns, you found it (WooCommerce)
- If no problem, rename back to woocommerce-disabled and try the next plugin
- Repeat until problem returns
If problem persists: It's a theme or server issue, not a plugin.
Option B: Deactivate All via WordPress Admin
Scenario: You CAN access WordPress admin, but not using troubleshooting plugins.
- Go to Plugins > Installed Plugins
- Select all plugins with checkboxes
- Bulk Actions dropdown > "Deactivate" > Apply
- All plugins instantly deactivate
- Test your site ā is the problem gone?
If problem is gone: Reactivate plugins one-by-one:
- Activate the plugin you updated/installed most recently
- Test site
- If problem returns, you found it
- If no problem, deactivate it and activate the next plugin
- Repeat until problem returns
If problem persists: It's a theme or server issue.
Expected time: 15-30 minutes (depending on how many plugins you have).
Once You Find the Problem Plugin
Step 1: Document It
Write down:
- Plugin name
- Plugin version
- What exactly breaks (forms, layout, admin, etc.)
- When it started (after updating? after installing?)
Step 2: Check for Updates
The issue might be fixed already:
- Go to Plugins > Installed Plugins
- Find the problem plugin
- If an "Update" button appears, update it
- Test if the problem is fixed
Step 3: Check Plugin Support Forums
- Go to wordpress.org/plugins/[plugin-name]
- Click "Support" tab
- Search for your problem (someone probably reported it)
- If found, apply the workaround they suggest
Step 4: Contact Plugin Developer
If no update or workaround exists:
- Go to wordpress.org/plugins/[plugin-name]
- Click "Support" tab
- Create a new support topic
- Explain: plugin name, version, what breaks, WordPress version, PHP version
- Wait for response (usually 24-48 hours)
Step 5: Choose Your Next Step
Option A: Update/Fix the Plugin
If plugin is actively maintained and developer fixes it, great. Update and re-test.
Option B: Find an Alternative Plugin
If the plugin is abandoned or the conflict can't be fixed, replace it:
- Deactivate and delete the problem plugin
- Find a similar plugin that doesn't conflict (check reviews, active installs)
- Install and configure the replacement
Option C: Keep It Deactivated
If you don't actually need the feature, just leave it disabled.
Option D: Roll Back to Previous Version
If the plugin worked before an update, downgrade it:
- Go to wordpress.org/plugins/[plugin-name]
- Look for "Version History" or "Previous Versions" link
- Download the previous stable version (one back from current)
- Delete current version via FTP
- Upload the older version
- Reactivate and test
ā ļø Only downgrade for 1-2 versions maximum. Don't go too far back, or you'll miss security patches.
If It's Not a Plugin (Server-Level Issues)
If all plugins deactivated but problem persists, it's a server issue:
- Hosting firewall blocking requests
- PHP version incompatible (recommended: PHP 8.3 or newer)
- mod_security restrictions
- MySQL/Database errors
- Malware
What to Do:
- Contact your hosting provider
- Tell them: "All plugins deactivated, issue persists"
- Ask them to:
- Check firewall rules
- Verify PHP version (8.3+)
- Check mod_security logs
- Run malware scan
- They can usually fix it in 30 minutes
Prevention: Avoid Plugin Conflicts in the Future
Before Installing a Plugin
- Check "Active Installs" ā widely used plugins have better compatibility
- Read recent reviews for compatibility issues
- Check when it was last updated ā plugins updated monthly are maintained; plugins last updated 2 years ago are probably abandoned
- Test on a staging site before live site
Before Updating Anything
- Backup your site first (use UpdraftPlus or hosting backup)
- Test updates on staging site
- Never update 3+ things simultaneously (if something breaks, you won't know which caused it)
Keep PHP Current
As of 2026, PHP 8.3 or newer is recommended for most WordPress sites. Check with your host to confirm your PHP version.
Delete Unused Plugins
Each extra plugin is another potential conflict. Delete plugins you don't use.
Use Staging for Testing
A staging site is a clone of your live site. It's the best practice for safe web management. This is where you can safely test updates and plugins.
Timeline: How Long Will This Take?
Health Check & Troubleshooting method:
- Installation: 2 minutes
- Identifying plugin: 10-20 minutes (depending on plugin count)
- Total: 15-25 minutes
Manual FTP method:
- Disabling all plugins: 5 minutes
- Testing one-by-one: 15-30 minutes (depending on plugin count)
- Total: 20-40 minutes
Hiring help:
- Fiverr/Upwork freelancer: $50-200 (30-60 min)
- Premium support from plugin developer: Usually free
When to Call a Professional
Hire a developer if:
- You've tried all methods and can't find the problem
- Admin is completely broken and you can't access FTP
- You're not comfortable with technical troubleshooting
- The conflict is between custom code and a plugin (very specific situation)
- Your site is business-critical and you can't afford downtime
Cost: $50-200 via Fiverr/Upwork for straightforward conflicts. Usually takes 1-2 hours.
The Real Talk
Plugin conflicts are not mysterious. There's a proven process to find them. Don't waste hours guessing or blindly disabling plugins.
Use Health Check & Troubleshooting (free, safe, no visitor impact). Follow it systematically. You'll find the culprit in 15 minutes.
Once found, you have clear options: update it, replace it, or deactivate it. No more "my site just randomly breaks and I have no idea why."
And next time? Backup before updating anything. Test on staging. Check active installs and update frequency before installing new plugins.
Prevention beats troubleshooting every time.
