Turn CSV spreadsheets into JSON arrays of objects for APIs and apps—comma, semicolon, tab, or pipe. Processing stays in your browser; files are never uploaded to our servers.
A CSV to JSON converter turns comma-separated (or tab/semicolon) spreadsheet rows into a JSON array of objects—first row keys become property names, processed locally in your browser.
CSV (Comma-Separated Values) is the lingua franca of spreadsheets, exports, and flat-file data feeds. APIs and modern apps usually expect JSON—an array of objects where each row becomes `{ "column": value }`.
This tool parses RFC 4180-style CSV: quoted fields, escaped quotes, multi-line cells, and auto-detected delimiters (comma, semicolon, tab, pipe). Header mode maps the first row to JSON keys; without headers you get arrays of values. Type inference turns numbers, booleans, and null where appropriate while preserving leading zeros in ZIP codes.
Everything runs in your browser—paste CSV or upload a file up to 10 MB. Data is not uploaded to EverydayTools servers.
Use CSV to JSON when you need API-ready objects; use JSON to CSV for spreadsheet export.
Concise answers for common searches — definitions, steps, and comparisons.
European Excel locales (de-DE, fr-FR) export CSV with semicolon separators because comma is the decimal separator in those regions. Set delimiter to ; when opening a European Excel export in a JSON pipeline. TSV (tab) is common for scientific data and log exports. Mismatch symptom: one giant column in preview or thousands of columns from splitting on wrong character.
No. Parsing and conversion run entirely in your browser. Files are read with FileReader locally—they are not sent to EverydayTools servers.
Values like 02110 or 00501 that start with 0 stay as JSON strings so they are not converted to numbers and stripped.
Drop a .csv file or paste spreadsheet export text. UTF-8 BOM is stripped automatically.
Choose Auto, comma, semicolon, tab, or pipe. Set Headers to Auto-detect, On, or Off if the first row is not column names.
Click Convert or press Ctrl+Enter. Preview the first 50 rows in the table, then copy or download pretty-printed JSON.
Paste output into the JSON Validator if you need strict syntax checks before deploying to production.
Input
id,name,active
1,Ada,true
2,Linus,falseOutput
[{"id":1,"name":"Ada","active":true},{"id":2,"name":"Linus","active":false}]Header row becomes keys; booleans and numbers are inferred from cell text.
Input
sku;price;qty
A-001;19,99;3Output
JSON array with sku, price, qty keys—set delimiter to semicolon for de-DE Excel exports.Auto-detect often picks semicolon when commas appear inside numeric fields.
Common real-world scenarios where this tool saves time.
Convert legacy CSV exports into JSON payloads for REST endpoints, serverless functions, or test fixtures.
Export from Excel to CSV, then JSON for Node, Python, or no-code tools that accept JSON imports.
Normalize tabular dumps before loading into databases or document stores that prefer JSON documents.
Step-by-step chains that connect related tools for common tasks.
| Direction | Tool | When to use |
|---|---|---|
| CSV → JSON | This tool | Spreadsheet or export → API objects |
| JSON → CSV | /json-to-csv | API array → Excel or Sheets |
| Excel → CSV | /excel-to-csv | XLSX first, then CSV to JSON in two steps |
| Setting | Typical source | Result shape |
|---|---|---|
| Comma + headers On | US/UK CSV | Array of objects with named keys |
| Semicolon + headers On | European Excel | Same object shape, different separator |
| Headers Off | Raw data grids | Array of arrays (no key names) |
Likely cause: Unescaped newline inside a quoted field split rows incorrectly.
Fix: Ensure RFC 4180 quoting — fields with line breaks must be wrapped in double quotes.
Likely cause: Auto-type detection disabled or values quoted as text.
Fix: Unquoted numeric cells infer as numbers; leading-zero codes stay strings by design.
Likely cause: Wrong delimiter for European or TSV export.
Fix: Switch delimiter to semicolon or tab manually and convert again.
Advertisement
Paste CSV or upload a file, confirm delimiter and header settings, click Convert, then copy or download the JSON array. First row headers become object property names when headers are enabled.
Yes—comma, semicolon, tab, and pipe, plus Auto-detect from the first line. European Excel exports often need semicolon.
With headers On or Auto-detect, row one becomes JSON keys. With headers Off, each row is a JSON array of values and generic column names are not invented.
Up to 10 MB per file and 100,000 rows in the browser. Larger files need server-side ETL or chunked processing.
No. All processing happens locally in your browser. We do not store or access your CSV or JSON output.
Use Excel to CSV first, then this tool—or export CSV from Excel and upload here. Two-step flow keeps each tool focused and reliable.
CSV and JSON are processed in your browser with JavaScript—they are not uploaded to EverydayTools servers.
Parser follows RFC 4180 quoting rules with delimiter auto-detect and optional header row mapping.
Verify portal-specific CSV dialects (encoding, delimiter) before production imports.
Part of File Converters
More free tools for the same workflow.
Free JSON to CSV converter — convert JSON arrays to CSV with automatic header row extraction. Download for Excel or Google Sheets. Handles nested objects. No signup.
Free JSON to XML converter — transform JSON objects and arrays into well-formed XML with pretty-print output. Supports attribute mapping. Perfect for SOAP APIs and legacy integrations.
Free XML to JSON converter — paste XML and instantly get clean, structured JSON output. Handles attributes, nested elements, and CDATA sections. Perfect for REST API migration. No signup.
Advertisement
Reviewed by EverydayTools Editorial Team on 2026-05-20.