JSON to CSV for Excel users: open API dumps without losing accents

You paste an API response into Notepad, then need columns in Excel for a stakeholder. Manual copy fails past twenty fields. A JSON to CSV converter turns an array of objects into rows with headers from the keys. Toolsy JSON to CSV runs in your browser: paste JSON, pick comma, semicolon, or TAB, then download or copy. The download includes a UTF-8 BOM so Excel on Windows usually keeps accents intact. This guide is for Excel users and analysts, not for reversing CSV back into fixtures. For that direction, use CSV to JSON for API mocks and CSV to JSON.

Why Excel users still need JSON to CSV

Product APIs speak JSON. Finance and ops live in spreadsheets. The handoff is a CSV someone can double-click. Power Query can read JSON, but many teammates only want File → Open on a .csv.

API dumps also arrive in Slack as pretty-printed blobs. Converting once beats asking engineering for a one-off export every Friday. Keep the converter for ad hoc checks. Automate in code when the same dump lands nightly.

Prepare the JSON before you convert

Garbage keys become garbage columns. Nested objects and mixed types are the usual traps.

Prefer an array of objects with the same keys on every row. A single object works for one row. An array of arrays works when you already think in positional columns. Toolsy accepts those shapes; array-of-objects is still the happiest path for Excel headers.

Arrays of objects vs nested trees

Flatten nested fields before paste when you need address.city as its own column. Deep trees often stringify into a single cell that nobody can filter. If the API nests user.profile.name, ask for a flat export or flatten in a quick script first.

Mixed types and empty fields

Keep IDs as strings when leading zeros matter. JSON numbers become Excel numbers and drop those zeros on open. Empty fields may become blank cells; that is usually fine for filters. Decide whether null should look empty before you hand the sheet to finance.

Walkthrough: JSON to CSV in the browser

1. Copy a JSON array from your API client or log file.
2. Open JSON to CSV.
3. Paste the JSON and pick comma for US Excel, semicolon for many EU locales, or TAB for TSV.
4. Preview the table mentally: headers should match keys you recognize.
5. Download the CSV and open it in Excel.
6. Spot-check accents, dates, and ID columns on three rows.

Nothing uploads. Conversion stays on your device. There is no daily cap on this page. An account is only for favorites and paid plans elsewhere.

Delimiters and regional Excel

US Excel expects commas. Many European Excels expect semicolons when the OS locale uses comma as a decimal mark. If every row lands in column A, re-export with the other delimiter or use Excel’s Text Import wizard. TAB exports play well with Sheets paste.

UTF-8 BOM and accents

Toolsy’s download includes a UTF-8 BOM so Excel usually detects UTF-8 and keeps characters like café or München. If accents still break, confirm you opened the downloaded file rather than a re-saved copy from an editor that stripped the BOM. See also Invisible characters breaking your CSV when columns shift for hidden reasons.

Nested JSON and large dumps

Huge pretty-printed responses slow the browser tab. Trim to the array you need before paste. Paginated APIs should be merged into one array in your client, then converted once.

When to flatten in code instead

Nightly warehouse extracts belong in a scripted job, not in a paste box. Use Python or Node when the same nested schema repeats every sprint. Keep the browser tool for stakeholder emergencies and QA samples.

When CSV is the wrong answer

Excel also auto-converts some strings into dates and scientific notation. If your next pain is broken dates after CSV open, plan for a dedicated CSV→Excel path in a later guide rather than fighting cell formats by hand every time. For now, format ID columns as text after open when Excel invents dates from codes like 10-11.

Related jobs next to JSON to CSV

Fixtures and mocks still start from spreadsheets more often than from JSON. Use CSV to JSON for API mocks when the sheet is the source of truth. Developers wiring OCR or Markdown intake can keep Developer integrations: complete guide nearby; that hub does not replace tabular converters.

UUID columns in dumps sometimes need generation for test rows. UUID v4 vs v7 for databases covers ID strategy when you fabricate companion fixtures.

Privacy and limits for tabular tools

JSON to CSV and CSV to JSON run in the browser. Toolsy does not see the paste. That differs from PDF and OCR tools that upload briefly for processing. Read Privacy and document safety: complete guide when the same laptop also handles client PDFs.

Still treat API dumps as sensitive. A customer email column in a CSV on a shared desktop is a leak even when the converter never touched a server.

Common Excel failures after conversion

Columns stacked into one cell usually mean the wrong delimiter. Accent mojibake usually means a missing UTF-8 read path. Dates that were order codes usually mean Excel’s auto-detect; prefix with a tab or format as text. Nested JSON stuck in one cell means you needed a flatten step first.

Re-run the converter after you fix the JSON shape. Do not “fix” a broken CSV with Find & Replace for an hour when the source keys were wrong.

Frequently asked questions

How do I convert JSON to CSV for Excel?

Paste an array of objects into JSON to CSV, choose a delimiter, and download the file. Open the CSV in Excel and check three rows for headers and accents. Prefer comma in the US and semicolon when your Excel locale expects it.

Will Excel open JSON to CSV output with accents?

Yes in the common case. Toolsy’s download includes a UTF-8 BOM so Excel on Windows usually detects UTF-8. If characters still break, reopen via Data → From Text/CSV and force UTF-8. Avoid re-saving through editors that strip the BOM.

What JSON shape works best?

An array of objects with stable keys on every row. A single object becomes one data row. Arrays of arrays work when columns are positional. Deeply nested objects often need flattening before CSV is useful.

JSON to CSV or CSV to JSON?

Use JSON to CSV when the API or log is the source and Excel is the destination. Use CSV to JSON when a spreadsheet feeds mocks or scripts. See CSV to JSON for API mocks for the reverse workflow.

Does JSON to CSV upload my data?

No. Conversion runs in your browser. Nothing is sent to a Toolsy server for this tool. That differs from OCR and many PDF tools that upload briefly for processing.

Which delimiter should I pick?

Comma for typical US Excel. Semicolon for many EU Excel installs. TAB when you want TSV for Sheets or data tools. If everything lands in column A, switch delimiter and download again.

Can I convert nested JSON with one click?

Only if you accept nested objects as JSON text inside a cell, or if you flatten first. Spreadsheets want flat columns for filters and pivots. Flatten address.city-style fields before paste when analysis matters.

Is there a daily limit on Toolsy JSON to CSV?

No daily limit on this page. Accounts are optional for favorites and paid products elsewhere. Paste size is still bounded by what your browser can handle comfortably.

Why do some ID values become dates in Excel?

Excel guesses formats aggressively. Codes like 3-4 or 10-11 become dates. Format those columns as text after open, or prefix values in JSON as strings Excel will not coerce. A later CSV→Excel guide covers date pitfalls in more depth.

How do invisible characters break my CSV?

Zero-width spaces and odd quotes shift columns or break imports. If headers look duplicated or splits fail, read Invisible characters breaking your CSV and clean the source JSON strings before converting again.

For the reverse direction and fixture hygiene, keep CSV to JSON for API mocks next to this guide. When several exports must become one workbook, clean columns first with Data cleaning before you merge CSV files.