If you’ve ever asked “how do I find a plugin conflict without breaking my site?”, someone has probably pointed you to Health Check & Troubleshooting, the plugin made by the WordPress.org community. It’s been the standard answer for years, and for good reason.
We make Culprit Finder, so we’re not neutral. But both tools solve the same core problem in a similar way, and the right choice really does depend on your situation. Here’s how they differ.
What they have in common
Both tools switch plugins off only for your browser. Visitors, customers and other administrators keep the normal site the whole time. Neither one touches your real list of active plugins, which is the main thing that makes them safer than deactivating everything from the Plugins screen.
Both also work from a cookie. If something goes badly wrong, clearing your cookies or opening a different browser puts you back on the normal site.
How Health Check’s Troubleshooting Mode works
When you turn on Troubleshooting Mode, Health Check gives you a clean WordPress for your session: every plugin off and a default theme on. From a menu in the admin toolbar you then switch plugins back on one at a time, and switch themes, checking your site after each change.
That gives you full manual control. You decide the order, you can try any combination you like, and you can test the theme in the same session. It also comes with useful extras: debug information you can copy for a support forum, a test for whether your site can send email, and a file integrity check.
The downside is the manual part. With 30 plugins, re-enabling them one by one can take 30 rounds of “switch on, reload, check”. And you have to keep track yourself of what you’ve tried, which gets confusing when two plugins only break together.
It’s also worth knowing that, at the time of writing, Health Check’s page on WordPress.org says it hasn’t been tested with the latest major WordPress releases. That doesn’t mean it’s broken, but check the page for its current status before relying on it.
How Culprit Finder works
Culprit Finder starts from your normal site and does the searching for you. Each step switches off part of your plugin list for your browser, and asks one question: is the problem still there? You answer yes or no, and it halves the list of suspects each time. With 30 plugins that’s around seven questions. Pairs of plugins that only fail together take a few more, and it names both of them.
A few things are built around getting a trustworthy answer:
- You can keep plugins on that the problem needs, like your shop plugin for a checkout bug, so the problem doesn’t vanish for the wrong reason.
- It gives you two safety links before you start, including an emergency exit that works even when you’re logged out.
- If your answers contradict each other, it tells you so instead of blaming the wrong plugin.
- At the end you get a result you can paste into a support forum or send to the plugin author.
What it doesn’t do on its own: test your theme, or give you a general health report of your site. The free plugin only tests plugins. The optional Pro add-on adds a theme check step.
Side by side
| Health Check & Troubleshooting | Culprit Finder | |
|---|---|---|
| Visitors affected | No | No |
| Starting point | Everything off, you switch plugins back on | Your normal site, it switches plugins off |
| Who decides what to test next | You | The plugin, by halving the list |
| Steps for 30 plugins | Up to 30 | About 7 |
| Finds two plugins that only fail together | Yes, if you spot the pattern yourself | Yes, and names both |
| Tests the theme | Yes | Pro only |
| Site Health and debug info | Yes | No |
| Names the culprit at the end | No, you work it out | Yes, with a support report |
| Price | Free | Free (optional paid Pro) |
Which one should you use?
Pick Health Check if you think the theme might be the problem, if you want to poke around freely and try your own combinations, or if you mainly need the debug information for a support request. If you only have a handful of plugins, the manual approach is quick anyway.
Pick Culprit Finder if you have a lot of plugins, if you’d rather answer questions than keep notes, or if you suspect two plugins are clashing. It’s also the better fit when you’re fixing a client’s site and want a clear, shareable result at the end.
There’s no rule against having both. Some people run Culprit Finder to find which plugin is involved, then use Health Check’s debug information when they report the bug. Just don’t run both troubleshooting sessions at the same time. Two tools deciding which plugins load in your browser will only confuse each other, and you.
Either way, do these first
Whichever tool you use, a few minutes of preparation saves a lot of guessing:
- Write down the problem in one sentence you can check, and the exact page where it happens.
- Clear your caches, so you’re not testing an old copy of the page.
- Know how to get back in if a step crashes your site: your host’s file manager or FTP details.
Our guide on how to find which plugin is breaking your site walks through the whole process, with or without a tool.