Convert CSV to JSON
online, free & instant

CSV to structured JSON in three steps

No account. No upload. No nonsense.

Related JSON tools

Common questions answered

Converting CSV to JSON

CSV to JSON conversion transforms tabular spreadsheet data into structured JSON. This is essential when migrating from Excel or databases to web applications and APIs that expect JSON. The converter treats the first row as column headers and each subsequent row as a JSON object, producing an array ready for any JSON-consuming application.

This tool handles CSV edge cases: quoted values with commas, escaped quotes (""), multi-line values, and varying column counts. It auto-detects delimiters (comma, semicolon, tab) and handles BOM characters from Excel exports. Numbers are converted from strings, "true"/"false" become booleans, and empty cells become null.

name,age,city
Alice,30,Portland
Bob,25,Seattle
Charlie,35,Denver

[
  {"name":"Alice","age":30,
   "city":"Portland"},
  {"name":"Bob","age":25,
   "city":"Seattle"},
  {"name":"Charlie","age":35,
   "city":"Denver"}
]

Get the most out of this tool

• Ensure your CSV has a header row — the first row becomes JSON key names for all subsequent rows.
• The converter auto-detects delimiters: comma, semicolon, and tab-separated values are all supported.
• Review output for type accuracy: the converter infers numbers and booleans from string values automatically.

How CSV-to-JSON conversion works

CSV (Comma-Separated Values) is a tabular format where the first row typically contains column headers and subsequent rows contain data values. Converting CSV to JSON transforms this flat tabular structure into an array of objects, where each row becomes a JSON object with keys derived from the header row. The resulting JSON is immediately usable in JavaScript, Python, and any REST API that accepts JSON payloads.

RFC 4180 defines the CSV standard, but real-world CSV files deviate from it frequently. Quoted fields containing commas, newlines within quoted fields, escaped double-quotes (represented as two consecutive double-quotes), and varying line endings (CRLF vs LF) all require a robust parser rather than a simple split(",") approach. A proper CSV parser handles all these edge cases and is essential for reliable conversion.

Type inference is a critical feature during CSV-to-JSON conversion. CSV represents everything as strings — there is no native type system. A good converter detects when a column contains only numeric values and converts them to JSON numbers, when a column contains only "true" or "false" values and converts them to JSON booleans, and when a column is empty and converts those cells to JSON null rather than empty strings.

Delimiter detection matters because not all CSV-like files use commas. TSV (Tab-Separated Values) files use tabs, European locales often use semicolons (because commas are decimal separators in those regions), and pipe-delimited files use the | character. A smart converter auto-detects the delimiter by sampling the first few lines and choosing the character that appears most consistently across rows.

Encoding issues are a common source of conversion problems. CSV files exported from Excel often use Windows-1252 encoding rather than UTF-8, which causes special characters like accented letters and currency symbols to appear as garbled mojibake. Always verify that your CSV file is saved as UTF-8 before converting, or use a text editor to re-save it in the correct encoding first.

Nested JSON from flat CSV is achievable using dot-notation or bracket-notation column names. A column named address.city can be interpreted as a nested address object with a city property. Similarly, columns named tags[0], tags[1], and tags[2] can be assembled into a tags array. This convention is used by tools like Papa Parse and allows CSV exports from relational databases to round-trip back to their original nested JSON structure.

The reverse operation — JSON to CSV — flattens the nested structure. Together, CSV-to-JSON and JSON-to-CSV form a bidirectional bridge between tabular and hierarchical data representations. Data engineers use this pair of operations to move data between spreadsheet-based workflows and API-based workflows, enabling collaboration between analysts (who prefer spreadsheets) and engineers (who prefer JSON).

When developers convert CSV to JSON

CSV-to-JSON conversion pitfalls to avoid

• Assuming the first row is always headers: Some CSV files start with metadata rows before the actual header row — for example, a report title on row 1 and column names on row 2. Always inspect the first few rows of your CSV before converting and skip non-header rows as needed.
• Ignoring encoding problems: CSV files from Windows applications often use Windows-1252 encoding. Characters like em-dashes, curly quotes, and the Euro sign (€) will appear as garbled text if the file is not re-encoded to UTF-8 before conversion. Open in a text editor, verify the encoding, and resave as UTF-8.
• Treating all values as strings: Leaving numeric columns as strings in the JSON output causes downstream issues — arithmetic operations fail, sort orders are lexicographic instead of numeric, and schema validators expect number types. Always enable type inference to automatically convert numeric and boolean columns to their proper JSON types.
• Missing quoted-field handling: A field containing a comma must be wrapped in double-quotes in CSV: "New York, NY". If your converter splits on every comma without parsing quotes, this value will be split into two separate fields, corrupting all subsequent columns in that row.
• Blank rows creating null records: Trailing blank lines at the end of a CSV file, or blank rows between data sections, produce empty JSON objects ({}) in the output array. Always trim blank rows before converting, or filter out empty objects from the resulting JSON array.

Additional frequently asked questions