--- title: What's new in Unity 6.6 | daily.dev description: Unity 6.6 ships as an incremental release ahead of Unity 7's Core CLR runtime change. Highlights include fast enter play mode enabled by default (using scene... canonical: https://daily.dev/posts/what-s-new-in-unity-6-6-7ls9sbv5x twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: What's new in Unity 6.6 | daily.dev og:description: Unity 6.6 ships as an incremental release ahead of Unity 7's Core CLR runtime change. Highlights include fast enter play mode enabled by default (using scene... og:url: https://daily.dev/posts/what-s-new-in-unity-6-6-7ls9sbv5x og:image: https://api.daily.dev/og/posts/7Ls9SbV5X.png og:image:alt: What's new in Unity 6.6 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # What's new in Unity 6.6 **[Collections](https://daily.dev/sources/collections)** · 4 min read · 6 upvotes · 0 comments ## Summary Unity 6.6 ships as an incremental release ahead of Unity 7's Core CLR runtime change. Highlights include fast enter play mode enabled by default (using scene reload instead of full domain reload, requiring manual static field cleanup), and content directories, a new content build/load system replacing asset bundles that fixes bundle-level invalidation, monolithic coupling, and layout trade-offs. Benchmarks show 70% faster incremental rebuilds, 83% less retained memory, and 48% shorter scene load times, though only local content is supported (remote distribution comes in Unity 7). Other changes include native dictionary serialization in the inspector, a new compute light baker using ray tracing, rendering layer-based light control, DXC shader compilation for DirectX 12, WebGPU moving out of experimental to production-ready status, WebAssembly64 raising the web memory ceiling from 4GB to 16GB, reduced build sizes, and a new build analysis and history window with JSON/Chrome trace export. ## Content Unity 6.6 is out now via the Unity Hub as a supported release. It's an incremental update ahead of the bigger Unity 7 milestone, but several of the changes are genuinely useful rather than just checkbox features. ## Fast enter play mode is now the default Quick entry into play mode is enabled by default, using "reload scene" instead of full domain reload. This removes the delay most developers have been living with for years. The catch: you now need to manage static field cleanup yourself, either via new attributes or the Project Auditor tool. Unity 7 will drop domain reload entirely. ## Serialized dictionaries Dictionaries are finally serializable and show up in the inspector. This has been a long-standing gap that forced workarounds involving parallel lists or custom property drawers. It's a small thing that will quietly save a lot of time. ## Redesigned hierarchy window The hierarchy window has been rebuilt with horizontal scrolling, custom columns, better search, and icons. Entities from the DOTS workflow now integrate into the standard hierarchy rather than living in a separate window. ## Content directories replace asset bundles This is probably the most structurally significant change in 6.6. Content directories are a new content build and load system designed to fix three real problems with asset bundles: - **Bundle-level invalidation**: one changed asset forces a full bundle rebuild - **Monolithic coupling**: dependencies baked into bundles cause cascading rebuilds - **Layout trade-offs**: no single bundle layout works well for both memory and load performance Instead of monolithic bundles, content directories store individual content files with weak, runtime-resolved references tracked in a build manifest. This allows granular rebuilds and partial memory unloading. Benchmarks on a URP 3D sample showed 70% faster incremental rebuilds, 83% less retained memory, and 48% shorter scene load times. Addressables can use content directories as a backend with minimal code changes. The limitation in 6.6 is that only local content is supported; remote distribution is planned for Unity 7. ## New compute light baker A new compute-based light baker uses ray tracing APIs and will become the default light baking backend in Unity 7. It's available now in 6.6 for those who want to try it early. ## Rendering and graphics Several rendering improvements landed in 6.6 and are continuing into 6.7: - **Rendering layer-based light interaction control**: lets you control which lights affect which objects at a granular level - **DXC shader compilation for DirectX 12 on Windows**: native 16-bit shader precision via DXC can reduce GPU time by around 40% - **Shader build time improvements**: one internal benchmark went from a 1h46m shader build down to 32 minutes - **2D lighting improvements**: rendering layers, GPU skin sprite shadows, and sprite editor updates - **Shader Graph and Visual Effects Graph interoperability** Looking slightly ahead to 6.7, the URP roadmap includes fully dynamic surface cache global illumination (removing the need for baked light probes), screen space reflections replacing baked cube map reflection probes, ground truth ambient occlusion, and a unified upscaling framework supporting DLSS 4, FSR, PSSR, and Unity's own STP. Neural texture compression (NTC) is also coming, reducing texture memory by 40-50%. There's a Unity neural rendering framework for training custom models with PyTorch or TensorFlow and running inference in-engine. ## WebGPU and WebAssembly WebGPU moves out of experimental status and is now production-ready. WebAssembly64 support raises the memory ceiling for web builds from 4GB to 16GB. Web, Android, and iOS build sizes are also reduced in this release. ## UI Toolkit New additions include backdrop filters (frosted-glass effects), drop shadows, mesh editing, and a safe area component for handling device notches and rounded corners. UGUI continues to be supported alongside UI Toolkit. ## Build analysis tools A new Build Analysis window exposes build size, timing, and errors through a GUI, with JSON and Chrome trace exports and a queryable build history API. Profiler snapshots and pinning are also new. ## Package changes Animation Rigging, Timeline, Cinemachine, and Performance Testing are becoming core packages. Cinemachine 2.0 is deprecated in favor of 3.0. --- The next version, 6.7, will be the next LTS release. Unity 7 follows after that, with Core CLR and the full removal of domain reload. ## Questions this post answers ### What replaces asset bundles in Unity 6.6? Content directories replace asset bundles as the content build and load system in Unity 6.6. Instead of monolithic bundles, they store individual content files with weak references resolved at runtime via a build manifest, so only changed files need rebuilding. Benchmarks on a URP 3D sample showed 70% faster incremental rebuilds, 83% less retained memory, and 48% shorter scene load times. Only local content is supported; remote distribution arrives in Unity 7. _Teams planning a content pipeline migration can track Unity's build system changes on daily.dev._ ### Is WebGPU production-ready in Unity 6.6? Yes, WebGPU moves out of experimental status and is considered production-ready in Unity 6.6. Additionally, WebAssembly64 support raises the memory ceiling for web builds from 4GB to 16GB, and web, Android, and iOS build sizes are reduced in this release. _daily.dev helps developers targeting web platforms keep up with engine build changes like this._ ### Why does Unity 6.6 enable fast enter play mode by default and what should I watch out for? Unity 6.6 turns on fast enter play mode by default, using scene reload instead of a full domain reload, which speeds up iteration significantly. The catch is that developers now must manually clean up static fields between play sessions, since they no longer reset automatically. Unity added new attributes and a Project Auditor integration to help locate problem spots caused by this change. _Developers adapting workflows to engine defaults like this can follow Unity updates on daily.dev._ --- Tags: [#game-development](https://daily.dev/tags/game-development), [#unity](https://daily.dev/tags/unity), [#webgpu](https://daily.dev/tags/webgpu) [View this post on daily.dev](https://daily.dev/posts/what-s-new-in-unity-6-6-7ls9sbv5x) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"What's new in Unity 6.6","url":"https://daily.dev/posts/what-s-new-in-unity-6-6-7ls9sbv5x","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/what-s-new-in-unity-6-6-7ls9sbv5x"},"datePublished":"2026-09-01T17:04:01.467Z","dateModified":"2026-09-05T20:22:06.431Z","description":"Unity 6.6 ships as an incremental release ahead of Unity 7's Core CLR runtime change. Highlights include fast enter play mode enabled by default (using scene...","image":"https://i.ytimg.com/vi/bzk9ZeQ-_ns/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/bzk9ZeQ-_ns/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/what-s-new-in-unity-6-6-7ls9sbv5x","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"game-development,unity,webgpu","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"What's new in Unity 6.6"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/what-s-new-in-unity-6-6-7ls9sbv5x#faq","mainEntity":[{"@type":"Question","name":"What replaces asset bundles in Unity 6.6?","acceptedAnswer":{"@type":"Answer","text":"Content directories replace asset bundles as the content build and load system in Unity 6.6. Instead of monolithic bundles, they store individual content files with weak references resolved at runtime via a build manifest, so only changed files need rebuilding. Benchmarks on a URP 3D sample showed 70% faster incremental rebuilds, 83% less retained memory, and 48% shorter scene load times. Only local content is supported; remote distribution arrives in Unity 7. Teams planning a content pipeline migration can track Unity's build system changes on daily.dev."}},{"@type":"Question","name":"Is WebGPU production-ready in Unity 6.6?","acceptedAnswer":{"@type":"Answer","text":"Yes, WebGPU moves out of experimental status and is considered production-ready in Unity 6.6. Additionally, WebAssembly64 support raises the memory ceiling for web builds from 4GB to 16GB, and web, Android, and iOS build sizes are reduced in this release. daily.dev helps developers targeting web platforms keep up with engine build changes like this."}},{"@type":"Question","name":"Why does Unity 6.6 enable fast enter play mode by default and what should I watch out for?","acceptedAnswer":{"@type":"Answer","text":"Unity 6.6 turns on fast enter play mode by default, using scene reload instead of a full domain reload, which speeds up iteration significantly. The catch is that developers now must manually clean up static fields between play sessions, since they no longer reset automatically. Unity added new attributes and a Project Auditor integration to help locate problem spots caused by this change. Developers adapting workflows to engine defaults like this can follow Unity updates on daily.dev."}}]} ```