CSV ↔ JSON Converter

Convert CSV to JSON or JSON to CSV — instant, browser-based, no uploads

📂 Drop a CSV file here or click to upload
CSV Input
JSON Output

CSV → JSON Example

Input CSV

name,age,city
Alice,30,New York
Bob,25,London
Carol,35,Tokyo

Output JSON

[
  {"name":"Alice","age":30,"city":"New York"},
  {"name":"Bob","age":25,"city":"London"},
  {"name":"Carol","age":35,"city":"Tokyo"}
]

Frequently Asked Questions

The first row becomes JSON property names. Each subsequent row becomes a JSON object in an array. Missing values become empty strings or null.

Yes. Fields wrapped in double quotes — including those containing commas, newlines, or escaped quotes — are parsed correctly per RFC 4180 standard.

When enabled, values that look like numbers (e.g. "42", "3.14") are converted to JSON numbers instead of strings. Phone numbers and zip codes with leading zeros should have this turned off.

No hard limit — processing runs entirely in your browser. Files over 50MB may be slow depending on your device.

Common Use Cases

Data migration

Exported a spreadsheet or database table as CSV? Convert it to JSON for loading into a REST API, MongoDB, or NoSQL database with one click.

Front-end mock data

Generate test fixtures for a web app. Start from a CSV of sample rows and get a clean JSON array ready for fetch() or import.

Analytics exports

Google Analytics, Mixpanel, and most BI tools export CSV. Convert to JSON to feed into dashboards, scripts, or data pipelines.

Config files

Maintain localization strings or feature-flag mappings in a spreadsheet. Export as CSV, convert to JSON, commit to repo — no manual JSON editing needed.

Tips for Clean Conversions

Always use a header row

The first row defines the JSON property names. Use short, snake_case or camelCase names without spaces to produce clean, usable JSON keys.

Watch the delimiter

European spreadsheet exports often use semicolons (;) instead of commas. If your output looks garbled, switch the delimiter setting.

Validate the output

Paste the generated JSON into the JSON Formatter to check validity and catch any parsing issues before using it in your code.

UTF-8 BOM still bites

In 2026, a very common CSV-to-JSON bug is an invisible UTF-8 BOM at the start of the file, especially from Excel exports and older data pipelines. If your first JSON key comes out as something like "id" instead of "id", that hidden marker is the reason. Before converting, open the CSV in a text editor that shows encoding, or strip the BOM during import. Also watch for BOMs after concatenating files: only the first file should ever contain one, or later rows can break parsing unexpectedly.