◆ File conversionFREE

Engineering ships YAML.
Translators just want Excel.

YAML⇄XLSXNested keys, sequences, placeholders — all preserved · refill never drifts, hierarchy never collapses.
Converter· Local processing
Drop your .yaml here
or pick from your device · your file never leaves your browser
01 · what this tool actually does for you

Flatten a YAML language file into an Excel sheet a translator can edit, then load it straight back to YAML — nested keys, sequences, placeholders, escapes and key order all preserved, refill never drifts, hierarchy never collapses. Not generic YAML-to-table — the one step a localization workflow actually needs.

Files never leave your deviceIn-browser · zero upload · NDA-friendly
Deterministic conversionThe same input always yields the same output
Lossless round-tripYAML→Excel→YAML keeps every key
02 · two formats, one round-trip

YAML and Excel are each good at different things

This conversion exists so engineers and translators each use the tool they're comfortable with — without losing anything in between.

i18n YAML.yaml

The language file back-end, Rails, Flutter and CI teams use: indented key-value pairs, often nested (menu.start.label), with sequences and plural branches (items[0]), values carrying placeholders ({name}, %{count}, %s). Clean for engineers — not something to hand-edit row by row.

Excel.xlsx

The interface translators, reviewers and vendors find most natural: one row per string, key and translation side by side, easy to filter, bulk-edit and annotate. The catch: raw Excel flattens the nesting, treats {name} as plain text, and an unquoted NO or 42 gets re-typed into a boolean or number — and then it won't load back into the codebase.

What this tool guards is exactly that "won't load back": on export it carries nested keys, sequence indices, placeholders and escapes faithfully into the sheet, and keeps every scalar's type — so a quoted "42" stays a string and an unquoted NO never flips to a boolean; on import it refills by key and restores the hierarchy. A few YAML constructs can't survive a spreadsheet and are reported, never silently dropped: comments, anchors / aliases / merge keys (expanded to their values), multi-document streams (only the first is converted) and block-scalar styling (the value is kept, the byte-exact style is not).

03 · common questions

You're probably wondering

Will my file be uploaded?+
No. Parsing and conversion run entirely in your browser (a Web Worker handles large files); the file never leaves your machine and never touches a server. That's a hard requirement for NDA-bound localization work, so the tool is built fully client-side.
Does converting YAML to Excel lose anything?+
The essentials don't: nested keys, sequence indices, placeholders, escapes, scalar types and empty values are all carried by rule, and the round-trip is faithful. A few constructs that can't map — comments, anchors/aliases/merge keys, extra documents in a stream, and block-scalar styling — are reported at export, never silently dropped. Every conversion comes with a fidelity report.
Converting Excel back to YAML — will the hierarchy, order or types break?+
No. Refill anchors by key, restoring flattened paths to their original nesting; reordering rows in Excel doesn't matter. A Type column keeps each scalar's type, so a quoted "42" stays a string and an unquoted yes never becomes a boolean. Placeholders are re-checked against the source and mismatches flagged; rows you added with no matching key are listed for review.
What about YAML's yes/no, and an unquoted NO turning into a boolean?+
This tool follows the modern (YAML 1.2 core / js-yaml v4) rules: unquoted yes, no, on, off and NO are read as strings, not booleans — and they stay strings on the way back. Quoted "42", "true" and "null" stay strings too; they're re-quoted on export so they never re-parse as a number, boolean or null. The old YAML 1.1 "Norway problem" does not bite here.
Does it support nesting, sequences and plurals, and is it free?+
It supports nested keys, sequences and plural branches. This tier is completely free, no account, no usage limits — a client-side tool has no server cost. The exact YAML dialect and edge cases are described in the tool's format notes.
04 · who made this / why

Built by someone who's done this work

This isn't a thin wrapper over a large model, and it isn't an open-source library reskinned. It comes from years of game-localization frontline work and the pile of "nobody notices until it breaks" details that come with it.

Engineering hands over a YAML; the translator only wants to edit in Excel — the format loss in between shouldn't be a human's job to absorb.

Hand a language file to a vendor and nine times out of ten it comes back with placeholders "auto-corrected" away, an unquoted NO flipped to false, nesting flattened, plural branches misaligned — and it lights up red back in the codebase. We hit every one of those, so the tool guards them by default: key-anchored refill, type-preserving columns, placeholder checks, hierarchy restored.

Free, fully local, instant. It's one step in a workflow, not a platform — but it comes from a place that genuinely understands localization.