Documentation

Unity Engine

User Manual

Script Reference

Unity Engine

Profiler window reference

Explore the modules and controls you can use to check your application's performance in the main Profiler window.
Read time 10 minutesLast updated 7 days ago
The Profiler window has the following areas:
  • Captures list: Contains a list of saved Profiler sessions in the 
    ProfilerCaptures
    folder of your project.
  • Profiler modules: Add and remove modules to the window which collect different types of data related to your application. Each module has its own chart in the top half of the window.
  • Profiler controls: At the top of the window there are controls which you can use to stop, start, and navigate profiling sessions.
  • Module details pane: The bottom half of the Profiler window displays detailed information about the selected frame, depending on the selected module.

Profiler window with a frame in the CPU Usage Profiler module selected.

Captures list

When you save a Profiler capture, Unity saves it as a 
.data
file to the 
ProfilerCaptures
folder of your project. You can also save files in the 
.raw
format with the 
-profiler-log-file
command. The Captures List displays all the Profiler sessions in the 
ProfilerCaptures
folder. You can change the save location in the Profiler Preferences window.

Operation

Description

ImportSelect a 
.data
file, or a 
.raw
file to import into your project. Unity saves it into the 
ProfilerCaptures
folder.
Context menuRight-click on a capture to edit its details:
  • Delete: Permanently deletes the §
    .data
    file from the 
    ProfilerCaptures
    folder.
  • Rename: Rename the file.
  • Open Folder: Opens the containing folder for the capture.
  • Target Frame Time: Select a target frame time from a default list, or add your own custom frame time to benchmark the data in the capture. The target frame time is used in the Highlights module
Tip
Use the 
SetScreenshotCaptureFrameInterval
 API to set the frequency at which Unity captures the screenshot for the thumbnail in the list.

Default Profiler modules

Use the dropdown to add or remove modules to the Profiler. Profiler modules display performance data over time on a frame-by-frame basis in the charts in the top half of the window.
When you select a Profiler module its chart displays in the top half of the Profiler window. The bottom half of the window contains a module details panel which displays information related to the Profiler module selected. This area is blank when you open the Profiler for the first time, and fills with information when you start profiling your application.
For more information about how to use Profiler modules, refer to Profiler modules introduction.
The Profiler window contains the following default modules:

Module

Description

HighlightsDisplays information on whether your application is meeting its target frame rate and if its performance is bound by the CPU or the GPU. For more information, refer to the Highlights Profiler module.
ScreenshotsDisplays a screenshot of your application for individual frames, synced to the Profiler timeline. This module is active by default. For more information, refer to Screenshots Profiler module.
CPU UsageDisplays an overview of where your application spends the most time, in areas such as physics, scripts, animation, and garbage collection. This module contains broad profiling information about your application, and you can use it to decide which further modules to use to investigate more specific issues in your application. This module is always active, even if you close it. For more information, refer to CPU Usage Profiler module.
ScreenshotsDisplays a timeline of screenshot thumbnails that Unity captures alongside profiled frames, so you can compare what's on screen with performance spikes.
GPU UsageDisplays information related to graphics processing. By default this module isn't active, because it has a high overhead. For more information, refer to GPU Usage Profiler module.
RenderingDisplays information on how Unity renders graphics in your application. For more information, refer to Rendering Profiler module.
MemoryDisplays information on how Unity allocates memory in your application. This module is useful to investigate how scripting allocations lead to garbage collection, or how your application's asset memory usage trends over time. For more information, refer to Memory Profiler module.
AudioDisplays information related to the audio in your application, such as how much CPU usage the audio system requires, and how much memory Unity allocates to it. For more information, refer to Audio Profiler module.
VideoDisplays information related to video in your application. For more information, refer Video Profiler module.
PhysicsDisplays information about the physics in your application that the physics system has processed. For more information, refer to Physics Profiler module.
Physics (2D)Displays information about where the physics system has processed 2D physics in your application. For more information, refer to 2D Physics Profiler module.
UI ToolkitDisplays information about the time spent to render and update your UI, such as how long it takes to update runtime bindings, render, and perform layout updates. For more information, refer to UI Toolkit profiler module reference.
UI Toolkit DetailsDisplays information about the work required to render and update your UI, such as the number of batches, draw calls, and vertices. For more information, refer to UI Toolkit Details profiler module reference.
UI (Canvas)Displays information about how uGUI handles UI batching for your application, including why and how uGUI batches items. For more information, refer to UI (Canvas) and UI Details (Canvas) Profiler module.
UI Details (Canvas)This module's chart adds data about batch and vertices count, and markers which include information about user input events that trigger uGUI's UI changes. For more information, refer to UI (Canvas) and UI Details (Canvas) Profiler module.
Realtime GIDisplays information on how much CPU resource Unity spends on the Global Illumination lighting subsystem in your application. For more information, refer to Global Illumination Profiler window.
2DDisplays statistics about how many sprites Unity renders and which sprite atlases it uses. For more information, refer to 2D Profiler module reference.
Virtual TexturingDisplays statistics about Streaming Virtual Texturing in your application. For more information, refer to Virtual Texturing Profiler module.
Adaptive PerformanceDisplays Adaptive Performance metrics, including frame timing, performance bottlenecks, CPU core configuration, and thermal warnings. For more information, refer to Adaptive Performance Profiler integration.
File AccessDisplays information about file accesses in your application. For more information, refer to File Access Profiler module.
Asset LoadingDisplays information about how your application loads assets. For more information, refer to Asset Loading Profiler module.
2D TilemapDisplays statistics about the tilemaps Unity renders, and how long Unity spends rendering, updating, and processing collisions for them. For more information, refer to 2D Tilemap Profiler module reference.
Web RequestsDisplays information about 
UnityWebRequest
 activity in your application, including how many transfers are in flight, how many bytes they send and receive each frame, and how long each request takes.
