Culprit – Conflict Detection
Find the plugin or theme that broke your site. Culprit catches fatal errors and white screens and names the culprit in plain English.
Use with caution
Culprit – Conflict Detection works, but test it on a staging site before relying on it in 2026. Was last updated 2 months ago, and scores 55/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Culprit – Conflict Detection stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| conflict | >100 |
| debug | >100 |
| fatal error | >100 |
| troubleshooting | >100 |
| white screen | >100 |
About Culprit – Conflict Detection
From the official readme · v1.0.1Description
When your WordPress site breaks, the first question is always the same: which plugin or theme did it? Culprit answers that.
Culprit catches PHP fatal errors and the White Screen of Death the moment they happen, identifies the plugin or theme that owns the failing code, and shows you a clear, readable incident: what broke, when, and how many times. If you choose to enable it, an optional early-boot watcher extends coverage to crashes that occur before plugins load — even when the crash happens so early that you can’t reach your admin.
This is the free core. It runs quietly, costs almost nothing, and never touches your site — it only observes.
What Culprit does (free)
- Catches PHP fatal errors and white screens the moment they happen.
- Optional early-boot watcher (explicit opt-in) that also catches crashes occurring before plugins load.
- Identifies the plugin or theme responsible for the failing file.
- Shows recent changes around the time of the crash for context.
- Lists incidents with the culprit, time, and occurrence count.
- Environment report — WordPress, PHP, database, server, theme, and plugin versions in one place, exportable as a support report.
- Reports the watcher’s health, with a graceful fallback if your host restricts the mu-plugins directory.
Premium (available at manicsoup.com)
- Correlation and confidence scoring — see what changed right before the crash.
- Time Machine debugging — compare the last known good state with today and see exactly what changed before the problem started.
- Hook Inspector — see which plugins attach to any hook, in execution order, plus a lifecycle timeline of real page loads.
- Conflict history to surface chronic offenders.
- Exportable conflict reports.
Elite
- Active deep scan — prove the culprit by safely reproducing the conflict.
- Recovery Assistant — one-click recovery that disables only the plugin that broke your site.
- Detect conflicts that break behavior without throwing an error.
Installation
- Upload the plugin to
/wp-content/plugins/culpritor install it through the Plugins screen. - Activate it. Crash capture works immediately, no setup required.
- Optionally, enable the early-boot watcher on the Culprit → Status screen to also catch crashes that happen before plugins load.
- Visit the Culprit menu to see detected incidents.
Frequently asked questions
Does Culprit slow down my site?
No. The watcher is tiny and only does work when a fatal error actually occurs.
Does it change anything on my site?
No. The free version only observes and reports. It never modifies, disables, or deletes anything.
Does Culprit write files outside its own folder?
Only if you explicitly enable the optional early-boot watcher on the Status screen — that installs a small must-use loader in wp-content/mu-plugins so crashes during earliest boot can be caught. Nothing is installed automatically, and disabling the watcher (or deactivating/uninstalling Culprit) removes it. Crash captures are stored in a protected folder inside your uploads directory.
What if my host won’t let it install the watcher?
Culprit falls back to a standard handler that still catches most crashes, and tells you in the Status tab.
Changelog
1.0.1
- The early-boot watcher is now an explicit opt-in on the Status screen; nothing is written outside the plugin folder without your action, and the standard crash handler is always active.
- Crash captures now live in a protected, unpredictably-named file in the uploads directory, resolved via wp_upload_dir() with no hard-coded paths.
- Request URLs recorded with a crash are sanitized before being stored.
1.0.0
- First public release.
- Early-boot watcher catches fatal errors and white screens, even when the crash happens before WordPress finishes loading.
- Culprit identification: the plugin or theme that owns the failing code, named in plain English with an honest confidence score.
- Recent-change context around every crash.
- Environment report with a downloadable plain-text support report.
- Premium: correlation & confidence scoring, Time Machine debugging, Hook Inspector & page-load timeline, conflict history, exportable conflict reports.
- Elite: active deep scan that safely reproduces a conflict to prove the culprit, and the Recovery Assistant for one-click recovery.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Culprit – Conflict Detection alternatives
All conflict plugins →
FAQ
Culprit – Conflict Detection: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 28, 2026
Is Culprit – Conflict Detection free?
Yes. Culprit – Conflict Detection is free to download and use from the official WordPress.org plugin directory.
Is Culprit – Conflict Detection safe to use in 2026?
Culprit – Conflict Detection works, but test it on a staging site before relying on it in 2026. Was last updated 2 months ago, and scores 55/100 on our health check.
How many websites use Culprit – Conflict Detection?
Culprit – Conflict Detection is active on <10 WordPress websites and has been downloaded 167 times since it launched in August 2026. It was downloaded 64 times in the last 30 days.
Does Culprit – Conflict Detection work with WordPress 7.1?
Culprit – Conflict Detection is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Culprit – Conflict Detection need?
Culprit – Conflict Detection requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Culprit – Conflict Detection last updated?
The latest version, 1.0.1, was released on August 6, 2026 (2 months ago).
Who makes Culprit – Conflict Detection?
Culprit – Conflict Detection is developed and maintained by ManicSoup.
What are the best alternatives to Culprit – Conflict Detection?
The most popular alternatives to Culprit – Conflict Detection are Block editor assets filter (10+ installs), Tahhan Conflict Detective (<10 installs) and PreFlight Scanner (<10 installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
