# Improving FPS on FiveM

> Improve FiveM FPS from both sides: player graphics settings, resmon for heavy client scripts, server-side causes like huge MLOs and textures, and NUI HUD costs.

Source: https://fam-tools.com/guides/fivem-client-fps-optimization · FAM Tools · published 2026-09-11 · updated 2026-09-11 · about 10 min

**Short answer.** Players: lower texture quality and extended distance scaling, reduce shadows and MSAA, and clear the cache if textures misbehave. Server owners: open `resmon` in game to find client scripts using more than a fraction of a millisecond, fix oversized textures and heavy MLOs, avoid streaming dozens of heavy cars at once, and keep NUI HUDs cheap. Together those recover most lost frames.

## Key points

- Server content decides much of client FPS.
- `resmon` shows the client cost of every resource.
- Oversized textures cause stutter and texture loss.
- HUDs and loops running every frame add up.
- Players: textures, distance scaling and shadows first.

Low FPS on a FiveM server is rarely only the player’s PC. The same machine can run one server at a steady 100 FPS and another at 40, because the server decides how heavy the world is: scripts running every frame, huge textures, dense MLOs and HUDs that redraw constantly. Both sides have levers.

## Player-side settings

| Setting | Suggestion |
| --- | --- |
| Texture quality | High instead of Very High on cards with less VRAM |
| Extended distance scaling | Low — big FPS gain in cities |
| Shadow quality / soft shadows | Normal / Sharp |
| MSAA | Off; use FXAA |
| Grass quality | Normal |

If textures stay broken after server updates, clear the cache — see [clearing FiveM cache](https://fam-tools.com/guides/fivem-clear-cache).

## Finding heavy scripts with resmon

Type `resmon 1` in F8. Each resource shows its client CPU time. Idle resources should sit at 0.00–0.02 ms; anything constantly above 0.1–0.2 ms deserves a look, and several of them together cost real frames. Script-side fixes: [Lua performance](https://pityus.net/guides/fivem-lua-performance-optimization).

## Server-side causes

- Oversized textures in cars, clothing and MLOs — see [oversized assets](https://fam-tools.com/guides/fivem-oversized-assets-warning).
- Many MLOs in one area, each with its own textures and props.
- Traffic and ped density set high — see [traffic and ped density](https://fam-tools.com/guides/fivem-traffic-ped-density).
- Heavy add-on vehicles replacing common traffic cars.
- NUI HUDs updating every frame.

## Owner checklist

1. Walk the busiest area with `resmon 1` open and note the top five resources.
2. Fix or replace scripts that never go idle.
3. Resolve the largest oversized-asset warnings.
4. Review MLO density downtown.
5. Measure FPS in the same spot before and after each change.

## Questions

### Why is my FPS low on one FiveM server but fine on another?

Servers differ in scripts, streamed assets and MLOs. A heavy server costs frames on any PC.

### What settings give the most FPS in FiveM?

Lower extended distance scaling, shadows and MSAA, and use High instead of Very High textures on limited VRAM.

### How do I see which script lowers my FPS?

Open `resmon 1` in F8 and look for resources with high client time.

### Does clearing cache improve FPS?

It fixes broken or outdated textures; it does not make a heavy server light.

## Related

- https://fam-tools.com/guides/fivem-texture-budget-streaming-memory
- https://fam-tools.com/guides/fivem-oversized-assets-warning
- https://fam-tools.com/guides/fivem-clear-cache
- https://fam-tools.com/guides/fivem-too-many-resources