WordPress Debug Log Analyzer
Paste or upload a WordPress debug.log to parse entries by type, group duplicate errors with counts, and see a filterable list of the unique problems sorted by frequency. The log never leaves your browser.
About the WordPress Debug Log Analyzer
The WordPress Debug Log Analyzer reads a debug.log file and turns a wall of repeated errors into a clear summary. It parses each line by type (PHP Fatal, Warning, Notice, Deprecated, and Database errors), groups identical messages together with an occurrence count, and lists the unique problems sorted by how often they happen. It is built for WordPress developers, site owners, and support staff who need to find the real issues fast. The log is read entirely in your browser; nothing is uploaded or stored.
How it works
- Paste the contents of your debug.log into the box, or upload the file with the Upload button.
- Click Analyze. The tool parses every line, sorts entries into types, and merges duplicate messages into one row with a count.
- Read the summary counts per type at the top, then scan the unique-message list, which is sorted by frequency by default.
- Use the type filters and the search box to narrow the list down to the errors you care about.
Features
- Parses PHP Fatal, Warning, Notice, Deprecated, and WordPress Database entries.
- Groups identical messages and shows an occurrence count for each unique issue.
- Summary bar with a total and a count for every error type.
- Filter by type and search by text, with results sorted by frequency.
- Runs fully client-side: your log never leaves the browser.
Frequently asked questions
Is my debug.log uploaded anywhere?
No. The file is read and parsed entirely in your browser. Nothing is sent to a server or saved, so logs that contain file paths or internal details stay on your machine.
How do I enable the debug log in WordPress?
Add these lines to wp-config.php above the "stop editing" comment: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); The log is then written to wp-content/debug.log.
How are duplicate errors grouped?
Entries are normalized so messages that differ only by numbers, quoted strings, or variable names are treated as the same issue. Matching entries are merged into one row and the count shows how many times that issue appeared.
Which entry types does it detect?
It recognizes PHP Fatal error and Parse error (shown as Fatal), PHP Warning, PHP Notice, PHP Deprecated, and WordPress database error lines. Lines it cannot classify are listed as Other.
Is there a size limit?
There is no fixed limit set by the tool. Because parsing happens in your browser, very large logs are limited only by your device's available memory and may take a moment to process.