CSV to JSON

Converting CSV data to JSON takes under thirty seconds.

1. 1

   Paste your CSV data into the input field. Your CSV should have a header row as the first line. The column names in the header row become the keys in each JSON object. Each subsequent row becomes one JSON object in the output array.

2. 2

   Choose your output format. Toggle the "Pretty Print" option on for formatted JSON with indentation that is easy to read and inspect. Leave it off for compact JSON with no extra whitespace, which is smaller and more suitable for production use or pasting directly into code.

3. 3

   Click "Convert to JSON." The JSON output appears instantly in the result area.

4. 4

   Copy your JSON. Use the copy button to grab the complete JSON output and paste it into your code, API tool, database, or any other destination.

The tool includes a "Load Example" button to show a working sample CSV if you need to see the expected format before entering your own data.

CSV stands for Comma Separated Values. It is one of the oldest and most universally supported data exchange formats in computing. A CSV file is a plain text file where each line represents one record and the values within each record are separated by a delimiter, most commonly a comma.

The first row in a well-formed CSV file is typically the header row. It contains the column names that describe what each value in the subsequent rows represents. Every data row below the header contains values in the same order as the header columns.

A simple CSV file looks like this:

• name,email,age

• Alice Johnson,alice@example.com,30

• Bob Smith,bob@example.com,25

• Carol White,carol@example.com,35

CSV is produced by virtually every database, spreadsheet application, analytics platform, and data reporting tool in existence. Excel, Google Sheets, LibreOffice Calc, MySQL, PostgreSQL, Salesforce, HubSpot, Airtable, and most other data tools can export data as CSV. This universality makes CSV the most common starting point when moving data between systems.

Despite its simplicity, CSV has several well-known limitations. It has no standard way to represent nested or hierarchical data. All values are stored as text and data types must be inferred. Fields containing commas or newlines must be wrapped in quotation marks. Different systems use different delimiters, newline characters, and character encodings, which can cause compatibility issues.

JSON stands for JavaScript Object Notation. It is a lightweight, text-based data format that has become the dominant format for exchanging data between web services, APIs, and applications. JSON is defined by RFC 8259 and ECMA-404.

A JSON value can be an object (a set of key-value pairs), an array (an ordered list of values), a string, a number, a boolean, or null. These primitives can be nested to any depth, enabling JSON to represent complex hierarchical data structures that CSV cannot.

A JSON file equivalent to the CSV example above looks like this:

• {"name": "Alice Johnson", "email": "alice@example.com", "age": 30}

• {"name": "Bob Smith", "email": "bob@example.com", "age": 25}

• {"name": "Carol White", "email": "carol@example.com", "age": 35}

JSON is the format of choice for REST APIs because it is compact, human-readable, natively parsed by JavaScript, and supported by every modern programming language. Configuration files, database documents in MongoDB and Firestore, and data exchange between microservices all commonly use JSON.

CSV and JSON serve different purposes and are optimized for different contexts. Converting from one to the other is necessary when moving data between systems with different requirements.

API integration requires JSON. The vast majority of modern REST and GraphQL APIs communicate in JSON. When you have data in a spreadsheet or CSV export that needs to be sent to an API, ingested by a web application, or stored in a document database like MongoDB or Firestore, converting from CSV to JSON is the first step.

JavaScript applications work natively with JSON. Frontend frameworks like React, Vue, and Angular can import JSON files directly and work with the data as native JavaScript objects. CSV requires additional parsing before it can be used as data in JavaScript applications. Importing a CSV file as JSON eliminates this parsing step.

Configuration and seed data often uses JSON format. Development databases need to be seeded with initial data. Many seeding tools, ORM fixtures, and migration scripts accept JSON arrays. Converting a spreadsheet of seed data to JSON is faster than writing fixture files by hand.

Document databases store JSON. MongoDB, CouchDB, Firestore, and similar NoSQL databases store documents that are structurally identical to JSON objects. Importing a CSV file into one of these databases involves converting each row to a JSON document first.

Data pipelines and ETL processes use JSON. Many data pipeline tools, workflow automation systems like Zapier and Make, and ETL (Extract, Transform, Load) platforms work natively with JSON. Converting CSV data to JSON is a standard step in connecting spreadsheet-based data sources to these systems.

Code samples and documentation benefit from JSON format. When documenting an API or writing a tutorial, showing example data in JSON format is more familiar and useful to developers than showing the same data as a CSV.

For the CSV to JSON conversion to produce clean, usable output, your CSV data should follow certain conventions.

A header row is required. The first row of your CSV must contain the column names. These names become the keys in each JSON object. If your CSV has no header row, the first data row will be misinterpreted as column names and the resulting JSON key names will be your actual data values.

Header names should be valid JSON keys. While JSON allows any string as a key, header names that are valid JavaScript identifiers (no spaces, no special characters, not starting with a number) are the most compatible with the widest range of JSON consumers. If your CSV headers contain spaces, many converters transform them to camelCase or snake_case, or wrap them in quotes. Thetoolity preserves headers exactly as they appear in the CSV.

Consistent column counts across rows produce the cleanest output. When every data row has exactly as many values as the header row, every JSON object has the same keys with no missing fields. Rows with fewer values than the header produce JSON objects with missing keys. Rows with more values than the header produce extra values that may be discarded or mapped to unexpected keys.

Values containing commas must be quoted. In a standard CSV file, a value that contains a comma must be wrapped in double quotation marks. A value containing double quotes must escape them by doubling: two consecutive quotation marks represent one literal quotation mark inside a quoted field. Thetoolity's converter handles these standard CSV quoting rules correctly.

