Convert JSON to CSV and CSV back to JSON, both ways. Choose the delimiter, handle quoted fields, and copy the result. Everything runs in your browser.
How to use the JSON ⇄ CSV
Choose the direction: JSON to CSV or CSV to JSON.
Paste your data and pick the delimiter (comma, semicolon or tab).
Copy the converted result from the output panel.
This converter turns a JSON array of objects into CSV and parses CSV back into JSON, in both directions. Pick the direction, paste your data, choose the delimiter, and copy the result.
It is handy for moving data between spreadsheets, APIs and config files, and the whole conversion is client-side, so your data stays private.
It expects JSON as an array of objects, like [{"name":"Mo","age":3}]. The CSV columns are the union of all the keys across the objects, a single object becomes one row, and any nested value is written as JSON text inside its cell.
It follows the standard CSV quoting rules, so a value that contains the delimiter, a quote or a line break is wrapped in quotes and escaped correctly, and the CSV parser reads those values back without losing data.
You can choose comma, semicolon or tab as the delimiter. Comma is the default and most common; semicolon suits regions where the comma is the decimal separator and spreadsheets expect it; tab produces TSV.
When reading CSV back into JSON, it infers types sensibly: plain numbers and true/false become real JSON values, while a value with a leading zero such as 007 stays as text so identifiers and codes are not mangled.
Frequently asked questions
An array of objects, like [{"name":"Mo","age":3}]. The columns are the union of all keys. A single object becomes one row, and nested values are written as JSON inside the cell.
Yes. Fields containing the delimiter, quotes or line breaks are quoted and escaped following the CSV standard, and the CSV parser reads them back correctly.
When reading CSV, plain numbers and true/false become real JSON values, while values with a leading zero (like 007) stay as text so identifiers are not mangled.
No. The conversion runs entirely in your browser; nothing you paste leaves your device.
Comma is the standard default. Use semicolon in regions where the comma is the decimal separator and spreadsheets expect it, or tab to produce a TSV file.
Embed this tool
Add this tool to your own website. Copy the snippet below; it stays up to date automatically.
<iframe src="https://monu.tools/embed/en/json-csv-converter" width="100%" height="640" style="border:1px solid #e5e5e5;border-radius:12px;max-width:680px" loading="lazy" title="Monu Tools"></iframe>Learn more
How to Convert JSON to CSV (and Keep Nested Data Sane)
Convert JSON to CSV without losing your nested objects: flattening, exploding arrays, delimiters, Excel BOM gotchas, and the round-trip back.
Why Is My JSON Invalid? How to Find and Fix the Error
The six mistakes that break JSON, how to read a parser error, and how to fix invalid JSON fast.
How to Minify JSON to Shrink API Payloads
What minifying JSON actually removes, the realistic 20 to 40 percent size win, and why server compression usually matters more.
YAML vs JSON: Which One Should Your Config Use?
YAML vs JSON compared for config files and APIs: syntax, comments, the Norway problem, indentation traps, TOML, and lossless conversion.
Turn a JSON Response into a TypeScript Interface in Seconds
Generate a TypeScript interface from any JSON response: optional fields, nullables, nested types, and where a single sample falls short.
Related tools
Format, beautify and validate JSON online with clear error messages for invalid input.
Minify and validate JSON in your browser, and see how many bytes you save.
Convert YAML to JSON and JSON back to YAML, both ways. Validates as it converts and shows clear errors. Everything runs in your browser.
Generate TypeScript interfaces from a JSON sample, with nested types, arrays and optional fields. Runs in your browser.