Converters
CSV to JSON
Paste CSV on the left, hit Run, copy the same facts in a different wrapper. No Node, no pip, no Docker for a five-minute job. That is the csv to json.
Drop a file on the left. Drafts stay in this browser. Shortcut: Ctrl or Cmd + Enter to run.
How this csv to json works
- Paste or drop a .csv file into the input on the left.
- Flip options if you see them (comments, indent, case). Defaults are the safe ones.
- Hit Run, or Ctrl / Cmd + Enter. Leave “Process on server” off unless you mean it.
- Read the status line, then copy, download, or jump to a related tool.
What this csv to json is for
The file is already in front of you. You need to convert it without opening a whole IDE profile. Paste, run, copy. Typical timing: a CMS, a legacy SOAP client, a spreadsheet, or a PHP config wants another shape.
You walk away with the same facts in a different wrapper.
What it will not pretend to be
This is not a lossless guarantee across every edge of YAML tags, XML attributes, and CSV dialects. Quoted commas and newlines belong inside fields. A naive split-on-comma will lie to you — this converter uses a real CSV read.
By default nothing leaves the tab. Tick “Process on server” only if you want to compare results or use gzip numbers that match the server library.
A practical way to use it
Drop a .csv file onto the input or paste. Flip options if they are there. Run. Read the status line. Copy or download. Drafts stay on this device so a refresh does not punish you.
When you are done, hop a related tool instead of starting over: minify and beautify toss the file back and forth, format and validate often share a parser, convert wants valid input first.
The small print that saves a round-trip
Quoted commas and newlines belong inside fields. A naive split-on-comma will lie to you — this converter uses a real CSV read.
You searched “csv to json online.” You got an editor, not a login wall. That is the deal.
Frequently asked questions
How does CSV become JSON?
Row one is keys. Each following row is an object. name,cat\nHTML Minifier,minify becomes [{"name":"HTML Minifier","cat":"minify"}]. Quoted commas stay inside fields: "Portland, Oregon" is one cell.
What if a header is missing?
You get empty strings or odd keys. Always check the first line. Excel exports love a blank title row. Delete it before you convert.
Fun fact?
Fun fact: RFC 4180 is the CSV “spec,” and almost nobody implements only that. Excel, numbers, and locale decimal commas (1,5) are why people still email each other “please save as CSV UTF-8.”
Types: are numbers really numbers?
Simple converters often keep everything as strings: "42" not 42. If your API wants numbers, coerce after. "true" is also a string. JSON will not guess unless you ask it to.
UTF-8 BOM?
Excel sometimes prefixes \uFEFF. That can poison the first header (name). Strip the BOM or your first key looks haunted.
Newlines inside cells?
Legal if the field is quoted. A naive split-on-newline will invent extra rows. Use a real CSV parse, not line.split(",").
CSV to JSON vs JSON to CSV?
JSON to CSV needs a table: an array of flat objects. Nested {meta:{n:1}} has to flatten or stringify. That is why going round-trip can lose shape.
When not to use CSV?
Nested documents, arrays of arrays, or binary. Use JSON. CSV is a rectangle. JSON is a tree. Do not force a tree into a rectangle unless you like pain.