Invalid TSV Example: Stray Quote Character in a Field
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 a product name reads 24" Monitor — using a literal double-quote character as the inch symbol. The validator runs the instant the page loads, so the error shown below reflects a real, live check of this exact text.
This is a subtler failure than a stray tab: a single double-quote character anywhere in a field is treated as the start of a quoted value, and since no matching closing quote follows on that line, the parser reports the field as an unterminated quoted string rather than guessing what was meant. Product names and measurements that use the inch symbol ("), the ditto mark, or a straight quote for feet/inches are a common real-world source of this exact bug in TSV exports.
The result panel below identifies the exact row where the unmatched quote appears. The fix is usually to remove or escape the stray quote character in the source data before re-exporting — compare this preset against valid-inventory-tsv to see the same row shape without it.
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.