Inspect a tab-separated table without opening a spreadsheet
Paste TSV and choose View table. The first parsed record supplies column names. The result shows the number of data records and columns, followed by a table preview. Up to 100 data records and 200 characters per cell are displayed; the complete parsed table remains available in the JSON detail and download.
Example: commas are ordinary data
The sample contains two data records and two columns. Ada's note is one,two; the comma stays inside that note because tabs, not commas, separate fields. No number or date inference occurs, so leading zeros and textual identifiers remain strings.
Supported quoted TSV dialect
A double quote at the beginning of a field opens a quoted field. Inside it, doubled quotes represent one literal quote, and tabs or line breaks remain part of the cell. After the closing quote, only a tab, record ending or end of input is accepted. A quote inside an unquoted field is rejected. Some TSV producers treat quotes differently, so confirm that this explicit dialect matches your source.
LF, CRLF and standalone CR end records outside quoted fields. A final record ending does not add a blank record; an extra blank record is still data and must match the header width. Browser textareas can normalize pasted line endings to LF before parsing. Unique, nonempty headers are required; header-only input is accepted with zero data records.
Read the export correctly
The JSON download is an array of string arrays including the header as its first array. It is a parsed representation, not the original TSV bytes. It retains values but not original quote spelling or record separators. Use TSV to CSV Converter when the destination requires comma-separated text.
Input and output limits
The page supports up to 200,000 input characters, 200 columns and 10,000 data records, with a two-million-character output limit. Processing stays in this browser. Editing source text or options clears prior results and download links. No source file is overwritten.
A leading byte-order mark is rejected rather than retained in the first field. Unpaired surrogate code units are rejected because a UTF-8 download could not preserve them.





