Your Flutter ARB files, checked the way gen-l10n reads them

Paste your template app_en.arb. Your browser checks every message with a port of gen-l10n's own ICU parser and shows what each plural really prints for 1, 2, 5 or 21 in any language - free, nothing uploaded. A paid run annotates the template for translators or translates it into a new locale, and every message it returns is checked again.

The first three replay saved model runs; the Polish one shows what the free check catches. All free.

1. The template ARB (the file named in template-arb-file, usually app_en.arb)

JSONFile name

Drop an .arb file here, or

use-escaping: true in my l10n.yaml relax-syntax: true

2. The target locale

Locale

Existing translation (optional - paste app_de.arb to check it and fill only its missing keys)File name

Drop the translation's .arb here, or

Paste a template ARB, or load an example.

Check (free, in your browser, no AI)

messages

plurals / selects

placeholders

findings

locale

Template findings (what gen-l10n would stop on, then what translators will trip on)

Messages

key	message	placeholders	translation

Project setup for these files (Flutter 3.35 and later)

Since Flutter 3.35, synthetic-package: true is an error and package:flutter_gen is gone: the code is generated into arb-dir and imported from there (breaking-change note).

l10n.yaml

pubspec.yaml

Dart

iOS also needs each language listed in Xcode (Runner > Info > Localizations) for the App Store and system settings to see it.

Free: no account, no run.

3. Guidance (optional - formality, glossary, tone)

Check a template first to price the run.

Raw model reply

The reply did not parse as the structured result, so it is shown as it arrived.

Your recent runs

What this does, and what it does not

Flutter apps keep their text in ARB files: a template such as lib/l10n/app_en.arb and one file per language. flutter gen-l10n (run by flutter pub get when generate: true is set) compiles them into AppLocalizations. Messages use ICU syntax - {name}, {count, plural, one{...} other{...}}, {gender, select, ...} - and the metadata under "@key" declares each placeholder's type and tells translators what the text means.

The check is a JavaScript port of gen-l10n's own message parser and placeholder rules (from the Flutter tool's source, BSD-3-Clause), so a message it rejects is one gen-l10n rejects. Two rules catch translations out: in gen-l10n =1 is the one case, not an exact match, so in Russian or Ukrainian it also prints for 21 and 31; and a plural without a category the language needs (Polish few and many) silently shows the other text. The preview shows both. The page never runs Flutter and cannot tell whether a translation reads well - that is what a native reviewer is for. Derived from the agent skill @flutter/flutter-localizing-apps (flutter/agent-plugins, BSD-3-Clause; see the notice).

Your Flutter ARB files, checked the way gen-l10n reads them

1. The template ARB (the file named in template-arb-file, usually app_en.arb)

2. The target locale

Check (free, in your browser, no AI)

Template findings (what gen-l10n would stop on, then what translators will trip on)

Translation findings

What Flutter shows for each count

Messages

3. About the app (optional - descriptions are written from it)

3. Guidance (optional - formality, glossary, tone)

Reconciliation with the browser

Raw model reply

Your recent runs

If that did not work

What this does, and what it does not