CSV
Parse CSV properly — quotes, embedded commas and newlines included — then view it as a table or convert it to JSON.
[
{
"id": "1",
"name": "Sanders, Chance",
"role": "dev",
"note": "said \"ship it\" and left"
},
{
"id": "2",
"name": "Ada Lovelace",
"role": "eng",
"note": "two\nlines"
},
{
"id": "3",
"name": "Grace Hopper",
"role": "eng",
"note": ""
}
]RFC 4180 all the way: a quoted field can hold the delimiter, a newline or a doubled "" quote, and comes back out intact. Auto picks the delimiter that gives the most rows the same column count, so a semicolon file full of decimal commas still reads correctly. Short rows are padded rather than rejected and the fix is reported above. Typed values turns 12 into a number and true into a boolean, but leaves 007, 1.50 and anything past 2^53 as strings so nothing is quietly lost.
Splitting CSV on commas works until a field contains a comma, a quote or a line break, which in real exports it always eventually does. Getting this right requires a real parser rather than a one-liner.
Paste or drop a file and it is parsed to the actual format rules, shown as a sortable table, and convertible to JSON. Delimiters other than comma are detected, so tab-separated exports work too.
What people open it for
- Reading a CSV export without opening a spreadsheet
- Converting CSV into JSON for a fixture or an import
- Checking whether a file's quoting is well-formed
In the terminal
tools csv
Every utility is also a command in the desktop's shell.