Generating a Profiler Recording

If you are experiencing performance issues, low FPS, or server hitches, our support team may ask you for a Profiler Recording. This file contains detailed information about which scripts are consuming the most resources on your server or client.

Providing a profiler recording allows us to pinpoint the exact lines of code causing issues, significantly speeding up the troubleshooting process.

How to Capture a Recording

Follow these steps to generate the data needed for a support ticket.

Start the Recording

Open your console (F8 on the client, or the server console) and type:

profiler record 500

This will record 500 frames of performance data. If the issue is intermittent, you may want to increase this number (e.g., profiler record 1000).

Reproduce the Issue

While the profiler is recording, perform the actions that cause the performance drop or wait for the server hitch to occur.

Save the Recording

Once the recording is finished (you will see a message in the console), save it to a file by typing:

profiler saveJSON my_profile.json

What to Send to Support

To help us diagnose your issue, please provide the following in your support ticket:

The .json file: Locate the my_profile.json file.

For server-side issues, it is in your server's root folder (where run.bat or FXServer.exe is located).
For client-side issues, it is in your FiveM application data folder.

Technical Details (Optional)

If you wish to view the data yourself before sending it, you can load the file into Google Chrome:

Open Google Chrome.
Press F12 or CTRL + SHIFT + I to open Developer Tools.
Navigate to the Performance tab.
Right-click anywhere in the main panel and select Load profile....
Select your my_profile.json file.

Our team uses this data to look for "Resource Tick" spikes, which indicate exactly which script, file, and line of code is causing the performance bottleneck.