Window Framework for UI Toolkit v2.0.x
Asset Requirements

WindowFramework is designed for developers building runtime interfaces with Unity UI Toolkit. It provides the windowing and theming layer around your application's content, with optional integrations for Addressables loading and Unity Visual Scripting.

This page explains the environment you need and the additional requirements for those integrations. Detailed configuration belongs in Installation and Setup, so you can check suitability here before moving on to setup.

Required Environment

Unity 6.3 or Later

The current release requires Unity 6.3 or later. This gives you the modern UI Toolkit features used by WindowFramework, including vector graphics support. Older Unity versions are outside the supported scope of this release.

You do not need to choose an older editor version to follow the manual: the workflows are written for the current release and its supported Unity environment.

Unity UI Toolkit

WindowFramework is a UI Toolkit windowing system. Its windows and controls are VisualElements, its interface layouts can be authored in UXML, and its styling uses USS and theme stylesheets.

UI Toolkit is part of Unity. You can build window content in C#, author it through UXML and UI Builder, or combine those approaches to suit your project. The framework provides the surrounding window behavior; you supply the content and application logic.

WindowFramework does not convert Canvas/uGUI interfaces into UI Toolkit windows. An existing Canvas-based interface should not be treated as interchangeable with a WindowFrame content tree.

Unity Input System

WindowFramework uses Unity's Input System for its input handling. Your project's Active Input Handling must allow the new Input System. Select Input System Package (New), or Both if your application also needs legacy input.

This does not require replacing your application's player controller. The framework's UI input and your gameplay input still need to be coordinated according to your application's design, particularly when showing modal interfaces.

Optional Integrations

Choose these integrations when they fit your project. They are separate from the basic requirement to build your interface with UI Toolkit.

Addressables 2.9.0 or Later

Addressables 2.9.0 or later** is supported for the Addressables features.

This integration lets you load configured theme data through Unity Addressables. Use it when Addressables is part of your application's asset-loading workflow; it is not a requirement to distribute your player-editable theme files through Addressables.

To use the integration, install the Addressables package and configure the relevant assets and Addressables content for your application. Installing the package alone does not supply a built content catalog or select which theme data your application should load.

See Installation and Setup for the Addressables setup instructions.

Unity Visual Scripting 1.8.0 or Later

Unity Visual Scripting 1.8.0 or later** is required to use the supplied Visual Scripting integration.

Use this integration when you want to drive supported framework operations from graphs. You do not need Visual Scripting to create windows or use the framework through C# and UXML.

The integration is a preview feature. See Visual Scripting Integration for its setup, available operations, and current limitations.

Player Theme Environment

Player Themes allow your users to customize supported appearance settings without opening the Unity Editor. To offer this feature, your application needs access to the configured player-theme folder: reading is needed to discover and apply themes, and writing is needed to create editable copies.

Plan that folder access for your target platform. Do not assume that every deployment environment offers the same access to local files or lets users edit those files in the same way.

Editable copies also depend on prepared application theme data. Your configured themes supply the supported defaults, font references, and any declared Developer Extension settings. Players customize within that application-defined environment rather than supplying arbitrary executable stylesheets or new font imports.

See Theme Studio and Manager for authoring and preparation, Developer Extensions for custom UI settings, and Player Themes for enabling player customization.

Next Step

Once your project meets these requirements, continue to Installation and Setup to configure the framework's UI document, controller, panel settings, and theme data. From there, Windows and Layout walks through building and arranging your own windows.