JSON to CSV Converter

Converting JSON data to CSV takes about fifteen seconds.

Step 1: Paste your JSON into the input field. Your JSON should be an array of objects where each object represents one row of data. Each object's keys will become the CSV column headers. The tool also accepts a single JSON object.

Step 2: Click "Convert to CSV." The tool instantly parses your JSON, extracts all keys as column headers, and maps each object's values to the correct columns.

Step 3: Copy or download the CSV output. The resulting CSV appears in the output area. Copy it to your clipboard or download it as a .csv file ready to open in Excel, Google Sheets, Numbers, or any other spreadsheet application.

The tool includes a "Load Example" button to demonstrate the expected JSON format if you need to see a working sample before pasting your own data.

JSON stands for JavaScript Object Notation. It is a lightweight, text-based data format used for storing and transmitting structured data. Despite its name containing "JavaScript," JSON is language-independent and is used in virtually every programming language and technology stack.

A JSON file or string contains data organized as key-value pairs (called objects) and ordered lists of values (called arrays). The format is human-readable, making it easy to inspect, edit, and debug.

A JSON object looks like this: {"name": "Alice", "email": "alice@example.com", "age": 30}

A JSON array is a collection of values enclosed in square brackets. An array of objects, where each object has the same keys, is the most common JSON structure that maps directly to tabular data like a spreadsheet: [{"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}]

JSON is the dominant format for REST API responses. When you fetch data from a web API, whether it is a social media platform, a payment gateway, a database, or any other service, the response is almost always in JSON format. Converting that API data to CSV is one of the most common data tasks in development and data analysis work.

CSV stands for Comma Separated Values. It is a plain text format for storing tabular data where each row is a line and each column value is separated by a delimiter, most commonly a comma.

A CSV file is essentially a text representation of a spreadsheet. The first row typically contains the column headers. Each subsequent row contains the data values for one record.

A CSV equivalent of the JSON example above would look like this:

name,email,age
Alice,alice@example.com,30
Bob,bob@example.com,25

CSV is one of the most universally compatible data formats in existence. It can be opened by Excel, Google Sheets, LibreOffice Calc, Numbers, and virtually every data analysis tool, database import wizard, and business intelligence platform. This universal compatibility is the main reason why converting JSON to CSV is such a frequent task.

CSV files are also significantly smaller and more memory-efficient than JSON for the same tabular data, because they have no key repetition. In JSON, the field name "name" appears in every single object. In CSV, it appears only once in the header row.

JSON and CSV serve different purposes and are optimized for different contexts. Understanding why you might need to convert from one to the other helps you make better workflow decisions.

Opening data in a spreadsheet

This is the most common reason. Analysts, marketers, finance teams, and non-developers who receive data from APIs or databases as JSON need a way to open and work with that data in familiar tools like Excel or Google Sheets. Neither Excel nor Google Sheets natively handles raw JSON arrays. Converting to CSV provides immediate access to the data in a format everyone can use.

Importing data into another system

Many database import tools, CRM systems, email marketing platforms, e-commerce backends, and project management tools accept CSV for bulk data import but do not accept JSON. Converting your JSON export to CSV enables import into these systems.

Data analysis with Python or R

Pandas (Python) and tidyverse (R) have highly optimized CSV readers that are faster than JSON parsers for large tabular datasets. Analysts working with data from API responses often convert to CSV as a first step in their data pipeline.

Sharing data with non-technical stakeholders

This is easier in CSV format. A product manager, an executive, or a client who receives a CSV file can open it directly in Excel. Someone who receives a raw JSON file needs either a developer or a JSON viewer to work with it.

Version control and diff tracking

This is easier with CSV than with JSON for tabular data. Each row is one line, so changes are visible as line diffs. JSON objects with multi-line formatting produce noisy diffs when single fields change.

Reducing file size for large datasets

This can make CSV the better choice for storage and transmission. The repeated key names in JSON arrays add significant overhead. A dataset with 10 fields and 100,000 rows uses each field name 100,000 times in JSON but only once in CSV.

For a JSON to CSV conversion to produce clean, useful output, the input JSON should follow certain structural conventions. Understanding these helps you prepare your data correctly.

Array of objects is the ideal structure. The converter works best when the input is a JSON array where every element is a flat object with the same keys. This maps directly to tabular CSV: the keys become column headers and each object becomes a row.

Example of ideal structure: [ {"id": 1, "name": "Alice", "email": "alice@example.com"}, {"id": 2, "name": "Bob", "email": "bob@example.com"}, {"id": 3, "name": "Carol", "email": "carol@example.com"} ]

Consistent keys across objects produce the cleanest output. When all objects have the same keys, every column is populated for every row. When some objects have extra keys that others lack, the converter creates columns for all unique keys and leaves blank values where a key is missing from an object.

Flat objects (no nesting) produce the simplest CSV. CSV is inherently flat: each cell holds a single scalar value. JSON supports nested objects and arrays as values, which CSV cannot represent directly. A nested object like {"address": {"city": "London", "country": "UK"}} must either be flattened into separate columns (city, country) or serialized as a string in a single column. Thetoolity's converter handles nested values by serializing them as strings in the CSV cell.

A single object (not an array) can also be converted. A single JSON object produces a two-column CSV with "key" and "value" headers, or a single-row CSV with the object's keys as headers and its values as the row.

The comma is the standard separator in CSV files, but real-world CSV usage involves several formatting details that affect whether files open correctly in different tools.

• The comma delimiter is the default and most widely used separator. Excel, Google Sheets, and most data tools recognize comma-separated files immediately. Thetoolity's converter uses commas as the default delimiter.

• Quoting fields that contain commas is essential to prevent misparse. If a field value contains a comma, the entire value must be enclosed in double quotes. For example, the address "123 Main St, London" in a CSV must be quoted: "123 Main St, London". Without quoting, the comma in the address would be interpreted as a column separator.

• Quoting fields that contain double quotes requires escaping the inner quote by doubling it. A field containing the value He said "hello" becomes "He said ""hello""" in properly formatted CSV.

• Newlines within field values also require quoting the field. A multi-line text field must be enclosed in double quotes in the CSV output.

• Alternative delimiters are sometimes used. Semicolons are common in European countries where the comma is used as a decimal separator (1.000,50 for one thousand). Tab-separated values (TSV) are used for data that commonly contains commas. Pipe characters are used in some systems. If you need a non-comma delimiter, the CSV output from Thetoolity can be opened in a text editor and the delimiters replaced before importing into Excel.

The header row is the first row of a CSV and contains the column names. Well-formed CSV files always include a header row. Thetoolity's converter derives column headers automatically from the keys of your JSON objects.

Once you have converted your JSON to CSV, here is how to open the result in the most common tools.

• Microsoft Excel: If you save the CSV file with a .csv extension and double-click it, Excel typically opens it automatically with comma detection. For more control, use the Data tab and choose "From Text/CSV" or "Get External Data" to use the Text Import Wizard, which lets you specify the delimiter and data types for each column.

• Google Sheets: Open Google Sheets and use File, then Import. Select your CSV file or paste the CSV text. In the import dialog, select "Detect automatically" for the separator type or choose "Comma" explicitly. Google Sheets then creates a new sheet with your data in tabular form.

• LibreOffice Calc: Open the application and drag the CSV file onto it, or use File then Open. A dialog will appear letting you specify the character set, delimiter, and how to handle quoted fields.

• Apple Numbers: Numbers opens CSV files directly. Double-click the file or use File, Open. Numbers typically detects the comma delimiter automatically.

• Python with Pandas: If you are working programmatically, pandas.read_csv() reads CSV files with a single line of code and provides a DataFrame ready for analysis, filtering, and transformation.

For developers who need to convert JSON to CSV programmatically in their applications rather than using an online tool, here is how to do it in common languages.

• JavaScript (browser and Node.js): The simplest approach is to extract the keys from the first object as headers, then map each object to a row of comma-joined values, joining rows with newlines. Libraries like Papa Parse handle edge cases including quoting, nested values, and encoding. In Node.js, the json2csv package is a popular option with many configuration options.

• Python: The csv module in the standard library handles CSV writing. Load your JSON with json.loads() or json.load(), then create a csv.DictWriter with the field names from the first object's keys, and write each row. The pandas library provides an even simpler approach: pandas.DataFrame(data).to_csv() converts a list of dictionaries to a CSV file with one line.

• Node.js: The json2csv library provides flexible conversion with support for nested paths, custom delimiters, and large file streaming. For simple flat structures, a few lines of vanilla JavaScript suffice.

• PHP: PHP's array_map() and implode() functions can produce CSV rows. The fputcsv() function writes properly quoted and escaped CSV rows to a file handle. For in-memory CSV generation, write to php://output or a string buffer.

• Java: The Apache Commons CSV library provides robust CSV writing with proper quoting and escaping. For simple cases, StringBuilder with manual formatting and quoting logic is straightforward.

For quick, one-off conversions and working with data you already have in hand, Thetoolity's browser-based tool is faster than any code solution.

A few common issues arise when converting JSON to CSV. Knowing how to recognize and fix them saves significant debugging time.

• Invalid JSON input is the most frequent cause of conversion failure. Common JSON syntax errors include using single quotes instead of double quotes around strings and keys, missing commas between objects in an array, trailing commas after the last element (which JavaScript allows but JSON does not), and unquoted key names. Paste your JSON into a JSON validator before attempting conversion if the converter returns an error.

• Nested objects producing unexpected output happens when your JSON contains objects within objects or arrays within objects. CSV cannot directly represent hierarchy. The nested content will be serialized as a string in the output cell, which may need to be parsed further in your destination tool.

• Missing columns for some rows appears when objects in the array do not all have the same keys. The converter creates columns for all unique keys found across all objects and leaves empty cells where keys are absent. This is usually correct behavior, but if you expected all rows to have the same columns, review your source data for inconsistencies.

• Encoding issues produce garbled characters when the JSON contains non-ASCII characters (accented letters, Chinese characters, Arabic script, emoji) and the CSV is opened in a tool that expects a different character encoding. Ensure your CSV file is saved as UTF-8 and that Excel or your spreadsheet tool opens it with UTF-8 encoding selected.

• Date values as numbers appear when your JSON contains Unix timestamps (numbers representing seconds since January 1, 1970). These will appear as plain numbers in the CSV. You may need to use a formula in Excel or a conversion step in your data pipeline to convert them to readable date formats.

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 JSON to CSV converter is one of many tools designed to handle common data transformation tasks instantly, without any account, installation, or upload required.

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.