JSON to CSV for flat tables — not magic for deep trees

Spreadsheets want rows. Paste a JSON **array of objects**, pick headers from keys, download/copy CSV. Nested objects/arrays are stringified or dotted — labeled clearly so you don’t corrupt analytics.

chars: 41

Input

Output

When to use

Exporting a simple API list for Excel/Sheets, or handing PMs a flat table from an array of objects.

Examples

Input

[{"id":1,"name":"a"},{"id":2,"name":"b"}]

Output

id,name
1,a
2,b

How it works

Detects an array of objects, unions keys for the header, escapes RFC-style fields, joins with commas and newlines. Nested objects become strings or are flattened per implementation.

Common pitfalls

Nested objects/arrays don’t become perfect spreadsheets — flatten first if needed.
Commas and quotes inside fields must be escaped.
Non-array roots aren’t a table; wrap as [{...}].

How this differs

JSON→CSV for tables out; CSV→JSON to rebuild objects. Formatter doesn’t produce CSV.

FAQ

What about nested JSON?

Flatten shallow keys or JSON-stringify nested values; deep trees belong in JSON.

Single object instead of array?

Wrap as one-row array or reject with guidance.

Excel UTF-8 BOM?

Optional BOM toggle if implemented.

Reverse?

CSV to JSON.

Runs in your browser. Nothing is uploaded. Not a security product —hashes and JWT decode are for debugging, not password storage or auth advice.