YAML to TSV Converter

TSV is the format a spreadsheet accepts from the clipboard without an import dialog: copy tab-separated text, paste it into a cell, and every value lands in its own column. This converter produces exactly that from YAML, so a list of records or a block of settings goes from an editor into Excel, Google Sheets or Numbers in one paste.

Typical uses are reviewing a YAML data file with a colleague who lives in spreadsheets, checking a list of feature flags or translations for gaps, and moving records into a tool that reads tab-separated input, such as many database import screens and command-line utilities.

Parsing happens in your browser tab. Nothing is uploaded, and nothing remains once you close it.

Paste the YAML, open a .yaml file or drop one onto the input, then press Run or Ctrl/Cmd+Enter. Copy puts the TSV on your clipboard for pasting straight into a sheet; Download saves it as a .tsv file.

The YAML is read in full: nesting, lists, comments, quoted strings and multi-line text all work. A top-level list of mappings becomes one row per item, a mapping that only wraps a list uses the list, and any other mapping becomes a single row. Headers are all the keys found, in first-seen order.

Values containing a tab, a line break or a quote are quoted so columns stay aligned. Lists and mappings nested inside a record are written as compact JSON in their cell.

Invalid YAML stops the conversion with the line and the reason, rather than producing a partial table. The usual causes are a tab character used for indentation, a key repeated in one mapping, or a line that is indented inconsistently.

yes, no, on and off are kept as text, following YAML 1.2, and values with leading zeros stay text too. When you paste into a spreadsheet, though, the spreadsheet may still turn 01234 into 1234 or a date-like value into a date; format those columns as text first if that matters.

Anchors, aliases, tags and files with several --- documents are not converted; the error names the feature so you know what to remove or expand by hand.

After pasting, check that the header row sits above the right columns and that the number of rows matches the number of items in your YAML list.

Look at any cell that holds JSON: it marks a nested value. If you need it split into columns, restructure the YAML or go through JSON first.

For official or financial use, compare the result with the source YAML before relying on it.