Skip to main content
Studio has an instance-level interface catalog, Laravel package translation files, and locale-labelled tags. These are separate from translating the content of an uploaded document. Built-in interface and Laravel catalogs currently ship in English and Polish. Additional languages are application-provided catalogs.

Set an initial interface language

Locales use BCP 47 identifiers such as pl-PL, de-DE or ar. Underscore input is normalized before canonicalization. On initial mount Studio tries the device’s saved preference, the supplied locale, the document language and browser languages, then English. A saved device preference can therefore take precedence over the initial prop. A later prop change requests the new locale. Do not mutate Studio’s private localStorage format as a localization API. Workspace/device preference behavior is described in language and timezone preferences. Locale and time zone are independent: changing language does not change a file timestamp.

Lazy language loading

Studio resolves regional/script catalogs and the base language, then uses English for omitted keys. A custom de-DE catalog can override de; neither requires editing package source. Invalid non-string overrides do not replace valid fallback strings. A selected language does not imply every surface has been translated. Shipped catalogs are separate studio-locale-<code>.js assets. Emoji datasets use emoji-data-<code>.js for the 28 languages included with the pinned emoji package; those datasets are fetched only when needed, not when opening the library. Serve the complete built asset directory rather than copying only studio.js. See custom translations for static overrides, lazy modules, typed complete catalogs, placeholders and load-failure behavior. See RTL for direction, mixed-script filenames and the current support boundary.