CSV ↔ JSON Converter
Convert CSV to JSON and back — with real CSV parsing that handles quotes, commas and line breaks in fields.
About this tool
CSV and JSON are the two universal data formats — spreadsheets and exports speak CSV, APIs and code speak JSON — and moving data between them is one of the most common tasks in practical data work. It's also where naive converters quietly corrupt data: real CSV allows commas inside quoted fields ("Mumbai, India"), quotes escaped by doubling (""), and even line breaks within a field. Split on commas and all of that breaks.
This converter parses CSV properly, with a real state machine that honors the quoting rules — so an address field containing a comma stays one field, and a quoted note spanning two lines stays one value. Going the other way, JSON → CSV unions the keys across all objects (so records with different fields still align into consistent columns), quotes and escapes any field that needs it, and stringifies nested values rather than dropping them.
CSV → JSON treats the first row as headers and produces an array of objects — the shape APIs and JavaScript code expect. Delimiter is selectable: comma, semicolon (common in European locales where the comma is the decimal separator), or tab. Convert, then copy or download the result as a file. Everything runs locally, which matters here more than most tools — customer lists and business exports never leave your machine.
How to use the CSV ↔ JSON Converter
- 1Choose direction: CSV → JSON or JSON → CSV.
- 2Pick your delimiter — comma is standard; semicolon is common in European exports.
- 3Paste your data — CSV needs a header row; JSON should be an array of objects.
- 4Copy the result or download it as a file.
Frequently asked questions
My CSV has commas inside values — will it break?
Not here. Proper CSV wraps such fields in quotes ("Mumbai, India"), and this converter implements the real quoting rules — embedded commas, doubled quotes and even line breaks inside quoted fields all parse correctly, where naive split-on-comma tools fail.
Why do my European CSV files use semicolons?
In locales where the comma is the decimal separator (1,5 meaning 1.5), spreadsheets export with semicolons as the field delimiter to avoid ambiguity. Switch the delimiter to semicolon and those files convert normally.
What JSON shape does the converter expect and produce?
An array of flat objects: [{"name": "Jane", "age": 34}, …]. CSV → JSON produces exactly this shape, using the header row as keys. JSON → CSV accepts objects with differing keys and unions them into one consistent column set.
What happens to nested objects when converting to CSV?
CSV is flat, so nested values are stringified into their JSON text within the cell — data is preserved rather than dropped, but a deeply nested structure is fundamentally better represented in JSON. Flatten first if you need true columns.
Related tools
JSON Formatter & Validator
Format, minify and validate JSON instantly — with exact error positions when something's wrong.
Open toolDiff Checker
Compare two texts and see every added and removed line highlighted — like git diff, in your browser.
Open toolRemove Duplicate Lines
Delete duplicate lines from any list in one click — with a count of exactly how many were removed.
Open toolBase64 Encode / Decode
Convert text to Base64 and back — UTF-8 safe, so emoji and non-English characters survive.
Open tool