JSON to CSV Converter

Transform nested or flat JSON into clean delimited files with our JSON to CSV converter. Switch between comma, semicolon, and tab delimiters, prepend UTF-8 BOM for Microsoft Excel, and copy or download locally.

1. Input JSON Payload

Drop a .json file here or paste JSON array/object below

0 rows UTF-8 BOM
100% Client-Side · Your JSON never leaves your browser

How the JSON to CSV Converter Works

Generate clean, Excel-safe delimited text files in four quick steps.

  1. 01

    Paste or Drop JSON

    Paste a JSON array or envelope object, upload a .json file, or load the multilingual sample payload.

  2. 02

    Pick Delimiter & BOM

    Select comma, semicolon, or tab delimiter and keep UTF-8 BOM enabled if opening the file in Excel.

  3. 03

    Preview Table or Raw CSV

    Switch between live Table View and Raw CSV View, and uncheck any columns you want excluded.

  4. 04

    Download or Copy CSV

    Download the .csv/.tsv file directly from local memory or copy escaped CSV text to your clipboard.

Why Developers Need an RFC 4180 Compliant JSON to CSV Converter

Plain-text CSV remains the universal interchange format between REST APIs, relational databases (COPY FROM in PostgreSQL, BigQuery loads), Python pandas pipelines, and desktop spreadsheet editors. Yet converting real-world JSON into valid CSV quickly breaks naive string-join scripts whenever text fields contain commas, double quotes, line breaks, or international UTF-8 characters.

This browser-based JSON to CSV converter implements strict RFC 4180 escaping alongside hierarchical dot-notation flattening. Every record is parsed in local browser memory—never uploaded to a remote server, as guaranteed in our privacy policy—so you can safely transform production customer exports, webhook logs, and financial ledgers.

Fixing Garbled Characters in Excel with UTF-8 BOM

One of the most frustrating spreadsheet bugs happens when you double-click a valid UTF-8 .csv file in Microsoft Excel on Windows or macOS and discover that names like Müller, São Paulo, 東京, or 深圳 render as unreadable mojibake (Müller). That happens because Excel assumes legacy ANSI/Windows-1252 encoding unless the file begins with a 3-byte UTF-8 Byte Order Mark (EF BB BF / \uFEFF).

Our JSON to CSV converter enables Include UTF-8 BOM by default for file downloads:

  • With UTF-8 BOM Checked: Microsoft Excel immediately recognizes UTF-8 encoding upon double-click, displaying European accents, CJK characters, and currency symbols cleanly.
  • Without UTF-8 BOM: Ideal when feeding CSV files into strict command-line parsers or older UNIX ingestion scripts that expect byte 0 to be the first column header character.

Choosing the Right Delimiter: Comma vs Semicolon vs Tab

Regional operating system settings change how desktop spreadsheets split CSV columns. In North America and the UK, numbers use a period decimal (14.50) and CSV files separate columns with a comma (,). Across Germany, France, Spain, Brazil, and much of continental Europe, numbers use a comma decimal (14,50), so Microsoft Excel expects a semicolon (;) delimiter when opening CSV files directly.

Using the Field delimiter selector in our JSON to CSV converter, you can switch instantly between:

  1. Comma (,): Standard RFC 4180 CSV output for US/UK Excel, databases, and cloud warehouses.
  2. Semicolon (;): Opens cleanly into separate columns on European Windows and macOS Excel installations without triggering the Text Import Wizard.
  3. Tab (\t): Generates a .tsv file ideal for copying to your clipboard and pasting directly into an open Excel or Google Sheets selection.

When you need multi-type native workbooks with pre-sized column widths or legacy binary .xls files instead of plain text, switch to our JSON to XLS workbench. Or if you need to pull structured grids out of Word reports, open our Word to Excel converter.

Delimiter & Encoding Compatibility Matrix

Match delimiter and BOM settings to your target spreadsheet application or ingestion pipeline.

Target EnvironmentRecommended DelimiterUTF-8 BOM SettingOutput Extension
Microsoft Excel (US / UK / APAC)Comma (,)Enabled (On).csv
Microsoft Excel (EU / LATAM)Semicolon (;)Enabled (On).csv
Direct Clipboard Paste into SheetTab (\t)Not needed for clipboard.tsv
PostgreSQL COPY / pandas / CLIComma (,)Optional (Off for strict CLI).csv

JSON to CSV Converter FAQ

Key details on UTF-8 BOM encoding, regional Excel delimiters, and RFC 4180 quoting rules.

Why does Excel show garbled symbols when opening UTF-8 CSV files, and how does this JSON to CSV converter fix it?

Enable the Include UTF-8 BOM checkbox (checked by default) before clicking Download .CSV. Prepending the 3-byte UTF-8 Byte Order Mark instructs Microsoft Excel to read international accents, CJK characters, and symbols as UTF-8 instead of legacy ANSI encoding.

When should I choose a semicolon (;) instead of a comma (,) in the JSON to CSV converter?

In countries where a comma is the decimal separator (such as Germany, France, Italy, and Brazil), desktop Excel expects CSV fields to be separated by semicolons (;). Selecting Semicolon (;) lets European Excel installations split columns automatically on double-click.

How are embedded commas, quotes, and line breaks escaped in the generated CSV?

Any field containing the active delimiter, a newline (\r or \n), or a double quote (") is automatically wrapped in double quotes, and internal double quotes are escaped by doubling them ("") per RFC 4180.

Does this JSON to CSV converter upload my JSON payload anywhere?

No. All JSON parsing, dot-notation flattening, and Blob generation run strictly inside your browser memory. Your data never touches an external server.