For FiveM Legacy, start by turning off MSAA and Reflection MSAA, reducing Grass Quality to Normal, and leaving Extended Distance Scaling at its minimum. Keep Texture Quality at High if your graphics card has memory headroom; drop it to Normal if loading textures brings hitches. That gives you a practical starting point without making every nearby surface look worse.
Check your edition before copying the rest. FiveM now offers both Legacy and Enhanced, and Enhanced is in Early Access. It requires GTA V Enhanced and has a different rendering menu. A Legacy preset with DirectX 11 and MSAA instructions doesn’t describe that edition.
These are graphics starting choices, not a measured FiveM preset or a promise of a particular FPS. Your server’s scripts, custom vehicles, interiors and population change the workload. If other players teleport while your camera stays smooth, start with the connection and server checks in our FiveM stuttering guide ; lowering shadows won’t address that symptom.
Pick the right FiveM edition
Use the client and GTA V edition your server supports. The official FiveM download page separates Legacy from Enhanced, so check that pairing before reinstalling or changing settings.
The current FiveM homepage lists 4 GB RAM minimum and 8 GB recommended for Legacy, compared with 8 GB minimum and 16 GB dual channel recommended for Enhanced. Those are base client requirements. They don’t guarantee enough memory for a heavy custom server. GTA V Enhanced’s publisher requirements also specify an SSD; the old habit of treating storage as an optional upgrade doesn’t fit that edition.
Enhanced’s ray tracing and upscaling choices need their own treatment. Our GTA V settings guide explains the edition split; the Legacy table below stays focused on the menu it actually describes.
FiveM Legacy graphics starting point
Choose the tradeoff
Find a setting to try first
This tool connects a visible concern to this guide’s starting choices. It does not estimate FPS or diagnose your hardware.
Legacy: try Grass Quality at Normal
This reduces rural vegetation detail. If the countryside becomes too bare for your taste, try High after establishing the first comparison. No current FiveM FPS gain is measured here.
Legacy: compare FXAA by looking at the picture
With MSAA and Reflection MSAA Off, try FXAA if jagged edges bother you. Keep it off if you dislike its softer picture. This is an image choice, not a promised speed improvement.
Legacy: compare Texture Quality at Normal
Use the same troublesome area to see whether reducing texture detail changes the loading symptom. Late textures alone do not prove memory pressure. Leave Extended Texture Budget at its default for the first comparison.
Legacy: reduce Extended Distance Scaling first
Start at the minimum before spending extra rendering work on distant detail. Restore it only if that detail matters to you and the troublesome route remains satisfactory.
Enhanced: use the menu your client exposes
Do not translate the Legacy MSAA or DirectX recipe into an Enhanced configuration file. No current FiveM Enhanced menu capture establishes a best profile here. Its Early Access pure mode also prevents graphics mods.
Use your display’s native resolution initially. It gives you a clear reference picture while you remove costly extras. If rendering remains the limiting factor, resolution is another tradeoff to try after these settings.
| Setting | Start here | What you’re choosing |
|---|---|---|
| Resolution | Native display resolution | Preserve a clear picture while changing effects first. |
| MSAA | Off | Remove multisample anti-aliasing work; expect more visible jagged edges. |
| Reflection MSAA | Off | Give up extra anti-aliasing inside reflections. |
| FXAA | Optional | Try it if jagged edges bother you; keep it off if you dislike its softer picture. |
| Texture Quality | High with memory headroom; Normal when constrained | Keep nearby surfaces readable without overcommitting graphics memory. |
| Grass Quality | Normal when prioritizing FPS | Reduce rural vegetation detail; the visual reduction can be substantial. |
| Shadow Quality | Normal; High if you prefer the extra detail | Choose shadow detail you can afford in the areas you actually play. |
| Extended Distance Scaling | Minimum initially | Avoid spending extra rendering work on distant detail before the nearby scene is satisfactory. |
| Population Density | Lower only where the server allows it to matter | The server can control population; this slider isn’t a universal crowded-server fix. |
Leave other settings unchanged for the first comparison. Applying a giant preset makes it harder to tell which compromise helped and which only made the game uglier.
Spend less on grass and distant detail first
Grass Quality deserves attention if your route leaves the city. GTA V Legacy’s rendering behavior makes dense rural vegetation a different workload from a downtown street. Normal cuts vegetation detail noticeably, so a player who spends most of the evening outside Los Santos has a stronger reason to start there than someone who rarely leaves an interior.
Extended Distance Scaling adds detail beyond the ordinary distance setting and increases detail within it. That’s a luxury worth postponing when the nearby scene already struggles. Reduce it before flattening every texture: distant detail and the legibility of a wall beside your character serve different purposes.
Once the route runs acceptably, raise the setting whose visual loss bothers you most. If Normal grass makes the countryside too bare, try High before restoring the distant detail you’ve just removed. The order reflects what you want to see, rather than a claim that one preset suits every server.
Texture Quality needs memory headroom
Texture Quality is an easy setting to punish for the wrong problem. Lowering it reduces texture detail and can help when graphics memory is constrained, but a low average FPS by itself doesn’t establish that condition.
Keep High if the world loads consistently and your graphics card has room for the server’s assets. If hitches appear as vehicles or interiors load, try Normal and revisit the same area. A stock GTA V memory estimate cannot account for every custom resource the server streams.
The Legacy Extended Texture Budget slider also needs restraint. Start with the default. Raising it isn’t a free repair for missing roads: historical Cfx developer guidance warns that a larger budget can worsen memory pressure on constrained hardware. Reverse the change if hitching worsens. There is no supported rule that maps every VRAM capacity to a particular slider percentage.
Anti-aliasing is a picture choice with a cost
MSAA smooths edges, but Off is the sensible first choice when reducing rendering cost is your priority. Reflection MSAA is a separate setting; turn that off too rather than assuming the main toggle covers it.
FXAA gives you another way to treat jagged edges, with a softer result. Choose it by looking at the picture you actually play: a clean screenshot isn’t useful if distant objects become harder for you to read. Keep the choice separate from texture detail so you can tell which setting changed the image.
FiveM Enhanced: don’t copy the Legacy menu
Enhanced introduces rendering options that the Legacy shortlist doesn’t cover, including ray tracing and upscaling choices. Use the settings your current client exposes, with our GTA V edition comparison as background, rather than assuming a Legacy menu choice has an Enhanced equivalent.
We don’t have a current FiveM Enhanced menu capture or same-hardware benchmark that establishes a best ray-tracing combination, upscaling mode or FPS result. Don’t paste a Legacy DirectX or MSAA recipe into an Enhanced configuration file. Preserve the picture you can use during movement, including distant vehicles and road markings, when evaluating its available options.
Enhanced Early Access currently runs with pure mode enabled, and Cfx’s migration documentation says graphics mods are unavailable. Leave QuantV, NaturalVision and shader-pack instructions out of this edition’s tuning plan. Mod support is a compatibility question before it becomes a visual preference.
Decide whether a change helped
One change, same route
Keep a useful tuning note
Write what you changed and what you observed. The note organizes your own comparison; it does not certify a performance gain.
Enter your observations, or edit the note directly.
Open the F8 console and enter:
cl_drawperf trueFiveM’s user overlay shows FPS, ping and packet loss separately. Return to the same server and repeat the same route, including the busy area or interior that causes trouble. Change one setting, then repeat that route. An empty car park is a poor substitute for the junction where your camera keeps hitching.
Watch consistency as well as the FPS number. A setting that raises the average while leaving the troublesome pause unchanged hasn’t finished the job. Turn the overlay off with:
cl_drawperf falseVSync and a frame-rate limit involve your display, tearing tolerance and sustainable frame rate. Keep them fixed during a graphics comparison so they don’t hide the effect of the setting you changed. Afterwards, choose a cap your demanding route can sustain and judge the result. There isn’t a universal FiveM cap that guarantees stable physics or removes input lag.
If several graphics cuts barely change the symptom, move to diagnosis rather than another settings dump. A resource can consume client CPU time, assets can load poorly, and network updates can arrive late. Low aggregate CPU or GPU usage doesn’t distinguish those causes on its own.
Leave the miracle tweaks out
Skip enormous shader-cache allocations, forced game-build numbers and routine cache deletion as a general FPS recipe. They add changes without establishing why the game is slow. Server compatibility belongs to the server owner, and repeatedly deleting downloaded resources isn’t a substitute for identifying a hitch.
The useful next step is specific: retain the graphics tradeoffs that improved your route, then investigate any remaining repeatable symptom. If the issue follows a particular interior, vehicle or action, the server administrator needs that detail more than another screenshot of a low FPS counter.
Frequently asked questions
What are the best FiveM settings for low-end PCs?
For Legacy, start with MSAA and Reflection MSAA Off, Grass Quality Normal and Extended Distance Scaling at minimum. Use Normal textures when memory is constrained. These are starting choices; server assets and scripts can leave performance problems that graphics settings won’t resolve.
Does this preset work in FiveM Enhanced?
The table describes Legacy. Enhanced requires GTA V Enhanced and has different rendering options. Use its current menu rather than copying Legacy settings; no measured Enhanced preset or FPS target is established here.
Should I lower Texture Quality for more FPS?
Lower it when texture loading or graphics-memory pressure is the concern. High can preserve nearby detail when there is headroom. Don’t assume a low FPS reading alone means textures are the cause.
What should I set Extended Texture Budget to?
Start at the Legacy default. A larger budget can worsen memory pressure, so reverse a change if hitches increase. There is no universal percentage for each VRAM capacity.
Should I cap FPS in FiveM?
A cap is a display and consistency choice. Choose one your demanding route can sustain, keep it fixed while comparing graphics settings, and judge tearing and pacing afterwards. No single cap guarantees a latency or physics improvement.
Can I use graphics mods in FiveM Enhanced?
Cfx’s current Enhanced Early Access documentation says graphics mods are unavailable because pure mode is always enabled. Don’t follow Legacy graphics-pack instructions for Enhanced.
Will clearing FiveM cache fix low FPS?
Routine cache deletion isn’t an established general FPS fix. Identify whether the symptom involves rendering, resource execution, streaming or network updates before changing downloaded files. Follow specific support instructions when troubleshooting a particular error.
Why is FiveM slower on one server than another?
Servers can expose you to different scripts, assets, populations and locations. A second-server comparison helps identify workload dependence, but doesn’t prove the first server is solely responsible or that your PC has enough headroom for it.
Youtube