Translate YAML locale files with AI
Import Rails-style YAML locale files with nested keys, let AI translate them with your glossary and context, review and export valid YAML.
Used by Ruby on Rails i18n and many configuration-driven frameworks.
What a YAML file actually holds
Rails popularised the convention of keeping translations in YAML, nested under a top-level locale key. Symfony, Jekyll, Hugo and a great many configuration-driven tools followed. The format reads beautifully and is unusually easy to corrupt, because in YAML whitespace is syntax.
Translation makes that worse, not better: translated strings are longer, more likely to contain colons and quotes, and more likely to need multi-line formatting — all of which interact with YAML's indentation rules in ways that are invisible until something fails to load.
.yml, .yaml
en:
welcome:
title: "Welcome back!"
buttons:
save: "Save changes"What goes wrong when YAML files are translated badly
These are the failures that reach production, because none of them look like errors until they do.
Indentation shifts change the key path
Two extra spaces silently move a key under a different parent. The file still parses; your application just cannot find the string any more.
Colons in translated text break the line
A colon followed by a space is how YAML separates key from value. A translation containing one has to be quoted, or the line stops meaning what it did in English.
The locale root does not get renamed
The top-level key is the language code. Copy en.yml to it.yml without changing the root and Rails loads the file as English.
Interpolations are treated as words
%{name} carries a value. Translate the word inside the braces and Rails raises a missing-interpolation error at render time.
How GetTranslated handles it
Import your YAML file
AI translates with your glossary
Review and approve every string
Export and ship
Want to see it on your own file first?
Paste a YAML file into the free tool and get the translated version back straight away — no account, no email address.
Open the free YAML translatorFrequently asked questions
Is the locale root handled?
Yes. Files nested under a single locale key are read correctly, and the export is written back under the same structure.
Are quoting and escaping handled?
Yes. Exported values are quoted whenever the content requires it, so translations containing colons, quotes or leading symbols stay valid YAML.
Does it work with Symfony and Hugo YAML?
Yes. Any nested key/value YAML file is supported — the Rails locale root is recognised, not required.
500 keys free forever. No credit card.