Describe the job, not the file layout
Describe the job, not the layout. It reads the tree and tells you which branches it will touch.
Translate a whole YAML file at once. Say what you need in plain English. The keys, tags and delimiters stay where they are.
Drop your YAML file here
Up to 2 MB, five files a day. Nothing to install, no account.
Describe the job, not the layout. It reads the tree and tells you which branches it will touch.
A glossary keeps the same English word becoming the same French word, this file and the next.
Lite for a large config-adjacent catalogue, Standard for user-facing flows. Chosen per upload.
Key hierarchy and key order are preserved, and only the leaf values change. The file is written back as clean, valid YAML: comments are not kept, and indentation and quoting are normalised.
AI Glot reads the file and separates the text from the structure. It then tells you how much there is to translate, before anything runs.
No column mapping and no configuration screen. Write what you need, then read the plan it produced. If it misread you, say so and it plans again.
Translate into German and Spanish. Keep product names in English, use our glossary, and make the copy sound natural for e-commerce.
One file comes back, translated. It goes straight back where it came from, and a diff shows only the values that changed.
Four jobs that come up again and again. Each one is one upload and one sentence.
A full Rails locale file into new languages. Pluralisation keys are kept, and the file loads as before.
Front matter and content values for a static site. Keys and ordering come through unchanged.
Descriptions and labels people read, across a large config tree. Identifiers and paths are not copy, so they stay.
A design or component catalogue in one pass, rather than one job per section.
More than 35 formats, each with a workflow built around its own structure.
AI Glot uses analytics cookies, and a support chat that sets its own. You can decline without affecting your browsing.