Log files are usually one long line per event, which makes them hard to read in a spreadsheet. Paste your log lines here and each space-separated field lands in its own column. Everything runs in your browser, so your logs never leave this machine.
How the splitting works
Log lines rarely use commas, so this page splits on runs of whitespace. Extra spaces between fields collapse away, and each remaining field becomes one cell. Timestamps, levels, component names and message text each get a column of their own. Because the split is on whitespace rather than a fixed character, lines with different numbers of fields still work: the table simply widens to fit the longest line, and shorter lines are padded with empty cells so the rows stay square. If a message body itself contains spaces, those words spread across extra columns, which is usually fine for filtering, but you can switch to a different delimiter in the picker if your log uses one consistently.
Keeping the text as text
Numbers are not converted and dates are not reformatted by default, because log fields like request ids and versions must stay exactly as written. A version string such as 2.10 would be mangled by numeric casting, and a timestamp column reformatted as a date can lose the time-of-day detail you need when correlating events. Turn on number or date casting in the fixes panel if you do want conversion, and the change applies to every cell in the table at once, so you can compare both readings before downloading.
Cleaning up the result
Blank lines can be dropped, duplicate events removed, and the whole table sorted by any column once it is split. Sorting by the timestamp column puts events back in order even if you pasted the lines out of sequence, and sorting by the level column groups all the errors together for a quick triage pass. Duplicate removal is exact-match: two rows must be identical in every cell to count as repeats, so two logins from different users are never collapsed into one. Download the result as CSV or Excel when it looks right.
Reading a log table in a spreadsheet
Once the lines are split, the usual spreadsheet tools start to work. Filter the level column to see only errors, sort by timestamp to restore chronological order after you have grouped events, or use a text filter on the component column to pull out one service. Because every field sits in its own cell, none of this needs formulas or manual copying. Pivoting also becomes possible: count events per component per level, or spot which minute of the morning produced the most warnings, directly from the downloaded file.
Private by design
The whole tool runs in your browser. There is no upload step, no account, and no server holding your text, so log lines pasted here never travel anywhere. That matters for logs, which often contain internal hostnames, request paths and user identifiers that you would not want leaving your machine. Close the tab and the pasted text is gone unless you choose to keep your fix settings, which are stored locally and contain no row data.
Questions
Will my log file be uploaded anywhere?
No. The splitting happens entirely in your browser and nothing is sent to a server. You can even disconnect from the network after loading the page and the tool keeps working, which is a simple way to confirm nothing is leaving your machine.
What if my log lines use a different separator?
Pick another delimiter in the picker below the paste box. Comma, tab, semicolon, pipe and whitespace are all supported, and the Auto-detect option there asks the tool to find the separator for you. Some log formats use a tab between structured fields and spaces inside messages; forcing the tab delimiter then gives the cleanest split.
Why are my numbers still text?
Number casting is off by default so ids and version strings stay intact. Tick the cast numbers option to convert numeric-looking cells. This is worth doing before sorting by a numeric column such as a duration in milliseconds, because text sorting would otherwise place 1000 before 900.
Can I handle very large log files?
Paste as much as your browser can hold. The work is local, so large pastes just take a moment longer. If a file is too big to select in your editor, paste it in chunks and tidy each chunk separately, then combine the downloaded CSV files afterwards.
Why is there no header row in the preview?
Log lines are data from the first line, so the header row option is off by default and every pasted line becomes a table row. If your paste does start with a column title line, tick the header row option in the fixes panel and that line moves up to become the header.