---
title: "V-Ray Profiler"
canonical: "https://documentation.chaos.com/space/VMAYA/111740132/V-Ray%20Profiler"
format: markdown
---
This page provides information about the V-Ray Profiler tool.
## **Overview**
---
## **UI Path**
---
||Render Settings|| > **Settings** > **System **> **V-Ray Profiler**
## **Settings**
---
## **Workflow**
---
1. Turn on the V-Ray Profiler by setting the **Profiler mode** to **System **or** All**.* *
2. Set the output location of the *.json and .html files*. If this field is left empty, the generated files are saved in the default Temp folder in your system.
3. Render your scene[3](https://docs-chaos.atlassian.net/wiki/spaces/VMAYA/pages/111740132/V-Ray+Profiler#V-RayProfiler-Notes). Once you finish the render, you are able to find the *.html and .json* *files* in your designated directory. Rendering a second or third time generates more reports. Up to 3 reports can be generated in the same folder. Generating more, without changing the **Output directory**, causes the oldest report to be replaced by the new one. **Tip:** if you forget where you set the output files to be, the location is recorded in the log file.
4. Open the generated report[2](https://docs-chaos.atlassian.net/wiki/spaces/VMAYA/pages/111740132/V-Ray+Profiler#V-RayProfiler-Notes) :
- If you want to open the .json file:
Go to a third-party tracking software. We recommend using Google Chrome's tracer. Open Google Chrome and enter **chrome://tracing/** in the URL field. Drag and drop your .json report onto Google Chrome and explore. The report shows the duration it took to render each element in nanoseconds. Alternatively, you can open the .json file in any text editing software on your machine.
- If you want to open the .html file:
Double-click on the file and it opens the report in the default browser. Most browsers are suitable for this. Explore the report. The report shows the duration it took to render each element in nanoseconds.
5. You can view the report's metadata either through the > Macro (inline-media-image)
button in the browser report, or at the top of the .json file, when read through a text editor, under "product".
> Macro (ui-text-box)
>
> If, at any point during the render, the CPU performance drops, a **High bundle size wait** section appears in the profiler.
>
>
> > Macro (legacy-content)
Example of a result in All mode opened in a browser
---
Example of a result in System mode opened in a browser
---
## **Notes**
---
1. If there is only layered materials in the scene (e.g. VRayBlendMtl) and the Max depth parameter of the Profiler is set to 8, no more than 5 ray bounces are displayed in the profile. Make sure to lower the Max depth for an accurate reading of such a scene.
2. When reading a Profiler report in a browser, keep in mind that only up to 16 simultaneous events can be displayed. Simultaneous events are stacked down on each other when displayed this way and only up to 16 can fit at the same time, even though V-Ray can render more.
3. If you are rendering a scene with Bitmaps multiple times, the Bitmaps will not be read by the Profiler after the first render. To profile the Bitmaps after the initial render, you need to go to **Render Settings** > **Overrides**> **Rendering** and click on **Clear bitmap cache**. Then you can proceed with a second render.