Most online converters make you upload your file first. This one never leaves your browser.
Free data tool
CSV to JSON Converter
Convert CSV to JSON or JSON back to CSV, right in your browser. Nothing you paste is uploaded.
Runs entirely in your browser using JavaScript. Nothing you paste here is sent to a server, logged, or stored.
How CSV to JSON conversion works
Each CSV row becomes one JSON object, with the first row supplying the field names (turn that off to get an array of arrays instead). Fields wrapped in double quotes can safely contain commas, line breaks, or the delimiter itself, and a doubled quote ("") inside a quoted field represents one literal quote character.
CSV to JSON converter FAQ
How do I convert CSV to JSON?
Paste your CSV into the box, choose the delimiter it uses (comma, semicolon, tab or pipe), and the JSON output updates instantly. Each row becomes one JSON object, using the first row as field names by default.
Does this tool work the other way, JSON to CSV?
Yes. Switch to JSON → CSV mode and paste an array of objects (or an array of arrays); the tool builds a CSV with a header row and correctly quotes any field containing a comma, quote mark or line break.
Is my data uploaded anywhere?
No. The conversion runs entirely in your browser using JavaScript — nothing you paste is sent to a server, logged, or stored, which makes this safe for sensitive spreadsheets and client data.
Why does my CSV need a specific delimiter setting?
Not all CSV files use a comma. Excel exports in many European locales (including Germany) use a semicolon by default, since the comma is already the decimal separator there. Picking the wrong delimiter is the most common reason a "CSV to JSON" conversion comes out wrong.
What happens to quoted fields and commas inside values?
The parser follows the standard CSV quoting rules: a field wrapped in double quotes can contain commas, line breaks or the delimiter itself, and a doubled quote ("") inside a quoted field represents one literal quote character.
Free CSV to JSON converter by ANUPRESS
Why the delimiter setting trips people up
A CSV that opens perfectly in Excel can come out wrong here if you assume the wrong delimiter. Excel in Germany, France and most of continental Europe exports with a semicolon by default, not a comma, because the comma is already used as the decimal separator in those locales. If your JSON output looks like everything got crammed into one field, that’s almost always the fix: switch the delimiter dropdown to semicolon and try again.
Array of objects, or array of arrays
With “First row is header” turned on, each row becomes a JSON object keyed by the column names, which is what most APIs and JavaScript code expect. Turn it off and you get a plain array of arrays instead, useful when the data doesn’t really have a header row, or when you want the raw grid rather than named fields.
What happens to quoted fields
Fields wrapped in double quotes can contain commas, line breaks, or the delimiter itself without breaking the row. A doubled quote inside a quoted field ("") represents one literal quote character, which is the standard CSV escaping rule, and the part most hand-rolled converters get wrong.
Where this fits in a workflow
A common case: export a table from Grist or a spreadsheet, then convert it to JSON to feed into a small script or test against an API. It also runs the other way, turning a JSON API response into a CSV a non-technical teammate can open straight in Excel or Sheets.