# Free Online JSON to CSV Converter

> Convert JSON to CSV and CSV back to JSON. Nested objects flatten to dotted columns, quoting follows RFC 4180. Runs in your browser. Free online.

Canonical: https://stayslocal.app/dev/json-to-csv-converter
Last updated: 2026-08-16

JSON is a tree and CSV is a rectangle, so converting between them is a decision about how to lose or restore structure. This does it in both directions, in the browser, so a customer export never has to be uploaded to a stranger's server to become a spreadsheet.

## RFC 4180, and where real files break it

CSV's rules are short: fields are comma-separated, a field containing a comma, a quote or a newline is wrapped in double quotes, and a literal double quote inside a quoted field is doubled. RFC 4180 specifies CRLF line endings, though almost everything accepts LF. The rest — semicolons in European exports, tab-separated files, a UTF-8 BOM that Excel wants and parsers do not — is convention rather than spec.

Fields:
- Delimiter: Comma by default. Semicolon is common wherever the comma is a decimal separator; tab makes a TSV.
- Quoting: A field is quoted when it contains the delimiter, a double quote or a line break. Inner quotes are doubled: she said "no" becomes "she said ""no""".
- Flattening: Nested objects become dotted headers — {"user":{"id":7}} is a column named user.id. Arrays are indexed as tags.0, tags.1.
- Ragged rows: Records with different keys produce the union of all columns; a record missing a key gets an empty cell, not a dropped row.
- Types: CSV has no types. Converting back, everything arrives as a string unless you ask for numbers and booleans to be inferred.

## How to convert JSON to CSV online

1. Paste JSON or CSV — An array of objects converts most cleanly; a single object becomes one row.
2. Set the delimiter and header options — Comma, semicolon or tab, and whether the first row is a header.
3. Copy or download the result — Take the CSV into a spreadsheet, or the JSON into a request body.

## Where JSON to CSV conversion earns its place

- Turning an API export into something a colleague can open in Excel.
- Loading a spreadsheet of test data into a seed script as JSON.
- Flattening nested analytics events into columns for a quick pivot.
- Checking that a CSV a client sent parses before a bulk import touches it.

## Questions

**Does deeply nested JSON survive the round trip?**

Not always. Flattening to dotted columns and back reconstructs objects and indexed arrays, but an array of mixed shapes, or a key that already contains a dot, cannot be restored unambiguously. Check a sample before trusting a bulk conversion.

**Is my data uploaded to convert it?**

No. Both directions run in this browser tab, so an export containing names, emails or order data never leaves your device.

**Why does Excel mangle my accented characters?**

Excel guesses the encoding of a plain UTF-8 CSV and often guesses wrong. Adding a UTF-8 byte order mark fixes it in Excel and can confuse stricter parsers, so it is an option rather than the default.

**What happens to null values?**

A null becomes an empty cell, which is the usual convention but is lossy: on the way back, an empty cell is indistinguishable from an empty string. If the difference matters, keep the data as JSON.

## Related

- [JSON Formatter](https://stayslocal.app/dev/json-formatter): Format, validate and minify JSON
- [JSON ↔ YAML](https://stayslocal.app/dev/json-to-yaml-converter): Convert JSON to YAML and back
- [Developer Tools](https://stayslocal.app/dev): every tool in this family
