How to Create a FiveM Car Pack by Hand: Merging Meta Files and Stream Folders

The manual method for combining several converted vehicles into one resource: folder layout, merging vehicles.meta, handling.meta and carvariations.meta, the manifest, and the mistakes that break a pack.

Updated 6 min read11 sections

Want the pack without the manual merging? The Car Pack Builder combines the cars into one resource with a single manifest and checks for conflicts. Open the Car Pack Builder

Manual Method or the Builder?

Note

This guide is the manual method: what a car pack is made of and how to merge the files yourself. If you only want the finished pack, the Car Pack Builder does the same job in the browser; follow the Car Pack Builder tutorial instead.

Doing it by hand once is still worth it. When a pack breaks six months from now, you will know which file to open.

Why Use Car Packs?

As your FiveM server grows, you add more and more vehicles. A hundred individual folders for a hundred cars means a hundred manifests to load, a hundred ensure lines and a server.cfg nobody wants to read. FiveM server resource limits covers where that starts to hurt.

A car pack combines multiple vehicles into a single resource folder. It is cleaner and much easier to manage. Group by purpose (police_pack, civ_pack, dealership_pack) rather than building one giant pack, so you can replace one group without touching the rest.

Step 1: Convert Your Vehicles

Before you can make a pack, you need the individual FiveM resources.

  1. Find the cars you want on GTA5-Mods.com.
  2. Use GTA5 Mods Convertor to convert each one (how conversion works).
  3. Download and extract them to your desktop.
  4. Make sure each car works on its own first. A pack merges resources; it does not repair them. The Resource Inspector checks one in a few seconds.

Tip

Converting dozens of cars in one sitting? A desktop queue can be quicker than pasting links one at a time; our rpf2fivem comparison sets out when each approach fits.

Step 2: Create the Pack Structure

Create a new folder named my_car_pack. Inside it, create:

Warning

Do not put the pack name in square brackets. A folder like [cars] is a category that holds resources; it is not a resource itself, and FiveM will not read a manifest placed directly inside it. Your pack can live inside one: resources/[cars]/my_car_pack/.

Step 3: Move the Streaming Files

Take all the model and texture files from every car and move them into the pack's stream/ folder. Subfolders are fine and keep things tidy:

text
my_car_pack/
├── fxmanifest.lua
├── data/
└── stream/
    ├── bmwm4/
    │   ├── bmwm4.yft
    │   ├── bmwm4_hi.yft
    │   └── bmwm4.ytd
    └── rs6avant/
        ├── rs6avant.yft
        ├── rs6avant_hi.yft
        └── rs6avant.ytd

Two things to check while you copy:

  • File name clashes. Two cars that both ship a file with the same name but different content (wheel or shared texture dictionaries are the usual suspects) cannot both win. Only one copy is streamed.
  • Oversized files. An asset above the 16 MiB warning is just as unreliable inside a pack. Shrink it first with the Texture Optimizer; for a whole folder at once, Glory Optimizer works on your PC.

Step 4: Merge the Meta Files

This is the step that matters. Every car arrives with its own set of meta files, and the game needs to see all of them. You have two options.

Option A: One merged file per type

Open the vehicles.meta of every car. Copy each <Item> block found inside <InitDatas> (from the opening <Item> to its closing </Item>) and paste them one after another inside the <InitDatas> section of the pack's data/vehicles.meta. If a car also has entries under <txdRelationships>, copy those into the same section of the merged file.

Do the same for the other files:

  • handling.meta: each <Item type="CHandlingData"> block inside <HandlingData>
  • carvariations.meta: each <Item> block inside <variationData>
  • carcols.meta (only cars with tuning parts or sirens): each <Item> inside <Kits>, plus any siren settings

Option B: Keep one data folder per car

Skip the merging and keep each car's meta files in their own subfolder (data/bmwm4/, data/rs6avant/), then declare each file in the manifest. It is more lines in fxmanifest.lua but there is no XML editing, and removing a car later means deleting two folders and a few lines. This is the layout the Car Pack Builder writes.

Warning

Whichever option you choose, mod kit IDs in carcols.meta must be unique across the whole server, not only inside the pack. Two cars sharing a kit ID end up with each other's tuning parts.

Step 5: Configure the Manifest

For Option A the fxmanifest.lua looks like this:

lua
fx_version 'cerulean'
game 'gta5'

files {
    'data/**/*.meta'
}

data_file 'HANDLING_FILE' 'data/handling.meta'
data_file 'VEHICLE_METADATA_FILE' 'data/vehicles.meta'
data_file 'VEHICLE_VARIATION_FILE' 'data/carvariations.meta'
-- only if the pack has one:
data_file 'CARCOLS_FILE' 'data/carcols.meta'

For Option B, keep the same files block and repeat the data_file lines once per car:

lua
data_file 'HANDLING_FILE' 'data/bmwm4/handling.meta'
data_file 'VEHICLE_METADATA_FILE' 'data/bmwm4/vehicles.meta'
data_file 'VEHICLE_VARIATION_FILE' 'data/bmwm4/carvariations.meta'

data_file 'HANDLING_FILE' 'data/rs6avant/handling.meta'
data_file 'VEHICLE_METADATA_FILE' 'data/rs6avant/vehicles.meta'
data_file 'VEHICLE_VARIATION_FILE' 'data/rs6avant/carvariations.meta'

The FXManifest Generator writes a valid starting manifest if you would rather not type it.

Step 6: Test

  1. Add ensure my_car_pack to your server.cfg.
  2. Restart the server and watch the console while the pack starts.
  3. Spawn every car in the pack, one by one.

Common Mistakes

  • "Invalid Model" after merging. Usually a missing closing tag (</Item>) from copy-pasting, which makes the game discard the whole file. Work through fixing 'Invalid Model' errors.
  • One car has another car's handling. Two handlingName entries with the same name; rename one and update that car's handlingId.
  • Duplicate spawn names. Two cars with the same <modelName> cannot coexist. Rename the model files and every reference in one of them.
  • Police pack with dead light bars. ELS vehicles also need their VCF file installed: see installing ELS police cars.

Manual Merge vs. Car Pack Builder

By hand (this guide)Car Pack Builder
Time for 20 carsHoursMinutes
Duplicate spawn names and kit IDsYou find them when something breaks in gameListed before you download
Identical duplicate filesRemoved by handRemoved automatically
CostFreeFree up to 3 cars per pack, any size with the $15 Unlimited plan

It is the same trade-off described in manual vs. automated conversion: the manual route teaches you the format, the tool gets the pack onto the server.

After the Pack Is Installed

A pack makes its cars spawnable; it does not put them in a dealership. Every car in it still needs its own entry in your framework's vehicle list: see the guides for the QBCore vehicle shop, the ESX vehicle shop and Qbox's vehicle list.

Have a gta5-mods.com link ready?

Paste it into the converter and download a FiveM resource with the stream folder, meta files and fxmanifest.lua in place.

  • 3 conversions free, no account needed
  • 2 more free if you leave an email
  • After that: $15 once for unlimited conversions and the Pro tools. No subscription, 14-day refund policy