Skip to content
TechSolve

CSV Converter & Viewer

View CSV or TSV as a table and convert it to JSON, NDJSON, Markdown, HTML or SQL inserts — or JSON back to CSV. Handles quoted fields and embedded newlines; Excel-safe UTF-8 download.

CSV Converter & Viewer

How to use CSV Converter & Viewer

  1. 1Paste or drop a CSV, TSV or JSON file — the direction and delimiter are detected.
  2. 2Pick the output: JSON, NDJSON, Markdown, HTML, SQL or CSV/TSV, and tune its options.
  3. 3Check the table preview, then copy or download the result.

What it does

  • Correct RFC 4180 parsing: quoted fields, doubled quotes, newlines inside fields, CRLF and BOM
  • Auto-detects the delimiter — comma, semicolon, tab or pipe — with a manual override
  • Table preview with a header-row toggle (first 500 rows for big files)
  • Convert to JSON (objects or arrays), NDJSON, Markdown table, HTML table or SQL INSERTs
  • JSON → CSV too: one level flattened over the union of keys, nested values as JSON
  • CSV/TSV output with your delimiter and quote-all; downloads add a UTF-8 BOM for Excel

FAQ

Why does Excel break Thai text in CSV files, and how does this tool avoid it?
Excel assumes a legacy encoding unless the file starts with a UTF-8 byte-order mark. CSV and TSV files downloaded from this tool start with that BOM, so Thai and other non-Latin text opens correctly with a double-click.
Can it handle commas and line breaks inside a field?
Yes. The parser follows RFC 4180: a field wrapped in quotes may contain the delimiter, doubled quotes ("") and even line breaks, so a cell like an address spanning two lines converts to one JSON value with the newline preserved.
Should I convert to JSON objects or arrays?
Objects (one {column: value} per row) are what most APIs and scripts expect, and they need a header row. Arrays keep every row as a plain list, which suits spreadsheets without headers or when column order matters. NDJSON writes one object per line — the format logging pipelines and jq handle best.
How do the SQL inserts escape values?
Column and table names are double-quoted with internal quotes doubled, and string values are single-quoted with ' doubled — the standard SQL escape. With Types on, numeric fields are written unquoted, true/false become TRUE/FALSE and empty fields become NULL.
How does JSON to CSV handle nested objects?
One level is flattened: the columns are the union of every object's top-level keys, in first-seen order, and a nested object or array is written as its JSON text in that cell. Rows missing a key get an empty cell.

You might also like