TSV to YAML
Convert a table into a YAML sequence of mappings — one list item per row, keyed by the header. That's the shape YAML is genuinely good for as data: a list of services, users, test cases, or config entries that a human will read and edit. Values are quoted where YAML needs them quoted, which is more often than people expect.
How to use
- Paste or drop the TSV.
- Decide about coercion — off keeps every value a string, on lets numbers and booleans become YAML scalars.
- Copy or download as
.yaml.
YAML's famous type surprises
This is the format where yes, no, on, off, and y historically parse as booleans, where 1.10 becomes 1.1, where a leading zero can mean octal, and where a value like NO as a country code turns into false. YAML 1.2 narrowed some of this, but plenty of parsers still implement 1.1 behaviour.
The protection is quoting, which is why string values are quoted here when their content could be misread. With coercion off, everything stays a quoted string and nothing surprises you. Turn it on only when you want real numbers and booleans and you've looked at the columns involved.
Where the output goes
Kubernetes manifests, CI configuration, Ansible inventories, OpenAPI fragments, application config. For anything machine-to-machine, JSON is a better target — YAML's value is that people edit it by hand. The reverse conversion, for flat lists, is YAML → TSV.
FAQ
Can it produce nested YAML?
No — one flat mapping per row. A header name containing a dot stays a literal key with a dot in it rather than becoming a nested path.
Are multi-line values handled?
A value containing a newline is emitted as a quoted string with escapes rather than a block scalar. Valid, if less pretty than | style.
Is the indentation configurable?
No — two spaces, which is the near-universal convention and what every linter expects.
Why are so many values quoted?
Because unquoted YAML scalars are typed by pattern, and quoting is the only way to guarantee a value survives as the text you wrote. It's verbose and it's correct.
Privacy
100% client-side. No upload. See the privacy policy.