CSV to JSON converts comma-separated values into a JSON array of objects. The first row is used as headers (keys), and each subsequent row becomes an object in the array.
This tool handles RFC 4180 compliant CSV, including quoted fields with embedded commas, newlines, and escaped double-quotes. It also auto-detects numbers, booleans, and null values so your JSON output has proper types instead of all strings.
Everything runs in your browser — your CSV data is never uploaded to any server. Ideal for converting spreadsheet exports, database dumps, or log files into JSON for use in APIs, config files, or data pipelines.
name,age,city
Alice,30,New York
Bob,25,London // Converts to:
[ { "name": "Alice", "age": 30, "city": "New York" }, { "name": "Bob", "age": 25, "city": "London" }
]Numbers are auto-detected when the "Auto-detect types" option is enabled.
name,description,price
"Widget, Large","A big widget",19.99
"Gadget ""Pro""","The best gadget",29.99 // Quoted fields can contain commas and escaped quotesDouble-quotes inside quoted fields are escaped as "" per RFC 4180.
If a row has fewer fields than the header, missing values become empty strings. Extra fields beyond the header count are ignored. Make sure your CSV has consistent column counts for clean results.
This tool expects UTF-8 text. If your CSV was exported from Excel with special characters, make sure to save as "CSV UTF-8" rather than plain CSV to avoid encoding artifacts.
Header names are trimmed automatically. Cell values preserve their whitespace. If you need trimmed values, post-process the JSON output or clean your CSV before converting.
Paste your CSV data into the input panel and click "Convert to JSON". The first row becomes the object keys, and each row after that becomes a JSON object in the output array.
Yes. The parser follows RFC 4180: fields in double quotes can contain commas, newlines, and escaped quotes (""). This means complex spreadsheet data converts correctly.
Yes. Use the delimiter dropdown to select comma, semicolon, or tab. European CSV files often use semicolons — just switch the delimiter and convert.
Yes. All processing happens in your browser. No data is sent to any server. You can verify this by disconnecting from the internet and using the tool offline.
When enabled, the tool converts values that look like numbers (e.g., 42, 3.14), booleans (true/false), and null to their JSON equivalents instead of leaving them as strings.