FiveM Upvotes
Frameworks & scripts

Streamed assets

Also called stream folder, custom cars, addon vehicles

Models, textures and map data delivered to the player's client at connect time from a resource's stream folder.

Anything the base game does not have — custom vehicles, clothing, weapons, MLO interiors, map edits — reaches the player as streamed assets: files in a resource's stream folder that the client downloads on first connect.

Two costs follow. The first is download size: every megabyte is a player waiting on a loading screen, and the drop-off on a long first connect is severe. A server with 4 GB of streamed content loses players who would have stayed on a 400 MB one. The second is memory: streamed models consume client VRAM whether or not anyone is looking at them, and a server that streams hundreds of vehicles will crash lower-spec players.

The discipline is curation. Compressed textures (YTD files at sane resolutions), vehicles that are actually used, and MLOs that justify their size. Tools exist to audit this, and most servers discover several hundred megabytes of content nobody has touched in a year.

Streamed content is also the usual source of game-build mismatch crashes.

Related terms

ResourceA self-contained folder of scripts, assets and a manifest that the server loads to add functionality.Server artifactsThe versioned FXServer binaries a FiveM server runs on, published by Cfx.re as numbered builds.resmonThe in-client profiler that shows how much CPU time each resource consumes per frame.

Trying to get your server seen?

The live leaderboard shows what the numbers look like at the top of the list, and the upvote calculator turns a target server into a campaign size. The full glossary is here.