🔄 Dev

JSON ↔ CSV Converter

Convert data between JSON (array of objects) and CSV bidirectionally. Paste and convert instantly in the browser, no file upload needed.

JSON → CSV CSV → JSON Pretty JSON

Input (JSON) Output (CSV)

How to use?

If you're in JSON → CSV mode, paste a JSON array of objects. Going the other way, in CSV → JSON mode, paste a CSV whose first line is the header. Everything gets converted on the spot, right inside the browser.

Convert between JSON and CSV both ways

JSON is the language of APIs and CSV is the language of spreadsheets. Crossing those two worlds becomes routine, whether you're exporting data from a system into Excel or turning a table into a format code can read. This converter handles the translation in both directions in the same moment.

Paste a JSON array of objects and the matching CSV comes back, with headers taken from the keys. Paste a CSV and the structured JSON shows up. Good for prepping data before an import, opening an API response in a spreadsheet, or converting a report without firing up any heavy program.

None of it goes through a server. Everything happens in the browser, with no file uploads, and your data never leaves the device, which keeps it safe to convert even sensitive information.

Frequently asked questions

What happens to nested objects and arrays inside the JSON?

They are not flattened. Every field is written out as plain text, so a nested object lands in the cell as [object Object] and an array arrives as its items joined by commas, with the structure gone. Flatten the JSON to a single level of simple values before converting, or repair the affected columns later in the spreadsheet.

Can I use a semicolon instead of a comma as the separator?

No, the separator is fixed as a comma in both directions, following RFC 4180. If Excel in a European or Brazilian locale drops the whole row into one column, use Data and then Text to Columns and pick comma. Values holding a comma, a quote mark or a line break come out wrapped in quotes, with inner quotes doubled.

Why do numbers come out as text when converting CSV to JSON?

Every cell is kept as a string, with no type guessing. A 30 in an age column arrives as text rather than a number, and that is exactly what protects postcodes, phone numbers and any code with leading zeros. Cast the types in your own application if the target needs real numbers. Note as well that a quoted field spanning several lines is not supported: each line of the file becomes one record.

Related Tools

📊

CSV Validator & Viewer

Validate, parse and visualize CSV data in table format. Automatically detects delimiters (comma, semicolon or tab) and highlights formatting errors.

🪜

JSON Flatten / Unflatten

Flatten a nested JSON into dot-notation keys (e.g. user.address.city) and rebuild the reverse path. Useful to export to CSV, generate .env files or compare configs. Everything in your browser.

🗂️

HTML Table Generator

Paste CSV, TSV or semicolon-separated data and instantly generate an HTML table with thead, tbody and live preview.

⚙️

VS Code tasks.json Generator

Build a VS Code tasks.json with label, type, command, group and problemMatcher. Includes configurable default shell.

🎮

Discord Embed Builder

Build Discord embeds (title, description, color, fields, footer, thumbnail) and export the JSON ready for webhook. Includes preview. Everything in your browser.

📊

OpenTelemetry Span JSON Generator

Produce an OpenTelemetry span as JSON with a 32-hex traceId and a 16-hex spanId from the crypto random source, or keep a valid traceId you paste in.