CSV to JSON / JSON to CSV
Convert spreadsheet exports to JSON for APIs, or flatten JSON arrays to CSV for analysts who prefer Excel.
Choose delimiters and header rows explicitly—misconfiguration is the top cause of misaligned columns.
How to use
- CSV to JSON: Paste CSV, select delimiter and "First row as headers" if needed. JSON appears below; use Copy or Download.
- JSON to CSV: Paste a JSON array of objects (e.g.
[{"id":1,"name":"A"}...]). Object keys become CSV headers. - Use Share URL to copy a link that restores your input and options.
- Use Download to save as
.jsonor.csv.
1CSV and JSON solve different problems
CSV shines for tabular exports from spreadsheets and legacy systems; JSON handles nested structures, heterogeneous arrays, and richer typing in modern APIs.
Converting between them is a daily task when you ingest a vendor file into an app or flatten an API response for analysts.
- Decide whether the first row is headers up front—misclassification produces objects with numeric keys or misaligned columns.
- Delimiter choice matters when text fields contain commas; RFC-compliant CSV escapes quotes by doubling them.
2Data cleaning reminders
Trim surrounding whitespace and normalize unicode before conversion if your downstream database enforces unique constraints.
Watch for thousand separators and locale-specific dates in CSV that JSON consumers will parse as plain strings unless you transform them.
3Large files
Browser-based converters work well for moderate sizes; multi-gigabyte dumps belong in streaming ETL pipelines instead.
When memory limits bite, split the CSV by time range or primary key ranges, convert chunks, and merge results with deterministic ordering.
4Spreadsheet exports in data pipelines
Finance and operations teams export CSV from Excel; engineering ingests JSON. Column renames, BOM markers, and locale-specific decimals are frequent sources of silent data corruption.
Always validate row counts and sample hashes after conversion in automated jobs.
5Nested JSON to flat CSV
Deeply nested objects do not map cleanly to a single CSV row without flattening rules. Document how arrays become multiple rows or joined strings.
6Quick checklist for CSV ↔ JSON
Confirm header row handling before converting large exports. Inspect the first and last rows after conversion for off-by-one delimiter issues.
- Escape embedded quotes in CSV source data.
- Validate JSON schema after conversion when downstream is strict.
Examples
CSV with headers
First row becomes JSON keys.
id,name
1,Ada
2,BobJSON array to CSV
Flatten objects with consistent keys.
[{"id":1,"name":"Ada"},{"id":2,"name":"Bob"}]