Log and Stack Trace Formatter
Turn raw logs and JSON log lines into a readable table you can filter by level and search, and tidy stack traces with library frames folded away.
How to make logs readable
Paste your log lines or stack trace
Paste or type your log lines or stack trace into the box, or press Try an example.
Filter
Choose the lowest level to show and search the messages.
Read or copy
Each entry shows its time, level and message, with stack traces kept with their entry.
Worked example
This is what Log and Stack Trace Formatter gives for its own sample values. Open the tool above and change anything to try your own.
Log lines or a stack trace
{"level":"info","time":"2026-11-18T09:14:02.118Z","msg":"server started","port":3000}
{"level":"warn","time":"2026-11-18T09:14:09.402Z","msg":"slow query","ms":1840,"sql":"select * from orders"}
2026-11-18 09:14:12,551 ERROR [worker-2] Payment failed for order 1042
java.lang.IllegalStateException: card declined
at com.acme.pay.Gateway.charge(Gateway.java:88)
at com.acme.pay.Worker.run(Worker.java:41)
at java.base/java.lang.Thread.run(Thread.java:1583)
{"level":"debug","time":"2026-11-18T09:14:13.004Z","msg":"retry scheduled","order":1042}
[2026-11-18T09:14:20Z] INFO health check ok- Read as
- Detect
- Lowest level to show
- Everything
- Search
- Fold library frames in stack traces
- Yes
Readable log
2026-11-18T09:14:02.118Z INFO server started {"port":3000}
2026-11-18T09:14:09.402Z WARN slow query {"ms":1840,"sql":"select * from orders"}
2026-11-18 09:14:12,551 ERROR [worker-2] Payment failed for order 1042
java.lang.IllegalStateException: card declined
at com.acme.pay.Gateway.charge(Gateway.java:88)
at com.acme.pay.Worker.run(Worker.java:41)
... 1 library frame hidden
2026-11-18T09:14:13.004Z DEBUG retry scheduled {"order":1042}
2026-11-18T09:14:20Z INFO health check okResult
- Entries
- 6 shown of 6
- By level
- debug 1, info 2, warn 1, error 1
| Time | Level | Message | Other fields |
|---|---|---|---|
| 2026-11-18T09:14:02.118Z | INFO | server started | {"port":3000} |
| 2026-11-18T09:14:09.402Z | WARN | slow query | {"ms":1840,"sql":"select * from orders"} |
| 2026-11-18 09:14:12,551 | ERROR | [worker-2] Payment failed for order 1042 | |
| java.lang.IllegalStateException: card declined at com.acme.pay.Gateway.charge(Gateway.java:88) at com.acme.pay.Worker.run(Worker.java:41) ... 1 library frame hidden | |||
| 2026-11-18T09:14:13.004Z | DEBUG | retry scheduled | {"order":1042} |
When to use Log and Stack Trace Formatter
A wall of JSON log lines from a container or cloud console needs to be read quickly during an incident.
An exception was logged on one line with escaped newlines and you need it in a readable form.
Tips for a better Log and Stack Trace Formatter result
Set the lowest level to warn to hide routine messages, then search for an id such as an order number to follow one request.
Keep library frames folded to find your own code fast, and unfold them only when the fault seems to be inside a library.
Log and Stack Trace Formatter: limits and what to check
Log formats vary widely, so a line without a recognisable time or level is shown with those columns empty.
Very large logs are better filtered on the server first, since only the first 2,000 entries are shown in the table.
About Log and Stack Trace Formatter
Make raw logs readable. JSON logs from tools such as pino, bunyan, winston and structlog are split into time, level and message with the other fields kept, and plain text logs are read by their timestamp and level. Stack traces from JavaScript, Java, Python, .NET and Go are tidied, and library frames are folded so your own code stands out.
FAQs
My stack trace is on one line with \n in it. Will that work?
Yes. Escaped newlines from JSON logs are turned back into lines first.
How are numeric levels read?
pino and bunyan numbers map to names: 10 trace, 20 debug, 30 info, 40 warn, 50 error, 60 fatal.
Which frames are folded?
Frames from node_modules, Node.js internals, the Java and Spring runtime, Python site-packages and similar library code.