How are quoted fields and special characters handled in CSV?

The parser fully supports RFC 4180 CSV rules. Fields containing the delimiter, double quotes, or newlines are wrapped in quotes. Double quotes inside quoted fields are escaped by doubling them. You can also enable the Quote All Fields option to wrap every value in quotes.

JSON ↔ CSV Converter

Q: How does the JSON to CSV converter handle nested objects?

Nested objects are flattened using dot notation. For example, an object with address.city and address.zip becomes two separate CSV columns named address.city and address.zip. Arrays are serialized as JSON strings within the CSV cell.

Q: Does the CSV to JSON converter auto-detect the delimiter?

Yes. The tool analyses the first row of your CSV to detect whether it uses commas, semicolons, tabs, or pipes as the delimiter. It counts occurrences of each and selects the most likely one automatically.

Q: Is my data safe when using this converter?

Yes. All conversion happens entirely in your browser using JavaScript. Your data never leaves your device — nothing is sent to a server, logged, or stored. You can safely convert files containing API keys, user data, or proprietary information.

Q: Can I convert a single JSON object instead of an array?

Yes. If you paste a single JSON object (not wrapped in an array), the tool automatically wraps it in an array and produces a one-row CSV. This is useful for quickly converting individual API response objects.

Q: What CSV delimiters are supported?

In JSON to CSV mode, you can choose from comma, semicolon, tab, or pipe as your delimiter. In CSV to JSON mode, the delimiter is auto-detected from your input. This covers all common CSV formats including TSV files.

Q: Can I upload files instead of pasting text?

Yes. Click the Upload button or drag and drop a .json or .csv file onto the input panel. The file is read locally in your browser and its contents are loaded into the input area. You can then convert and download the result.

Q: Does the CSV to JSON converter parse numbers automatically?

By default, yes. Values that look like numbers (integers and decimals) are converted to JSON number types instead of strings. You can toggle this off with the Parse Numbers option if you want all values to remain as strings in the output.

Convert JSON to CSV and CSV to JSON instantly. Handles nested objects with dot notation, auto-detects delimiters, supports file upload and download. Free. No sign-up.

DelimiterInclude headersQuote all fields

JSON Input

Drop a .json file here

CSV Output

How it works

1
Choose your mode
Select JSON to CSV or CSV to JSON. Toggle between them with one click, or swap input and output with the arrow button.
2
Paste or upload
Paste your data into the input panel or drag and drop a .json or .csv file. Configure delimiter, header, and parsing options.
3
Convert and export
Click Convert and get your result instantly. Copy to clipboard or download as a .csv or .json file with one click.

Why You Need a JSON to CSV and CSV to JSON Converter

JSON and CSV are the two most common data interchange formats on the web. APIs return JSON, spreadsheets use CSV, databases export both, and data pipelines move between them constantly. Converting between these formats manually is tedious and error-prone, especially when dealing with nested JSON structures, special characters, or large datasets. A dedicated converter handles the edge cases that trip up manual approaches.

The JSON to CSV direction is essential when you need to import API data into Excel, Google Sheets, or a business intelligence tool. Nested objects are automatically flattened using dot notation, so a field like address.city becomes its own column. Arrays within objects are serialised as JSON strings, preserving the data without losing structure.

The CSV to JSON direction is equally important. When you export data from a spreadsheet or receive a CSV file from a client, you often need to transform it into JSON for an API request, a configuration file, or a database import. The converter auto-detects the delimiter, uses the first row as field names, trims whitespace, and converts numeric strings to actual numbers so you get clean, type-safe JSON output.

Both conversions happen entirely in your browser. Your data never leaves your device, making this tool safe for files containing API keys, customer information, financial records, or any other sensitive data. There is no server processing, no logging, and no storage.

Handling Nested JSON Objects

Real-world JSON from APIs is rarely flat. Stripe payment objects have nested customer data, Shopify orders contain nested line items, and CRM exports include nested contact details. The converter flattens these using dot notation: a key path like customer.address.city becomes a single CSV column header. This preserves the full path so you can trace each value back to its original location in the JSON structure.

CSV Parsing Done Right

CSV looks simple but has surprising complexity. Fields can contain commas, newlines, and double quotes. The correct handling follows RFC 4180: fields with special characters are wrapped in double quotes, and double quotes inside a field are escaped by doubling them. Our parser handles all of these cases, plus tab-separated and pipe-separated files. The auto-detect feature analyses the first row to determine which delimiter your file uses.

Common Use Cases

Developers use this converter to transform API responses into spreadsheets for non-technical stakeholders. Data analysts use it to prepare CSV exports for JSON-based APIs. QA teams convert test fixtures between formats. Marketing teams transform CRM exports into JSON for email automation platforms. The swap button makes it easy to convert in both directions without switching tools.