--- title: What's new in 6.6 | daily.dev description: Unity 6.6, a supported release, introduces fast enter play mode enabled by default (reload scene instead of domain), which requires developers to manage static... canonical: https://daily.dev/posts/what-s-new-in-6-6-uzlw1bgtp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: What's new in 6.6 | daily.dev og:description: Unity 6.6, a supported release, introduces fast enter play mode enabled by default (reload scene instead of domain), which requires developers to manage static... og:url: https://daily.dev/posts/what-s-new-in-6-6-uzlw1bgtp og:image: https://api.daily.dev/og/posts/UZLw1BGTP.png og:image:alt: What's new in 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 6.6 **[Unity](https://daily.dev/sources/unity)** · 23 min read · 0 upvotes · 0 comments ## Summary Unity 6.6, a supported release, introduces fast enter play mode enabled by default (reload scene instead of domain), which requires developers to manage static field cleanup via new attributes or the project auditor tool. Other highlights include native dictionary serialization, a new build analysis/history window, content directories for granular asset loading, reduced web/Android/iOS build sizes, a redesigned hierarchy window with horizontal scrolling and custom columns, entities integration into the standard hierarchy, a new compute light baker, 2D lighting improvements with rendering layers and GPU skin sprite shadows, shader graph and visual effects graph interoperability, UI Toolkit backdrop filters and drop shadows, safe area UI components, and WebGPU moving from experimental to production-ready status with WebAssembly64 raising web memory limits from 4GB to 16GB. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did my static fields stop resetting between play sessions after upgrading to Unity 6.6? Unity 6.6 enables fast enter play mode by default, which reloads the scene instead of the domain, so static fields are no longer cleared between play sessions. To fix this, add the using Unity.Scripting Lifecycle Management namespace and apply the AutoStaticsCleanup attribute to a partial class, or use the Project Auditor tool (rule UL0013) to detect fields needing this attribute. Use NoAutoStaticCleanup if persistence is intentional. _Developers tracking Unity upgrade gotchas like this one follow release breakdowns on daily.dev._ ### Is WebGPU production ready in Unity 6.6? Yes, WebGPU moved from experimental to production ready status in Unity 6.6. Web builds using WebGPU gain access to compute shaders, GPU skinning, indirect rendering, and visual effects graph support, while retaining a WebGL2 fallback for unsupported browsers. It can be enabled in Player Settings by adding WebGPU to the graphics API list and moving it above WebGL2. _Teams deciding when to adopt WebGPU for web builds can follow platform readiness updates on daily.dev._ ### How much has Unity's web build memory limit increased with WebAssembly64 in Unity 6.6? WebAssembly64 in Unity 6.6 raises the maximum memory available to web builds from 4 GB to 16 GB. The default memory size setting remains lower, but 32-bit builds are still preferable for projects that do not need the extra memory, since 64-bit adds overhead. This is configured in Project Settings under Player, Publisher Settings, Maximum Memory Size. _Developers scaling memory-heavy web games can track platform capability changes like this on daily.dev._ --- Tags: [#performance](https://daily.dev/tags/performance), [#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-6-6-uzlw1bgtp) ```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 6.6","url":"https://daily.dev/posts/what-s-new-in-6-6-uzlw1bgtp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/what-s-new-in-6-6-uzlw1bgtp"},"datePublished":"2026-09-01T16:31:41.940Z","dateModified":"2026-09-05T20:22:06.408Z","description":"Unity 6.6, a supported release, introduces fast enter play mode enabled by default (reload scene instead of domain), which requires developers to manage static...","image":"https://i.ytimg.com/vi/u7TQJWmZ_rk/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/u7TQJWmZ_rk/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Unity","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":"Unity","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/9afe038cc27e4d95ad581284cea8578d","url":"https://daily.dev/sources/unity"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/what-s-new-in-6-6-uzlw1bgtp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"performance,game-development,unity,webgpu","timeRequired":"PT23M","video":{"@type":"VideoObject","name":"What's new in 6.6","description":"Unity 6.6, a supported release, introduces fast enter play mode enabled by default (reload scene instead of domain), which requires developers to manage static...","thumbnailUrl":"https://i.ytimg.com/vi/u7TQJWmZ_rk/sddefault.jpg","uploadDate":"2026-09-01T16:31:41.940Z","duration":"PT23M","url":"https://api.daily.dev/r/UZLw1BGTP","embedUrl":"https://www.youtube.com/embed/u7TQJWmZ_rk"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Unity","item":"https://daily.dev/sources/unity"},{"@type":"ListItem","position":3,"name":"What's new in 6.6"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/what-s-new-in-6-6-uzlw1bgtp#faq","mainEntity":[{"@type":"Question","name":"Why did my static fields stop resetting between play sessions after upgrading to Unity 6.6?","acceptedAnswer":{"@type":"Answer","text":"Unity 6.6 enables fast enter play mode by default, which reloads the scene instead of the domain, so static fields are no longer cleared between play sessions. To fix this, add the using Unity.Scripting Lifecycle Management namespace and apply the AutoStaticsCleanup attribute to a partial class, or use the Project Auditor tool (rule UL0013) to detect fields needing this attribute. Use NoAutoStaticCleanup if persistence is intentional. Developers tracking Unity upgrade gotchas like this one follow release breakdowns on daily.dev."}},{"@type":"Question","name":"Is WebGPU production ready in Unity 6.6?","acceptedAnswer":{"@type":"Answer","text":"Yes, WebGPU moved from experimental to production ready status in Unity 6.6. Web builds using WebGPU gain access to compute shaders, GPU skinning, indirect rendering, and visual effects graph support, while retaining a WebGL2 fallback for unsupported browsers. It can be enabled in Player Settings by adding WebGPU to the graphics API list and moving it above WebGL2. Teams deciding when to adopt WebGPU for web builds can follow platform readiness updates on daily.dev."}},{"@type":"Question","name":"How much has Unity's web build memory limit increased with WebAssembly64 in Unity 6.6?","acceptedAnswer":{"@type":"Answer","text":"WebAssembly64 in Unity 6.6 raises the maximum memory available to web builds from 4 GB to 16 GB. The default memory size setting remains lower, but 32-bit builds are still preferable for projects that do not need the extra memory, since 64-bit adds overhead. This is configured in Project Settings under Player, Publisher Settings, Maximum Memory Size. Developers scaling memory-heavy web games can track platform capability changes like this on daily.dev."}}]} ```