Delimiter.live
Data Conversion Tools Runs in your browser Free · no account

CSV to JSON Converter

The CSV to JSON converter reads delimited rows and produces a JSON array in which each row becomes an object keyed by the header names. It handles quoted fields, embedded commas and line breaks, and can convert numbers and booleans to their real JSON types.

Options
CSV data 0 characters
JSON to CSV
JSON

Your result will appear here.

Not sure where to start? Use Load example.

Results update automatically and are calculated on your device. Nothing you type is sent to a server.

Runs in your browser. Processing happens entirely in your browser. Nothing you enter is sent to Delimiter.live.

How to use the CSV to JSON Converter

  1. Paste your CSV, or use the file button to load a .csv file from your device.
  2. Confirm the delimiter — leave it on "Detect automatically" if you are unsure.
  3. Keep "First row contains column names" ticked so the headers become JSON keys.
  4. Copy the JSON or download it as a .json file.

Example

Input
name,age
Ada,36
Output
[
  {
    "name": "Ada",
    "age": 36
  }
]

Common use cases

  • Turning a spreadsheet export into a fixture file for an API or test suite.
  • Preparing seed data for a database import that expects JSON.
  • Converting an analytics or CRM export so it can be processed by a script.
  • Inspecting a CSV as structured data when the raw file is hard to read.

Limitations and things to watch for

  • Duplicate header names are made unique by appending a number, because a JSON object cannot hold two identical keys.
  • Type conversion is opt-in per value: a field that looks like a number becomes a number. Leading-zero values such as postcodes or product codes are kept as strings so they are not corrupted.
  • Rows with more fields than there are headers get numbered extra keys rather than being discarded.

Frequently asked questions

Is my CSV file uploaded to a server?
No. The file is read and parsed by JavaScript in your browser. Nothing is transmitted, which is why the converter is safe for customer exports and internal reports.
Does it handle commas inside quoted fields?
Yes. The parser follows RFC 4180, so quoted fields may contain the delimiter, double quotes escaped as "" and even line breaks.
What if my file has no header row?
Untick "First row contains column names" and each row becomes an object keyed by column position (column1, column2, …).
Why is my postcode still a string?
Values with a leading zero are deliberately kept as strings. Converting "01234" to the number 1234 would silently lose data.

Share this tool