ToolsRiver Income Tax

WordPress Plugin Conflict Detective

  • Free, no sign-up
  • Instant results
  • Works on mobile
What it does. Find out which plugins or theme are likely breaking your WordPress site. Enter the site address, paste error messages from the browser console or debug.log, or both. The report ranks suspects by evidence, shows likely conflict pairs and gives a safe step-by-step way to confirm them.

How to use the WordPress Plugin Conflict Detective

  1. Enter the address of the WordPress page that misbehaves. This is optional if you only want to analyse error messages.
  2. Paste error messages if you have them: browser console (press F12, open Console), the file wp-content/debug.log, or the PHP error log from your hosting panel. Pasted text stays in your browser.
  3. Press Find conflicts. The page is checked for overlapping plugins, duplicate jQuery, PHP errors, missing plugin files and JavaScript errors in a real browser.
  4. Read the suspects table. The highest score has the most evidence against it.
  5. Confirm with the troubleshooting steps at the end of the report before you remove anything.

What the report shows

CheckWhat you learn
Suspects ranked by evidenceEach plugin or theme with a score and the exact messages that point to it.
Likely conflict pairsTwo components named in the same fatal error, or two plugins that do the same job.
Overlapping pluginsTwo SEO, caching, optimisation, page builder, lazy load, security, analytics, slider or cookie plugins.
Duplicate jQueryA second jQuery copy that removes features added by other plugins.
Duplicate PHP names"Cannot redeclare" and "Cannot declare class" fatal errors between two components.
Load order problems"$ is not a function" and "jQuery is not defined" errors, often caused by defer or delay settings.

Tips for better results

  • Turn on the debug log to get the best evidence: add WP_DEBUG and WP_DEBUG_LOG to wp-config.php, reproduce the problem, then paste wp-content/debug.log here.
  • Copy console errors right after the problem happens, for example after clicking the broken button.
  • Test fixes with the Health Check and Troubleshooting plugin. It disables plugins for your session only, so visitors are not affected.
  • After you find the pair, keep one plugin or report the conflict to both authors with the error text.

Limits to know about

  • From outside, a tool can only see evidence, not prove a conflict. The troubleshooting steps give the proof.
  • Only plugins that load files on the page are visible. Plugins that work in the background or only in wp-admin stay hidden unless they appear in pasted errors.
  • Real-browser checks capture errors during page load only, not after clicks. Paste console errors for those.
  • Do not paste passwords or private customer data. Error logs rarely contain them, but check before pasting.

Frequently asked questions

How do I know if a plugin conflict is breaking my site?

Signs are features that stopped working after an update, JavaScript errors in the browser console, fatal errors in debug.log, or two plugins doing the same job. This tool collects that evidence and ranks the likely culprits.

What is a plugin conflict?

It happens when two plugins, or a plugin and the theme, load incompatible code: the same PHP function name, two copies of jQuery, or two tools that rewrite the same page output.

Will deactivating plugins break my live site?

It can change what visitors see. Use the Health Check and Troubleshooting plugin, which disables plugins only for your own session, or test on a staging copy.

Where do I find debug.log?

Add the lines WP_DEBUG and WP_DEBUG_LOG set to true in wp-config.php, reproduce the problem, and open wp-content/debug.log through your hosting file manager.

Is my pasted log sent to your server?

No. Pasted messages are analysed in your browser. Only the site address, if you enter one, is checked by our server.

Related tools

About this tool: free, no sign-up, works on phone and desktop. Last reviewed: November 2026.

Try these next

Share this tool

Scroll to Top