Content storage and loading
Choose how the project stores localized content, ships it in a build, and loads it at runtime.
Read time 1 minuteLast updated 17 days ago
Choose how the project stores localized content, ships it in a build, and loads it at runtime.
Each table collection is assigned to a content source. The source you pick controls how the collection's tables and assets are stored on disk, packaged into a build, and loaded at runtime, and whether that loading happens synchronously or asynchronously.
Configure sources in the Localization settings. Refer to Localization settings reference for the settings UI.
Topic | Description |
|---|---|
| Content sources | Understand how content source providers store and load table collections and their assets. |
| Data file tables | Understand how table collections ship and load as data files instead of assets. |
| Add a language to a built Player | Add a language to a shipped build by dropping in a new table file. |
| Synchronous and asynchronous loading | Understand when localized content loads synchronously and when it must load asynchronously. |