Build a FiveM carpack from scratch

Adding vehicles to FiveM is the most common first project for server owners. A carpack bundles everything - 3D models, textures, audio, handling data - into one resource. This lesson walks through the full structure using a real working example (Karin 98S), so you can swap in any add-on vehicle.

You'll build: A complete carpack with proper folder structure, spawn code, and fxmanifest that loads automatically.
Time: ~30 minutes
You need: A local FiveM server, a text editor, and the carpack example files.
You'll learn: The carpack folder structure (data/, stream/, audio/), file types (.meta, .yft, .ytd, .awc, .dat, .rel), spawn codes, and fxmanifest auto-integration.

BEFORE YOU START

Build it

Learn the folder structure

You know what each folder and file type does.

Every carpack follows this structure:

code

carpack/
fxmanifest.lua         <- tells FiveM what to load
data/                  <- vehicle metadata
handling.meta        <- physics: mass, traction, suspension
vehicles.meta        <- vehicle definition: model name, type, plates
carvariations.meta   <- color variations and liveries
carcols.meta         <- color definitions
stream/                <- 3D models and textures (streamed to clients)
modelname.yft        <- vehicle 3D model (fragment)
modelname_hi.yft     <- high-detail interior model
modelname.ytd        <- texture dictionary (paint, interior, details)
audio/                 <- engine sounds
modelname.awc        <- audio wave container
modelname.dat        <- audio configuration (rel files reference)
modelname.rel        <- audio relationship data

Build a FiveM carpack from scratch

Build it

Learn the folder structure

Write the fxmanifest

Understand the spawn code

Keep reading the full lesson