Convert JSON to CSV Online
Private by design — runs entirely in your browser
Flatten a JSON array of objects into a clean CSV file, in your browser. Toova picks up column names from your keys, escapes commas and quotes properly, and gives you CSV output that opens cleanly in Excel, Google Sheets, or any data pipeline.
Why use Toova for JSON to CSV
Most online converters refuse anything beyond a simple flat structure. Toova handles nested objects by dotting the keys (user.email) and lets you skip fields you do not want. The output uses RFC 4180 quoting, so commas inside strings, embedded quotes, and newlines all survive a round trip through Excel or any CSV parser without breaking columns.
Headers, delimiters, and quoting
The first row is generated from the union of keys in your input, so missing fields show up as empty cells instead of misaligning the columns. You can pick comma, semicolon, or tab as the delimiter — useful when the locale on the target machine uses semicolons. Strings are quoted only when necessary, keeping the output compact.
Private by default
Toova converts everything locally in your browser. The JSON array you paste is never transmitted to any server. That is the right model when the data contains user records, billing rows, or anything you cannot share. After the page loads you can disconnect from the network and the conversion still works.
Frequently Asked Questions
- What if my JSON objects have different keys?
- The converter scans every object and builds the column header from the union of all keys. Missing fields produce empty cells instead of shifting columns, so the CSV stays aligned even when the input is heterogeneous.
- How are nested objects handled?
- Nested objects flatten using dot notation, so user.email and user.address.city become their own columns. Arrays of primitives serialize as JSON strings inside a single cell — predictable and easy to parse back.
- Can I change the delimiter?
- Yes. Pick comma, semicolon, or tab depending on what the target tool expects. Spreadsheet apps in European locales often default to semicolons because the comma is used as the decimal separator.
- Will the output open cleanly in Excel?
- Yes. The CSV uses RFC 4180 quoting rules, escapes embedded quotes, and quotes strings that contain commas or newlines. Excel, Google Sheets, and Numbers all read it without column drift.
- Is my data sent anywhere?
- No. The conversion runs locally in your browser. Nothing is uploaded or stored. That matters when the JSON contains customer records, billing data, or anything covered by privacy rules.