JSON to CSV Converter

The JSON to CSV Converter is a free online tool that convert json arrays or objects to csv with custom delimiters, header toggle, nested-key flattening, preview table, and one-click .csv download.. It runs entirely in your browser with no installation or sign-up needed.

An array of objects, an object wrapping an array under a "data" key, or a single object (converted to one row). Array items must be objects.

Enable Flatten nested objects to convert nested keys to dot notation (user.name). Disable to keep nested values as JSON strings inside a single cell.

Fields are wrapped in double quotes only when they contain the delimiter, a quote, or a newline. Inner quotes are doubled per RFC 4180. Toggle wrap-all to force quoting everywhere.

Yes, the JSON to CSV Converter is 100% free with no registration, no hidden fees, and no usage limits. All processing happens locally in your browser, ensuring complete privacy.

Absolutely. The JSON to CSV Converter processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the JSON to CSV Converter is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the JSON to CSV Converter in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The JSON to CSV Converter works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

The converter builds the column list from the union of every key found across all your objects, in first-seen order. So if the first record has "id" and "name" and a later one adds "email", the CSV gets all three columns and the records that lack "email" simply get an empty cell there. This means inconsistent API responses, where some items carry extra optional fields, still line up into a clean, rectangular table instead of misaligning. Values stay matched to their correct header regardless of the order keys appear inside each object, so a field placed last in one record still drops into the right column. The row and column counts shown above the output confirm the final shape before you export, and the live preview table lets you eyeball the alignment. Paste your mixed-shape JSON and the tool reconciles the columns automatically, giving every record the same header row with no manual cleanup.

A CSV cell holds a single value, so an array nested inside a record has no fixed column shape to spread across. Because of that, this tool always serialises an inner array back to a compact JSON string and places it in one cell — for example a "tags" field becomes ["a","b"] inside that column, even when flattening is enabled. This is intentional: flattening only expands nested objects into dot-notation columns like address.city, while arrays are kept intact as text so no data is lost. If you need each array element on its own row instead, restructure the JSON first so each element becomes its own object, then convert. The same applies to deeply nested structures: objects flatten into dot-notation columns while any array at any level stays as a JSON string. Paste your JSON and check the preview table to see exactly how array fields are rendered, then copy or download once the layout looks right.

Comma is the default and the most widely supported separator, but it causes problems in some situations. In many European locales the comma is the decimal mark, so spreadsheets there expect a semicolon between fields — choosing semicolon makes the file open correctly in those regional Excel installs. The tab delimiter produces TSV, which pastes cleanly straight into a spreadsheet cell without a separate import step and avoids comma collisions entirely. Pipe is handy when your data itself contains commas and semicolons and you want a separator that almost never appears in real values. Whichever you pick, the tool still quotes any field that contains that delimiter, so the output stays valid and parseable. The chosen delimiter also shows on a badge beside the output so you always know what separates the columns. Pick the delimiter from the options above to match your target program or locale, then download the .csv.

Yes. The output follows RFC 4180, the de facto CSV standard, so the downloaded converted.csv file opens in Excel, Google Sheets, Numbers, and database import tools without manual fixing. Fields containing a delimiter, quote, or line break are wrapped in double quotes and inner quotes are doubled, which is exactly what these programs expect when parsing. If commas in your numbers cause Excel to split columns in your locale, switch the delimiter to semicolon before exporting. For Google Sheets, you can also use File then Import, or simply copy the output and paste it into a sheet. Keep the header row toggle on so the first line becomes your column titles, or turn it off when you only need the raw data rows. The file is saved with a UTF-8 character set, so accented names and non-Latin text survive the round trip into your spreadsheet. Paste your JSON, confirm the preview table, then copy or download the spreadsheet-ready file.

Nothing breaks. If the text cannot be parsed, the tool shows an "Invalid JSON" message with the underlying reason rather than producing a corrupt file, so you can find the stray comma or unclosed bracket. If the JSON parses but an array item is a string, number, array, or null instead of an object, it stops and tells you the exact index that is invalid, since every item must be an object to become a row. An empty array produces a clear "nothing to convert" notice, and a single object is accepted but flagged as being treated as one row. These guards mean you always get either a correct CSV or a precise explanation, never a silently broken export that fails later. The messages appear inline right under the input as you type, so you can fix and re-paste without losing your place. Paste your data and let the notices guide you to a clean, valid result.