Convert JSON to CSV

Why Convert JSON to CSV?

Converting JSON to CSV is one of the most common data transformation tasks in modern workflows. JSON files from APIs and web services often contain structured, nested data that needs to be analyzed in spreadsheet applications like Microsoft Excel or Google Sheets. By flattening JSON into a CSV table, you make the data immediately accessible to business analysts, data scientists, and anyone who works with tabular data tools.

Many database systems, reporting platforms, and data visualization tools accept CSV as their primary import format. When you receive data from a REST API in JSON format and need to load it into a relational database, converting to CSV provides a clean, universally compatible intermediate format. The conversion process flattens nested JSON objects into columns and maps array elements into individual rows, preserving the essential data relationships.

CSV files are also dramatically smaller than their JSON equivalents because they eliminate the overhead of repeated key names, braces, and brackets. For large datasets with thousands or millions of records, this reduction in file size can be significant, making CSV the preferred format for data archival, batch processing, and efficient storage of homogeneous record sets.

Key Benefits of Converting JSON to CSV:

• Spreadsheet Compatibility: Open converted data directly in Excel, Google Sheets, or LibreOffice Calc for instant analysis
• Database Import: Load data into MySQL, PostgreSQL, or SQLite using native CSV import tools
• Reduced File Size: CSV eliminates repeated key names, producing files up to 50-70% smaller than JSON
• Universal Accessibility: Share data with non-technical users who are comfortable with spreadsheets
• Data Pipeline Integration: CSV is the standard input format for ETL tools, Hadoop, and data warehouses
• Simplified Analysis: Flat tabular structure enables quick sorting, filtering, and pivot table creation
• Batch Processing: Process millions of records efficiently with command-line tools like awk, cut, and csvkit

Practical Examples

Example 1: Simple Array of Objects

Converting a flat JSON array of product records into a CSV table:

Input JSON file:

[
  {"id": 1, "product": "Laptop", "price": 999.99, "stock": 45},
  {"id": 2, "product": "Mouse", "price": 29.99, "stock": 200},
  {"id": 3, "product": "Keyboard", "price": 79.99, "stock": 150}
]

Output CSV file:

id,product,price,stock
1,Laptop,999.99,45
2,Mouse,29.99,200
3,Keyboard,79.99,150

Example 2: Nested Objects with Flattening

Converting JSON with nested address objects into a flat CSV structure:

Input JSON file:

[
  {
    "name": "Alice Smith",
    "email": "[email protected]",
    "address": {
      "city": "New York",
      "country": "US"
    }
  },
  {
    "name": "Bob Jones",
    "email": "[email protected]",
    "address": {
      "city": "London",
      "country": "UK"
    }
  }
]

Output CSV file:

name,email,address.city,address.country
Alice Smith,[email protected],New York,US
Bob Jones,[email protected],London,UK

Example 3: JSON with Special Characters and Quoting

Handling values that contain commas and quotes in CSV output:

Input JSON file:

[
  {"title": "War and Peace", "author": "Tolstoy, Leo", "year": 1869},
  {"title": "\"1984\"", "author": "Orwell, George", "year": 1949},
  {"title": "The Great Gatsby", "author": "Fitzgerald, F. Scott", "year": 1925}
]

Output CSV file:

title,author,year
War and Peace,"Tolstoy, Leo",1869
"""1984""","Orwell, George",1949
The Great Gatsby,"Fitzgerald, F. Scott",1925

Frequently Asked Questions (FAQ)

Q: How does the converter handle nested JSON objects?

A: Nested JSON objects are flattened using dot notation for column headers. For example, an object with {"address": {"city": "NYC"}} becomes a column named address.city with value NYC. This preserves the data hierarchy in a flat tabular structure.

Q: What happens to JSON arrays inside records?

A: Arrays within individual records are serialized as strings in the CSV cell. For simple arrays, values are joined with a separator. For arrays of objects, each element may be expanded into separate rows depending on the conversion settings.

Q: Will my CSV file open correctly in Excel?

A: Yes. The output CSV follows RFC 4180 conventions, including proper quoting of fields that contain commas, double quotes, or newlines. The file uses UTF-8 encoding and is fully compatible with Microsoft Excel, Google Sheets, and LibreOffice Calc.

Q: Can I convert JSON with inconsistent keys across objects?

A: Yes. The converter scans all objects in the JSON array to collect the complete set of unique keys. Objects that are missing certain keys will have empty values in the corresponding CSV columns, ensuring a consistent table structure.

Q: Is there a limit on the number of records?

A: Our converter handles JSON files of any reasonable size, including files with tens of thousands of records. The conversion is processed server-side, so it works efficiently regardless of your device capabilities.

Q: Does the conversion preserve data types?

A: CSV is an untyped format, so all values are stored as plain text. Numbers, booleans, and null values from JSON are converted to their string representations. When you import the CSV into a spreadsheet or database, you may need to set column types manually.

Q: How are JSON null and boolean values represented in CSV?

A: JSON null values are converted to empty fields in the CSV output. Boolean values true and false are written as the literal strings "true" and "false". This ensures all data from the source JSON is represented in the output.