What the profiler actually captures

FiveM ships a native profiler — no resource changes, no external tools needed. Running profiler record 500 tells the Citizen Lua scheduler to time every thread in every resource for 500 consecutive ticks. This includes escrowed resources, so nothing hides from it.

The output is a standard Chrome Trace Event file. This tool processes it entirely inside your browser — nothing is sent to any server. Run profiler saveJSON myprofile then grab myprofile.json from your server's resources/ folder and drop it in.

Why 50ms is your hard limit

The server runs at 20 ticks per second, so each tick has a 50ms window. Inside that window every active resource runs its threads, event handlers, and callbacks — back to back, in one queue.

Script time is the total Lua execution across all resources in that window. Keep it under 10ms and the server has plenty of headroom left for networking and entity sync. Push past 30ms and you're eating into that headroom hard — players will notice as rubber-banding and delayed inputs.

Reading the resource breakdown

Grade thresholds

Calculated from average script ms per tick and the percentage of ticks that exceeded 25ms.

How to capture a profile

1. 1Get into your txAdmin live console while players are on the server.
2. 2Run profiler record 500. This instruments every resource for 500 ticks (~25 seconds).
3. 3Wait for the console to confirm the recording is done. Don't restart or stop anything.
4. 4Run profiler saveJSON myprofile to export the results.
5. 5Grab myprofile.json from the resources/ folder on your server.
6. 6Drop it on the Profiler Analyzer tab and the results appear instantly.

Always profile with real players connected. An empty or near-empty server will show almost nothing useful.