100% Client-Side Privacy
Adawaty Pro • adawaty-pro.com
48+ Offline Client-Side Converters & Technical Guides
Home / Legacy Data & Business / TSV to CSV / XLSX / JSON
Read Technical Guides →

TSV to CSV / XLSX / JSON

Convert Tab-Separated Values (.tsv) to CSV, Excel, or JSON — 100% private client-side processing.

100% Client-Side JS

Active Converter

Smart Auto-Fix:
1. Source File(s) or Paste Input: No file selected
2. Live Output (Editable):
IANA Tab-Separated Values (text/tab-separated-values)

TSV to CSV / Excel / JSON: Converting Tab-Delimited Feeds Without Column Shift

Technical Anatomy of the .TSV Specification

Registered with IANA as text/tab-separated-values, a TSV file separates fields using the horizontal tab byte (0x09, written \t) and separates records using line feeds (0x0A) or CRLF pairs (0x0D 0x0A). Unlike RFC 4180 CSV—which requires complex double-quote escaping whenever a cell contains a comma or newline—strict TSV forbids raw tabs inside cell values, allowing single-pass tokenization at line boundaries.

When translating .tsv into .csv, .xlsx, or .json, the converter splits each record on 0x09, wraps any field containing commas or quotes in RFC 4180 double quotes for CSV safety, or constructs keyed JSON objects using the header row as property names. Exporting to native .xlsx via SheetJS eliminates Excel's notorious single-column import bug.

Raw Tab-Delimited Input vs. Keyed JSON Output

# Input: Amazon Seller / Bioinformatics Export (catalog.tsv)
sku	product_name	price_eur	origin
SKU-901	Wireless Sensor, Gen 2	49,90	DE
SKU-902	USB-C Logic Analyzer	89,00	NL

# Converted .JSON Output:
[
  { "sku": "SKU-901", "product_name": "Wireless Sensor, Gen 2", "price_eur": "49,90", "origin": "DE" },
  { "sku": "SKU-902", "product_name": "USB-C Logic Analyzer", "price_eur": "89,00", "origin": "NL" }
]

Real-World Software & Hardware Ecosystem

Data engineers and e-commerce operators encounter .tsv exports daily from Amazon Seller Central (inventory and FBA settlement reports), Google Merchant Center product feeds, NCBI / Ensembl genomic annotation tables, PostgreSQL COPY dumps, R / Bioconductor, and Apache Hive queries.

Troubleshooting & Edge Cases

  • Trailing Empty Tabs: Database exports frequently append extra trailing \t characters on sparse rows, creating blank unnamed columns in JSON. Use the Interactive Table view to remove empty columns cleanly.
  • Gene Names & SKUs Auto-Converted to Dates in Excel: Classic Excel famously turns gene symbols like MARCH1 or SKUs like 04-12 into calendar dates when opening raw CSV. Inspecting or exporting directly to JSON preserves exact string values.
  • Spaces Mistaken for Tabs: Copy-pasting a TSV through some chat apps or code editors converts tabs (0x09) into 4 spaces (0x20). Always upload the original .tsv file directly from disk so tab bytes remain intact.

TSV vs. CSV Delimiter Safety Comparison

ScenarioComma CSVTab TSV (0x09)
European Decimals (14,95)Requires quoting or shifts columnsSafe without quotes
Product Titles with CommasMust wrap in "..."Zero escaping needed
Double-Click in ExcelAuto-splits (locale-dependent)Often jams into Col A → export .XLSX

Unix Command-Line TSV Verification

# Verify true tab characters (^I) and column counts per row in Linux/macOS:
head -n 5 catalog.tsv | cat -A
awk -F'	' '{print NF}' catalog.tsv | sort -u

Frequently Asked Questions

Why do bioinformatics and European datasets prefer TSV (0x09 Tab) over CSV?

Because commas appear constantly inside street addresses, product descriptions, and European decimal numbers (like 14,95 EUR). Using the horizontal tab character (ASCII 0x09) as a delimiter eliminates quoting ambiguity and makes command-line parsing with awk or cut dramatically simpler.

What happens if a TSV cell contains literal quotes or embedded commas when converting to JSON?

Converting TSV to JSON maps row 1 column names to object keys and preserves commas, semicolons, and Unicode text inside properly escaped JSON strings without breaking column boundaries.

Why does Microsoft Excel merge all TSV columns into Column A when I double-click a .tsv file?

Excel binds .csv to its automatic comma splitter, but often opens .tsv files as unparsed plain text unless you run the Text Import Wizard. Converting directly to native .XLSX writes real cell coordinates so every column opens cleanly on the first click.

Can I filter rows or drop unused metadata columns from a large TSV before saving to Excel?

Yes. Switch the output preview to Table mode, type a keyword in the filter box, click × on any column header you do not need, and export the trimmed dataset directly to .XLSX.