Using Addressables at runtime

Once you have your Addressable assets organized into groups and built into AssetBundles, you must still load, instantiate, and, in the end release them at runtime.

Addressables uses a reference counting system to make sure that assets are only kept in memory while they are needed. See Memory management for more information about reference counting and how you can minimize the amount of memory used by assets at any given time.

Addressables provides several options and APIs for loading and instantiating Addressable assets. See Loading Addressable assets for information and examples, including:

• Loading an single asset
• Loading multiple assets
• Loading an AssetReference
• Loading Scenes
• Loading assets by location
• Instantiating objects from Addressables
• Releasing Addressable assets
• Using Addressables in a Scene
• Downloading dependencies in advance

Addressables uses asynchronous operations for most loading tasks. See Operations for information on how to handle operations in your code, including:

• Releasing AsyncOperationHandle instances
• Coroutine- and IEnumerator-based operation handling
• Event-based operation handling
• Task-based operation handling
• Using operations synchronously
• Custom operations
• Using typed versus untyped operation handles
• Reporting operation progress

See the following for information about other runtime topics:

• Customizing initialization
• Loading additional catalogs
• Updating catalogs
• Modifying resource URLs at runtime
• Getting the address of an asset at runtime