Overview
This workspace parses JSON into a format-neutral value, validates and lints it, then serializes the same data as CSV.
JSON to CSV Converter
Convert JSON to CSV with live validation, linting, and browser-local processing.
English
Operation
Input
JSON
0 chars0 B0 linesUTF-8
Output
CSV · read only
0 objects0 arrays0 propsdepth 00 chars0 B0 lines
Waiting for input
0.0 ms · 0 errors · 0 warningsProcessed locally. Your data never leaves this device.Worker processing
Conversion example
JSON objects, arrays, strings, numbers, booleans, and null-like values are mapped to the closest compatible CSV representation.
Common mistakes
Duplicate keys, unsupported top-level TOML values, unsafe integers, aliases, and format-specific date types can prevent exact cross-format equivalence.
Frequently asked questions
Processing occurs in a browser worker. Input, output, keys, and values are never uploaded or included in analytics events.
RFC 4180, pragmatically
Quoted fields, doubled-quote escapes, and embedded newlines inside quotes are parsed per RFC 4180. Delimiter (comma, semicolon, tab, or pipe) is auto-detected from the first 20 records, or set it explicitly in the options.
Type inference you can trust
Numbers, true/false, and null are inferred from unquoted cells — but a leading zero ("007") and integers beyond JavaScript's safe range are deliberately kept as strings, since converting them would silently change the value.
Quoted cells always stay strings
Wrapping a cell in quotes (e.g. "42") opts it out of type inference entirely, even with inference enabled — useful for IDs or codes that happen to look numeric.
Converting to TOML
TOML has no top-level array type, so an array of CSV rows needs a wrapping table to convert to TOML — this shows as a clear diagnostic rather than a crash. Converting to JSON, YAML, or back to CSV needs no such wrapping.