by
kuber
0 (0 reviews)
Tracedown Culprit Finder
Finds the plugin behind a critical error or white screen, without ever writing the active plugin list. You cannot get stuck, and you get a name.
Tracedown Culprit Finder ranks #62,556 among WordPress.org plugins with 0+ active installations, is #1,273 of 1,633 in the Performance category, and was last updated Oct 16, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.3
v0.1.0
Current Version v0.1.0
Updated 1 week ago
Last Update on 16 Oct, 2026
Refreshed 10 hours ago
Last Refreshed on
#1,273 of 1,633 in Performance
Downloads -42.9% this week
Actively maintained
Rank
#62,556
—
No change
Active Installs
0+
—
No change
KW Avg Position
N/A
—
No change
Downloads
98
+2 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
30,954
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#62,556
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.1.0
- Last Updated
- Oct 16, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.1.3
- PHP Version
- 7.4 or higher
- Author
- kuber
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,762
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,018
LiteSpeed Cache
7M+ installs
#5
Wordfence Security - Firewall, Malware Scan, and Login Security
5M+ installs
#11
Hostinger Tools
3M+ installs
#20
WP Super Cache
1M+ installs
#37
Speed Optimizer - The All-In-One Performance-Boosting Plugin
1M+ installs
#44
WP Fastest Cache - WordPress Cache Plugin
1M+ installs
#47
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
1M+ installs
#52
Maintenance
1M+ installs
#58
Frequently Asked Questions
Common questions about Tracedown Culprit Finder
Yes, as long as you can still reach wp-admin. Start a session, choose "Find it for me", and Tracedown probes your front page with different subsets of plugins loaded until it has the smallest set that still reproduces the error. A PHP fatal error, a 500, a white screen and a blank page all count as broken. If the error is also on the admin side and you cannot log in, see the next question.
Tracedown needs wp-admin to run. If WordPress cannot start at all, rename the plugins folder over SFTP or your host's file manager to get back in, then let Tracedown name the culprit so you only have to remove one plugin instead of guessing.
Run a session. Tracedown tests the plugins that are active right now and returns the minimal set that reproduces the fault, so a plugin that only breaks in combination with another one is still caught. The report lists the plugin name, file and version so you can roll it back or report the bug.
Three ways. It is faster: a deterministic halving search needs a handful of probes instead of one per plugin. It is safer: nothing is ever written to the active plugin list, so there is no "I deactivated everything and now I cannot remember what was on" moment. And it is correct for pairs: two plugins that only break together are found, where a one-at-a-time check reports every single plugin as fine.
Same family of idea, different architecture. Both use a must-use plugin to filter the plugin list for one administrator. Tracedown additionally never writes the active_plugins option on any code path, so there is no restore step that can fail and leave plugins deactivated. It also runs the search for you and names a minimal set instead of leaving the toggling to you.
No. The filter only applies to requests carrying your signed session cookie. Tracedown also marks its own responses as uncacheable so a page cache or CDN cannot store a safe-mode response and serve it to someone else. There is a button in the session bar that opens a logged-out preview so you can see this for yourself.
The session ends by itself. Expiry is evaluated every time the safe-mode file loads, so it needs no cron job, no scheduled task, no traffic and no action from you. Nothing was written to the database, so when the session ends the site is exactly as it was.
If WordPress cannot start at all, no plugin can help you, including this one. Add define( 'TRACEDOWN_DISABLE', true ); to wp-config.php or delete wp-content/mu-plugins/tracedown-safe-mode.php, and you are back to the state you were in before Tracedown was involved.
No. It changes what WordPress loads for one request, for one person. The stored list of active plugins is never modified, which is also why Tracedown complies with the WordPress.org rule that a plugin may not change the activation status of other plugins.
Yes, and safe mode never applies to WP-CLI. wp tracedown status, wp tracedown abort, wp tracedown restore and wp tracedown nuke are registered from the safe-mode file so they keep working even while the plugin itself is filtered out of the active list.
