JSON ↔ CSV Converter

// HOW TO USE

1. 01Pick a direction. Nested objects flatten with dot-notation keys (e.g. user.email); arrays serialize as JSON strings inside cells.
2. 02Choose a delimiter and whether headers are present. Values that contain the delimiter, quotes, or newlines are quoted/escaped per RFC 4180.
3. 03Click Download to save the output as a file — the file is built locally in your browser.

// WHEN TO USE

Use this when you need tabular test data from a JSON API response or fixture — for spreadsheet review, data-driven test seeding, or import into a test management tool. Convert a JSON array of objects to CSV to feed into Cypress fixtures, Playwright data tables, or any tool that accepts delimited files. Use the reverse (CSV → JSON) when a QA team maintains test cases in spreadsheets and you need a JSON fixture from them.

// WHAT BUGS THIS FINDS

• Delimiter collision in field values

  A field value containing commas is not quoted, causing it to be parsed as multiple columns by the consumer — Convert with the correct delimiter and confirm the output escapes field values per RFC 4180.

• Nested object flattening discrepancy

  A nested key user.address.city appears as a column header after dot-notation flattening — if the consumer expects a flat key 'city', the mismatch silently misaligns data. Convert and review the header row.

• Array field serialized as string

  A JSON array inside an object cell is serialized as a JSON string literal in the CSV — a consumer trying to parse it as a native array will fail. Convert and confirm whether the downstream tool handles this encoding.

• Encoding and header row issues

  A CSV opened in Excel may show garbled characters or treat the first row as data — Convert surfaces the raw output so you can verify encoding and header presence before importing into test data tools.

// QA USE CASES