CSV to JSON Converter

What is CSV to JSON conversion?

CSV stores tabular data as rows and columns, usually separated by commas or another delimiter. JSON represents data using objects, arrays, keys, and values. Converting CSV to JSON usually means using the header row as property names and turning each following row into a JSON object.

This is useful when data starts in a spreadsheet or CSV export but needs to be used by an API, application, script, test fixture, or another system that works with JSON.

Here is a simple CSV example:

name,age,city
Asha,29,Delhi
Ravi,34,Pune

After conversion, the headers become JSON keys and each row becomes an object:

[
  {
    "name": "Asha",
    "age": 29,
    "city": "Delhi"
  },
  {
    "name": "Ravi",
    "age": 34,
    "city": "Pune"
  }
]

How to convert CSV to JSON

1. Paste or upload CSV Paste CSV text into the input editor or upload a supported .csv, .tsv, or text file from your device.
2. Check the delimiter Use automatic detection or select the correct separator manually if your data uses commas, semicolons, or tabs.
3. Convert to JSON Run the conversion to turn CSV rows into structured JSON objects.
4. Review the result Check the generated keys, values, data types, and any parsing warnings before using the output.
5. Copy or download Copy the JSON to your clipboard or download the generated .json file.

CSV to JSON examples and column mapping

The converter maps common CSV structures into JSON using these rules:

How CSV headers become JSON keys

The first row provides the property names for the generated JSON objects:

name,email,status
Asha,asha@example.com,active

The values in the next row are matched to those headers by column position:

[
  {
    "name": "Asha",
    "email": "asha@example.com",
    "status": "active"
  }
]

The converter also handles common header problems:

• Blank headers: A column without a header is assigned a fallback name such as column_2 and can be flagged for review.
• Duplicate headers: Repeated names are given a numbered suffix such as name_2 so values are not silently overwritten.

How commas and quotes inside CSV values are parsed

CSV fields can contain commas and quotation marks when they are quoted correctly.

• Commas inside values: A field such as "Likes coffee, tea, and coding" remains one value instead of being split into multiple columns.
• Quotation marks inside values: In CSV, a double quote inside a quoted field is written as two double quotes ("").

Example:

name,city,note
Asha,Delhi,"Likes coffee, tea, and coding"
Ravi,Pune,"She said ""hello"" before leaving"

The converted JSON contains the parsed text:

[
  {
    "name": "Asha",
    "city": "Delhi",
    "note": "Likes coffee, tea, and coding"
  },
  {
    "name": "Ravi",
    "city": "Pune",
    "note": "She said \"hello\" before leaving"
  }
]

Multiline CSV fields

A quoted CSV field can also contain a line break. When the field is parsed correctly, the newline remains part of the value instead of starting another CSV record:

name,note
Asha,"First line
Second line"

The JSON output represents that line break inside the string:

[
  {
    "name": "Asha",
    "note": "First line\nSecond line"
  }
]

Comma, semicolon, and tab delimiters

Not every tabular text file uses commas. Some spreadsheet exports use semicolons, while TSV files use tab characters between fields.

The converter can detect commonly used delimiters such as commas, semicolons, and tabs. If detection is incorrect for a particular file, choose the delimiter manually before converting.

Are CSV numbers and booleans converted to JSON types?

CSV itself stores text without JSON-style type information. This converter applies type detection so common values can become more useful JSON types while protecting values that should remain text.

• Numbers: Values such as 29 and 3.14 become JSON numbers.
• Leading zeros: Values such as 00123 remain strings so identifiers, postal codes, and similar values keep their original format.
• Booleans: Recognized true and false values become JSON booleans.
• Empty cells: Empty values are represented as null.

Review the output when exact typing matters, because a CSV file does not carry an explicit schema for each column.

Uneven rows and missing values

Some CSV files contain rows with fewer values than the header:

name,age,city
Asha,29,Delhi
Ravi,34

When a row is missing a value, the corresponding property can be set to null so the generated objects keep a consistent set of keys.

If a row contains more values than there are headers, review the parsing warning before using the output because the extra values may not have meaningful property names.

When CSV to JSON is useful

Common use cases for converting CSV to JSON include:

CSV that converts well to JSON

CSV converts most cleanly when the file has one clear header row and each following row uses the same number of columns.

Files with unclosed quotes, duplicate headers, inconsistent delimiters, or uneven row lengths should be reviewed before the generated JSON is used in another system.

You can inspect the output with the JSON Formatter. To reverse the conversion, use the JSON to CSV Converter. You can also convert JSON into other structured formats using JSON to XML or JSON to YAML.

Common CSV-to-JSON problems

• Incorrect delimiter: If an entire row appears as one value, check whether the file uses a comma, semicolon, or tab separator.
• Unclosed quotes: A missing closing quote can cause commas or following lines to be treated as part of the same field.
• Duplicate headers: Repeated column names need unique JSON property names. Review any automatically renamed headers before using the result.
• Missing headers: CSV data without a header row does not provide meaningful JSON property names. Add clear column names before conversion.
• Uneven rows: Rows with missing or extra values should be reviewed so each value maps to the intended property.
• Large files: Browser-based parsing can take longer with large datasets depending on row count, file size, and available device memory.

Before using the JSON

• Confirm that CSV headers became the expected JSON property names.
• Check values with leading zeros to make sure their original formatting was preserved.
• Review empty cells and confirm that null is appropriate for your application.
• Check quoted, multiline, and escaped values for correct parsing.
• Review warnings for duplicate headers or uneven rows.
• Validate the generated JSON against your application's expected structure when a schema is required.

Browser-based processing

CSV parsing and JSON generation run locally in your browser to maintain your privacy. TryFormatter does not need to upload the CSV input to its server to perform the conversion.

Avoid including passwords, API keys, access tokens, or other secrets in datasets unless they are required for the task.