TSV to YAML Converter
FileFlip converts TSV to YAML entirely inside your browser, using the text engine compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert a TSV file to YAML?#
- Drop your TSV file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to YAML and the conversion starts on its own. FileFlip downloads nothing at all, because everything it needs is already built into your browser, then runs the text engine on your own machine.
- Save the YAML file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting TSV to YAML lose quality?#
No. Converting TSV to YAML writes the data out again without discarding any of it, so nothing that was in the TSV file is lost on the way. What changes is the size of the file, not what is inside it.
Is it safe to convert TSV files online?#
Yes, because nothing is uploaded. FileFlip converts TSV files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What TSV to YAML actually does to the file#
Converting TSV to YAML runs on the text engine, downloads nothing at all, because everything it needs is already built into your browser, writes the data out again without discarding any of it, and drops comments and value types.
| Engine | the text engine |
|---|---|
| Conversion path | One step: TSV → YAML |
| Downloaded to your browser | Nothing. Your browser already has everything this conversion needs |
| Quality | Lossless |
| You get back | One file |
| Where it runs | On the page's own thread, so a very large file will make the tab wait |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Comments | Dropped | The target format has nowhere to put it. |
| Value types | Dropped | The target format has nowhere to put it. |
Worth knowing before you start:
- this conversion runs on the page's own thread, so a large file will freeze the tab while it works
What is a TSV file?#
A TSV file holds a table as one line of text per row, with values separated by tab characters instead of the commas CSV uses.
Use TSV instead of CSV when the data itself might contain commas, since tabs are rare enough in real text that quoting is usually unnecessary.
Convert TSV to CSV when the destination tool defaults to comma parsing and doesn't offer a delimiter option.
What is a YAML file?#
A YAML file holds structured data written with indentation instead of brackets, extending JSON's data model with comments, references and multi-line strings meant to be edited by a person.
Choose YAML for configuration a person edits by hand and wants to comment, like CI pipelines or Kubernetes manifests.
Convert YAML to JSON when a program needs to consume the file and comments and anchors aren't needed, since most JSON libraries won't read YAML directly.
TSV to YAML questions people ask#
What's the difference between TSV and CSV?
TSV separates values with a tab character instead of the comma CSV uses. Because tabs almost never appear inside ordinary text, TSV files usually need no quoting at all, while CSV has to wrap any value containing a comma in double quotes.
Is there an official TSV specification?
No. TSV has only an informal IANA media type registration, text/tab-separated-values, submitted by the University of Minnesota's Internet Gopher team in 1993, and it leaves details like how to escape a literal tab inside a value unspecified. Different tools handle that case differently, which is the same gap CSV has with RFC 4180, just with less documentation around it.
Does converting TSV to CSV lose any data?
Not usually, as long as none of the values already contain a comma. If a value does contain a comma, the converter has to wrap it in double quotes to keep the row from splitting incorrectly, which TSV's tab delimiter never required in the first place.
Why does YAML turn NO into false?
YAML's core schema treats a set of unquoted words, including no, off and n, as boolean false, and yes, on and y as true. This is called the Norway problem because a two-letter country code or an abbreviation typed without quotes gets silently converted to a boolean. Wrapping the value in quotes, so it reads as the string NO rather than the word no, avoids it.