TSV to YAML Converter

This tool takes tab-separated rows, the format you get when you copy a block of cells from Excel, Google Sheets, or Numbers, and rewrites them as a YAML list of records. It treats the first row as field names and turns every following row into a mapping under those keys, so a flat export becomes a readable sequence of entries rather than a wall of tabs.

It is most useful for developers and data prep work: turning a quick spreadsheet of seed data, lookup tables, or environment values into YAML fixtures, sample payloads, or config-shaped snippets that read well in a pull request or a docs page. Because tabs survive copy-paste from sheets without the comma-escaping headaches of CSV, it is a low-friction way to move a small table from a spreadsheet into a YAML-friendly context.

It also helps non-developers and admins who have been handed a TSV and simply want to read it. YAML's indented key-value layout is easier to scan line by line than raw columns, which makes it handy for reviewing a short dataset, sharing a tidy excerpt, or eyeballing what a sheet actually contains before passing it on.

The flow is direct: paste your TSV or load a .tsv file, and the tool converts in your browser, then lets you copy the result or download it. Everything runs locally on the page, so nothing is uploaded and nothing is retained once you close the tab. Parsing is quote-aware and handles Windows, Mac, and Unix line endings, and double-quoted fields that contain tabs or newlines are kept intact.

Output is a YAML sequence where each data row is a mapping, with header names as keys. If a header cell is blank, that column is named column_1, column_2, and so on by position, and rows with fewer cells than the header simply get empty values for the missing fields, so ragged rows still produce valid structure.

Be aware of what it does not do. It does not infer types: numbers, booleans, and dates are all written as plain strings exactly as typed, and values are emitted unquoted without YAML escaping. It produces a flat list of single-level records only, with no nested objects, anchors, comments, or multi-document output, and it does not validate against any schema.

The most common surprise is that the first row is always treated as headers. If your TSV has no header line, the real first record is consumed as field names and every other row inherits them, so add a header row first if your data does not have one.

The second is the missing escaping. Because values are written bare, a cell containing a colon followed by a space, a leading dash, a hash, or a leading or trailing space can change how a strict YAML parser reads the line, and a value that looks like a number or true/false will be interpreted as that type even though it came from text. If those values matter, wrap or quote them yourself in the output.

Also watch your delimiter and your copy source. Data that is actually comma-separated, or a spreadsheet selection where some cells were turned into tabs but others were not, will misalign columns. Spaces used for alignment are not tabs, and a stray blank line or trailing tab can shift fields, so confirm the input is genuinely tab-delimited before trusting the result.

Skim the output top to bottom: confirm the keys match your intended headers, that the number of records equals your data rows minus the header, and that no column landed under a placeholder name like column_2, which signals a blank header cell. Spot-check a few rows against the source to make sure values sit under the right keys and that no field spilled because of an unexpected tab or line break.

Pay attention to values that need to stay textual, such as IDs with leading zeros, postal codes, version strings, or anything containing a colon, hash, or leading dash, and quote them in the output if a downstream parser would otherwise reinterpret them. If you plan to feed the YAML into another tool, run it through that tool's loader or a YAML linter once to catch anything the bare formatting left ambiguous.

For anything official, financial, or legal, treat this as a formatting step, not a source of truth. Verify the converted content by hand against the original TSV before using it in records or filings, since the tool reproduces what you paste without checking correctness or meaning.