Add and manage translations in table collections, then reference them from scripts, components, and UI Toolkit bindings.
Localization tables hold your translations, with one entry per key and one column per locale. Author your translations in table collections, then hand collections off to translators or reference their entries wherever you need to display a localized value.
Once your tables are ready, you can reference their entries from scripts to drive dynamic text, swap assets per locale, or bind UI Toolkit elements. Refer to Get started with localization if you haven’t set up localization in your project yet.
| Topic | Description |
|---|---|
| How Localization tables work | Understand table collections, keys, entries, and metadata. |
| Create and edit table collections | Create a table collection and author keys, translations, variants, and metadata. |
| Import and export table collections | Export a table collection to JSON for translators and import the result back. |
| Localize strings | Display localized and dynamic text from scripts and components. |
| Localize assets | Swap textures, audio, and other assets per language. |
| Localize UI created with UI Toolkit | Bind UI Toolkit elements to localized strings and assets. |