About these CSV utilities
CSV looks simple until you encounter quoted fields, embedded commas, or regional exports from finance teams. This workspace helps you visually align columns for code review, shrink files back to strict delimiter-only rows, and move between CSV and JSON when APIs demand structured objects.
The delimiter field defaults to comma but accepts semicolons or tabs when you work with European spreadsheets or TSV dumps. Parsing follows a standard quoted-field state machine so newline characters inside quotes are preserved.
When teams use this page
- Beautifying a vendor CSV before attaching it to a ticket.
- Converting spreadsheet exports to JSON arrays for unit tests.
- Generating CSV fixtures from JSON objects returned by staging APIs.
How to use this page
- Paste CSV into the editor (include a header row for JSON conversion).
- Set the delimiter character if you are not using commas.
- Choose Format (columns) for monospace-aligned columns, or Minify to remove padding.
- Use CSV → JSON when the first row should become object keys.
- Use JSON → CSV when the left editor contains an array of homogeneous objects.
Data handling
All transformations execute locally. Large CSV files may stress the tab; trim columns or sample rows if performance drops.
Frequently asked questions
- Why is my JSON → CSV empty?
- Ensure the payload is an array of objects (or a single object). Arrays of strings are not supported by this generator.
- How are missing keys handled?
- The exporter uses the union of keys across rows. Missing values become blank cells.
- Does CSV → JSON support nested objects?
- No. Each row becomes a flat object with string values. Normalize nested structures before converting.
- Is data uploaded?
- No. Everything stays in your browser session.