YAML to TSV Converter

This converter is aimed at people who keep small amounts of configuration or metadata in YAML and need it as a tab-separated row they can drop into a spreadsheet or a tab-aware editor. Typical fits are reviewing a service config, a CI variable block, a front-matter snippet, or an app settings file as columns rather than indented text, so a key like timeout or replicas lines up under its own header.

It suits developers comparing two YAML configs side by side once each is pasted into a sheet, and office or admin users who want a key/value block in a form they can sort, filter, or hand to someone who lives in spreadsheets. Because TSV pastes cleanly into Excel, Google Sheets, and Numbers without comma-quoting surprises, it is a practical bridge for ad hoc data prep and quick sharing.

It is built for short, flat content, not large data pipelines. If your YAML is a tidy list of settings, this gives you a header line of field names and one matching line of values that is easy to scan or archive alongside other notes.

The flow is direct: paste your YAML or load a file, run the conversion, then copy the result or download it as a .tsv. Everything runs locally in your browser tab, so nothing is uploaded and nothing is retained once the tab is closed.

The parser reads line by line, matching simple key: value pairs. It coerces values sensibly: true and false become booleans, null becomes null, plain numbers become numbers, and surrounding single or double quotes are stripped from strings. Comment lines and blank lines are skipped. The output is one header row of keys and one data row of values, with tab, newline, or quote characters wrapped in quotes so columns stay aligned.

What it does not do is full YAML. Nested mappings, sequences and bullet lists, multi-line block scalars, anchors and aliases, and multiple documents separated by --- are not interpreted as structure; indentation is not read as nesting. Treat it as a flat key/value tool, not a general YAML engine.

The most common mistake is feeding it nested or list-based YAML and expecting columns per item. A nested block will not expand into rows, and list entries under a key are not split out — only top-level key: value lines are captured, so deeper data is silently dropped rather than flagged.

A few formatting details matter. A value containing a # may be read as part of the value rather than an inline comment, and a key that itself contains a colon or hash can be mis-split. Quoted strings have their outer quotes removed, so a deliberately quoted number or boolean will be converted to that type. The result is a single data row, not one row per record, so this is not the tool for tabular datasets.

If your source is genuinely structured YAML, convert it to JSON first or use a full YAML parser, then bring the flattened result here. Keeping input to a clean, flat block of settings avoids almost all of these pitfalls.

Open the output and confirm the header row lists every key you expected and the value row sits directly beneath the right columns. Spot-check that numbers, true/false, and empty fields landed as intended, and look for any key that quietly disappeared — usually a sign it was nested, a list, or had unusual punctuation. Paste it into your spreadsheet to verify the tabs split into separate cells rather than collapsing into one.

Watch for values that lost meaning during coercion, such as a version string like 1.10 that became a number, or a quoted entry whose quotes were stripped. If a field needs to stay an exact string, confirm it reads the way you need after import.

For anything official, financial, or legal, verify the converted values manually against the original YAML before using or sharing them. This tool does no semantic validation, so a human read-through is the safeguard for records that have to be exactly right.