Category guide

CSV Tools

CSV looks simple until a field contains a delimiter, a quote, or a line break. View a table, check its row shape, normalize its formatting, or convert it to JSON, YAML, or XML. Local processing lets you inspect an export without uploading the file.

Choose the right tool

CSV Viewer

Use the table view to scan headers and rows and find a value in a large export.

CSV Validator

Use the validator when an import rejects a file or rows appear to have different numbers of fields.

CSV Formatter

Use the formatter to normalize quoting and line endings after choosing the right delimiter.

CSV to JSON

Use the converter when application code needs one object per row with header names as keys.

All tools

Example workflow: check a customer export

  1. Open the export in CSV Viewer and confirm that the header names and a few sampled records align.
  2. Run CSV Validator with the file's actual delimiter to catch empty or duplicate headers and uneven rows.
  3. Convert to JSON only after checking how empty cells and text values should be interpreted by the destination.

Before you use the result

The CSV parser expects a nonempty, unique header and the same field count in every data row. Converted JSON and YAML cells remain strings; dates, booleans, and numbers need deliberate type conversion in your application.

Read the header before the data

A CSV file often has no separate schema. The first row supplies names, and every following row should match those names. A misplaced delimiter may shift the rest of a row without making the file obviously unreadable. The CSV Viewer makes such shifts easier to spot. If an import fails, CSV Validator checks row width and header quality before you investigate application rules.

This site supports comma, semicolon, and tab delimiters. Quoted fields can contain a delimiter or line break, and doubled quotes represent a quote inside a field. Choose the delimiter that matches the source export. The CSV Formatter can normalize quoting, but it cannot infer whether a comma in an unquoted field was intended as data or a separator.

Conversion limits

CSV to JSON creates objects using header names. It deliberately leaves cell values as strings, so 00123 can remain an identifier instead of silently becoming 123. The same caution applies when converting to YAML or XML. If your destination expects dates or numbers, define those rules in the application and test representative rows, including empty cells and quoted delimiters.