Convert JSON to CSV

Transform JSON data into CSV (Comma-Separated Values) format instantly with this free online converter. Whether you're working with API responses, database exports, or configuration files, this tool flattens JSON arrays of objects into clean tabular rows and columns — making your data immediately usable in spreadsheet applications like Microsoft Excel, Google Sheets, or LibreOffice Calc. The converter automatically generates column headers from your JSON object keys, maps each object to a corresponding CSV row, and intelligently handles nested structures using dot notation (e.g., a key like address.city becomes its own column). Special characters that would break CSV parsing — such as commas, quotation marks, and newlines — are properly escaped to ensure the output is RFC 4180-compliant and opens correctly in any spreadsheet tool. This converter is ideal for developers, data analysts, business intelligence professionals, and anyone who regularly works with JSON payloads and needs to share or analyze that data in a more accessible, tabular format. No installation required, no file size limits for typical datasets, and your data never leaves your browser — making it safe to use even with sensitive information.

Input (JSON)

Options

CSV Header Row

Convert the keys of JSON objects into the header row of the CSV

CSV Column Separator

Character that separates columns. (By default, CSV uses a comma as a delimiter.)

CSV Field Quote

Character that encloses fields in quotes. (By default, CSV uses double quotes.)

Enclose all CSV Values in quotes

Output (CSV)

What It Does

How It Works

Convert JSON to CSV changes data from Json into Csv. That is more than a cosmetic rewrite. Field layout, quoting, nesting, and even type representation can shift because the destination format has different rules and limits.

Conversion tools are constrained by the destination format. If the source can express nesting, comments, repeated keys, or mixed data types more richly than the target, the output may need to flatten or reinterpret part of the structure.

All processing happens in your browser, so your input stays on your device during the transformation.

Common Use Cases

Exporting JSON API responses to Excel or Google Sheets for stakeholder reporting and business review.
Converting JSON-formatted reports from web applications into spreadsheet-friendly CSV files for further analysis.
Preparing JSON datasets for use in Python's pandas library or R by generating a clean CSV starting point.
Creating downloadable CSV exports from JSON payloads returned by REST APIs in web development projects.
Migrating JSON data records into relational database systems that accept CSV as an import format.
Transforming e-commerce order data or CRM exports stored as JSON into tabular format for pivot table analysis.
Validating and previewing JSON data structure by converting it to a table to spot missing fields or inconsistencies.

How to Use

Paste your JSON array of objects into the input field — ensure the top-level structure is an array (wrapped in square brackets) containing one or more objects.
The tool automatically parses your JSON and extracts all unique keys across every object to generate column headers for the CSV output.
Each object in the JSON array is mapped to a single row in the CSV, with values placed under their corresponding column headers.
Nested objects are automatically flattened using dot notation — for example, a field like 'user.address.city' becomes a separate column named 'user.address.city'.
Review the generated CSV output in the preview area, then click the Copy or Download button to save the file to your computer or clipboard.
Open the downloaded CSV file directly in Excel, Google Sheets, or any other spreadsheet application — no additional formatting steps required.

Features

Automatic header generation by scanning all unique keys across every object in the JSON array, ensuring no columns are missed even in sparse datasets.
Nested object flattening using dot notation, so deeply structured JSON like API responses with sub-objects are fully converted without data loss.
RFC 4180-compliant CSV output that correctly escapes commas, double quotes, and embedded newlines within field values.
Handles sparse or inconsistent JSON objects gracefully — if some objects are missing certain keys, the corresponding cells are left empty rather than throwing an error.
Client-side processing means your JSON data is never uploaded to a server, making this safe for use with confidential or proprietary datasets.
One-click copy and download options let you instantly transfer the CSV output to your clipboard or save it as a .csv file.
Real-time conversion with instant feedback — as soon as valid JSON is detected, the CSV output updates without needing to click a convert button.

Examples

Below is a representative input and output so you can see the transformation clearly.

Input

[{"name":"Ada","score":9},{"name":"Lin","score":7}]

Output

name,score
Ada,9
Lin,7

Edge Cases

Very large inputs can still stress the browser, especially when the tool is working across many JSON values. Split huge jobs into smaller batches if the page becomes sluggish.
Source values that look similar can map differently in the target format when data types are inferred, flattened, or serialized.
If the output looks wrong, compare the exact input and option values first, because Convert JSON to CSV should be repeatable with the same settings.

Troubleshooting

Unexpected output often means the input is being split or interpreted at the wrong unit. For Convert JSON to CSV, that unit is usually JSON values.
If a previous run looked different, check for hidden whitespace, changed separators, or a setting that was toggled accidentally.
If nothing changes, confirm that the input actually contains the pattern or structure this tool operates on.
If the page feels slow, reduce the input size and test a smaller sample first.

Tips

For best results, structure your JSON as a flat array where each object shares a consistent set of keys — this produces the cleanest, most readable CSV. If your JSON contains deeply nested arrays within objects (e.g., an order with a nested line items array), consider pre-processing or extracting the sub-array separately before converting, as nested arrays may not translate meaningfully to flat CSV rows. When opening the CSV in Excel on Windows, watch for encoding issues with special characters — saving the file as UTF-8 with BOM or importing via Excel's 'Get Data' wizard rather than double-clicking ensures accented characters and symbols display correctly. If your JSON keys contain spaces or special characters, those will carry over as column headers, so clean up key names in the source JSON first if you plan to import the CSV into a database or use it in code.

