What JSON structure works best?

An array of flat objects with consistent keys: [{name:'Alice',age:30},{name:'Bob',age:25}]. The converter creates a CSV with headers from the keys (name,age) and rows from each object. Arrays of nested objects (with sub-objects or sub-arrays) require flattening — see the converter's options for handling nested data.

How are nested objects handled?

Most converters flatten nested keys with dot notation: {user:{name:'Alice'}} becomes a column 'user.name'. Arrays-of-objects nest is harder — typically you'd extract them or repeat parent rows. For complex nesting, pre-process the JSON to flatten it (using jq or a script) before converting.

What happens to objects with different keys?

If different objects in the array have different keys (Alice has 'email', Bob doesn't), the converter creates a column for every unique key across all objects. Missing values become empty cells. This 'union of keys' approach matches Excel's behavior and is the safest default.

Are values escaped properly?

Yes. Values containing commas, quotes, or newlines are wrapped in double quotes per RFC 4180. Internal quotes are escaped by doubling (""). The output is valid CSV that opens correctly in Excel, Google Sheets, and any standards-compliant CSV parser.

Can I customize the delimiter?

Most CSV converters offer delimiter options: comma (CSV, default), tab (TSV), semicolon (European CSV format), or pipe. Choose based on the consuming tool — Excel in many European countries expects semicolons, while standard CSV uses commas.

What's the size limit?

Browser memory dependent. Up to 100 MB JSON converts quickly. Very large JSON (multi-GB) requires streaming approaches with command-line tools. Most use cases (API responses, query results, exports) are well under typical limits.

Is the data sent to a server?

No. All conversion happens entirely in your browser. Your JSON never leaves your device — safe for proprietary API responses, customer data, financial records, or any sensitive information.

JSON to CSV

Convert JSON arrays to CSV format online. Free JSON to CSV converter for exporting data to spreadsheets with proper formatting.

Code Converters JSON Tools

Instant results

Delimiter:

Include headerCSV to JSON

JSON Input (Array of Objects)

CSV Output

CSV output will appear here...

About JSON to CSV Conversion

Convert JSON arrays to CSV (Comma-Separated Values) format. Each object in the array becomes a row, with object keys as column headers. Nested objects are serialized as JSON strings.

How to Use JSON to CSV

Paste your JSON

Paste a JSON array of objects into the input editor. Each object should have similar keys; rows are derived from object values, columns from object keys.

Configure output

Choose delimiter (comma for standard CSV, tab for TSV, semicolon for European CSV). Decide whether to flatten nested objects (user.name) or fail on nesting.

Verify the headers

Headers come from the union of all object keys across the array. Missing fields become empty cells. Inspect the first row to confirm column order matches your expectations.

Download or copy

Click Download to save as .csv (opens in Excel/Google Sheets) or Copy for clipboard. The output is RFC 4180 compliant — quotes around values containing commas, escaped internal quotes.

When to Use JSON to CSV

Generating Excel-friendly reports from APIs

When non-technical users need to analyze API data, deliver it as CSV that opens directly in Excel. Common scenarios: customer lists from CRM, transaction reports from billing, user analytics from product platforms — all typically JSON via API but consumed via spreadsheet.

Data exports for business intelligence

BI tools like Tableau, PowerBI, and Looker prefer CSV (or its big-data cousin Parquet) for ingestion. Converting JSON exports to CSV creates a standard pipeline: JSON → CSV → BI tool, regardless of source data structure. Especially useful for ad-hoc analyses.

Bulk operations in CRM/marketing tools

Tools like Salesforce, HubSpot, and Mailchimp accept CSV uploads for bulk record creation/updates. When your data is in JSON (from another system), converting to CSV bridges to these platforms without writing custom integrations.

Backup and archival in human-readable form

JSON is great for code, but CSV is the universal format that's readable in 50 years (Excel will still open it). For long-term archival of structured data, CSV with proper headers is more durable than JSON which depends on having compatible parsers.

JSON to CSV Examples

Array of flat objects

Input

[{"name":"Alice","age":30},{"name":"Bob","age":25}]

Output

name,age
Alice,30
Bob,25

Each object becomes a row; keys become headers. Output opens in Excel with two columns and two data rows. Most common JSON-to-CSV conversion pattern — flat objects with consistent keys.

Objects with different keys

Input

[{"name":"Alice","email":"a@x.com"},{"name":"Bob","phone":"555-1234"}]

Output

name,email,phone
Alice,a@x.com,
Bob,,555-1234

Headers union all keys across all objects. Missing fields become empty cells. Excel and downstream tools handle this gracefully — empty cells are simply blank when displayed.

Values containing commas

Input

[{"name":"Alice","note":"VIP, premium tier"}]

Output

name,note
Alice,"VIP, premium tier"

Values containing the delimiter are wrapped in double quotes. Internal quotes would be escaped by doubling (""). The output is RFC 4180 compliant — opens correctly in Excel without splitting the comma-containing value into separate cells.

Tips & Best Practices for JSON to CSV

1.Flatten nested objects before converting. {user: {name: 'Alice'}} doesn't fit the row/column model. Either pre-process to {user_name: 'Alice'} or use a converter option to flatten with dot notation (user.name).
2.Watch for inconsistent object shapes. If 99 objects have keys A, B, C and one object has D, the CSV will have 4 columns with mostly-empty D. Either normalize the JSON first or accept the wider CSV.
3.For Excel internationalization, use the right delimiter. US Excel expects commas; many European versions expect semicolons. Choose based on your audience's Excel version, or distribute as TSV (tab-delimited) which works universally.
4.Add UTF-8 BOM (Byte Order Mark) at the start of CSV when sharing with Excel users — without it, Excel may misinterpret special characters (é, ä, 中) as Latin-1. The byte order mark signals UTF-8 encoding to Excel's CSV importer.
5.For numeric data with leading zeros (zip codes, IDs starting with 0), Excel auto-converts to numbers, dropping the leading zero. Either pre-format as text in the CSV ('="01234"') or instruct users to import as text instead of using auto-detection.
6.Don't include sensitive data in CSV columns visible to anyone receiving the file. Excel's column filtering is no security barrier. For sensitive exports, encrypt the file or use access-controlled platforms instead of CSV email attachments.

Frequently Asked Questions

CSV is the universal format for spreadsheets — Excel, Google Sheets, and Numbers all open CSV directly. Converting API responses, database query results, or any tabular JSON to CSV lets non-developer users analyze data in familiar tools. Also useful for: Excel reports, BigQuery uploads, data lake imports, and Salesforce data loaders.

JSON to CSV

About JSON to CSV Conversion

How to Use JSON to CSV

Paste your JSON

Configure output

Verify the headers

Download or copy

When to Use JSON to CSV

Generating Excel-friendly reports from APIs

Data exports for business intelligence

Bulk operations in CRM/marketing tools

Backup and archival in human-readable form

JSON to CSV Examples

Array of flat objects

Objects with different keys

Values containing commas

Tips & Best Practices for JSON to CSV

Frequently Asked Questions

Related Tools

CSV to JSON

CSV JSON Converter

JSON to XML

XML to JSON

JSON to YAML

YAML to JSON