Convert JSON records to CSV online for Excel, Google Sheets, and other spreadsheet tools. Paste JSON or open a file, preview the detected columns, optionally flatten nested objects, and download a CSV file directly from your browser.
Convert a JSON array of objects into CSV rows and columns. Each object becomes a record, and the detected fields are used as CSV headers.
Review the detected columns and converted rows before downloading. This helps you find missing fields, unexpected values, and flattening issues before exporting the file.
Convert nested object properties into dot-notation columns such as user.name or address.city. Nested arrays may be serialized or require a separate transformation depending on their structure.
Choose the columns to include in the CSV output when you only need selected fields from a larger JSON response or dataset.
Generate standard comma-separated output and correctly escape values containing commas, quotation marks, or line breaks. Use the available delimiter and encoding options supported by the page.
Download the generated CSV file for use in Excel, Google Sheets, database imports, reporting workflows, or other applications that accept delimited text.
Paste JSON directly into the editor or open a .json file from your device. The input is parsed in the browser before the CSV is generated.
JSON parsing, table preparation, and CSV generation happen in your browser. The converter does not require an account or a server upload.
Paste a JSON array of objects into the input field or open a .json file. API responses and exported records usually need to be reduced to the array that contains the rows.
Run the conversion and inspect the table preview. The converter collects fields across the records, so rows with different keys may produce empty cells in some columns.
Enable nested-object flattening when you need properties such as user.name or address.city as separate columns. Select only the fields you want to export when the dataset contains unnecessary properties.
Review the converted rows, then download the CSV file. Open it in Excel or import it into Google Sheets and confirm the delimiter and character encoding if the spreadsheet displays unexpected characters.
[
{ "name": "Alice", "age": 30, "city": "New York" },
{ "name": "Bob", "age": 25, "city": "London" }
]name,age,city Alice,30,New York Bob,25,London
JSON is commonly used for APIs, application data, configuration, and database exports. CSV is a flat, delimited format that works well with spreadsheets, reporting tools, and simple data-import workflows. Converting JSON to CSV is useful when you need to inspect records as rows and columns rather than as nested objects.
The most suitable JSON input is a top-level array of objects. Each object represents one record, and its properties become CSV fields. Because CSV has only two dimensions, nested objects and arrays need an explicit representation before they can be exported.
user.name and address.city to become separate columns.Nested objects cannot be placed directly into a flat spreadsheet cell without choosing a representation. A common approach is to flatten object paths with dot notation:
{"user":{"name":"Alice","address":{"city":"New York"}},"status":"active"}After flattening, the fields may become user.name, user.address.city, and status. This works well for nested objects, but nested arrays need separate rules. They may be serialized as JSON text, joined into a single cell, expanded into columns, or handled as additional rows depending on the conversion design.
Real-world records often do not share exactly the same fields. A converter can scan the records and create a union of the discovered keys. When one record does not contain a field, the corresponding CSV cell is empty. This preserves the row alignment but may create a wide spreadsheet when the source data contains many optional properties.
CSV values containing commas, double quotes, or line breaks need special handling. A value containing a comma is normally enclosed in double quotes, and an internal double quote is escaped by doubling it. Correct escaping is important when names, descriptions, addresses, or API fields contain punctuation or multiline text.
CSV is a relatively simple format, but spreadsheet programs may differ in their assumptions about delimiters, line endings, character encoding, and formula interpretation. Test a representative sample before distributing a large export.
For multilingual data, UTF-8 is usually the most interoperable encoding. Microsoft documents that a UTF-8 CSV saved with a BOM can be opened correctly in Excel, while files without a BOM may need to be imported through Excel's data or text-import workflow with UTF-8 selected manually.[164][166]
A BOM can improve direct opening in some Excel environments, but it is not a universal solution for every spreadsheet application. If the file still displays incorrectly, use the import dialog and explicitly select UTF-8 and the correct delimiter.
=, +, -, or @ as formulas. Treat untrusted exports carefully and consider formula-injection protection when exporting data for other users.This converter is designed to process JSON and create CSV in the browser rather than sending the source data to a remote conversion service. That can be useful for internal records and development data. However, a browser-based tool should not be treated as a secure secret-management system. Avoid entering credentials, tokens, private customer data, or production secrets into any online converter.
CSV is useful for flat records and spreadsheet workflows, but JSON is usually a better choice when nested structure, arrays, exact data types, or machine-to-machine interchange must be preserved. If converting to CSV would create many ambiguous columns or lose important relationships, keep the original JSON or use a format designed for nested data.