Log formatter for raw and JSON logs
Paste raw log output and get embedded JSON pretty-printed, lines color-coded by level, error/warning filters, and per-level counts — without uploading a single line.
Log Formatter
Paste raw application logs. JSON payloads are pretty-printed, levels are color-coded, timestamps dimmed. Everything stays in your browser.
Formatted output will appear here.
Make a wall of log text readable in seconds
Logs copied from a terminal, a container, or a CI run arrive as a dense wall of text: single-line JSON blobs, mixed levels, and the one error you need buried between hundreds of info lines. Reading them raw means squinting for "level":"error" and mentally re-indenting JSON — slow exactly when you are debugging under pressure.
This formatter takes the paste as-is. Embedded JSON is detected and pretty-printed, every line is color-coded by its detected level, and one click filters down to errors or warnings only. Per-level counts at the top tell you instantly whether you are looking at three errors or three hundred. It all runs locally in your browser — your logs, which often contain internal details, never leave your machine.
How to format your logs
- 1
Paste raw log output
Copy logs from your terminal, docker logs, kubectl, or a CI job and paste them straight in — mixed plain-text and JSON lines are fine.
- 2
Read the formatted view
Embedded JSON is pretty-printed and each line is color-coded by level, so errors, warnings, and info lines separate visually at a glance.
- 3
Filter and count by level
Use the level filters to show only errors or warnings, and check the per-level counts to size the problem before you dig in.
Log formatter FAQ
Is this log formatter free?
Yes. It is completely free with no signup and no limits on how much you paste.
Are my logs uploaded anywhere?
No. Parsing, coloring, and filtering all happen in your browser. Logs often contain internal hostnames, IDs, and stack traces — they stay on your machine.
What log formats does it understand?
Plain text lines, single-line JSON (one object per line, as most structured loggers emit), and mixed output where JSON is embedded inside text lines.
How are log levels detected?
From common patterns: level/severity fields in JSON lines, and tokens like ERROR, WARN, INFO, and DEBUG in plain-text lines. Lines without a recognizable level are left unstyled.
Explore more
Capabilities
By framework
Tired of pasting logs into a formatter?
AllStak log management ingests your structured logs directly, with level filtering, full-text search, and linking from a log line to the error and trace behind it — across every service, in one place.