What's the difference vs CSV?
TSV uses a tab character between fields instead of a comma. Tabs are unlikely to appear inside data values, so TSV avoids most quoting hassles. CSV is more common for archives and spreadsheet downloads; TSV is the default when you copy a range out of Excel or Google Sheets and paste into a text editor.
Can I paste from Excel?
Yes — that is the primary use case. Selecting a range in Excel, Google Sheets, Numbers, or LibreOffice and pressing Ctrl+C puts tab-separated text on the clipboard. Paste it here and you get a sortable, filterable preview without a spreadsheet open.
How are quoted fields handled?
Fields wrapped in double quotes can contain tabs, newlines, and embedded quotes (escaped as ""). Most TSV producers do not quote since tabs rarely occur in values, but the parser still handles them correctly when present.
Why use TSV instead of CSV?
TSV is friendlier for data containing commas (financial figures, addresses, prose). It also round-trips cleanly through Excel's clipboard. CSV remains better when you need a single-byte delimiter that cannot appear in source code or terminals (some terminals interpret tabs).
Can I export as CSV?
Yes — Copy as CSV serialises the current sorted/filtered rows with comma delimiters, RFC 4180 quoting, and CRLF-safe newlines. Useful for sending the data to a system that requires CSV.
Does it auto-detect the delimiter?
No — this tool is TSV-only by design (always splits on tab). For comma, semicolon, or pipe input, use the CSV to Table tool instead, which auto-detects the delimiter.
Is the data sent anywhere?
No. Parsing, sorting, filtering, and copying all run in JavaScript inside your browser. No request leaves the page when you load a sample, paste, sort, or filter.
How big a file can it handle?
Tens of thousands of rows render fine in modern browsers but the DOM gets sluggish past 50,000 rows. For very large datasets, filter or chunk before pasting, or use a streaming tool like xsv on the command line.