How to Convert CSV to JSON (and Back) Without Coding

To convert CSV to JSON, you need each spreadsheet row to become a JSON object, with the CSV's header row supplying the keys — and to go the other way, each JSON object becomes a row, with its keys becoming column headers. A browser-based converter does both in one paste: our free CSV to JSON Converter and JSON to CSV Converter run entirely on your device, so the data never leaves your browser.

Why would you need this? Because the two formats live on opposite sides of a wall: spreadsheets, exports and analytics tools speak CSV, while APIs, apps and databases speak JSON. Real work constantly crosses that wall — an Excel sheet that has to seed an API, an API response an analyst wants in Excel. Here's how to cross it cleanly, and the five traps that mangle data on the way.

CSV to JSON: what actually happens

Take this CSV:

name,age,city
Ali,30,Lahore
Sara,25,Karachi

Converted to JSON, it becomes an array of objects:

[
  { "name": "Ali", "age": 30, "city": "Lahore" },
  { "name": "Sara", "age": 25, "city": "Karachi" }
]

Three things happened, and each is a decision point:

1. The header row became the keys. If your CSV has no header row, the converter must generate keys (column1, column2…) — check which your file has before converting.
2. Types were inferred. 30 became the number 30, not the string "30". Good converters let you control this — important when "numbers" are actually codes (phone numbers, postal codes) that must keep leading zeros.
3. Each row became one object. Empty cells become empty strings or null, depending on the tool.

Paste your CSV into the CSV to JSON Converter, pick your delimiter and header option, and copy the result. If the output looks wrong, the input usually breaks one of the rules below.

JSON to CSV: the flattening problem

The reverse direction has one hard problem: JSON can nest, CSV cannot. This object:

{ "name": "Ali", "address": { "city": "Lahore", "zip": "54000" } }

has no natural single-row shape. The standard answer is flattening — nested keys join into column names like address.city and address.zip. Our JSON to CSV Converter flattens automatically and handles arrays sensibly, but know what to expect: deeply nested API responses produce wide CSVs with dotted column names, and that's correct behaviour, not a bug.

Also note: only a JSON array of objects converts cleanly. A single object converts to a one-row CSV; wildly mixed shapes (different keys per object) produce a sparse CSV with many empty cells — the union of all keys becomes the header row.

The 5 traps that mangle your data

Trap	What goes wrong	The fix
Wrong delimiter	European CSVs often use ; not , — everything lands in one column	Pick the semicolon option before converting
Commas inside values	"Lahore, Punjab" splits into two columns if unquoted	Values with commas must be wrapped in double quotes
Leading zeros	Phone/postal codes like 0300… become 300 as numbers	Keep them as strings, not numbers
Excel scientific notation	Long IDs display as 1.23E+15 and lose digits	In Excel, import via Data → From Text/CSV and set the column to Text
Broken JSON input	One missing bracket and nothing converts	Validate first with the JSON Formatter — see fixing "invalid JSON" errors

Step-by-step: Excel sheet to JSON

The most common real-world job, start to finish:

1. In Excel or Google Sheets: File → Save As / Download → CSV. This strips formulas and formatting, keeping only values — that's expected.
2. Open the file in any text editor (or straight in the converter's upload) and confirm the first line is your header row.
3. Paste or upload into the CSV to JSON Converter. Choose the delimiter your file actually uses.
4. Skim the first two objects in the output: are the keys right? Are numbers/strings what you expect?
5. Copy the JSON. If it's headed into code or an API request, run it through the JSON Formatter & Validator as a final check.

Going the other way (API response → spreadsheet) is the same in reverse: paste the JSON array into the JSON to CSV Converter, download the CSV, and import it into Excel via Data → From Text/CSV so you control the column types.

When conversion is the wrong answer

If you're converting the same data back and forth daily, the formats are telling you something: pick the one that matches the data's real home. Flat tables that humans edit belong in CSV/spreadsheets; nested, typed data that code consumes belongs in JSON. Our JSON vs CSV comparison covers how to choose — and if the data is configuration rather than records, JSON vs YAML is the comparison you want.

Frequently asked questions

Is it safe to convert sensitive data with an online converter? It depends where the processing happens. Our converters run 100% in your browser — the CSV or JSON is parsed by JavaScript on your own device and is never uploaded to any server. You can confirm this by loading the page, disconnecting from the internet, and converting offline.

How do I convert CSV to JSON without the first row becoming keys? Use the converter's header option: with "no header row" selected, keys are auto-generated (column1, column2…) and your first row stays as data. Converting with the wrong setting silently eats your first record — it becomes the keys instead.

Why did my converted CSV open as one column in Excel? Delimiter mismatch: your CSV uses commas but your Excel locale expects semicolons (or vice versa). Import via Data → From Text/CSV and set the delimiter manually instead of double-clicking the file.

Can I convert a huge CSV file this way? Browser-based converters comfortably handle files up to a few tens of megabytes — enough for hundreds of thousands of rows. Beyond that, a script (Python's pandas reads CSV and writes JSON in three lines) is the better tool for the job.

One paste to go from spreadsheet to API-ready JSON — or back — with nothing uploaded anywhere: CSV to JSON · JSON to CSV.