JSON to CSV Converter

JSON (JavaScript Object Notation) is a nested, hierarchical data format built for APIs and structured application data. It stores key-value pairs inside curly braces and supports arrays, nested objects, and multiple data types. CSV (Comma-Separated Values) is a flat, table-based format where each row is a record and each column is a field, separated by a delimiter (usually a comma). CSV works everywhere: Excel, Google Sheets, database imports, CRM uploads, and analytics platforms. JSON works for data transfer between systems, configuration files, and anything where structure matters more than readability. If your data has nested levels (like a product with variants, each variant with SKUs), JSON is the right export format. If you need to open the data in a spreadsheet, filter rows, run formulas, or hand it to a non-technical teammate, CSV is the answer. Our converter takes JSON of any structure, flattens nested keys with dot notation, handles arrays, and outputs clean CSV.

Yes, and you'll need to decide how to handle nested objects and arrays before the conversion makes sense. Paste or upload your JSON into the JSON or CSV input field. Pick JSON to CSV in the Mode dropdown. Toggle Flatten nested keys with dot notation on (the default) to turn nested structures into flat columns with dot names. Pick a Delimiter: comma for standard CSV, semicolon for European Excel (which already uses commas for decimals), tab for TSV, or pipe for systems that already have commas in the data. Hit convert. You get a live table preview showing the first 20 rows, plus a download button for the full CSV. If your JSON includes arrays, we offer two modes: join array items into one cell with semicolon separators, or split each item into its own row. The whole conversion runs client-side, so nothing uploads to a server.

Paste your JSON into the tool, or upload a .json file, or paste a URL that returns JSON (we fetch it for you). Select JSON to CSV in Mode. Check that Flatten nested keys with dot notation is toggled on if your JSON has more than one level of nesting. If it's off, only the top level becomes columns, and everything nested inside gets stringified into one ugly cell. Pick your Delimiter based on where you'll use the CSV: comma for Excel US, semicolon for Excel Europe, tab for database imports, pipe for systems where your data already contains commas. Hit convert. The output pane shows a table preview (first 20 rows, scrollable) so you can check the structure before downloading. Click Download CSV when it looks right. For reverse conversion (CSV back to JSON), flip the Mode to CSV to JSON. This is the fastest way to prep API response data for spreadsheet analysis.

Convert the JSON to CSV first, then open the CSV in Excel or import it directly. Paste or upload your JSON into the JSON or CSV input field. Set Mode to JSON to CSV. Turn on Flatten nested keys to ensure nested data doesn't get lumped into one unreadable cell. Pick comma as your Delimiter (the Excel default). Hit convert. Download the CSV. Open Excel, go to Data tab, click Get Data, then From Text/CSV, select your downloaded file, and Excel auto-detects the delimiter and loads the table. If your JSON has date fields or numbers stored as strings, Excel might misinterpret them. Check the column types in the import preview and change any that look wrong before clicking Load. Once it's in Excel, you can sort, filter, run pivot tables, or save it as .xlsx. If you skip the CSV step, Excel treats raw JSON as unstructured text.

Nested keys get flattened into dot-notation column names when Flatten nested keys is toggled on (the default). A JSON object with order, customer, and nested name fields becomes three columns with names like order.id and order.customer.name. Each level of nesting adds one more dot. This keeps the structure readable in a flat table and prevents data loss. If you turn off flattening, the tool only converts the top level into columns, and nested objects get stringified into a single cell as raw JSON. That's fine for debugging or cases where you plan to parse the nested data separately, but it breaks filtering and formulas in spreadsheets. Arrays pose a separate problem. If your JSON has an array field with multiple tags, you can choose to join the items into one cell or split them into separate rows (one row per tag, duplicating the rest of the row's data). Splitting is useful for sales line items or multi-category posts.

Yes, and it's faster than writing a manual parser. Flip the Mode dropdown from JSON to CSV to CSV to JSON. Paste your CSV into the input field, or upload a .csv file. The tool auto-detects your delimiter (comma, semicolon, tab, pipe) from the first few rows. If detection fails or you're using a non-standard delimiter, pick it manually in the Delimiter dropdown. Hit convert. You get JSON output in the pane below: an array of objects where each object is one row, and each key is a column header. Copy the JSON or download it as a .json file. If your CSV has a header row, we use those names as keys. If it doesn't, we generate numeric keys. For nested JSON output (turn a flattened CSV with dot-notation column names back into a hierarchical structure), toggle Flatten nested keys off and the tool reconstructs objects from any column name containing dots.

Excel expects a specific delimiter (usually comma) and encoding (UTF-8 or Windows-1252), and if the CSV uses something else, columns collapse, special characters turn into garbage, or everything lumps into one cell. Three common causes. First, delimiter mismatch: European Excel uses semicolon as the default delimiter because commas are already the decimal separator in many locales. If your CSV uses commas but Excel expects semicolons, everything stays in column A. Fix by changing Delimiter to semicolon before downloading, or use Excel's Data, then From Text/CSV import and manually set comma. Second, encoding issues: CSVs default to UTF-8, but older Excel versions expect Windows-1252. Any emoji, accented character, or CJK script breaks. Fix by saving the CSV as UTF-8 with BOM (byte-order mark) when exporting. Third, embedded commas: if any field contains a comma and the tool doesn't wrap that field in quotes, Excel treats the comma as a new column. Our tool auto-quotes fields that contain the delimiter.

Both work, but the output structure differs. If your JSON is an array of objects (the most common API response format), each object becomes one row in the CSV, and the keys become column headers. Example: an array of two people with name and age fields converts to two rows, two columns (name, age). This is the ideal input shape for conversion because it maps cleanly to a table. If your JSON is a single object with nested fields, the tool treats the top-level keys as column names and the values as one row. Example: a post object with title and nested author name becomes one row with columns title and author.name (if flattening is on). If your JSON is a nested array (an array inside an array), the tool either joins inner arrays into one cell or explodes them into separate rows, depending on your array-handling toggle. Most data exports, API responses, and database dumps return arrays of objects.

JSON is better for structured, hierarchical data that needs to preserve types and relationships. CSV is better for flat, tabular data you want to open in a spreadsheet, run SQL on, or hand to a non-technical user. JSON supports nesting (objects inside objects), arrays, booleans, nulls, and numeric precision without quotes. CSV supports none of that. Everything in a CSV is a string unless the consuming application infers types on import. JSON is the standard for APIs, config files, and data pipelines between systems. CSV is the standard for analytics exports, CRM imports, and anything where the end user is Excel or Google Sheets. Use JSON when you control both ends of the pipeline and structure matters. Use CSV when you need maximum compatibility, simplicity, and human readability. Convert between them when you need to analyze API data in a spreadsheet or push spreadsheet rows into a structured system.

Use comma for US and international Excel, semicolon for European Excel, tab for database imports, and pipe when your data already contains commas and semicolons. The delimiter is the character that separates one field from the next. Most tools and systems default to comma because that's the C in CSV (Comma-Separated Values). But commas appear inside data too: addresses, formatted numbers, natural-language text. If your data contains commas, you have two options. First, wrap affected fields in double quotes so the comma inside doesn't break the structure. Our tool does this automatically. Second, switch to a delimiter that doesn't appear in your data: semicolon, tab, or pipe. Semicolon is the standard in much of Europe because commas are already used as decimal separators. Tab (TSV) works well for database imports and scripts. Pipe is the fallback when commas, semicolons, and tabs all appear in your data. Pick the delimiter in the Delimiter dropdown before hitting convert.