JSON to CSV: instructions, examples and limits
Builds CSV columns from the union of object keys, preserving first-seen order.
Open JSON to CSVThis tool is registered for local processing. Its tool input is handled in the current page; LittleKit’s product analytics do not include the input value.
What it does
Builds CSV columns from the union of object keys, preserving first-seen order. Missing or null values become empty cells; nested values remain JSON strings. All cells are quoted and potential spreadsheet formulas are prefixed with an apostrophe.
Use JSON to CSV for a quick local export of an array of objects when a spreadsheet or analyst needs rows and columns.
How to use it
- 1
Provide a JSON array whose records are objects.
- 2
Review the union of column names and the escaped CSV output.
- 3
Download the file, then confirm how your spreadsheet interprets dates, nulls and nested values.
Worked example
[{"name":"Alex","hours":3}] becomes a CSV header and one data row.
The example demonstrates the operation. For file-based tools, results depend on the selected file and options.How the result is produced
Builds CSV columns from the union of object keys, preserving first-seen order. Missing or null values become empty cells; nested values remain JSON strings. All cells are quoted and potential spreadsheet formulas are prefixed with an apostrophe.
Important limits
Processed in this browser. Maximum 100,000 input characters and 10,000 records. JavaScript JSON parsing can round large numbers and keeps the last duplicate key; quote identifiers to preserve them. Formula protection intentionally changes leading =, +, -, @ and control-character values, including negative numbers. Verify spreadsheet import settings; CSV has no type information.
Checks before sharing or relying on the result
- Nested values are represented as JSON text rather than guessed into extra columns.
- Records with missing keys produce an empty cell for that column.
- CSV is a data interchange format; review formulas and leading zeros before opening it in a spreadsheet.
Choosing the next step
Treat these tools as a local scratchpad. Validate the format before transforming it, keep secrets out of shared screenshots and remember that a decoded token is not an authenticated token. Use the smallest input that reproduces the problem.
Related practical guides
See a mismatch between these instructions and the tool? Report a correction with a non-sensitive example.