Add your TSV file
Drop one or more .tsv files onto the converter above, or browse for them. They load into browser memory only. Nothing is uploaded, so there is no size-based pricing and no server queue.
Restructuring .tsv data as .arrow changes the serialization without touching the values themselves. Free, private, and validated: the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Restructuring .tsv data as .arrow changes the serialization without touching the values themselves. A .tsv file stores a table as plain text with one record per line and a tab character between columns. It is CSV's stricter sibling: because literal tabs almost never occur inside data, most TSV files need no quoting rules at all.
An .arrow file is an Apache Arrow IPC file: a columnar table written in exactly the memory layout Arrow uses at runtime, so a reader can point at the bytes and start working without parsing or copying anything. The file format is the in-memory format with a header, a footer and a little framing, which is the entire idea. For this route the practical draw is zero-copy reads: opening a file costs almost nothing regardless of its size and types are exact and preserved, including nulls, timestamps and nested structures, balanced against uncompressed by default, so files are substantially larger than Parquet, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .tsv, a single stray tab inside a value silently shifts every following column. Switching to .arrow buys you zero-copy reads: opening a file costs almost nothing regardless of its size, which is why it is the better fit for handing a table between Python, R, Java and JavaScript without a serialization step. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | TSV table (.tsv) | Apache Arrow IPC (.arrow) |
|---|---|---|
| Format type | Text-based: characters and structure, so there is no visual quality loss | Lossless: every pixel or sample is preserved exactly |
| How it stores data | one record per newline-terminated line, with fields split on the tab character (U+0009) | data is columnar: each column is one contiguous buffer plus an optional validity bitmap, so a scan touches only the columns it needs |
| Strongest at | database dumps, PostgreSQL's COPY and MySQL's SELECT INTO OUTFILE default to tabs | handing a table between Python, R, Java and JavaScript without a serialization step |
| Weak spot | a single stray tab inside a value silently shifts every following column | uncompressed by default, so files are substantially larger than Parquet |
Drop one or more .tsv files onto the converter above, or browse for them. They load into browser memory only. Nothing is uploaded, so there is no size-based pricing and no server queue.
Select .arrow in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if ARROW is selectable, the route is real and validated.
Press Convert. The restructuring is plain local parsing, and your data is never posted to a server for processing.
Each result is checked before the download unlocks: where ARROW has a signature or a structure this converter can read back, the file is re-opened and parsed, and where it has neither, the check is that a non-empty file of the declared type came back. A result that fails is reported as an error instead of being offered for download, and outputs keep the original filename with the .arrow extension.
There is no visual quality to lose, because tsv is text-oriented and arrow is lossless-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Yes. The .tsv file is processed inside your browser tab and never uploaded. The restructuring is plain local parsing, and your data is never posted to a server for processing. Close the tab and the file is gone from memory.
Arrow has first-party implementations for C++, Java, Python (pyarrow), R, Go, Rust, C#, Julia and JavaScript, and Pandas, Polars, DuckDB, Spark and BigQuery all speak it. Novus Convert reads .arrow files in the browser with the official JavaScript implementation and writes JSON, CSV, XLSX or Feather; because Feather v2 IS the Arrow IPC file format, arrow-to-feather is a renaming of the same bytes rather than a re-encoding.
It depends on the content: data is columnar: each column is one contiguous buffer plus an optional validity bitmap, so a scan touches only the columns it needs. Convert one representative file first and compare before batch-processing a large set.