Angular's own i18n
i18n="@@home.title" in templates, $localize in code, ng extract-i18n, one build per locale. Nothing to learn that the Angular docs do not already teach.
@angular/localize way. Import the messages.arb that ng extract-i18n writes, translate every language in one click, review with your team, and pull messages.<locale>.arb back for ng build --localize. No runtime library to add.
Free plan · no credit card · Angular 17 to 22
i18n="@@home.title" in templates, $localize in code, ng extract-i18n, one build per locale. Nothing to learn that the Angular docs do not already teach.
ng add @flutterlocalisation/angular adds @angular/localize, makes the extraction write ARB to src/locale, installs the fl command and three npm scripts.
{$INTERPOLATION}, links and bold text inside a sentence, ICU plurals: the AI translates around them and they come back exactly as Angular reads them.
fl pull writes every messages.<locale>.arb and lists each language under i18n.locales, so the next ng build --localize builds it.
A message without an @@id or a plural inside a sentence would lose its translations. The import leaves them out with the fix, and fl doctor lists them first.
A Flutter app and its Angular web app can share one set of keys: ARB files for Dart, Angular's ARB files for the web, one review, one Git sync.
i18n attributes to every languageng add @flutterlocalisation/angular and pick your project with npx fl init.The CLI also ships an MCP server, so an AI agent in your editor can add a message, translate it and pull it.
$ ng add @flutterlocalisation/angular ✓ @angular/localize, ARB extraction, fl $ npx fl init $ npm run i18n:push ✓ 41 keys imported, translated into 3 languages $ npm run i18n:pull ✓ src/locale/messages.fr.arb, messages.de.arb, messages.ja.arb $ ng build --localize
flutterlocalisation.json in the repo root holds the project name and angular_dir, the folder of your ARB files.
i18n="@@home.title", $localize`:@@id:…`One key per @@id, dots and hyphens allowed{$INTERPOLATION}, {$name}A placeholder the AI keeps, written back unchanged{$START_LINK}…{$CLOSE_LINK}A pair kept around the right words, in order{VAR_PLURAL, plural, …} as the whole messageA plural with the forms each language needsi18n="Meaning|Description@@id")Context the translator and the AI read@@id, a plural inside a sentence, a literal braceLeft out with the fix, never guessedYes. Since November 2026 a project can ship an Angular app, alone or beside a Flutter app. It uses Angular's own i18n, nothing else: @angular/localize, an @@id on every message, ng extract-i18n --format=arb and one build per locale with ng build --localize. No runtime library, no Transloco, no ngx-translate.
The ARB files Angular's own extraction writes. It reads messages.arb, the source file ng extract-i18n produces, and writes one messages.<locale>.arb per language, with @@locale and the messages, which is all Angular reads from a translation file. messages.arb is never written: the extraction owns it.
Yes. Angular's placeholders ({$INTERPOLATION}, {$START_LINK}…{$CLOSE_LINK}, {$START_BOLD_TEXT}…) are shown as placeholders in the editor, the AI keeps them and keeps each START before its CLOSE, and they are written back exactly as Angular expects. ICU plurals and selects keep their {VAR_PLURAL, plural, …} form, with the plural forms each language needs.
Without one, Angular names a message by a hash of its English text, so the id changes every time the English does and its translations are lost. With i18n="@@home.title" or $localize`:@@toast.saved:Saved` the id is yours. Messages without one are left out of an import and listed with the fix.
Make the plural the whole message, with the sentence inside each case: {count, plural, =1 {One post is planned.} other {{{count}} posts are planned.}}. Inside a sentence, Angular splits the plural into a second message that always gets a hash id. It reads better in every language anyway, and fl doctor points out the ones to change.
No. An Angular app gets its strings with the build (ng build --localize), so a copy change ships with the next deploy. Live updates are for the Flutter package and the native iOS SDK. AI translation, review, Git sync, the CLI and the MCP server work the same for Angular.
No. Angular is included in every plan, the free one too. Plans count keys and languages, not platforms, and one project can feed a Flutter app and an Angular app from the same keys.
Start with the free plan, push one extraction, and build every locale before lunch.