Use the profiler to find slow scripts

FiveM ships with a built-in profiler that shows exactly which lines of code are eating CPU time. It uses the same profiler record console command on both client (F8) and server. This lesson teaches you to capture a trace, open it in Chrome's built-in viewer, and read the flame graph so you stop guessing and start measuring.

You'll build: A captured profiler trace that pinpoints the exact function and line causing hitch warnings on your server.
Time: ~20 minutes
You need: A local FiveM server with at least one script running, Google Chrome installed.
You'll learn: Capturing a client and server profile, reading the flame graph, and identifying which function spends the most time.

BEFORE YOU START

Build it

Record a profile

The profiler captures a fixed number of frames, then auto-stops.

Join your server and open F8. To profile the client, run the record command with a frame count. It records that many frames and stops on its own:

code

profiler record 500

While it records, check progress at any time:

code

profiler status

Server-side profiling uses the SAME command. Run profiler record 500 in the server console (txAdmin Live Console or the FXServer window) instead of F8. There is no separate txAdmin profiler UI. The console command is the tool on both sides.

Use the profiler to find slow scripts

Build it

Record a profile

Open the trace

Read the flame graph

Fix and verify

Keep reading the full lesson