Locales and Output Folders

Supported locale codesCopy Anchor Link

There is no fixed list. A locale code is any key you use under localizations in your strings file. Open Assets uses the code as is for three things:

• the lang attribute on <html> (fonts, :lang() selectors),
• Intl.NumberFormat for number formatting,
• the folder name in the output.

So use valid BCP 47 language tags that match what your store expects. The Tax Days and Skimmer example strings files use the 38 codes below, which line up with App Store Connect languages:

ar ca cs da de el en en-AU en-GB es es-419 fi fr fr-CA he hi hr hu id it ja ko ms nb nl pl pt-BR pt-PT ro ru sk sv th tr uk vi zh-Hans zh-Hant

Codes are case sensitive when matching: pt-BR and pt-br are different locales.

Choosing which locales renderCopy Anchor Link

Details from the code:

• A locale counts as present if at least one string has a value for it. Missing strings fall back as described in Strings.
• If --locale names a locale the collection does not have, that collection is skipped with a warning.
• --locale does not affect collections without localizations. They render normally.
• npx open-assets validate fails when locales lists a code that is not in the strings file. render skips it silently, so run validate in CI.

Both Tax Days and Skimmer keep 38 locales in the strings file and set "locales": ["en", "ar", "de", "ja"] to render a representative subset.

Output foldersCopy Anchor Link

A localized collection adds a locale folder directly under the collection:

To use a different layout, set outFile with the {locale} and {template} placeholders. The Tax Days example writes the same layout explicitly:

{
  "name": "iphone-6.9",
  "size": { "width": 1320, "height": 2868 },
  "outFile": "exports/screenshots/{locale}/iphone-6.9/{template}.png"
}

An outFile in a localized collection should always contain {locale}, or every locale overwrites the same file. See outFile.

Caching per localeCopy Anchor Link

Each locale has its own entries in assets.lock (keyed as collection/locale/template), so adding a locale renders only that locale on the next run, and the rest are skipped as unchanged. Editing localizations.json does not by itself invalidate the cache, because the cache tracks template files, not the strings file. Run with --force after changing translations.

RelatedCopy Anchor Link

• Localization overview
• Upload to App Store Connect
• render command