Profiler module editor (⚙)Open the Profiler module editor to customize the Profiler modules in the list.
Restore defaultsSelect Restore Defaults to remove any custom Profiler modules and reorder the module list to its default ordering.

Profiler controls

The Profiler controls are in the toolbar at the top of the Profiler window. Use these to start or stop recording profiler data, and to navigate through profiled frames.

Property

Description

Target Selection dropdownUse the Target Selection dropdown to select a platform or player for the Profiler to collect data for:
  • Search: Use the search bar to find a player. You can search by its name or device category, for example 
    Remote
    . When you search by category, the result displays all devices in that category.
  • Player Name: Displays any running players that Unity detects through the network or by direct connection. You can identify these players by their name and the platform that's running the player, for example 
    iPhonePlayer (My iPhone)
    . You can override this name in the Profiler Preferences window.
  • Play Mode (default): Profile your application in Play mode. This is the default mode, but you can change this behavior in the Preferences window. For more information, refer to Collect performance data in Play mode.
  • Edit Mode: Profile the Unity Editor and display the resources that the Editor is currently using. For more information, refer to Collect performance data about the Unity Editor.
  • Direct Connection: Displays any devices directly connected to your computer. Select Enter IP to manually enter the IP address of the device you want to profile your application on. For more information, refer to Collect performance data on a target platform.
Record (⏺)Enable this setting to record profiling information for the active modules when you run your application. If Record is disabled, the Profiler doesn't collect any data when you run your application.
Previous frame (back arrow)Navigate one frame back.
Next frame (forward arrow)Navigate one frame forward.
Current frame (⏭)When you select the Current Frame button, the frame indicator line jumps to the last recorded frame, and the Profiler enters Current Frame mode. While the Profiler collects data in this mode, it stays on the current frame and displays the data it collects in real-time. Select the button again to exit Current Frame mode.
Frame numberIndicates the selected frame's number. The number on the left is the current frame selected, and the number on the right is the total number of frames combined that the Profiler collected during your entire profiling session.
ClearErase all data from the Profiler window.
Clear on PlayEnable this setting to erase all data from the Profiler window next time you click Play in the Player window, or when you connect to a new target device.
Deep ProfileProfiles all C# methods so that you can analyze scripts in more detail.

If a session started with Deep Profile enabled, then a warning icon appears next to the setting's label. This indicates that all managed code stays instrumented for the rest of the session. Deep Profile then only enables or disables data collection and doesn't add or remove the instrumentation overhead.
Instrument EverythingInstruments System libraries, as well as your Project and Unity's managed code. Use this setting when you profile the Unity Editor.

You can only use this setting when you enable Deep Profile and select its drop down menu.

This setting requires the Editor to launch with the 
-deepprofiling
command line argument, which also requires you to restart the Editor. When you profile a Player, this checkbox is disabled and indicates whether the connected Player was built with deep profiling support.

For more information, refer to Deep profiling.
Call StacksSelect samples to record full call stacks for scripting memory allocations. Frames that the Profiler records when you enable this option have information about the selected samples on the full call stack that lead to a managed scripting allocation, even when the Deep Profile setting isn't active.

You can select the following values, and have more than one selection active at once:
  • GC.Alloc: Enables call stacks for all managed memory allocations. Unity emits 
    GC.Alloc
    samples any time it makes a managed memory allocation.
  • UnsafeUtility.Malloc (Persistent): Enables call stacks for native memory allocations that are made with 
    Allocator.Persistent
    . While the Temp and TempJop allocators are faster, they only allow for short lived allocations and to keep them as fast as possible, Unity doesn't instrument them with call stacks.
  • JobHandle.Complete: Enables call stacks for jobs completed with 
    JobHandle.Complete
    . Whenever a job uses 
    Complete
    it results in idle time on the thread, so to optimize the code, you can enable call stacks to discover where in your code the sync point happened.
Load (square and arrow)Load saved Profiler data into the Profiler window. You can also load binary profile data that the Player has written out to file via the Profiler.logFile API.

Hold down the Shift button and click the Load button to append the file contents to the current profile frames.
Save (💾)Save the Profiler data into a 
.data
file in your Project folder.

More (⋮) menu settings

The More (⋮) menu contains the following settings.

Setting

Description

Color Blind ModeEnable this setting to make the Profiler use higher contrast colors in its graphs. This enhances visibility for users with red-green color blindness.
Show stats for "current" frameBy default, when you select the Current Frame button and enter Current Frame mode, the frame indicator line doesn't have annotations with the stats for the current frame. This is because the stats annotations might make it difficult to view data in real-time. To display the annotations, enable this setting.
PreferencesOpen the Preferences window to adjust Profiler-specific properties.

Additional resources