Translate iOS Localizable.strings files with AI
Import your iOS and macOS .strings files, let AI translate them with your glossary and context, review every string and export ready-to-ship files.
The classic localization format for iOS, iPadOS and macOS apps.
What a iOS .strings file actually holds
Localizable.strings is a flat list of "key" = "value"; pairs, one per line, wrapped in a .lproj folder per language. The simplicity is genuine — there is no nesting, no metadata, nothing to configure — which is why it remains the workhorse format for iOS, iPadOS and macOS apps.
The catch is that the format has no way to tell you when something is wrong. A missing semicolon, a stray quote, a key that exists in English and not in German: none of these fail loudly. They surface as an untranslated key on screen, or a string that silently falls back to the base language.
.strings
"welcome_title" = "Welcome back!";
"save_button" = "Save changes";What goes wrong when iOS .strings files are translated badly
These are the failures that reach production, because none of them look like errors until they do.
A missing semicolon voids the rest of the file
Each entry ends in a semicolon. Drop one and the parser gives up from that point on, so a single bad line can leave half your app untranslated.
Format specifiers get moved or dropped
%@ and %ld are filled in at runtime. A translation that reorders them without using positional forms crashes, and it crashes only in that language.
Keys get translated along with values
When keys are human-readable English sentences — a common convention — a naive tool cannot tell key from value and translates both.
Files drift out of sync between languages
Nothing enforces that every .lproj has every key. Missing entries fall back silently, so a half-finished translation looks finished.
How GetTranslated handles it
Import your iOS .strings 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 iOS .strings file into the free tool and get the translated version back straight away — no account, no email address.
Open the free iOS .strings translatorFrequently asked questions
Are keys left untouched?
Yes. Only the value on the right-hand side is translated, whatever the key looks like.
Does it work with .stringsdict?
Plain .strings files are fully supported. Plural rules in .stringsdict need their own handling and are best managed alongside, not through the same import.
How do I know a language is complete?
Each project shows per-language progress, so a locale that is missing keys is visible before you ship rather than after.
500 keys free forever. No credit card.