JSON to CSV Converter

Convert JSON data to CSV format

JSON to CSV Converter turns JSON objects into delimited text that spreadsheets can open, with an optional flattening mode for nested objects. It accepts either one object or an array of objects, then outputs CSV you can copy or download.

Content reviewed: August 27, 2026

Encrypted with HTTPSProcessed in your browser

All processing runs locally in your browser. Your files and text are not sent to Tool-web's server.

Actions:

How to Use

Paste your JSON array data
Configure output options
Click "Convert" to process
Copy or download the CSV file

Features

Automatic column detection
Nested JSON flattening
Custom delimiter options
Header row generation
Download as CSV file

Tips for getting JSON to CSV Converter right

A single object is accepted and exported as one CSV row; arrays of objects become multiple rows
Nested flattening creates one column per leaf path; deeply nested payloads produce very wide CSVs
Arrays inside objects don't fit columns — stringify them manually or restructure before export
Use flattening when the destination user needs readable column names instead of nested JSON blobs

Flattening behavior

JSON input	CSV columns produced
{"id": 1, "name": "Ada"}	id, name
{"user": {"email": "a@b.c"}}	user.email
{"tags": ["x","y"]}	tags (stringified) — arrays have no natural columns

Quoting and escaping

Papa Parse handles the RFC 4180 rules automatically: cells containing commas, quotes, or newlines get wrapped in quotes; embedded quotes double up ("). Excel and Google Sheets read this correctly.

Single object vs array input

If you paste one object, the tool wraps it internally and exports one CSV row. If you paste an array, each object becomes a row. That makes the tool flexible enough for both quick one-record exports and larger API payloads.

Real-World Use Cases

Turning API response data into a CSV for Excel or Google Sheets
Flattening nested JSON into dotted columns before handing it to a non-technical teammate
Exporting one structured record as a single-row CSV
Preparing fixture data for a spreadsheet-based review workflow
Comparing two nested payloads in a tabular format rather than raw JSON

Best Practices

Enable flattening when nested objects need to become explicit columns like `user.email`
Keep source arrays reasonably uniform so the resulting columns stay predictable
Use a single object when you only need one output row instead of manufacturing a fake array wrapper
Inspect array-valued fields after export because they are stringified rather than split into multiple rows
Choose the delimiter that best matches the destination spreadsheet or import system

Common Mistakes to Avoid

Assuming arrays inside objects naturally become clean spreadsheet columns
Leaving flattening off and then wondering why nested objects are not easy to review in a sheet
Expecting the tool to preserve numeric types once the data is exported to plain text
Copying a malformed JSON snippet and blaming the CSV output
Forgetting that very wide nested objects create very wide CSV files

Troubleshooting

If conversion fails, validate the JSON first because malformed input stops the export entirely
If nested fields disappear into `[object Object]`-style confusion elsewhere, turn flattening on before exporting
If array columns look messy, reshape them upstream because CSV has no native nested-array model
If the output has too many columns, flatten less or simplify the input structure before export
If a spreadsheet splits columns incorrectly, try a delimiter better suited to the destination locale

Frequently Asked Questions

What JSON format is expected?

The tool expects a JSON array of objects. Each object becomes a row and its keys become column headers.

Does it handle nested JSON?

Yes. Nested objects are flattened using dot notation (e.g., address.city) for CSV output.

Can I customize the CSV delimiter?

Yes. You can choose comma, semicolon, tab, or pipe as the field delimiter.

Privacy & Security

Conversion runs locally. API payloads and records never leave your device.

Tips & Best Practices

A single object is accepted and exported as one CSV row; arrays of objects become multiple rows
Nested flattening creates one column per leaf path; deeply nested payloads produce very wide CSVs
Arrays inside objects don't fit columns — stringify them manually or restructure before export
Use flattening when the destination user needs readable column names instead of nested JSON blobs

Comments

Name

Comment

0/1000

Explore more Developer Tools

Browse all tools in the Developer Tools collection.

View all Developer Tools

Tips for getting JSON to CSV Converter right

A single object is accepted and exported as one CSV row; arrays of objects become multiple rows

Nested flattening creates one column per leaf path; deeply nested payloads produce very wide CSVs

Arrays inside objects don't fit columns — stringify them manually or restructure before export

Use flattening when the destination user needs readable column names instead of nested JSON blobs

JSON input

CSV columns produced

{"id": 1, "name": "Ada"}

id, name

{"user": {"email": "a@b.c"}}

user.email

{"tags": ["x","y"]}

tags (stringified) — arrays have no natural columns

Real-World Use Cases

Turning API response data into a CSV for Excel or Google Sheets

Flattening nested JSON into dotted columns before handing it to a non-technical teammate

Exporting one structured record as a single-row CSV

Preparing fixture data for a spreadsheet-based review workflow

Comparing two nested payloads in a tabular format rather than raw JSON

Best Practices

Enable flattening when nested objects need to become explicit columns like `user.email`

Keep source arrays reasonably uniform so the resulting columns stay predictable

Use a single object when you only need one output row instead of manufacturing a fake array wrapper

Inspect array-valued fields after export because they are stringified rather than split into multiple rows

Choose the delimiter that best matches the destination spreadsheet or import system

Common Mistakes to Avoid

Assuming arrays inside objects naturally become clean spreadsheet columns

Leaving flattening off and then wondering why nested objects are not easy to review in a sheet

Expecting the tool to preserve numeric types once the data is exported to plain text

Copying a malformed JSON snippet and blaming the CSV output

Forgetting that very wide nested objects create very wide CSV files

Troubleshooting

If conversion fails, validate the JSON first because malformed input stops the export entirely

If nested fields disappear into `[object Object]`-style confusion elsewhere, turn flattening on before exporting

If array columns look messy, reshape them upstream because CSV has no native nested-array model

If the output has too many columns, flatten less or simplify the input structure before export

If a spreadsheet splits columns incorrectly, try a delimiter better suited to the destination locale