Log File Parser & Filter
Parse, filter, mask sensitive credentials and IP addresses, and export JSON Lines, Nginx access logs, and application logs locally.
Active File: sample-microservices.jsonl (8 lines parsed)
Log File Parser & Filter
Parse, filter by severity, mask sensitive fields, and export logs locally.
Overview
The Log File Parser & Filter inspects, structures, and queries large application logs, JSON Lines (JSONL), and Nginx or Apache access logs directly within your browser. With instant severity filtering, regex-powered search, configurable privacy masking (IP addresses, emails, and bearer credentials), and visible malformed line diagnosis, it provides full log analysis capabilities without exposing sensitive server logs to third-party cloud services.
How to Parse and Filter Log Files
Drag and drop any .log, .jsonl, or .txt file into the inspector, or select one of the built-in microservice, Nginx access, or Laravel application samples.
Use Auto-Detect to let the parser identify JSON Lines or Combined Access logs, or explicitly choose JSONL, Access, or Generic Syslog modes.
Filter entries by clicking severity badges (ERROR, WARN, INFO, DEBUG, CRITICAL) or search through message content and parsed fields using plain text or regex.
Any malformed lines or corrupted JSON rows remain visible with their original line numbers preserved for debugging.
Toggle privacy switches to automatically mask IP addresses, email addresses, and authorization tokens, then export the filtered and masked view as a clean log file.
A microservice log file containing 5,000 lines with user emails, IP addresses, and 12 unhandled 500 error exceptions
A filtered view of only the 12 error lines with all IPv4 addresses masked to ***.***.***.*** and emails masked to u***@***.com
The parser extracts structured JSON fields, isolates error severity lines, and applies regex masking before exporting.
- File Size Limit: Up to 20 MiB processed locally in memory.
- Supported Formats: JSON Lines (.jsonl), Nginx/Apache Combined & Common Access logs, and generic timestamped text logs.
- Pagination: Large files are paginated into 50-entry windows for instantaneous responsiveness.
- Zero log lines, passwords, or IP addresses are sent to any server.
- All parsing, filtering, and text exports run purely in client-side JavaScript.