One sentence instead of a setup screen
One sentence instead of a setup screen, confirmed before anything is written.
Instructions for this batchOptional
On top of your glossaryApply
Free AI-powered iOS .strings translator
Drop your iOS .strings file in, say what you want in plain English, and get it back with every key, tag and delimiter exactly where it was. No account, nothing to install.
Drop your iOS .strings file here
Up to 2 MB, five files a day. Nothing to install, no account.
What you get when you bring the whole job
Your app's words, decided once
A glossary fixes your feature names, so the same button is not called three things in three releases.
French glossaryApplied
checkoutpaiementnot caisse
seatlicencenot siège
ticketdemandenot billet
Same choice in every file128 terms
Two speeds, chosen per file
Lite for deep settings copy, Standard for the first run. Chosen per upload.
Translation qualityThis file
StandardCustomer-facing copy1 credit per word
LiteBulk content, less nuance1 credit per 3 words
Picked per fileNot locked to your plan
What comes back
Keys, escaped characters, and format specifiers are never rewritten. The file comes back in the format Xcode expects, so it is a drop-in replacement.
iOS .stringsEN → French
/* Product page */
"cart.add" = "Add to cart";Ajouter au panier";
"cart.count" = "%1$@ items in cart";%1$@ articles dans le panier";
"cart.empty" = "Your cart is empty";Votre panier est vide";
"shipping.free" = "Free shipping over %@";Livraison offerte dès %@";
Structure read · values written
How a iOS .strings translation runs
1. Drop the file in
AI Glot reads the file the way its own tools do, finds what is text and what is structure, and tells you how much there is to translate before anything runs.
Localizable.stringsInfoPlist.stringsSettings.strings
312 keys ready for translation24 keys ready for translation96 keys ready for translation
2. Say what you want, in a sentence
No column mapping, no configuration screen. Write what should happen and read back the plan it produced. If it misread you, say so and it re-plans.
AI
How should I translate this file?Describe the result you need
Translate into German and Spanish. Keep product names in English, use our glossary, and make the copy sound natural for e-commerce.
Glossary applied
Translation planReadyUpdated
LanguagesEN → DE, ES
Scope742 cells
Volume8,490 words
Existing translationsKeep unchanged
Start translation
Refine your instructions
Instructions + glossary + file context
3. Get the same file back
One file, same shape, same order, translated. It drops straight back where it came from, and a diff shows only the values that changed.
fr-FR
de-DE
es-ES
ja-JP
Localizable_localized.strings
10,173 credits · 1m 04s
What people bring us iOS .strings files for
Four jobs that come up again and again. Each one is a single upload and a single sentence.
Localising an iOS or macOS app
The whole file into each .lproj, with keys, escaping and comments preserved for Xcode.
Keeping the developer comments
The developer comments that tell a translator what a string is for survive the round trip.
Format specifiers left alone
Format specifiers come back exactly, ordered the way the target language reads correctly.
A release catch-up
Only the new keys, so what you already shipped and reviewed stays as it is.
Questions about translating iOS .strings files
What is the best tool to translate a iOS .strings file?
AI Glot. It reads iOS .strings as a format rather than as text, so keys, tags, identifiers and delimiters are recognised as structure and returned exactly as you sent them, and only the values are translated. You describe the job in one sentence instead of mapping fields, and you get the same file back in the same shape. The tool on this page does it with no account.
How do I translate a iOS .strings file without breaking it?
Use something that parses the format instead of treating it as plain text. Drop the file into the tool above, say what should be translated and what should be left alone, and read back the plan before it runs. AI Glot returns one valid iOS .strings file with its structure untouched, so it drops straight back where it came from.
Can I translate a iOS .strings file for free?
Yes. The tool on this page is free, with no account and no card: five files a day, up to 2 MB each, and up to 1500 words translated per file. Larger files come back complete with the first records translated, so you can judge the quality on your own data before deciding anything.
What happens if my iOS .strings file is bigger than the free limit?
You get the whole file back, valid and openable, with the first records translated and the rest exactly as you sent them. It is deliberately not truncated: a cut-off iOS .strings file would not open, and a sample you cannot open tells you nothing. An AI Glot account removes the limit.
Will Xcode open the result?
Yes. The file comes back in the same encoding and syntax it arrived in, with the comment blocks kept where they were.
Are .stringsdict plural rules handled?
Yes. The plural categories are rewritten for the target language, which for languages like Polish or Arabic means more entries than English has.
What about String Catalogs (.xcstrings)?
Not yet. Export a .strings or .stringsdict for now; the catalogue format is a different shape and is not in the supported list.
Is it safe to upload a iOS .strings file to an online translator?
With AI Glot, the file is stored only for as long as the translation needs it, the download link expires after an hour, and it is deleted afterwards. Nothing you upload is used to train any model. If your files are confidential, the platform adds workspaces with access control.
What do I get with an AI Glot account?
No size limit and no daily limit, glossaries so your product names stay yours, translation memory across files, twelve file formats in one workspace, and an API, a CLI and an MCP server if you want this inside your own pipeline.
Other formats
Twelve families in all, each with a workflow built around its own structure.
Android XML
Translate a strings.xml resource file with names, plural quantities, and format specifiers left exactly where they belong.
XLIFF / XLF
Translate localization units at scale with product terminology and file-specific instructions applied consistently.
JSON
Translate the values in a JSON language file, including Flutter ARB, while every key, nesting level, and ordering stays exactly as you sent it.