Your spreadsheet exports CSV. Your API wants JSON. That looks like a two-minute job — until a field has a comma inside it, or a header row needs to become nested keys. This guide covers three paths: browser, Node.js, and Python. Pick the one that fits and reach for the SnipKit CSV to JSON converter for one-offs.
Convert in Your Browser
For a single file, a browser tool is the fastest path. Open the CSV to JSON converter, then paste data or drag a file onto the input. Delimiters — comma, semicolon, tab, pipe — are auto-detected, so settings rarely need touching.
Four output shapes are available (more below). Click Convert, then copy or download. Nothing leaves your machine; everything runs in the browser.
Choosing the Right JSON Shape
Before you convert, decide what shape your consumer expects. The same CSV can produce four different JSON structures:
| Output | Shape | Best for |
|---|---|---|
| Array of objects | [{"name":"Alice","age":30}, ...] | REST APIs, NoSQL inserts (the default) |
| Array of arrays | [["name","age"],["Alice",30], ...] | Table libraries, spreadsheet round-trip |
| Column arrays | {"name":["Alice","Bob"],"age":[30,25]} | Analytics, pandas vectorized operations |
| NDJSON | {"name":"Alice","age":30}\n{"name":"Bob",...} | Log pipelines, BigQuery, streaming loads |
Array of objects fits 80% of use cases. Column arrays save a reshape step for charts or pandas. NDJSON earns its keep when the file is large enough that you need to stream it. Not sure JSON is even the right pick? The format comparison covers the trade-offs.
In Code
A browser tool doesn't belong in a script. Two snippets cover most needs.
JavaScript (Node.js)
Install csv-parse once, then:
const { parse } = require('csv-parse/sync');
const fs = require('fs');
const input = fs.readFileSync('data.csv', 'utf8');
const records = parse(input, { columns: true, skip_empty_lines: true });
fs.writeFileSync('out.json', JSON.stringify(records, null, 2));
{ columns: true } tells the parser to use the header row as keys. Without it, rows come back as arrays. Given name,age\nAlice,30, you get [{"name":"Alice","age":"30"}].
Python (pandas)
import pandas as pd
pd.read_csv('data.csv').to_json('out.json', orient='records', indent=2)
The orient='records' flag is load-bearing. Pandas' default is 'columns', which produces {"name":{"0":"Alice",...}} — a shape that surprises JavaScript readers. 'records' gives the familiar array of objects.
CLI: mlr --c2j cat data.csv (Miller) does the same in one command — handy for shell pipelines.
When CSV Fights You: 3 Edge Cases
Commas inside fields
RFC 4180 says: wrap the field in double quotes, and escape any inner double quotes by doubling them.
name,bio
Alice,"Loves cats, coffee"
Bob,"He said ""hello"""
A real parser handles this. A hand-rolled .split(',') splits on the inner comma and silently corrupts your data.
Nested JSON from a flat CSV
Some converters (including SnipKit's) read dot notation in header names and build nested objects:
name,address.city,address.zip,tags[0],tags[1]
Alice,Berlin,10115,dev,coffee
Produces:
{ "name": "Alice", "address": { "city": "Berlin", "zip": "10115" }, "tags": ["dev", "coffee"] }
This is a converter convention, not a CSV standard. Confirm your target tool supports it before relying on it.
Mismatched or empty cells
A row with fewer columns than the header gives null or an empty string, depending on the parser. SnipKit's converter ships with Skip empty lines and Trim whitespace toggles on by default.
After conversion, drop the result into the JSON formatter to pretty-print, or the JSON validator to catch structural errors early.
FAQ
How does the conversion work?
The converter reads the first row as field names, then maps each later row to an object using those names as keys. A row Alice,30 under headers name,age becomes {"name":"Alice","age":"30"}. Values start as strings; type inference is optional.
How do I create nested JSON from a flat CSV?
Use dot notation in headers: address.city becomes {address:{city:...}}. For arrays, use bracket notation: tags[0], tags[1] becomes {tags:["...", "..."]}. Not every converter supports this — test with a small sample first.
What about commas inside a field?
Wrap the field in double quotes: "New York, NY". If it contains a double quote, double it: "She said ""hello""". Per RFC 4180, any compliant parser handles this. Writing your own? Use a library — the rules have more edge cases than they appear to.
Conclusion
One-off? The CSV to JSON converter handles it in the browser — no setup, no upload. Scripted? Reach for csv-parse in Node or the pandas one-liner. Going the other direction? JSON to CSV works the same way.
