Key information
Unity is introducing content directories as an alternative to AssetBundles for assets shipped inside a Player build. The feature is available in Unity 6.6; more granular delivery of remote content is described as work for the Unity 7 generation.
Instead of treating a bundle as an indivisible loading unit, the new system identifies individual artifacts such as meshes and textures. Content hashes support deduplication, while stable identifiers and a manifest keep a changed dependency from unnecessarily changing every referring artifact.
The build process uses Unity’s asset-import infrastructure, including parallel work, caching and shared build acceleration. At runtime, individual artifacts can be loaded and unloaded asynchronously. A Loadable reference type provides an engine-level way to request content only when it is needed.
Unity uses Slime Rancher 2 to demonstrate a switch from Addressables’ bundle backend without changing project code. Its example was measured with a Unity 6.6 beta on a MacBook Pro, so it is a specific demonstration rather than a universal performance guarantee. Remote downloads of only missing or changed artifacts remain the next stage of the roadmap.
