---
title: "Unity 6.6 WebGPU for Browser IO Fat Games: URP GPU Resident Drawer, STP, and Fish-Net WebGL Fallback"
description: "Learn to ship Unity 6.6 WebGPU for browser IO fat games with URP GPU Resident Drawer, STP, device filtering, and a production Fish-Net WebGL fallback matrix."
url: "https://news.bigfatgames.com/unity-6-6-webgpu-browser-io-capability-matrix"
category: "Browser Games"
date_published: 2026-09-21
reading_time_minutes: 11
word_count: 2589
---

# Unity 6.6 WebGPU for Browser IO Fat Games: URP GPU Resident Drawer, STP, and Fish-Net WebGL Fallback

*A production capability matrix: when WebGPU pays for Resident Drawer and STP, and when Fish-Net players stay on WebGL*

![Unity 6.6 WebGPU for Browser IO Fat Games: URP GPU Resident Drawer, STP, and Fish-Net WebGL Fallback](https://pub-07fb5e4955ba485b822d6b388be96d9a.r2.dev/627e11da-a23a-494d-9964-843e8f31c507/unity-6-6-webgpu-browser-io-capability-matrix/hero-55f9bae5-ec7e-4b31-9eaf-5b8842048d4b.jpg)

**TL;DR:**

- Put WebGPU first and keep WebGL 2 second so unsupported browsers still boot without a custom fallback UI.
- GPU Resident Drawer, GPU occlusion, STP, VFX compute, APV, and compute skinning need WebGPU compute; WebGL cannot run them.
- Qualify Resident Drawer for Forward+/Deferred+ clutter under 128 materials — skip Animator players and MaterialPropertyBlocks.
- Filter weak adapters, require HTTPS, stay under 1 GB compressed for Unity Play, and log graphicsDeviceType because fallback is silent.
- Fish-Net simulation does not change with WebGPU; keep URP Render Graph and spend CPU on netcode, not extra post-FX passes.

## WebGPU is a ship gate, not a URP default

## Put WebGPU first, keep WebGL 2 as a silent fallback

## What WebGPU compute actually unlocks for fat IO worlds

## Which IO entities actually belong on GPU Resident Drawer

## Filter weak WebGPU adapters and log the backend you actually got

## Pass merging, STP, and the custom FX that wipe the win

## Reinvest the CPU in Fish-Net, then publish the two-cohort matrix

## Conclusion

- WebGPU is a ship gate — Unity 6.6 supports it fully, but it stays opt-in; put it first in Graphics APIs and treat it as the high-entity cohort, not URP’s default.
- Silent WebGL 2 fallback — Order WebGPU then WebGL 2, require HTTPS, log graphicsDeviceType, and never gate Fish-Net connect, scenes, or matchmaking on the backend.
- Compute is the IO unlock — GPU Resident Drawer, GPU occlusion, and STP exist only on WebGPU; spend them on pellets, static clutter, and 1080p-class looks, not title-wide VFX or skinning.
- Drawer has hard filters — Forward+/Deferred+, compute APIs, ≤128 materials, no Animator; WebGL cannot fall back to BRG, and enabling it compiles every BatchRendererGroup variant.
- Filter adapters, merge passes — Deny weak WebGPU devices so they take WebGL 2; keep the graph merged. Extra blits and brand FX wipe Resident Drawer wins, and STP cannot fix a split graph.
- Reinvest CPU in Fish-Net — Same ticks, observers, and Bayou transport; publish one silent-fallback build with a two-cohort visual matrix under Unity Play’s size and memory limits.

Ship the two-cohort URP matrix on one WebGPU-first build, then profile pass count and Fish-Net spawn churn on the adapters you actually allow.

## Frequently Asked Questions

### Is WebGPU the default Web backend in Unity 6.6?

No. As of Unity **6000.6** it is fully supported but not enabled by default. Add it to the Graphics APIs list and put it above WebGL 2 so the runtime can fall back automatically.

### What does WebGPU unlock that WebGL cannot run?

Compute on the GPU: GPU Resident Drawing, GPU occlusion culling, STP upscaling, VFX Graph compute particles, Adaptive Probe Volumes, and compute skinning. Those paths are off the table on WebGL.

### When does GPU Resident Drawer actually apply in URP?

Only on pipeline assets whose renderers use Forward+ or Deferred+, on compute-capable APIs (not OpenGL ES), with SRP Batcher and BatchRendererGroup variants, and on Mesh Renderers using no more than **128** materials. Animator hierarchies are excluded.

### Why would WebGPU still lose to WebGL on the same features?

Performance is context-sensitive. Large draw-call CPU cost and BindGroup caching can favor WebGL unless Resident Drawer actually takes the instanced GPU path and Render Graph merges raster passes instead of extra blits.

### What hosting and device rules break WebGPU silently?

Browsers only expose WebGPU in a secure HTTPS context. Unity Play rejects builds over **1 GB** compressed. Use Graphics Device Filtering and log `SystemInfo.graphicsDeviceType` — fallback does not announce itself.

### Does Fish-Net need a different transport for WebGPU?

No. TimeManager ticks, observers, and Bayou WebGL transport stay the same. Use the CPU you save on rendering for interpolation and interest management, not extra URP features that break pass merging.

## Sources

- [https://discussions.unity.com/t/webgpu-out-of-experimental-in-unity-6-6/1734694](https://discussions.unity.com/t/webgpu-out-of-experimental-in-unity-6-6/1734694)
- [https://unity.com/topics/render-pipelines-strategy-for-2026](https://unity.com/topics/render-pipelines-strategy-for-2026)
- [https://docs.unity3d.com/6000.6/Documentation/Manual/urp/gpu-resident-drawer.html](https://docs.unity3d.com/6000.6/Documentation/Manual/urp/gpu-resident-drawer.html)
- [https://docs.unity3d.com/6000.6/Documentation/Manual/urp/render-graph-optimize.html](https://docs.unity3d.com/6000.6/Documentation/Manual/urp/render-graph-optimize.html)
- [https://docs.unity3d.com/6000.6/Documentation/Manual/wasm-64bit-enable.html](https://docs.unity3d.com/6000.6/Documentation/Manual/wasm-64bit-enable.html)