Fast answer: use the FiveM client console and graphics/performance tools to check FPS, then use Resmon or the profiler when you need to diagnose resource cost. FPS is a client-side frame rate number. It is not the same thing as server tick health.
Last updated: June 25, 2026
Open the FiveM console
- Launch FiveM.
- Press
F8to open the console. - Use client commands or diagnostics depending on what you need to inspect.
The official Cfx.re client command docs describe the F8 console as the place for client-side commands. For resource performance, the Cfx.re fact sheet points to Resmon and the profiler as the tools to identify expensive resources.
FPS vs Resmon vs server hitch warnings
| Signal | What it tells you | Who should use it |
|---|---|---|
| FPS counter | How smoothly the local client renders frames. | Players and testers. |
| Resmon | Which client resources cost CPU time. | Developers and server owners. |
| Profiler | Detailed resource performance traces. | Developers debugging expensive code. |
| Hitch warnings | Server or resource stalls that need investigation. | Server owners. |
Quick client-side checks
- Lower extended texture budget or graphics settings if FPS is low everywhere.
- Disable heavy graphics mods before blaming a server resource.
- Test in a quiet area and a busy city area.
- Compare two servers to separate local PC limits from one server’s resource stack.
When FPS drops only on one server
If your FPS is fine elsewhere but bad on one FiveM server, check loaded resources, large MLOs, dense vehicle areas, clothing packs, and unoptimized scripts. Use Resmon to identify expensive client resources instead of guessing.
Server owner workflow
- Ask testers for PC specs, average FPS, and location in the city.
- Use Resmon to find expensive resources.
- Check txAdmin/server console for hitch warnings.
- Disable the latest changed resource and compare again.
- Fix the resource, not the whole server, when the issue is isolated.
Related guides
- How to use Resmon in FiveM
- FiveM server optimization guide
- Best FiveM settings to boost FPS
- How to check txAdmin logs
How to report FPS problems usefully
“Laggy” is not enough information for a developer. Ask testers for location, player count, average FPS, worst FPS, GPU, CPU, graphics preset, and whether the issue happens on other servers. With that context you can separate a weak client PC from a bad resource.
Client-side fixes to try first
- Lower texture and shadow settings.
- Disable ReShade, ENB, or heavy graphics mods for one test.
- Update GPU drivers.
- Test without background recording software.
- Clear FiveM cache if stutters started after a resource update.
Server-side fixes to investigate
If many players drop frames in the same place, inspect nearby MLOs, vehicle density, clothing packs, and scripts that run every frame. Pair FPS reports with Resmon readings and txAdmin logs. Fix the resource that spikes instead of removing random scripts from the server.
How to report FPS problems clearly
A useful FPS report includes location, player count, average FPS, worst FPS, graphics preset, GPU, CPU and whether the issue happens on other servers. That context separates a weak client PC from a heavy server area, bad MLO, expensive HUD or script that runs too often.
First checks before blaming the server
- Test with ReShade, ENB and recording software disabled.
- Lower shadows, textures and population settings for one comparison.
- Try the same area after clearing FiveM cache if stutter started after updates.
- Compare FPS with Resmon open when you suspect a resource problem.
Server-side interpretation
If many players lose FPS in the same block, inspect nearby MLOs, props, vehicles, clothing density and UI resources. If only one player has low FPS everywhere, focus on that PC. Treat FPS reports as evidence to narrow the search, not as proof that one script is broken.
Useful support template
Ask players for their PC specs, graphics preset, screenshot of the location, approximate player count and whether recording software was running. That template gives staff enough information to compare reports instead of answering every complaint from scratch.
Keep the first response short. Ask for evidence, then test the same area yourself. Long debates about FPS rarely help until you have comparable data.
When several reports point to one location, check that area before changing global client advice.
If the location contains a new interior or many streamed props, test that area with a clean client too.
