CSV to JSON
Paste CSV (or load a .csv file) and get a JSON array of objects instantly, side by side. Everything runs in your browser — nothing is uploaded.
Drop your file here
or click to browse
Nothing has left this page since you opened the tool. Show network activity
The browser enforces this: the site’s security policy only lets the page talk to the code libraries’ servers and an anonymous usage counter (tool name, file type, size range). A request carrying your file to anywhere else would be blocked before it left.
Check it yourself: open your browser’s developer tools, go to the Network tab, and run the tool. Or turn off Wi-Fi once the tool has loaded; it keeps working.
How it works
Paste CSV (or load a .csv file) and get a JSON array of objects instantly, side by side. Everything runs in your browser — nothing is uploaded.
Paste your CSV on the left and the JSON appears on the right as you type. The first row is treated as the header; every following row becomes an object keyed by those column names. The parser is RFC 4180-compatible: it handles quoted fields, escaped double-quotes (""), and multi-line values inside quotes, so real-world exports from Excel and Google Sheets work. Empty trailing cells are kept as empty strings so every object has the same keys. The output is a pretty-printed JSON array you can copy or download. You can load a .csv file instead of pasting. Everything runs locally in your browser — the CSV never leaves your device. Need the other direction? Use JSON to CSV.
How to use it
- Paste your CSV. Paste on the left or load a .csv file — Excel and Google Sheets exports work.
- Check the header row. The first row becomes the JSON keys; every following row becomes an object.
- Review the live JSON. Quoted fields, escaped quotes, and multi-line cells are parsed per RFC 4180.
- Copy or download. Grab the pretty-printed JSON array with one click.
Frequently asked questions
- Which row becomes the keys?
- The first row is the header. Each subsequent row becomes a JSON object using those header values as keys.
- Does the parser handle quoted fields and commas inside values?
- Yes. It follows RFC 4180: quoted fields, doubled quotes ("") inside a field, and newlines inside quoted cells are all parsed correctly.
- Is anything uploaded?
- No. Parsing happens entirely in your browser — no server, no accounts, no tracking.