Search for “WordPress plugin conflict checker” and you’ll find plenty of tools that promise to scan your plugins and tell you which ones don’t get along. It’s a nice idea. Unfortunately, it doesn’t really work that way, and knowing why will save you an afternoon.
What a plugin conflict is
A conflict is when two plugins each work fine on their own, but break something when they’re both active. Some common shapes it takes:
- Two plugins doing the same job. Two caching plugins, two SEO plugins, or two plugins that both rewrite your login page. They fight over the same settings or the same part of the page.
- Clashing code. Both plugins bundle the same library, or define a function with the same name. That’s when you see errors like “Cannot redeclare function” or “Cannot declare class, because the name is already in use”.
- Script problems. One plugin’s JavaScript throws an error, and that stops another plugin’s script from running. The page loads, but a button does nothing or a slider stays frozen.
- Optimisation going too far. Plugins that combine, delay or minify scripts can reorder code another plugin depends on. This one is extremely common.
- Style clashes. One plugin’s CSS overrides another’s, and a layout falls apart. Annoying, but usually harmless.
Notice that most of these depend on your site: your settings, your theme, the exact versions you’re running, sometimes even the page you’re looking at. Two plugins can clash on one site and work perfectly together on the next.
Why scanning can’t find conflicts
A scanner can read plugin code and look for obvious red flags, like two plugins declaring the same function. That catches a small slice of real problems. It can’t run your site the way a visitor does, with your settings and your content, so it misses almost everything in the list above.
The only reliable conflict checker is a test: switch plugins off, see whether the problem goes away, and narrow it down. Every method you’ll find, including ours, is some version of that.
How to test for a conflict
1. Make the problem easy to check
Write it down in one sentence and note the page: “On /checkout/, the Place order button spins forever.” You’ll be reloading that page a lot, so you want a clear yes or no every time.
2. Check the obvious suspects
Before testing everything, look at:
- What changed recently. A plugin you just installed or updated is the first suspect.
- Overlapping plugins. Do you have two plugins that do the same thing? Try with one of them off.
- Optimisation settings. If you use a performance plugin that combines or delays JavaScript, turn those options off and check again. If the problem disappears, you can usually exclude the affected script instead of giving up on the plugin.
- The browser console. Press F12, open the Console tab and reload the page. A red error often names the plugin folder the broken script comes from.
3. Narrow it down by halving
If nothing obvious turns up, test your plugins in halves rather than one by one. Switch off half, check the page, and keep halving whichever group contains the problem. Thirty plugins take about seven checks instead of thirty. Our guide on finding which plugin is breaking your site explains the method in detail.
4. Confirm it really is a conflict
When you’ve narrowed it to one plugin, try that plugin on its own, with everything else off. If the problem is still there, it’s a bug in that plugin. If it disappears, it needs a partner to break, and you’ve found a conflict. Turn plugins back on until you find the second one.
Doing it without your visitors noticing
The catch with all of this is that switching plugins off from the Plugins screen switches them off for everyone. On a shop or a busy blog, that’s a real cost.
That’s the reason troubleshooting plugins exist. Culprit Finder does the halving for you, but only in your browser. Visitors and other admins keep every plugin the whole time. It also handles the conflict case on its own: if the problem only appears with two plugins on together, it keeps searching until it can name both. If you prefer to work through plugins by hand, Health Check & Troubleshooting is the other well-known option, and we’ve compared the two honestly.
Whichever way you go, have a way back in before you start. Know where your host’s file manager is, or have your FTP details ready.
You found the conflict. Now what?
- Update both plugins. Conflicts are often fixed quietly in a later version.
- Report it to both authors. Either one might be able to fix it, and each will want to know which other plugin is involved. Include your WordPress version, PHP version and theme, plus the exact steps to see the problem.
- Look for a setting. Many conflicts go away by switching off one overlapping feature, like the duplicate sitemap in one of two SEO plugins.
- Choose one. If two plugins do the same job, you probably only need one of them anyway.
Conflicts feel mysterious because the problem doesn’t belong to any single plugin. But they follow the same rule as every other WordPress problem: change one thing at a time, check the same page, and write down what you tried.