Overview
UI Toolkit is Unity’s newer UI workflow built around UXML for structure, USS for styling, and UI Builder for authoring. Unity positions it as the more scalable and modern route for many runtime screen-space interfaces, while still acknowledging that Unity UI remains useful in some situations and that both systems can coexist in one project. (Unity, User Interface Design and Implementation in Unity, see source-unity-ui-design-and-implementation; Unity, Tips to Increase Productivity with Unity 6, see source-unity-productivity-tips)
Setup
Typical UI Toolkit workflow:
- Create a UXML document for structure.
- Create one or more USS files for styling.
- Use UI Builder to author and preview the layout.
- Attach the document to the scene through a UI Document component.
- Register input callbacks from C# where needed.
Usage
UI Toolkit is especially strong for:
- screen-space menus and HUDs
- reusable styled interfaces
- workflows where designers and programmers benefit from clearer separation
- interfaces that resemble structured layout and theming rather than one-off world-space widgets
Unity UI still has advantages in some world-space and highly GameObject-driven workflows, so the decision is not absolute.
Gotchas
- UI Toolkit and Unity UI have different mental models; mixing them casually confuses teams.
- UI Toolkit is not a drop-in replacement for every Unity UI use case.
- Naming consistency across C#, UXML, and USS matters, or the workflow becomes hard to maintain.
Related
ui-design · csharp-code-style · source-unity-ui-design-and-implementation · source-unity-productivity-tips