CSV → JSON — spreadsheets to typed API payloads
Choose delimiter and whether row one holds headers; uneven rows pad deterministically with warnings — no silent truncation beyond documented drops.
Developer notes
• Parser rejects unclosed quotes loudly. • Extra columns trimmed with warnings — review toast output. • All cell values remain strings — cast numbers/bools in your service.
When teams pick this route
• Glueing CRM CSV dumps into fetch() bodies. • Importing vendor grids before JSON Schema validation.
About these options
CSV exports: choose a delimiter (Auto follows locale — semicolon on /fr), RFC-minimal vs always-quoted fields, line endings, and whether to emit a header row. CSV imports: delimiter + whether row 1 holds column names (Auto delimiter follows locale only for convenience). JSON output (XML, YAML, or CSV sources): indentation (including compact one-line) and optional recursive key sort. JSON → XML: toggle pretty-printing and indent width. YAML output: indent width, readable vs tighter layout, and deterministic string quoting (there is no source YAML file to “preserve”). XML comments are not represented in the intermediate JSON tree.
Worked examples
Header row
Sample input
Sample output
Semicolon regional file
Sample input
Sample output
Navigate related converters
Go hierarchical with CSV → YAML, markup via CSV → XML, or revisit JSON → CSV for exports.
CSV → JSON FAQ
Parser guarantees
Why strings only?
CSV carries opaque text — FastMinify avoids guessing numeric types.
Embedded newlines inside quotes?
Supported when wrapped in double quotes per RFC-style parsing.
UTF-8 BOM?
Stripped automatically.
Multiple header rows?
Only row one participates — preprocess upstream.
Looking for every converter, encoder, and minifier in one place? Developer tools hub Open the curated developer tools catalogue.