JSON to CSV

Best results come from a homogeneous array of objects, like a database query result:

[
  { "id": 1, "name": "Alice" },
  { "id": 2, "name": "Bob" }
]

Mixed shapes still work — each unique key across all objects becomes a column, with empty cells where missing.

Real-world JSON has nesting. With Flatten on:

{ "user": { "address": { "city": "NYC" } } } → column "user.address.city"

You can change the separator (default .) to _ or / for tools that don't tolerate dots in column names. Arrays inside an object are JSON-encoded into a single cell — turn flatten off if you want to keep raw [Object] placeholders.

• UTF-8 BOM — without it, Excel misreads é, ü, 中. Always tick the BOM box when generating for Excel.
• Locale delimiter — Excel in German / French / Italian opens semicolon-delimited CSVs by default; comma-delimited files end up in column A.
• Leading zeros — "00123" becomes 123 because Excel auto-types as number. Pre-quote critical strings in the JSON before conversion.
• Long numbers — 15+ digit integers lose precision in Excel. Cast to string in your JSON if you need the exact value.

When to reach for it. Use it to turn an array of JSON objects into a spreadsheet-ready CSV for analysis or import.

When something else is better. Deeply nested or ragged JSON doesn’t map cleanly to a flat grid — you may need to pick which fields to flatten.

The pitfall to watch. Values containing commas, quotes or newlines must be quoted/escaped; unescaped ones silently shift every later column.

Everything runs on your device. The values you enter are processed locally in this browser tab — EpitomeTool does not send your input to a server, store it, or log it. That means you can use the tool offline once the page has loaded, and refreshing the tab wipes the slate.