About this tool
The first CSV row is read as headers, and every following row becomes a JSON object keyed by them. Quoted fields, embedded commas and line breaks are handled per RFC 4180.
Use it to turn spreadsheet exports into API fixtures, seed data or config files.
Numbers and booleans are auto-typed: "482" becomes 482, "true" becomes true.
Frequently asked questions
What if my CSV has no header row?
The first row is always read as the header row, supplying the JSON keys. If your data has no headers, add a header line before converting.
How are types detected?
Unquoted values that look like a plain number, true/false, or null are auto-typed: 482 becomes a number, true a boolean. Quoted values stay strings (so "007" or "482" keep their exact text), and leading-zero or exponent forms are left as strings to avoid surprising casts.
Does it handle quoted fields?
Yes — quoted fields with embedded commas, quotes and newlines parse per the CSV standard.