Skip to content
JSON to CSV

Free online JSON to Excel converter

Convert JSON to Excel in your browser

Turn a JSON array, object, or NDJSON export into a spreadsheet that opens directly in Microsoft Excel. This converter writes a UTF-8 byte-order mark so accents survive, uses Windows line endings, and neutralises formula cells — the three things that usually go wrong when JSON data meets Excel. Free, no signup, and your data never leaves your device.

  • Opens in Excel directly
  • Accents survive (BOM)
  • Formula-safe
  • No upload
  • 100% free

Accepts a JSON array, a single object, or NDJSON (one JSON object per line). You can also drop a file anywhere on this panel.

Advanced options

How to convert JSON to Excel

Three steps, entirely in your browser — your JSON never leaves your device.

  1. Paste JSON or add your files

    Paste a JSON array, a single object, or NDJSON into the box, or add up to 20 .json files (25 MB each) — drag them onto the panel, browse for them, or copy them in File Explorer and press Ctrl+V (⌘V on a Mac) anywhere on the page. The converter parses the data instantly and shows a spreadsheet preview.

  2. Keep the Excel-friendly defaults

    This page pre-selects what Excel expects: a UTF-8 byte-order mark so accented characters display correctly, Windows (CRLF) line endings, and formula neutralisation so cells starting with = + - @ are treated as text. If your regional Excel splits everything into one column, switch the delimiter to semicolon.

  3. Download and open in Excel

    Click Download CSV and double-click the file — Excel opens it directly with each JSON key as a column. In a hurry, Copy CSV puts the whole table on your clipboard for a paste into an open sheet. To keep formatting, formulas, or multiple sheets afterwards, use File → Save As and pick Excel Workbook (.xlsx).

Technical specifications

Input formatsJSON array, single JSON object, NDJSON / JSON Lines
OutputExcel-ready CSV — UTF-8 with BOM, CRLF line endings, RFC 4180 quoting
Opens inMicrosoft Excel (double-click), Google Sheets, LibreOffice, Numbers
DelimitersComma by default; semicolon for European Excel locales, tab, or pipe
Excel safetyFormula neutralisation for cells starting with = + - @ (pre-enabled)
Nested dataFlatten to dot-notation columns, join, or keep as JSON
Batch limitUp to 20 files, 25 MB each — download all as one ZIP
Processing location100% in your browser — no upload, works offline
PriceFree — no signup, no watermark, no row limit

Frequently asked questions

How do I convert JSON to Excel?
Paste your JSON above or drop a .json file onto the panel. The tool turns each record into a row and each key into a column, and downloads a UTF-8 CSV file that Excel opens with a double-click — no import wizard needed. Everything runs in your browser, so nothing is uploaded.
Can I paste a file instead of picking one?
Yes — copy a .json file in File Explorer or Finder and press Ctrl+V (⌘V on a Mac) with this page open; the file loads without touching the upload box. A whole selection copied at once loads together, newest at the top of the queue, and each pasted file is listed as pasted-1.json, pasted-2.json, because the clipboard usually strips the original name. Screenshots and other non-JSON clipboard content are ignored.
Does this create a real .xlsx file?
It produces an Excel-ready CSV, which Excel opens natively like any workbook — double-click it and you see rows and columns. CSV cannot hold formatting, formulas, or multiple sheets; if you need those, open the downloaded file in Excel and use File → Save As → Excel Workbook (.xlsx). For plain tabular data the CSV route is faster and works in Excel, Google Sheets, and Numbers alike.
Why do accented characters look broken when I open CSV in Excel?
Excel only detects UTF-8 encoding when the file starts with a byte-order mark (BOM); without it, names like Müller or José turn into garbled text. This converter writes the BOM by default, so accents, umlauts, and non-Latin scripts display correctly the moment Excel opens the file.
Excel put all my data into one column. How do I fix that?
Excel picks the expected separator from your Windows regional settings. In many European locales it expects a semicolon, so a comma-separated file lands in a single column. Switch the delimiter option above to Semicolon, download again, and Excel will split the columns correctly.
How is nested JSON shown in Excel?
Nested objects are flattened into dot-notation columns, so {"address": {"city": "London"}} becomes a column named address.city. Arrays can expand into indexed columns (tags.0, tags.1), join into one cell, or stay as raw JSON — pick whichever reads best in your spreadsheet.
Will Excel mangle leading zeros or long numbers?
If you double-click the CSV, Excel applies its automatic type detection, which can drop leading zeros (post codes, phone numbers) and round IDs longer than 15 digits. To keep such values exact, use Excel's Data → From Text/CSV import instead and set those columns to Text. The CSV itself always contains the exact original values.
What is formula neutralisation and why is it on here?
A value that starts with = + - or @ is executed by Excel as a formula, which malicious data can abuse (CSV injection). Because this page targets Excel, the option is pre-enabled: such cells are prefixed with an apostrophe, which Excel hides while treating the value as plain text. You can switch it off under Advanced options.
Is my data uploaded anywhere?
No. Parsing and conversion run locally in your browser tab with JavaScript. Your JSON is never sent to a server, logged, or stored, and the converter keeps working offline once the page has loaded.

Why Excel needs more than a plain CSV export

Excel opens CSV files, but with three quirks a generic exporter ignores. It only recognises UTF-8 when the file starts with a byte-order mark — otherwise every accented name arrives garbled. It expects Windows (CRLF) line endings. And it executes any cell that starts with =, +, -, or @ as a formula, which makes untrusted data a real risk. This page pre-configures all three for you, so the downloaded file opens in Excel correctly on the first try.

The converter itself is the same engine as the JSON to CSV converter: it flattens nested objects into dot-notation columns, expands or joins arrays, unions the keys of every record into a consistent column set, and quotes the output per RFC 4180. If you need the data for a database import or a script rather than a spreadsheet, use the homepage and switch the options freely — it is the identical tool with neutral defaults. And if you have already exported a sheet to CSV and need it as JSON instead, the CSV to JSON converter handles that direction, semicolon files included.

Because everything runs client-side, nothing is uploaded and nothing is stored. You can convert confidential exports, disconnect from the network, and keep working — the page is fully functional offline once it has loaded.

Your data never leaves your browser

Conversion runs locally in JavaScript using your browser's own JSON parser. We do not upload, store, or analyse your data — no records, keys, or values are sent anywhere. The tool keeps working even if you disconnect from the internet after the page loads.