Skip to content
AZ Tools

CSV Inspector

Auto-detects the delimiter from the first line (comma, tab, semicolon, pipe) and parses with proper RFC 4180 quoting. Each column gets a quick type inference (number, boolean, date, string) plus a count of empty cells, the number of distinct values, and a sample. Full-row duplicates are surfaced as a separate metric.

Rows

5

Cols

6

Duplicates

0

Columns
ColumnTypeEmptyUniqueSample
idnumber051
namestring04Alice
emailstring14alice@example.com
agenumber1430
signupdate042024-01-15
verifiedboolean02true

Everything runs in your browser — your data never leaves the device.

How to use

  1. Drop a CSV / TSV file or paste data directly into the box.
  2. Toggle the header-row checkbox to match your data.
  3. Read the row / column / duplicate cards, then the per-column type table.

Frequently asked questions

What counts as a duplicate?
An exact match across all fields. A row where one cell differs by a single character is not a duplicate. Use a dedicated dedupe step in your pipeline if you need fuzzy matching.
How accurate is the type inference?
Best-effort. A column passes as `number` only if every non-empty cell parses as a number, and similarly for boolean and ISO-ish dates. Mixed columns fall back to `string` rather than guessing.
The delimiter was detected wrong — why?
Detection reads the first line only. A file whose first line is a title rather than a header, or whose header contains commas inside quoted text, can tip the guess towards the wrong character. Pasting a few representative data lines instead of the whole file is usually enough to get a correct read.
Why does one row have far more columns than the rest?
Almost always an unbalanced quote somewhere above it. A single stray double quote makes the parser treat everything that follows as one long quoted field until it meets the next quote, so rows merge and field counts go wild. Fix the quote rather than the row that looks broken — the damage starts earlier in the file.

Guides on this topic

Related tools