Unity
Scalable Build Pipeline with Content Directories | Unite Seoul 2026
Summary
AI summaries can be incomplete or wrong. Verify anything important against the original video.
This presentation introduces Content Directories, a new, more efficient, and scalable content build and loading system in Unity 6.6 designed to overcome the limitations of traditional AssetBundles.
The speaker, a Senior Partner Engineer at Unity, outlines the limitations developers face as projects grow in size and complexity when relying on traditional AssetBundles. These limitations include bundle-level invalidation, which forces massive, unnecessary rebuilds for even minor changes; monolithic coupling, where dependencies are baked together and cannot be easily updated; and complex layout optimization trade-offs that demand significant engineering effort to manage performance and memory efficiently.
To solve these problems, the speaker introduces 'Content Directories,' Unity's new build and load model. This system offers a more granular approach, allowing for self-optimizing layouts and 'granular updates' where only the specific changed asset needs to be rebuilt and deployed. The system separates content identity, reference identity, and physical storage layout, ensuring developers no longer need to manually manage complex bundle layouts.
Performance benchmarks in the video demonstrate substantial improvements, including 70% faster rebuilds, an 83% reduction in residual memory usage, and 48% faster scene loading. The system is designed for modern pipelines, enabling automatic recording of build metadata to JSON/JSONL for integration with automated testing (CI) and build history analytics. The talk concludes by highlighting how to opt in via the Addressables system, with future plans in Unity 7 focused on extending these capabilities to support remote content distribution.
Verdict
Content Directories significantly outperform the legacy AssetBundle system in build times, memory efficiency, and loading speed, and provide a much more automated, scalable workflow for developers.
Pros
Cons
- Currently limited to local content only in Unity 6.6 27:12
Best for
Not for
Key Points
- 5:39 The speaker identifies three structural limits of traditional AssetBundles: bundle-level invalidation, monolithic coupling, and complex layout optimization.
- 6:47 Detailed explanation of bundle-level invalidation: a single minor asset change triggers a complete rebuild and re-download of the entire AssetBundle.
- 8:50 The issue of monolithic coupling where assets and dependency metadata are baked together, making patching difficult.
- 17:15 Introduction of Content Directories: a new system that treats build output as granular files rather than one monolithic archive.
- 18:12 Design goals for Content Directories: self-optimizing layouts and granular updates where only modified assets are processed.
- 23:24 Performance benchmark results: 70% faster rebuilds, 83% less residual memory, 48% faster loading compared to AssetBundles.
- 24:03 Technical explanation of how Content Directories achieve performance gains through out-of-process parallelization.
- 26:52 How memory efficiency is improved by loading granular files only when needed, avoiding memory waste from large bundle headers.
- 27:32 The Runtime Model consists of four stages: Register, Discover, Load, and Release.
- 32:32 Unity 6.6 supports local content migration to Content Directories via Addressables; remote distribution is planned for Unity 7.
Worth watching if: You are a Unity developer struggling with long build times, large application sizes, or complex memory management issues in your projects and want to understand how to optimize your asset pipeline using the new Content Directories feature in Unity 6.6.
Get every Unity video extracted like this
One daily email with structured extracts of every channel you follow. Free tier covers 15 videos a month.
Sign in with GoogleNo credit card. Free tier forever.