JSON to CSV Converter

Nested JSON to CSV Example

Input JSON

[
  {
    "id": 1001,
    "name": "Alice Chen",
    "active": true,
    "address": { "city": "Seattle", "country": "US" },
    "tags": ["customer", "beta"]
  },
  {
    "id": 1002,
    "name": "Marco Rossi",
    "active": false,
    "address": { "city": "Milan", "country": "IT" },
    "tags": []
  }
]

Expected Result

Output CSV

id,name,active,address.city,address.country,tags
1001,Alice Chen,true,Seattle,US,"customer,beta"
1002,Marco Rossi,false,Milan,IT,

How JSON Fields Become CSV Columns

• Each object in a JSON array becomes one CSV row, which is the most common format for API exports and application data.
• Nested object keys are flattened into column names such as address.city so the hierarchy is still readable in a spreadsheet.
• Missing keys become empty CSV cells instead of shifting the row, which keeps every row aligned with the same header.
• Array values are converted into a single cell. For deeply nested arrays of objects, review the output before importing into Excel or a database.
• Text with commas, quotes, or line breaks must be quoted correctly so the CSV does not break into the wrong number of columns.

Common JSON to CSV Problems

• If the output looks like one long row, the input may be a single JSON object rather than an array of records.
• If Excel displays strange characters, open the CSV as UTF-8 or import it through Excel’s data import flow instead of double-clicking the file.
• If arrays produce crowded cells, consider whether the data should be normalized into multiple CSV files instead of one flat table.
• If formula-like values begin with =, +, -, or @, check them before sharing the CSV to avoid spreadsheet formula injection risks.

Best Use Cases

• Convert API responses into rows for Excel or Google Sheets analysis.
• Flatten webhook logs, product feeds, user exports, and analytics payloads.
• Prepare structured JSON data for reporting tools that only accept CSV imports.

When This Tool Is Not Enough

• Very complex relational JSON where one parent record contains many child tables.
• Binary JSON-like formats or invalid JSON with comments, trailing commas, or unescaped quotes.
• Workflows that require guaranteed schema validation before export.