Official FiveM documentation points to three things for better frame rates: measure first with cl_drawperf, lower str_maxVehicleTextureRes from its default of 1024 only when memory runs short, and leave nui_useInProcessGpu at its default of false. This guide covers the FiveM client on the PC version of Grand Theft Auto V, both standard FiveM and FiveM for GTAV Enhanced, which are separate products with separate requirements tables. It uses only Cfx.re documentation checked on October 6, 2026, and quotes no 'FPS +N%' figures because the documentation has none. If your drops happen only while you are recording, fixing FPS drops while recording covers that side.
Bottom line: measure, trim, then compare against a server
The official documents give you five checks: hardware and an up-to-date GTA V, measuring with cl_drawfps and cl_drawperf, str_maxVehicleTextureRes when memory is short, keeping nui_useInProcessGpu at its default, and separating server-specific problems. Only str_maxVehicleTextureRes costs you visual quality, so touch it only when your readings point to memory pressure. Registry edits, third-party optimizer tools, hand-editing CitizenFX.ini and graphics mods are not recommended here. If recording is part of your load, reducing GPU load while recording is the companion read.
Order of checks
- 1Confirm your product and GTA V status first — According to the official FAQ (updated September 23, 2026), the FiveM client is for the PC version of Grand Theft Auto V, there are no console plans, and the client cannot run on Linux. Standard FiveM and FiveM for GTAV Enhanced are separate products with separate requirements tables. To play on FiveM servers, your installed GTA V must be up to date. Work out which product you run, then compare against only the matching table below. For the requirements of GTA V itself, read Rockstar's official support page directly.
- 2Record a baseline FPS from the F8 console — Press F8 to open the client console and enter cl_drawfps true, and an FPS counter appears in a corner of the screen. Write the number down in the situations where your frames usually wobble: right after joining, in crowded areas, and while driving. It is a regular command that does not need developer mode.
- 3Read the load with cl_drawperf — cl_drawperf true adds Ping (server round-trip time), PL (packet loss), CPU Usage, GPU Usage and GPU Temp to the FPS readout. When frames drop, compare whether CPU or GPU usage is higher and whether ping or packet loss spikes at the same moment. The documentation gives no percentage that counts as a problem, so use the overlay to compare situations on your own PC.
- 4Use str_maxVehicleTextureRes only when memory is short — This command limits the maximum vehicle texture resolution, and its default is 1024. The official description says it may reduce cases of running low on physical memory but sacrifices quality. Treat it as a candidate when your RAM is near the minimum in the table or when stutter appears only where many vehicles gather, lower it one step at a time, and go back to the default if cl_drawperf shows no change in the same spot. You change it from the F8 console by typing str_maxVehicleTextureRes followed by a number; the documentation recommends no specific number, so try values below the default of 1024 in small steps. The documentation gives no figure for how much FPS it adds.
- 5Check that nui_useInProcessGpu is at its default — nui_useInProcessGpu decides whether CEF uses the in-process GPU, and the default is false. By the official description, turning it on may improve compatibility but lowers NUI performance, and FiveM must be restarted after changing it. If you remember enabling it, turn it off and compare the same situation again.
- 6Compare with a test server and prepare an ETW trace — On the same PC, compare cl_drawperf readings on a FiveM.net test server and on the server you usually join. The documentation describes this order for crashes, and the same comparison helps separate the cause of frame drops. Each community decides how its server operates, so a drop on only one server is a question for that server's operator. If frames still drop on capable hardware, the support article asks for an ETW trace. Unzip the UIforETW release, run UIforETW.exe from the bin folder, launch FiveM, press Ctrl+Win+R when the problem appears, record for a few minutes, and save with Save Trace Buffers; the default location is the etwtraces folder inside Documents.
What the docs say about each item and which way to adjust
| Item | What the official docs describe | Direction |
|---|---|---|
| Standard FiveM requirements (support.cfx.re table) | Minimum: CPU Intel Core 2 Q6600 / AMD Phenom 9850, GPU NVIDIA 9800 GT 1GB and similar, 8GB RAM. Recommended: CPU Intel Core i5 3470 / AMD X8 FX-8350, GPU NVIDIA GTX 660 2GB / AMD HD7870 2GB, 16GB RAM | If you fall below the minimum, hardware is the cause rather than settings. Storage figures differ between documents, so check the current page |
| FiveM for GTAV Enhanced requirements | A separate product. Minimum: Windows 10 (build 1909 or later), CPU Intel Core i7-4770 / AMD FX-9590, 8GB RAM, GPU GTX 1630 4GB / RX 6400 4GB. Recommended: Windows 11, i5-9600K / Ryzen 5 3600, 16GB dual-channel, RTX 3060 8GB / RX 6600XT 8GB | Do not mix the two tables; compare only against the product you installed, and check storage on the current page |
| cl_drawfps | Shows a client FPS counter in a corner of the screen (true/false) | Turn it on to record a baseline FPS |
| cl_drawperf | Shows FPS, Ping (ms), PL (%), CPU Usage (%), GPU Usage (%) and GPU Temp (°C) | At the moment frames drop, see which usage is higher and whether ping or packet loss spikes with it |
| str_maxVehicleTextureRes | Caps the maximum vehicle texture resolution; the default is 1024. It can help when physical memory runs short, at the cost of quality | Lower it from the default only when memory looks short. Revert it if nothing improves |
| nui_useInProcessGpu | Decides whether CEF uses the in-process GPU; the default is false. Compatibility may improve but NUI performance drops, and a restart is required after changing it | Keep the default of false. If it is on, turn it off and restart |
| Test server comparison and ETW trace | The docs say crashes are often specific to a server and suggest checking a FiveM.net test server first; for frame drops on good hardware they ask for an ETW trace | If the test server is fine and only one server drops, ask that server's operator |
Checklist after applying
- I compared against the requirements table for the product I installed (standard FiveM or Enhanced).
- GTA V is up to date.
- I recorded cl_drawperf readings separately for right after joining, crowded areas and driving.
- If I changed str_maxVehicleTextureRes, I checked both the visual change and the readout change, and went back to the default of 1024 when nothing improved.
- I confirmed that nui_useInProcessGpu is false.
- I wrote up my test server comparison so I can hand it to a server operator as it is.
If you want to keep an eye on frames while recording
FiveM is a game DOR supports, and the FiveM game hub collects the related guides. For FiveM you can use full-match automatic recording saved as mp4, while automatic clips such as kill highlights are not offered for this game. Recording also uses CPU and GPU, so use the cl_drawperf overlay from the steps above to compare FPS and usage before and after you start. On an NVIDIA graphics card DOR uses NVENC hardware encoding by default, and it records game sound and your microphone together, which suits roleplay scenes where you want your voice kept. If you wonder how encoder choices differ, read NVENC vs x264.
Official sources
Checked on October 6, 2026. Documents can change, so confirm on the current page. Requirements: FiveM system requirements. Commands: FiveM console commands. Troubleshooting: FiveM Client Issues. The documentation is English-only, so setting and command names are kept as written. The two requirements documents list different storage figures, so those numbers are left out.
