> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/the-editor/how-to-use-the-profiler.md).

# How to use the profiler

Monitor a running Sandbox Studio project, record performance problems, and save a profiling report that can be reviewed during troubleshooting.

{% embed url="<https://youtu.be/dOqkAO9kMgE?si=GzRjd_0FumCj2AGf>" %}

{% stepper %}
{% step %}

## Open the profiler

Select the lightning or heartbeat-shaped button in the top-right corner of Sandbox Studio to open the profiler menu.
{% endstep %}

{% step %}

## Review the profiling actions

The menu may include Start Profiling, Download, Quick Snapshot, Full Profiling, and Report Console. Choose the action needed for the information you want to collect.
{% endstep %}

{% step %}

## Open the performance graph

Select the button beside the FPS display to show a graph of frame rate and related activity while the project runs.
{% endstep %}

{% step %}

## Start profiling

Run the game, open the profiler menu, and select Start Profiling. Sandbox Studio begins recording a log of activity from the running project.
{% endstep %}

{% step %}

## Reproduce the performance problem

Play through the part of the game where the frame-rate drop, spike, or other issue occurs. Keep the capture focused so the data is easier to review.

{% hint style="info" %}
*TIP: Record the scene, action, and approximate time when the issue appeared. This helps connect a profiler spike to its cause.*
{% endhint %}
{% endstep %}

{% step %}

## Download the profiling report

When the capture is complete, use Download to save the generated JSON profiling file to your computer.
{% endstep %}

{% step %}

## Share the report for analysis

Attach the JSON file to a troubleshooting request or provide it to your development agent. Explain the problem and when it occurred so possible fixes can be suggested.

{% hint style="info" %}
*NOTE: Review profiling files before sharing them outside your team. Remove private project information or local details that the recipient does not need.*
{% endhint %}
{% endstep %}
{% endstepper %}

## What You've Done

You can now monitor performance, capture a profiling session, and save its JSON report for analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://studio-docs.sandbox.game/the-editor/how-to-use-the-profiler.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.