Convert CSV files and pasted tables into JSON objects with automatic delimiter detection and header mapping.
Processed locally in your browser
Processed locally in your browser — data is never uploaded, logged, or stored.
A spreadsheet export contains name, age, and city columns. The converter maps the header row to keys and produces objects for each data row. Note that "30" stays a string — CSV carries no type information, and the converter never guesses.
| Input | Value |
|---|---|
| csv | name,age,city
Alice,30,Paris
Bob,25,"New York" |
| Result | [{"name":"Alice","age":"30","city":"Paris"},{"name":"Bob","age":"25","city":"New York"}] |
object = { header_1: cell_1, …, header_n: cell_n }
| Symbol | Meaning |
|---|---|
header_i | value of the first row, i-th column |
cell_i | value of the data row, i-th column |
Every value is a string — CSV has no type information. Numbers stay quoted in JSON output; convert types in your application.
quoted ⇔ cell contains delimiter, quote, or newline
| Symbol | Meaning |
|---|---|
quote | a double-quote inside a quoted field is doubled ("") |
Last reviewed August 4, 2026 · Version 1.0.0 · Toolivaro does not guarantee external content.
No — CSV has no type information, so every value stays a string ("30", not 30). Converting types in the receiving application is safer than guessing, which is why the converter never guesses.
It is parsed as a single cell: "New York, NY" stays one value. Embedded double quotes are doubled (RFC 4180) and unescaped on parse.
Yes — the delimiter is auto-detected from common candidates, and you can override it manually with the delimiter selector if detection picks wrong.
Found a mistake or have a correction? Report it — we review every correction.