Unity 6 Deep Dive: Everything That Actually Matters for Mobile Devs

11 min read
  • Unity 6
  • Mobile
  • URP
  • Performance
  • DOTS

Unity 6 dropped and the marketing bullet points are everywhere. This post is the version-control diff: what's actually new, what changed under the hood, and what you should care about if you're shipping mobile games.

I've migrated production projects to Unity 6 over the last few months. Here's the unvarnished breakdown.

1. The Render Pipeline Story

URP Got Serious

URP was always the "lighter" pipeline, often at the cost of features. Unity 6 closes the gap dramatically:

  • Render Graph for SRP — finally. You write less plumbing code, get automatic resource lifecycle management, and the pipeline can optimize execution order. Custom render features are 60% less code.
  • Forward+ rendering path — way more lights without the deferred memory hit. Mobile-friendly.
  • STP (Spatial-Temporal Post-Processing) — Unity's answer to FSR/DLSS. Render at 0.5x resolution, upscale with motion vectors. On a Pixel 7 we measured 38% GPU time savings with negligible quality loss.

HDRP Got Trimmed

HDRP also picked up Render Graph, and its Volumetric Clouds got way faster. But honestly, if you're shipping mobile, you're on URP. HDRP's mostly relevant for high-end visualization.

2. GPU Resident Drawer + Occlusion Culling

This is the headline performance feature. Two pieces:

GPU Resident Drawer keeps mesh/material data resident on the GPU between frames. CPU just submits "draw these IDs" instead of rebuilding command buffers. Result: massive batching of static meshes.

GPU Occlusion Culling uses depth-based heuristics ON the GPU to skip drawing things behind walls. Previously this was CPU-side and not free.

Real numbers from a project I migrated (3D crowd game with ~2000 instanced units):

  • Unity 2022.3 LTS: 11ms CPU, 14ms GPU on mid-range Android
  • Unity 6: 6ms CPU, 9ms GPU
  • ~40% total frame time reduction

If your game has lots of instances, this alone justifies the migration.

3. Multiplayer Center

Unity finally has a coherent multiplayer story.

What ships in Unity 6:

  • Netcode for GameObjects (mature now, not beta)
  • Netcode for Entities (DOTS-flavor, lower-level)
  • Lobby + Relay services baked in
  • Multiplayer Tools package (network simulator, profiler)
  • Distributed Authority topology — a hybrid between client-authoritative and dedicated server

Real talk: for fast-paced action multiplayer, you still want a dedicated server with Mirror or custom solution. But for turn-based, lobby-based, or casual real-time games (think Rest Poker, social/casino), Multiplayer Center is now the right answer.

4. Unity Sentis (On-Device ML)

This is the sleeper feature nobody's talking about enough.

Sentis runs ONNX models on-device using Unity's Compute Shaders. CPU and GPU inference. No Python, no cloud, no SDK bloat.

Use cases I've seen:

  • Procedural NPC behavior with a 5MB transformer
  • Adaptive difficulty based on player input patterns
  • Voice command recognition without sending audio to a server
  • Image classification for AR experiences

It runs on mobile. It's fast enough for real-time. Watch this space.

5. ECS / DOTS — Finally Stable 1.0

ECS hit 1.0 in late 2023 and stabilized in Unity 6. Combined with the Burst compiler and Job System, you get C++-tier performance for systems with thousands of entities.

Worth using for:

  • Crowd simulations (combat, traffic, particles)
  • Pathfinding with many agents
  • Procedural generation
  • Anything cache-coherent and parallelizable

Not worth using for:

  • Standard gameplay scripting
  • UI
  • Most mobile casual games

The learning curve is real. But for the right problem, the speedup is 10-100x.

6. AI Navigation v2

NavMesh got a complete API overhaul:

  • Runtime baking is real now. You can rebuild a navmesh in <50ms on mobile for typical scenes.
  • NavMeshSurface lets you have multiple overlapping meshes for different agent types.
  • NavMeshLink is way more flexible — jumps, ladders, teleports just work.
  • Dynamic obstacles without re-baking the whole mesh.

If you've avoided NavMesh because of its limitations, give it another look.

7. WebGPU Support (Experimental)

Unity 6 ships WebGPU as the preview backend for WebGL builds. Compared to WebGL 2:

  • Compute shaders work
  • Better instancing
  • 30-50% faster on supported browsers
  • Still experimental — fall back to WebGL 2 for production

For browser-deployed games (Crazy Games, Poki, etc.) this is the future. Not production-ready yet, but worth prototyping.

8. Adaptive Performance 5.0

Mobile-only. Sensors thermal/battery state and lets you dynamically scale quality settings.

In practice:

  • When the device thermal-throttles, you drop from 60fps target to 30fps before the OS kills your performance
  • You can scale resolution, post-fx, draw distance independently
  • Works on Samsung, Pixel, and most modern Android devices
  • iOS support uses MetalFX

For 1+ hour session games (puzzle, strategy), this is must-have.

9. UI Toolkit Maturity

UGUI is still there and isn't going anywhere. But UI Toolkit is now production-ready for runtime UI:

  • USS (Unity Style Sheets) — CSS-like styling
  • UXML — separation of structure from logic
  • Runtime data binding
  • Better performance than UGUI for complex UIs (data-driven lists, scrollers)

Migration cost: real. Long-term win: also real. Start new screens in UI Toolkit.

10. Tooling: Build Profiles

Underrated quality-of-life. You can now define multiple build profiles (Dev-iOS, Prod-Android, QA-WebGL) with their own scripting defines, asset bundles, and quality settings. CI/CD got way easier.

My Migration Playbook

If you're moving an existing project to Unity 6:

  1. Branch your project. Don't migrate in-place.
  2. Update packages first. TextMeshPro, Input System, Cinemachine — let them stabilize before touching gameplay.
  3. Switch URP to Render Graph mode in URP Asset settings. Test custom passes carefully.
  4. Enable GPU Resident Drawer in Project Settings → Quality. Profile before/after.
  5. Run the project on lowest target device. Performance regressions tend to be device-specific.
  6. Migrate UI Toolkit screens last. UGUI keeps working — no rush.

For new projects: just start on Unity 6. The migration cost from 2022 LTS to 6 is real, but starting fresh is painless.

Bottom Line

Unity 6 is the first version in years where the mobile improvements alone justify the upgrade. GPU Resident Drawer + STP + Render Graph cuts frame times measurably. Sentis opens new product categories. Multiplayer Center finally makes Unity's multiplayer story coherent.

If you're on 2022.3 LTS and your project is profitable, plan a Q2 migration. If you're starting fresh, there's no debate — Unity 6 from day one.

Chat