FiveM Vehicle Streaming: Add 500+ Cars Without Lag

Adding 50 vehicles to a FiveM server is trivial. Adding 500 breaks servers that were not built for it. Streaming dictionaries and model files consume both client VRAM and server streaming bandwidth — exceed FiveM's per-resource limits and vehicles randomly fail to load or cause client crashes. This guide covers the architecture that prevents both.

How FiveM Vehicle Streaming Works

FiveM loads vehicle models (.yft files) and texture dictionaries (.ytd files) on demand as players enter the stream range of a vehicle. The client maintains a global streaming budget — roughly 1 GB in the default configuration — shared across all active resources.

A single vehicle typically ships as a pair: one .yft model file and one .ytd texture file, averaging 6–14 MB combined. At 500 vehicles and 8 MB average, the total asset footprint is 4 GB — four times what a single resource can safely hold.

Splitting Across Multiple Resources

The solution is to split the vehicle pack across 4–6 stream resources, each holding roughly 100 cars. Never place more than 150 vehicle model pairs in a single resource's stream/ folder.

resources/
  [vehicles]/
    vehicles-pack-1/    ← 100 cars (~850 MB assets)
      fxmanifest.lua
      stream/
    vehicles-pack-2/    ← 100 cars (~850 MB assets)
      fxmanifest.lua
      stream/
    vehicles-pack-3/    ← 100 cars
    vehicles-pack-4/    ← 100 cars
    vehicles-pack-5/    ← remaining + all scripts (garage, keys, tuning)

Keep all Lua scripts in a single resource (vehicles-pack-5 above). Scripts do not need to be co-located with their stream assets — they reference vehicles by model name, not by resource path.

Resource Manifest Best Practices

Each streaming resource needs a minimal fxmanifest.lua. For pure stream resources (no Lua):

fx_version 'cerulean'
game 'gta5'

-- No client/server scripts needed for stream-only resources
-- FiveM auto-discovers files in stream/

For the script resource (the one with garage, keys and tuning):

fx_version 'cerulean'
game 'gta5'

client_scripts { 'client/*.lua' }
server_scripts { 'server/*.lua' }
shared_scripts  { '@ox_lib/init.lua', 'shared/*.lua' }

dependency 'ox_lib'

Handling Files and Vehicles.meta

Every addon vehicle requires correct handling.meta and vehicles.meta entries. Batch-verify them by starting your server in development mode and watching for streaming errors in the console. Common indicators of bad handling data:

• Vehicle spawns and immediately flips or has extreme bounce
• Console shows [citizen-server-impl] Couldn't load meta
• Vehicle name does not appear in /car [name] autocomplete

Testing Performance with the Profiler

After installing all stream resources, test with a full player load rather than alone. In the F8 console:

profiler record 100   -- record 100 frames
profiler save         -- save to disk for inspection

Open the saved profile in the FiveM resource profiler (accessible via the txAdmin UI). Look at streaming thread time — under 8ms is good; above 15ms with most players in the same area means your split strategy needs another pass.

For a fully pre-configured 530-car pack that handles all of this automatically, see the FiveM Vehicle Pack — split resource structure, correct handling files and garage integration included.