JSON (JavaScript Object Notation) and CSV (Comma-Separated Values) are two of the most widely used data interchange formats in modern software, but they serve very different purposes. JSON is hierarchical, flexible, and schema-free — it can represent deeply nested relationships, mixed data types, and complex structures that mirror how applications think about data internally. CSV, on the other hand, is flat, tabular, and universally understood by spreadsheet software, business intelligence tools, and relational databases. The need to convert between them is one of the most common data wrangling tasks developers and analysts face daily. When you receive data from a REST API, it almost always arrives as JSON. But if your stakeholders want to analyze that data in Excel, import it into a SQL database, or run it through a machine learning pipeline, they need it in tabular form. That translation process — flattening a hierarchical JSON structure into rows and columns — is what this tool automates for you. The key challenge in JSON-to-CSV conversion is handling nested structures. A simple JSON object like {"name": "Alice", "age": 30} maps trivially to a single CSV row. But real-world API data often looks more like {"user": {"name": "Alice", "address": {"city": "New York"}}, "age": 30} — multiple levels of nesting that have no direct CSV equivalent. The standard solution is dot notation flattening, where nested keys are concatenated with a period to create unique column names: user.name, user.address.city, age. This approach preserves all data while producing a valid, readable CSV. Arrays embedded within JSON objects present a separate challenge. If a JSON object contains a nested array (e.g., a customer record with an array of past orders), there is no clean way to represent that in a single CSV row without either losing data or creating a confusing multi-value cell. Best practice in these cases is to extract and convert the nested array separately, treating it as its own dataset with a foreign key linking back to the parent record — the same pattern used in relational database design. Compared to other data formats, CSV holds a unique position because of its simplicity and universal support. Unlike Excel's .xlsx format, which requires a specific library to generate or parse, CSV is plain text that any tool can read. Unlike JSON, it does not require a parser — you can open a CSV in Notepad and understand it immediately. Unlike XML, it has no verbose markup overhead. For data exchange between systems that don't share a common API, CSV remains the lowest common denominator that just works. From an SEO and data workflow perspective, JSON-to-CSV conversion is a foundational skill for anyone working in web development, data journalism, digital marketing analytics, or business intelligence. Google Analytics, Facebook Ads, and most SaaS platforms offer JSON exports from their APIs, while their human-facing import tools almost universally accept CSV. Knowing how to bridge that gap efficiently — and understanding the flattening logic behind it — makes you significantly more effective working across these platforms.

Frequently Asked Questions

What kind of JSON can be converted to CSV?

This tool works best with a JSON array of objects — that is, a top-level array (in square brackets) where each element is a JSON object (in curly braces) with key-value pairs. This structure maps naturally to rows and columns. Single objects, arrays of primitives, or deeply irregular structures may produce less predictable results, so it's worth reviewing the output when working with unusual JSON shapes.

How does the tool handle nested JSON objects?

Nested objects are flattened using dot notation. For example, if your JSON has a field like {"address": {"city": "London", "zip": "EC1A"}}, the converter will produce two columns named address.city and address.zip. This keeps all your data intact while producing a valid flat CSV structure. Very deeply nested objects will produce long column names but will still be converted correctly.

What happens if my JSON objects have inconsistent keys?

The converter scans all objects in the array to build a complete list of unique column headers. If some objects are missing certain keys that others have, the missing values are simply output as empty cells in the corresponding rows. This is standard CSV behavior and will import cleanly into Excel, Google Sheets, or any database tool without errors.

Is my data safe when I use this tool?

Yes — this converter runs entirely in your browser using client-side JavaScript. Your JSON data is never sent to any server or stored anywhere externally. This makes it safe to use even with sensitive, proprietary, or personally identifiable data. Simply close the browser tab when you're done and no trace of your data remains.

How is JSON-to-CSV conversion different from JSON-to-Excel conversion?

CSV is a plain text format that any spreadsheet application can open, while Excel's .xlsx format is a binary format with support for formatting, formulas, and multiple sheets. Converting to CSV is more universally compatible and simpler, but you lose Excel-specific features. For most data transfer and analysis purposes, CSV is the better starting point — you can always apply formatting in Excel after importing the CSV.

Can this tool handle large JSON files?

For typical API responses and datasets up to a few thousand records, the tool handles conversion instantly in the browser. Very large files (tens of thousands of rows or deeply nested structures) may cause the browser to slow down due to memory constraints of client-side processing. For very large datasets, consider splitting your JSON into smaller batches or using a server-side tool or command-line utility like jq or Python's csv module.

Why does my CSV look wrong when I open it in Excel?

The most common issue is character encoding — Excel on Windows sometimes misinterprets UTF-8 encoded files, causing accented characters or symbols to appear garbled. To fix this, use Excel's 'Data > Get External Data > From Text/CSV' import wizard rather than double-clicking the file, and select UTF-8 encoding during the import steps. Another common issue is Excel auto-formatting numbers or dates stored as strings — wrapping those values in quotes in the source JSON can help prevent that.

What should I do if my JSON contains arrays within objects?

Nested arrays (e.g., a product object containing an array of reviews) cannot be directly represented as flat CSV rows without losing structure. The best approach is to separate the nested array into its own dataset before converting — extract the reviews array into its own JSON array, add a parent ID field to link them back, and convert each dataset separately. This mirrors relational database normalization and produces clean, importable CSV files for each entity.