Convert TSV to Excel Online

Quick Guide: Converting TSV to Excel Online

To convert a TSV file to Excel: (1) drag the .tsv file into the upload box above, (2) select XLS (Excel 97-2003) or XLSX (Excel 2007+), (3) click Download converted file. Tab characters become column boundaries, newlines become row boundaries, the first line stays as the header row. Files up to 50 MB, no signup, no email.

TSV vs CSV: When TSV Wins

Both TSV and CSV store tabular data as plain text, one row per line. The only difference is the field separator: TSV uses a tab character, CSV uses a comma. That small difference matters in three real scenarios:

• Fields contain commas. Numerical data with thousands separators (1,234,567), addresses, names with titles, free-form text — all are unambiguous in TSV but require quoting in CSV.
• European locales. Many European countries use a comma as the decimal separator (3,14). CSV files in those locales often switch to semicolons, creating yet another dialect. TSV sidesteps the whole mess.
• Scientific and bioinformatics tools. BLAST results, FASTA-related metadata, R data frames written with write.table(), pandas to_csv(sep="\t") outputs — the de facto convention is TSV because the data fields routinely contain commas, parentheses, and quotation marks.

Real Use Cases for TSV to Excel

Genomics and Bioinformatics Output

Tools like BLAST, samtools, BEDTools, and most NGS pipelines emit results as TSV. Researchers who need to filter, sort, chart, or share with non-technical collaborators want it in Excel. The converter handles BLAST tabular output (-outfmt 6) directly: query ID, subject ID, percent identity, alignment length, mismatches, gap opens, query and subject start/end, e-value, bit score — each lands in its own column.

R and Python Data Frame Exports

R's write.table(df, "out.tsv", sep="\t") and pandas' df.to_csv("out.tsv", sep="\t") produce TSV files that downstream Excel users typically need to convert. The online converter preserves column types as much as Excel allows (numbers stay numeric, dates need column formatting in Excel after import).

Database Exports

MySQL's SELECT … INTO OUTFILE and PostgreSQL's COPY default to tab-separated output. Hand the resulting .tsv to Excel users without writing custom parsers.

Analytics and BI Tool Exports

Google Analytics, Mixpanel, Amplitude, and Looker often offer TSV alongside CSV for big exports because tab parsing is more reliable on free-form event-name text fields. Convert to Excel for ad-hoc analysis without setting up a BI tool seat.

Log and Webserver Data

Apache, nginx, and CDN logs are commonly post-processed into TSV by ETL pipelines (URLs and user-agent strings contain commas all the time). The Excel version is what auditors and product managers actually look at.

How the Conversion Works

The converter performs three steps:

1. Encoding detection. Reads the BOM (if present) and falls back to UTF-8 by default, with auto-detection for Latin-1 / Windows-1252.
2. Delimiter parsing. Splits each line on the tab character. Quoted fields (surrounded by double quotes) are parsed as a single value even if they contain embedded tabs or newlines.
3. Excel write-out. Each parsed cell is written to the corresponding XLS or XLSX cell. Numeric strings that look like numbers (no leading zeros, valid decimal separator) are written as numbers; everything else stays as text.

XLS vs XLSX: Which to Choose

Most TSV files now exceed 65,536 rows (genomics tables, log dumps, analytics exports), so XLSX is the right default. Use XLS only when the recipient is on an old Excel install.

Online Converter vs Desktop Total Excel Converter

For one-off conversions the online tool is the fastest. For nightly genomics pipelines, batch jobs over thousands of TSV exports, or sensitive data that must stay on-prem, install the desktop Total Excel Converter.

Common Issues and Fixes

• All data ends up in column A. The source is not actually tab-separated — usually it's CSV with the wrong extension, or uses spaces. Open in a text editor; if you see commas instead of tabs, use the CSV to Excel converter instead.
• Numbers shown as text in Excel. The source has leading zeros, embedded thousands separators, or different decimal markers. Select the column in Excel and apply a number format, or use Text to Columns with the right locale.
• Garbled accented characters. The source TSV is not UTF-8. Re-save it as UTF-8 in your text editor (Notepad++, VS Code, BBEdit all support this), then re-upload.
• Dates parsed wrong. Excel uses your local date format. ISO 8601 dates (2026-05-07) are typically interpreted correctly; ambiguous formats (05/07/2026) may be read as US (May 7) or EU (July 5). Use ISO format in the source TSV when possible.
• File too large. Online cap is 50 MB. Either split the TSV into smaller chunks or use the desktop converter for unlimited size.

• Command line support
• API integration
• 24/7 offline availability
• Enterprise licensing