Log Beautifier

Raw logs are written for machines, not for eyes. Log Beautifier turns delimiter-dense lines into aligned column tables and word-wraps the long ones, so a quick scroll tells the story instead of a squint.

Pipe-separated blocks line up; long lines wrap on word boundaries, keeping your reading flow intact.

The tool works line by line, so it does not need to know your log's schema in advance. Any run of consecutive lines that each contain two or more " | " separators is treated as one table block: the widest value in each column across that block sets the padding width, so every separator in the block lines up vertically no matter how much the field lengths vary from row to row. Once a block ends — a line without a pipe separator breaks it — a fresh block starts on the next qualifying line, so unrelated pipe-formatted sections in the same paste are aligned independently rather than forced into one oversized table. Lines that are not part of a pipe block go through the word wrapper instead: text is split on whitespace and rebuilt greedily up to the chosen width, wrapping only between words (never inside a token), so a long stack trace path or URL stays whole even if it pushes a wrapped line past the target width. Continuation lines are indented so it is visually clear they belong to the line above.

• Column alignment — consecutive pipe-delimited lines are grouped into blocks and aligned independently.
• Word wrap — selectable 60/80/100/120 character widths, never splitting a token mid-word.
• Auto mode — pipe blocks are aligned and everything else is wrapped, automatically, in a single pass.
• Per-run stats — lines in, lines out, and the widest resulting line.
• Clipboard export — copy the beautified result in one click.

1. Paste raw log lines — pipe-delimited event lines, long single-line stack traces, or a mix of both.
2. Choose auto (align + wrap), wrap-only, or columns-only mode, and a wrap width if wrapping applies.
3. Beautify. Pipe blocks align into tidy columns; long non-tabular lines wrap on word boundaries.
4. Copy the readable result into a ticket, chat message, or incident doc.

Example 1 — Structured spam. A run of lines like time | level | message | key=value | key=value becomes a tidy aligned table, with every column padded to the widest entry so the pipes form a straight line down the page.

Example 2 — Stack traces. 300-character one-liners wrap to a readable width without splitting file paths, URLs, or identifiers, since the wrapper only breaks on whitespace.

Example 3 — Incident review. Column-aligned output pastes cleanly into a ticket or Slack code block and looks like it was formatted on purpose, saving the manual cleanup reviewers usually do by hand.

Example 4 — Mixed paste. A paste containing both a block of structured event lines and a raw exception dump handles both correctly in auto mode — the event lines become a table, the exception wraps to width — without needing to run the tool twice.

• Readability — aligned columns make repeated fields easy to scan and compare.
• No token split — word-safe wrapping keeps identifiers, paths and URLs intact.
• Share-ready — output pastes cleanly into tickets, docs and chat.
• Measurable — in/out line counts and widest-line stat confirm the reformat did what you expect.
• Private — all formatting happens in-browser.