A quiet little converter
Paste a table or choose a file
Your result appears here
CSV TO JSON / GUIDE
CSV stores a table as rows of text; this converter maps each header to a JSON key and each data row to an object. Use it when a spreadsheet, report, or database export needs to feed a script or API that expects JSON. Paste the text or choose a local .csv file, then copy or download an array of objects, a keyed object, or JSON Lines. Parsing happens in this browser tab, so the input file is not uploaded.
HOW TO USE
.csv file with its column names in the first row.sku,name,active 0072,"Desk, walnut",true
[
{
"sku": "0072",
"name": "Desk, walnut",
"active": true
}
]The comma inside the quoted name stays in one field, the zero-padded SKU remains text, and true becomes a Boolean.
BEFORE YOU CONVERT
Symptom: every record appears as one field. Cause: a spreadsheet export can use semicolons or tabs even when the filename ends in .csv. Fix: inspect the header row and select the separator actually between its values; do not replace punctuation throughout the file.
One spreadsheet user described the result as “all concatenated in one column.” Read the discussion.
Symptom: a note is split into extra records or a row reports the wrong number of fields. Cause: a newline or separator inside a quoted field is data, while an unmatched quote makes the boundary ambiguous. Fix: keep the full field in double quotes, write a literal quote as "", and re-export the source if its quoting was stripped; a parser cannot safely reconstruct missing boundaries.
Parser troubleshooting discussions show why line-by-line splitting fails on quoted newlines; see the example.
Symptom: a label such as NULL becomes JSON null, or an empty cell is no longer an empty string. Cause: CSV has no declared cell types, and this page infers numbers, Booleans, and nulls while preserving leading-zero values such as 0072 as strings. Fix: keep identifiers zero-padded, replace a literal label like NULL with a temporary non-reserved marker before conversion, then restore it after checking the JSON.
That distinction matters in real exports: people report losing zeros when spreadsheet software reopens CSVs, while this converter preserves them in its output; read one such troubleshooting thread.
GOOD TO KNOW
Paste CSV text or choose a file, confirm the separator and header setting, then copy or download the live JSON result.
Yes—choose Tab in the Separator menu before you use the output.
The selected separator probably does not match the character between the fields; inspect the header row and choose Comma, Semicolon, Tab, Pipe, or the matching custom character.
Yes—keep the whole field inside double quotes and write each literal quote as "".
No—the text and selected file are parsed in this browser tab and are not sent to a conversion server.
The converter preserves leading-zero identifiers as strings so the zeros are not lost to number conversion.
This page maps an empty cell and the case-insensitive text token null to JSON null; use a temporary marker if that word is literal data.
No—each object key must be unique, so use Array of objects when repeated IDs represent separate records.