Invalid TSV Example: Extra Tab Breaks Column Count
Check that every non-empty TSV row has the same number of tab-separated fields as the first row.
🔒 Processed entirely in your browser — nothing you enter here is ever uploaded.
The result appears on this page after you run the tool. Nothing you enter is uploaded.
Result
About this tool
This page opens the TSV validator preloaded with an inventory export where one product name — "Laptop Stand Aluminum" — got an extra tab typed in the middle instead of a space, splitting it into two fields. The validator runs on load, so the failure shown below is a live, real check, not a staged screenshot.
This is a very ordinary way real TSV files break: when data is typed or pasted by hand, a stray tab keystroke inside what should be a single product name or description silently adds an extra column to that one row. Because TSV has no visual delimiter the way a comma does, an extra tab is easy to miss just by looking at the text — the row simply has one more field than the header defines.
The result panel below points to the exact row where the count breaks. Compare it against the valid-inventory-tsv preset linked here to see the same three columns without the stray tab, and the stray-quote-tsv preset for a different, equally common TSV failure mode.
Example. A header name and score separated by a tab, then Ada and 10 separated by a tab, passes as Data syntax is valid! Total parsed rows: 2, Columns: 2. A second row with no tab fails the column count on that line.
Limit. Quotes toggle a mode and are not an RFC 4180 escape. A blank line in the middle is a row. The page does not turn the TSV into a table or JSON.