Debug Log Viewer
View on WordPress.orgScores higher than 20% of indexed plugins
About
Effortlessly view, search, filter and manage your WordPress debug.log in the admin dashboard. Real-time monitoring and email alerts
Security History
What It Does
Debug Log Viewer adds an admin dashboard interface for reading, searching, and filtering the contents of WordPress's debug.log file without needing FTP or a file manager. It includes real-time monitoring of new log entries and email alerts, so you can be notified when errors appear on a live site.
Who It's For
This plugin fits developers, agency staff, and site maintainers who debug WordPress sites regularly and want a faster alternative to SSH or cPanel file access. The email alerts also make it useful for hosting support teams who need to react quickly to errors on client sites.
Who Should Skip It
If you only need to glance at a debug log once in a while or already use a full debugging suite like Query Monitor, this adds redundant surface area. Casual site owners without developer access probably do not need it either.
The Bottom Line
Debug Log Viewer delivers a focused, actively maintained log viewer with useful email alerts, but its tiny install count and lack of public support history make it hard to fully trust long term. It is a reasonable pick for agencies and freelancers who want a dedicated log tool, though Query Monitor remains the safer default for most developers. Overall Quality Score: 68.13/100.
Related Plugins
Pick Query Monitor if you need deep database, hook, and PHP error analysis in addition to log viewing, with a much larger community behind it.
Choose WP Crontrol if your real debugging pain point is scheduled events and cron jobs rather than log inspection.
WP Debugging is the better pick if you mainly need to toggle WP_DEBUG settings on and off with minimal configuration.
Debug Log Manager is a sensible alternative if you want similar log viewing features from a plugin with a larger install base.
Freesoul Deactivate Plugins only overlaps loosely here, but it is useful if your debugging workflow revolves around isolating plugin conflicts on specific pages.