Manage UI asset references from C# scripts

Unity represents UXML files as VisualTreeAsset objects in C# and represents USS files as StyleSheet objects in C#. Since VisualTreeAsset and StyleSheet are regular Unity assets, you can use Unity’s standard workflows to manage them.

Use serialization references

Unity automatically detect fields from your C# scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More info
See in Glossary which are of type VisualTreeAsset or StyleSheet. You can use the InspectorA Unity window that displays information about the currently selected GameObject, asset or project settings, allowing you to inspect and edit the values. More info
See in Glossary to set references to specific UXML or USS files imported in your project. Such references remain valid even when the location of your assets change in your project.

There are three ways to use this in your scripts:

Description	How to display the Inspector	Where is the reference saved?
Instances of custom scripts (such as `MonoBehaviour`)	Select the GameObjectThe fundamental object in Unity scenes, which can represent characters, props, scenery, cameras, waypoints, and more. A GameObject’s functionality is defined by the Components attached to it. More info See in Glossary holding the instance of the script	Inside the sceneA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info See in Glossary
Default references for a script that derives from `EditorWindow` or `Editor`	Select the actual C# file in the Project Browser	Inside the meta file associated with the script
Custom assets in your project that derive from `ScriptableObject`	Select the asset in the Project browser	Inside the serialized data of the asset itself

Note: The default references works for all scripts that derive from MonoBehaviour or ScriptableObject. It provides a way to populate default values for serialized fields of scripts.

The following example MonoBehaviour class receives a UXML file and a list of USS files from the Inspector:

using UnityEngine;
using UnityEngine.UIElements;

public class MyBehaviour : MonoBehaviour
{
  // Note that public fields are automatically exposed in the Inspector
  public VisualTreeAsset mainUI;
  [Reorderable]
  public StyleSheet[] seasonalThemes;
}

The following example EditorWindow class receives default references from the Inspector:

using UnityEditor;
using UnityEngine.UIElements;

public class MyWindow : EditorWindow
{
  [SerializeField]
  private VisualTreeAsset uxml;
  [SerializeField]
  private StyleSheet uss;
}

Use the Asset Database (Editor only)

You can load your UI(User Interface) Allows a user to interact with your application. Unity currently supports three UI systems. More info
See in Glossary Assets by path or GUID with the AssetDatabase class.

The following example shows how to locate an asset by path:

VisualTreeAsset asset = AssetDatabase.LoadAssetAtPath<VisualTreeAsset>("Assets/Editor/main_window.uxml");
StyleSheet asset = AssetDatabase.LoadAssetAtPath<StyleSheet>("Assets/Editor/main_styles.uss");

Use Addressables

The Addressables system provides tools and scripts to organize and package content for your application and an API to load and release assets at runtime.

You can use UXML and USS assets with the Addressable system.

For information about how to set up Addressables for any assets in Unity, see Getting started with Addressables.

Use a Resources folder

If you add a Resources folder in your project and place your UI assets in it, you can use the Resources.Load method to load your assets.

The following examples shows how to load an asset in the Resource folder:

VisualTreeAsset uxml = Resources.Load<VisualTreeAsset>("main_window");
StyleSheet uss = Resources.Load<StyleSheet>("main_styles");

Note: This method comes with significant downsides in terms of workflows and final build size. Unity recommends you to use the Addressables system instead.

Create a custom style for a custom control

Support for Editor UI