JSON to CSV Converter

What is JSON to CSV conversion?

JSON stores structured data using objects, arrays, keys, and values. CSV stores tabular data as rows and columns. Converting JSON to CSV means turning JSON keys into column headers and creating rows from individual records.

JSON is commonly used by APIs, applications, webhooks, and data exports, while CSV is useful for spreadsheets, reports, and tabular imports. This converter turns structured JSON into CSV directly in your browser.

Here is a basic example showing two records in a JSON array:

[
  {
    "name": "Asha",
    "age": 29,
    "city": "Delhi"
  },
  {
    "name": "Ravi",
    "age": 34,
    "city": "Pune"
  }
]

When converted to CSV, the keys become column headers and each object becomes one row:

name,age,city
Asha,29,Delhi
Ravi,34,Pune

How to convert JSON to CSV

1. Paste or upload JSON Paste JSON text into the source panel or use the upload option to choose a supported .json file from your device.
2. Check the JSON Use the formatting or validation controls, if available, to make the JSON easier to read and identify syntax problems before conversion.
3. Convert to CSV Run the conversion to turn JSON records into CSV rows and columns.
4. Review the output Check the generated headers and rows. Pay special attention to nested fields, missing keys, arrays, and values containing commas or quotes.
5. Copy or download Copy the CSV text to your clipboard or download the generated CSV file if that option is available.

JSON to CSV examples and conversion rules

JSON and CSV represent data differently. These common mappings show how structured JSON can be turned into a flat table:

Converting nested JSON with dot notation

Real JSON often contains objects inside other objects. For example, an address may be grouped under a parent key:

[
  {
    "name": "Asha",
    "address": {
      "city": "Delhi",
      "zip": "110001"
    }
  }
]

If the converter uses dot-notation flattening, the result can look like this:

name,address.city,address.zip
Asha,Delhi,110001

This keeps the relationship between the parent and child keys while fitting the data into a two-dimensional CSV table.

How arrays are handled

CSV does not have a native array type. When a JSON property contains an array, one practical approach is to preserve that array as text inside a single CSV cell.

[
  {
    "name": "Asha",
    "tags": ["news", "tech"]
  }
]

If arrays are serialized as compact JSON text, the CSV may look like this:

name,tags
Asha,"[""news"",""tech""]"

The array remains available as text in one cell instead of being split across separate CSV columns. Verify that this matches the converter's actual array-handling behavior.

How missing keys and inconsistent records are handled

JSON objects do not need to contain exactly the same keys. For example:

[
  { "name": "Asha", "city": "Delhi" },
  { "name": "Ravi" }
]

If the converter creates columns from the keys found across the records, the output can look like this:

name,city
Asha,Delhi
Ravi,

The second row keeps an empty cell for city, which preserves alignment with the CSV header.

How commas, quotes, and line breaks are handled

CSV uses commas to separate fields, so values containing commas, double quotes, or line breaks usually need quoting.

• Values with commas: A value such as Ravi, Jr. is enclosed in double quotes so the comma stays inside one cell.
• Values with double quotes: Quotes inside a quoted CSV field are represented by doubling them.
• Values with line breaks: Multi-line text is enclosed in double quotes so it remains inside one CSV field.

For example, this JSON:

[
  {
    "name": "Asha",
    "note": "Uses commas, quotes like \"this\", and line\nbreaks"
  }
]

can produce CSV like:

name,note
Asha,"Uses commas, quotes like ""this"", and line
breaks"

This follows common CSV escaping conventions for commas, quotes, and line breaks.

When JSON to CSV is useful

Common use cases for converting JSON to tabular CSV include:

JSON that converts well to CSV

CSV works best when the source JSON contains records with a similar structure. An array of objects with consistent keys is usually the easiest shape to convert:

[
  { "id": 1, "name": "Asha", "status": "active" },
  { "id": 2, "name": "Ravi", "status": "inactive" }
]

Keep in mind that spreadsheet applications may reinterpret some CSV values after opening the file. Dates, long numbers, and identifiers with leading zeros such as 00123 may need to be imported as text if their exact formatting matters.

When CSV may not be the right format

CSV is a flat table format. If you need to preserve deeply nested objects, multi-level arrays, strict data types, or schema relationships, keeping the data as JSON may be a better choice.

You can inspect or format JSON with the JSON Formatter, convert it to XML with JSON to XML, or convert it to YAML with JSON to YAML. To reverse the workflow, use the CSV to JSON Converter.

Common JSON-to-CSV issues

• Invalid JSON: Missing quotes, trailing commas, or broken brackets can prevent parsing. Use the JSON Formatter to inspect the input if needed.
• Unsupported root value: Primitive JSON values such as "hello" or 42 do not naturally map to rows and columns. Check whether the converter expects an object, an array of objects, or both.
• Primitive arrays: An array such as [1, 2, 3] has no object keys to use as column names unless the converter applies a special rule.
• Different keys across records: Records with missing fields may produce empty cells where other records contain values.
• Nested arrays or objects: Complex structures may need flattening or serialization before they fit cleanly into CSV.
• Large inputs: Browser-based conversion can take longer with larger files, deep nesting, or devices with limited memory.

Before using the CSV

• Check that the expected JSON properties became the correct CSV columns.
• Review how nested values were flattened or serialized.
• Check records with missing properties for correctly aligned empty cells.
• Confirm that commas, quotes, and line breaks appear correctly.
• Open the downloaded CSV in the destination application and review how it interprets dates, numbers, and leading zeros.

Browser-based processing

The JSON-to-CSV conversion runs locally in your browser to maintain privacy and does not require uploading the JSON input to TryFormatter's server to produce the CSV output.

Avoid including passwords, API keys, access tokens, or other secrets in datasets unless they are required for the task.