Skip to main content
When a FiveM server struggles, the console shows hitch warnings and players notice rubber-banding and delays. This guide explains what the warnings mean, how to find the script that causes them and how to fix it.

Difficulty

Intermediate

Time

20 minutes

​
What hitch warnings mean

The server works in short ticks. A hitch warning means one tick took far longer than it should. The number is how long the server was busy, in milliseconds. A few warnings during start-up, while resources load, are normal. Warnings that keep coming while players are online need fixing.
Check Statistics in the sidebar too. If CPU or memory sits at your plan’s limit, the server simply has too little room. See how to view server statistics.

​
Find the slow script with the profiler

FXServer has a built-in profiler that records what each resource does.
1

Record while it lags

Wait until the server is busy or hitching. In the Console, type:
This records the next 500 frames. Type profiler status to see how far it is.
2

Save the recording

When it’s done, type:
3

Download it

Open Files, find profile.json (it’s saved in the folder the server runs from, usually the main folder) and download it. See how to use the file manager.
4

Open it in Chrome

In Google Chrome, open the developer tools (F12), go to the Performance tab and load the file. Look for long bars: the resource name tells you which script used the time.

​
Check scripts on your own PC with resmon

Lag can also come from client scripts, which run on each player’s PC. In FiveM, press F8 and type:
The resource monitor lists every resource with its CPU time and memory. A resource that stays high while you do nothing is a good suspect. Type resmon 0 to close it.

​
Fix common causes

If a paid script causes the hitches, contact its author with your profiler file. They know their code best.

​
OneSync and performance

Keep OneSync set to On on the Server config page. It is the mode Cfx.re recommends, and modern scripts expect it. Legacy is an old compatibility mode and isn’t recommended.

​
Restart regularly

A daily restart clears memory that scripts don’t release and keeps the server fresh. Set one up in Schedules with a warning message first, or use txAdmin’s scheduled restarts. Use one of the two, not both.

​
When to upgrade

Consider a bigger plan when:
  • Statistics shows CPU or memory at the limit during your busy hours, even after you’ve removed slow scripts.
  • Your community has grown and you want more player slots.
  • You run a full framework with many scripts, cars and maps.
Upgrade in the client area. Not sure what you need? Open a ticket and share a log link and your player count.

Server configuration

OneSync, slots and FXServer builds.

Resources

Load order and removing resources.

Server statistics

CPU, memory and network over time.

Troubleshooting

Fix other common problems.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: October 2026