How to Reduce NPC Density in FiveM: Complete Guide

Launch faster

Compare curated bundles

Bundles shorten the path from planning to launch by grouping the highest-leverage scripts into a cleaner commercial starting point.

The Core Density Functions

There are five primary natives you need to know:

1. SetVehicleDensityMultiplierThisFrame(multiplier) - Controls moving traffic.
2. SetPedDensityMultiplierThisFrame(multiplier) - Controls walking pedestrians.
3. SetRandomVehicleDensityMultiplierThisFrame(multiplier) - Controls parked/random cars.
4. SetParkedVehicleDensityMultiplierThisFrame(multiplier) - Controls static parked cars in lots.
5. SetScenarioPedDensityMultiplierThisFrame(multiplier, multiplier) - Controls NPCs doing activities (smoking, drinking coffee, sitting).

The multiplier is a float value between 0.0 (completely disabled) and 1.0 (default GTA V density).

How to Create the Density Control Script

We will create a lightweight, standalone resource to handle this so it does not interfere with your other scripts.

Step 1: Create the Folder Structure

1. Navigate to your server's resources folder.
2. Create a new folder named traffic_control.
3. Inside traffic_control, create two files: fxmanifest.lua and client.lua.

Step 2: Configure the fxmanifest.lua

Open fxmanifest.lua and define the resource. This tells FiveM to load your client script.

fx_version 'cerulean'
game 'gta5'

author 'FiveMX'
description 'Controls NPC and Traffic Density'
version '1.0.0'

client_script 'client.lua'

Step 3: Write the Client Script (client.lua)

Open client.lua and insert the following code. This example reduces all traffic and pedestrians to 20% of their normal volume, which is the "sweet spot" for active RP servers.

-- Set the desired density multiplier (0.0 to 1.0)
local densityMultiplier = 0.2 

Citizen.CreateThread(function()
    while true do
        Citizen.Wait(0) -- Must run every frame
        
        -- Apply the multipliers
        SetVehicleDensityMultiplierThisFrame(densityMultiplier)
        SetPedDensityMultiplierThisFrame(densityMultiplier)
        SetRandomVehicleDensityMultiplierThisFrame(densityMultiplier)
        SetParkedVehicleDensityMultiplierThisFrame(densityMultiplier)
        SetScenarioPedDensityMultiplierThisFrame(densityMultiplier, densityMultiplier)
        
        -- Optional: Disable AI emergency services
        -- This prevents AI cops/medics from responding to player crimes
        local playerPed = GetPlayerPed(-1)
        local pos = GetEntityCoords(playerPed) 
        ClearAreaOfCops(pos.x, pos.y, pos.z, 400.0)
    end
end)

Complete Eradication (Zero NPCs)

If you are running a drift server or a pure PvP arena, you likely want zero AI. Simply change local densityMultiplier = 0.2 to 0.0.

You may also want to add garbage cleanup to remove broken AI vehicles:

-- Add inside the while loop if multiplier is 0.0
SetGarbageTrucks(false)
SetRandomBoats(false)

Advanced Tip: Dynamic Density

Running a zero-wait thread (Citizen.Wait(0)) is standard for these frame-based natives, but if you want to optimize even further, you can adjust the density based on the current player count.

Many advanced servers use server-side callbacks to check how many players are online:

• 0–30 Players: 0.8 Density (Make the city feel alive when it's quiet).
• 30–80 Players: 0.4 Density (Balance performance).
• 80+ Players: 0.0 Density (Players populate the city entirely, max performance).

Recommended Density Presets by Server Type

The biggest mistake is treating every server the same. A whitelisted city with 90 active civilians should not use the same density profile as a casual public freeroam server.

If you are unsure, start at 0.2 across the board, run a test event with 15-20 players, and profile the server before going lower.

Example: Dynamic Density by Player Count

This pattern keeps quiet hours immersive without punishing peak-time performance:

local function getDensityForPlayerCount(playerCount)
    if playerCount >= 80 then
        return 0.0
    end

    if playerCount >= 40 then
        return 0.2
    end

    return 0.5
end

Citizen.CreateThread(function()
    while true do
        Citizen.Wait(5000)
        LocalPlayer.state.trafficDensity = getDensityForPlayerCount(#GetActivePlayers())
    end
end)

Citizen.CreateThread(function()
    while true do
        Citizen.Wait(0)
        local densityMultiplier = LocalPlayer.state.trafficDensity or 0.2
        SetVehicleDensityMultiplierThisFrame(densityMultiplier)
        SetPedDensityMultiplierThisFrame(densityMultiplier)
        SetRandomVehicleDensityMultiplierThisFrame(densityMultiplier)
        SetParkedVehicleDensityMultiplierThisFrame(densityMultiplier)
        SetScenarioPedDensityMultiplierThisFrame(densityMultiplier, densityMultiplier)
    end
end)

The exact threshold values are less important than the operating principle: more players in the city means ambient AI should get out of the way.

Common Problems and Fixes

If density changes look inconsistent, the issue is usually not FiveM itself but resource interaction:

• Traffic returns after a few seconds: Another resource is likely calling the same natives with a higher value. Search your resource folder for SetVehicleDensityMultiplierThisFrame.
• Only some NPCs disappear: Scenario peds or parked vehicles are still enabled, so the world feels half-cleaned. Lower all five density groups together first, then fine-tune.
• Police keep spawning anyway: Ambient density and emergency-service cleanup are separate concerns. Use ClearAreaOfCops or disable wanted-level systems if needed.
• World feels too empty at low population: Raise only peds and parked cars slightly before reintroducing moving traffic.

Integration with Other Resources

Ensure that your new traffic_control script is added to your server.cfg:

ensure traffic_control

If you are using reliable frameworks like QBCore or ESX, ensure this script starts after the framework to prevent base resources from overriding your native calls.

Validation Checklist Before You Ship It

Before pushing density changes to production, verify these four points:

1. Resmon stays stable with the script running in a busy area for several minutes.
2. Two players in the same district see the same road state instead of different ghost vehicles.
3. Mission-critical resources like police jobs, delivery scripts, or custom traffic scripts still behave as expected.
4. Your city does not feel unnaturally dead during low-population hours.

That last point matters. Performance wins are real, but the right target is not "zero NPCs everywhere forever." The right target is "enough ambient life to support immersion, but not enough to waste sync budget."

Conclusion

Reducing NPC density is the simplest, most effective modification you can make to improve server stability and hit registration. Whether dialing it down for performance or turning it off completely for competitive gameplay, a few lines of Lua code will drastically improve the player experience.

Looking to optimize further? Check out our guides on migrating data properly from MySQL Async to OxMySQL or explore high-performance FiveM Scripts built with optimization in mind.