Log Formatter
Paste JSON, nginx, Docker, syslog, or plain logs to normalize, filter by level, and inspect them locally in your browser.
Paste JSON logs, nginx access/error lines, Docker logs, or syslog entries. TeaFun normalizes them locally and lets you filter by level or search terms.
What Is a Log Formatter?
The Log Formatter parses, normalizes, and filters log lines from multiple formats into a consistent, searchable view. It recognizes structured JSON logs, nginx access and error logs, Docker container output, syslog entries, and plain-text level-prefixed lines. During incident response, developers pull logs from multiple sources — a Docker container, an nginx reverse proxy, and an application emitting JSON — and need to correlate events quickly. This tool normalizes all of them into a common structure with timestamp, level, source, and message fields. Filter by severity level (trace through error) and search across all fields. Everything runs in the browser, so sensitive production logs are never uploaded.
How to Use the Log Formatter
Paste log lines from any supported source into the input area — you can mix formats in the same paste. Click "Format logs" to parse and normalize all lines. The summary shows total lines, how many were successfully structured, and which formats were detected. Use the level filter to isolate errors, warnings, or specific severity levels. Type in the search box to find lines containing specific messages, IP addresses, or metadata values. Copy the normalized JSON output for further processing in jq or your log aggregator. Lines that do not match any known format are preserved as plain text.
Why Log Normalization Matters
Production systems generate logs in wildly different formats. An nginx access log, a Node.js JSON log, and a syslog message from a Linux service all describe events differently. When an incident occurs, correlating these logs by timestamp and severity is critical for fast root-cause analysis. Log aggregation platforms like Elasticsearch, Datadog, and Grafana Loki work best with consistently structured input. Normalizing logs before ingestion improves search quality and reduces parsing errors downstream. For quick local debugging — especially when you cannot push logs to a central platform — a browser-based formatter that handles multiple formats simultaneously saves precious minutes during outages.
Frequently Asked Questions
Which log formats are supported?
The formatter recognizes structured JSON logs, nginx access/error logs, Docker stream output, syslog-style lines, and plain level-prefixed logs. Unknown lines are still shown as plain text.
Are logs uploaded anywhere?
No. Logs stay in the browser for parsing, filtering, and copy/export actions.
Why are some lines marked as plain?
If a line does not match one of the known formats, it is kept as plain text so you can still search it and inspect it without losing any content.
Use this tool inside a bigger workflow
These collections group follow-up tools and guides that commonly belong in the same job.
Browse same tags
Jump to other tools that share the same workflow, format, or use case.