>_ tools --debug-log

WordPress Debug Log Analyzer

Paste a WordPress debug.log (or upload it) and get a readable, grouped dashboard - top repeated errors, level breakdown, stack traces, and plain-language "what this means" hints. Your log never leaves this device.

paste or upload a WordPress debug.log → readable, grouped, actionable. 100% client-side.

your log never leaves this device - nothing is uploaded, ever

PASTE LOG

or
no server · no uploads · parses entirely in your browser
WordPress .htaccess Generator Lock down the paths your log keeps complaining about. wp-config.php Generator Flip WP_DEBUG rules correctly after you fix the cause. Nginx Config Generator Serve WP on nginx with the same hardening mindset. JSON Formatter Paste-and-go validation - same privacy promise.

>_ FAQ

How do I read a WordPress debug.log?

Paste the log into the analyzer (or upload the file) and it groups repeated errors, shows the level breakdown, surfaces stack traces, and adds a plain-language "what this means" hint per group - so you see what actually matters instead of scrolling thousands of lines.

Is my debug.log uploaded anywhere?

No. The log is parsed entirely in your browser - nothing is ever sent to a server, so your error log stays private even when it contains paths, usernames, or plugin names.

Why does the same warning appear hundreds of times?

That is a repeated error - WordPress re-logs it every time the code path runs. The analyzer aggregates identical messages (same level + message + file:line) into one group and counts the repeats, so a "wall of warnings" collapses into its real causes.