CSV files hold spreadsheet data as plain text, and JSON holds the same data as structured objects. Developers convert between them constantly: feeding spreadsheet data into an app, preparing API test data, or moving a table into code. This guide shows you the conversion, including the pitfalls that break it.
What the conversion looks like
Take this CSV: name,age,city on the first line, then Alice,30,New York and Bob,25,London. As JSON it becomes an array of objects: [{“name”: “Alice”, “age”: 30, “city”: “New York”}, {“name”: “Bob”, “age”: 25, “city”: “London”}]. The first row becomes the keys, and each later row becomes one object.
Step-by-step: convert CSV to JSON
- Open your CSV and check the delimiter. Commas are standard, but some exports use semicolons or tabs, especially where the comma is the decimal mark.
- Confirm the first row holds column names. If it holds data instead, your converter needs to know, or the first data row will become the keys.
- Check for quoted fields. A value like “Smith, John” contains a comma that is part of the value, not a separator. Good converters respect quotes; naive ones split it in two.
- Check for escaped quotes inside quoted fields, and for line breaks inside quoted values, which span multiple physical lines.
- Convert, then inspect the first and last objects. Confirm the keys match the header and no row lost or gained a field.
- Decide on types: should “30” stay a string or become the number 30? Some converters keep everything as strings, others guess types. Pick the behavior your destination expects.
Common mistakes
Splitting on every comma without respecting quotes is the top error; it breaks any value containing a comma. Using the wrong delimiter is second: a semicolon file converted as comma data produces one giant column. Forgetting the header question is third: treating data as headers, or headers as data, shifts everything by one row.
Try it the faster way
Convert your CSV to JSON instantly with the tool below.
Prefer the full page? Open the CSV to JSON converter directly.
Quick tips
- Check the delimiter before converting, not after.
- Quote values that contain the delimiter.
- Verify the first and last objects after every conversion.
CSV to JSON is a simple idea with three traps: delimiters, quotes, and headers. Check all three before converting, and the output will be clean.
Frequently asked questions
Should numbers stay strings or become numbers in JSON? It depends on the destination. APIs and databases usually want real numbers for quantities, while IDs, phone numbers, and codes should stay strings, since leading zeros matter and arithmetic on them is meaningless. Check what the receiving system expects.
What if my CSV has no header row? Then the converter must generate keys, often field1, field2, and so on, or you must add a header row yourself before converting. Converting headerless data without telling the tool produces objects keyed by your first data row, which is wrong.
Can I convert JSON back to CSV? Yes, with a reverse converter. The same traps apply in reverse: nested objects need flattening, values containing commas need quoting, and keys must be consistent across objects or columns will misalign.
Worked example
Convert this CSV: product,price,stock, then Lamp,25,40 and Chair,60,12. The JSON becomes [{“product”: “Lamp”, “price”: 25, “stock”: 40}, {“product”: “Chair”, “price”: 60, “stock”: 12}] if numbers are converted, or the same with quoted numbers if strings are kept. The choice matters downstream: an API expecting numbers will reject quoted prices, while an inventory code expecting strings may mishandle real numbers. Check the destination’s expectation before converting, and verify the first and last objects after every run.