JSON to CSV Converter Online – Two-Way, Free
JSON in, spreadsheet out — and back.
At a glance
- Input:
- JSON · CSV
- Processing:
- Runs locally in your browser
- Privacy:
- Nothing you type is sent to a server
Last updated: 2026-11-07
Common use cases
- Turning an API response into a spreadsheet for analysis
- Converting an exported CSV back into JSON for an import script
- Flattening nested user records into columns a spreadsheet can read
- Checking how RFC 4180 quoting handles commas and quotes in values
About this tool
A two-way JSON to CSV converter that runs entirely in your browser: nested objects flatten to dot-notation columns, fields are escaped to RFC 4180, delimiters are your choice, and a table preview shows the result before you download it.
How to use it
- Pick a direction: JSON to CSV or CSV to JSON.
- Paste your data, load a sample, or upload a .json or .csv file.
- Choose a delimiter — or leave Auto-detect on for CSV input.
- Copy the result, download it, or check the table preview.
Practical tips
- Use the Swap direction button on a result to round-trip it and verify nothing was lost.
- Leave the delimiter on Auto-detect for European exports — semicolon-separated files are picked up automatically.
- Check the preview table before downloading: empty cells show exactly where a row lacked a key.
Common mistakes
- Pasting a JSON object with trailing commas or single quotes — strict JSON rejects both, and the error names the line and column.
- Expecting a missing CSV cell to vanish in JSON — empty cells become null by design, so the key stays present.
- Forcing comma on a semicolon file — the whole row lands in one column; switch back to Auto-detect.
How this compares
Most online converters are one-way, upload your data, or choke on nested objects. This tool converts both ways locally, flattens nesting with dot notation, escapes to RFC 4180, and previews the table — no upload, no signup. The tradeoff: no streaming for multi-megabyte files; very large pastes convert in full but render in a capped preview.
Good to know
- JSON must be strict — comments, trailing commas and single quotes are rejected.
- Arrays inside objects are stringified into one cell, not expanded into rows.
- Table preview shows the first 10 rows; the full result is in the output box and the download.
- CSV to JSON types values by appearance — a product code like 0123 stays text, but 123 becomes a number.
Frequently asked questions
Does conversion upload my data?
No. Parsing, flattening and escaping all run in your browser — safe even for API payloads with tokens you'd rather not share.
How are nested objects handled?
Nested objects flatten to dot-notation columns — {"address": {"city": "Paris"}} becomes a column called address.city. Arrays are JSON-stringified into one cell. Converting CSV back to JSON restores the nesting from the dotted keys.
How are numbers and booleans handled in CSV to JSON?
Values that look like numbers become numbers, true and false become booleans, and empty cells become null. Values with leading zeros (007, ZIP codes, IDs) stay text so nothing is silently lost.
What if my CSV uses semicolons or tabs?
CSV to JSON auto-detects the delimiter from the header line — it picks the most frequent of comma, semicolon, tab or pipe. You can also force one with the delimiter picker.
What JSON shapes are accepted?
An array of objects, a single object (one row), or an object holding an array — the first array property is used. Missing keys across rows become empty cells.