Numeric strings versus numbers. In CSV, all values are text. Thetoolity's converter identifies values that look like numbers and converts them to JSON numbers rather than strings where appropriate. A CSV field containing 30 becomes the JSON number 30, not the string "30". This makes the JSON output more useful for most downstream applications.

Thetoolity's CSV to JSON converter offers two output formats: Pretty Print and Compact. Choosing the right one depends on how you plan to use the JSON output.

Pretty Print JSON adds indentation, line breaks, and spacing to make the structure visually clear and human-readable.

The pretty printed version of a two-field JSON array looks like this:

• [

• { "name": "Alice Johnson", "email": "alice@example.com" },

• { "name": "Bob Smith", "email": "bob@example.com" }

• ]

Pretty print is the right choice when you are inspecting the output to verify it looks correct, when you are copying it into documentation or a README file, when you are pasting it into a code editor where you want to read and edit it, and when you are sharing it with colleagues who need to review the data.

Compact JSON removes all unnecessary whitespace, producing the smallest possible JSON string.

The same data in compact format looks like this:

• [{"name":"Alice Johnson","email":"alice@example.com"},{"name":"Bob Smith","email":"bob@example.com"}]

Compact output is the right choice when you are copying JSON into code or a configuration file where file size matters, when you are sending JSON to an API where bandwidth efficiency is important, when you are storing JSON in a database field where compactness reduces storage cost, and when the JSON will be processed by a machine and never needs to be read by humans directly.

Toggle the Pretty Print option based on your intended use case before copying the output.

One of the most important aspects of CSV to JSON conversion is how data types are handled. CSV stores everything as text. JSON supports strings, numbers, booleans, null, arrays, and objects. A good converter makes intelligent decisions about which JSON type to use for each CSV value.

• Numbers: A CSV field containing digits and an optional decimal point (like 30, 3.14, or 100.50) is typically converted to a JSON number without quotation marks. This ensures arithmetic operations and numeric comparisons work correctly when the JSON is consumed by an application.

• Booleans: CSV fields containing true or false (case-insensitive) are typically converted to JSON boolean values without quotation marks: true or false.

• Empty fields: A CSV field with no value (two consecutive commas or a comma at the start or end of a row) is typically converted to a JSON null value or an empty string, depending on the converter.

• Everything else: All other values are converted to JSON strings, wrapped in double quotation marks.

Thetoolity's converter applies these type detection rules automatically, producing JSON with the most useful type representations for each field rather than treating all values as strings.

Even well-formed CSV files can produce unexpected JSON output due to subtle formatting issues. Here are the most common problems and their solutions.

Missing or incorrect header row. If the first row of your CSV is a data row rather than a header row, the first row of data will become the JSON key names. Always ensure your CSV has a header row with descriptive column names before converting.

Commas inside field values. A CSV field containing a comma must be wrapped in double quotation marks. If your CSV has unquoted commas inside values, the converter will treat them as column separators and produce incorrect output with misaligned columns. Fix the source CSV by quoting any fields that contain commas.

Inconsistent column counts. Rows with more or fewer columns than the header row produce JSON objects that are missing keys or have extra values. Review and clean the source data to ensure all rows have the same number of columns as the header.

Non-standard delimiters. Some CSV files use semicolons, tabs, or pipe characters as delimiters instead of commas. This is common in European locales where the comma is the decimal separator. If your data uses a non-comma delimiter, you may need to replace the delimiter characters before pasting into the converter.

Encoding issues. CSV files from Excel exported in certain locales may include a BOM (Byte Order Mark) at the start of the file or use Windows-1252 encoding rather than UTF-8. Characters with accents or non-Latin characters may appear garbled. Ensure your CSV is saved in UTF-8 encoding before converting.

Dates and timestamps as strings. Dates in CSV are plain text and have no standardized format. The converter treats them as strings. If you need your JSON dates to be in a specific format like ISO 8601, you will need to transform them either in the source data or in the application that processes the JSON.

For developers who need to convert CSV to JSON programmatically in their applications rather than using an online tool, here are the implementations in the most common languages.

• JavaScript (browser and Node.js): The Papa Parse library is the most robust CSV parser available for JavaScript. It handles all edge cases including quoted fields, escaped characters, and different delimiters. It returns a structured result with the header row mapped to keys. For simple cases without a library, split each line by the delimiter and map values to header keys using reduce().

• Python: The csv module in Python's standard library provides csv.DictReader(), which reads a CSV file and automatically maps each row to a dictionary using the header row as keys. This dictionary maps directly to a JSON object. Use json.dumps() to serialize the list of dictionaries to JSON.

• Node.js with csvtojson: The csvtojson package provides a simple Promise-based API for converting CSV to JSON. It handles all CSV formatting edge cases and supports file streams, making it suitable for large files.

• PHP: PHP's fgetcsv() function reads one row of a CSV file as an array. Combining it with array_combine() to map header keys to values produces an associative array equivalent to a JSON object. json_encode() serializes the array to JSON.

• Java: The Apache Commons CSV library provides CSVParser and CSVRecord classes for reading CSV data. Map each record to a Map using the header names as keys, then serialize to JSON using Jackson or Gson.

• Go: The encoding/csv package in Go's standard library reads CSV data. Use the first row as headers and map subsequent rows to slices of strings, then serialize to JSON using encoding/json.

For quick, one-off conversions without writing code, Thetoolity's tool is the fastest option.

Thetoolity brings together a growing collection of free, fast, and clean online tools for developers, data analysts, and anyone who works with data every day. Our CSV to JSON converter is one of many tools designed to handle common data transformation tasks instantly, with no account required and no data leaving your device.

No subscriptions. No paywalls. No cluttered interfaces. Just tools that load instantly and work every time.

Explore the full collection at Thetoolity.com and find generators, converters, calculators, checkers, and testers, all free and all instant.