FiveM vehicles.meta Generator

Pick a body template that mirrors a stock GTA V vehicle, enter your spawn name, and get vehicles.meta, carvariations.meta, a vehicle_names.lua for the display name and a matching fxmanifest.lua. Every value you do not type is copied from the game's own entry for that stock vehicle.

Identity

Classification

From stock comet2: VEHICLE_TYPE_CAR, seat layout LAYOUT_LOW, first-person drive-by entries, cover offsets, cameras, wheel scale, LOD distances and the shared texture parent vehicles_comet_interior. Changing the template resets the fields below to that vehicle's values. Pick the closest body shape: seats and doors must match your model.

Flags

Colour combos (carvariations.meta)

Combo 1

Combo 2

Combo 3

Combo 4

A generic stock kit. Use your own kit name only if you ship a carcols.meta that defines it.

<?xml version="1.0" encoding="UTF-8"?>
<CVehicleModelInfo__InitDataList>
  <residentTxd>vehshare</residentTxd>
  <residentAnims />
  <InitDatas>
    <Item>
      <modelName>mycar</modelName>
      <txdName>mycar</txdName>
      <handlingId>MYCAR</handlingId>
      <gameName>MYCAR</gameName>
      <vehicleMakeName />
      <expressionDictName>null</expressionDictName>
      <expressionName>null</expressionName>
      <animConvRoofDictName>null</animConvRoofDictName>
      <animConvRoofName>null</animConvRoofName>
      <animConvRoofWindowsAffected />
      <ptfxAssetName>null</ptfxAssetName>
      <audioNameHash>comet2</audioNameHash>
      <layout>LAYOUT_LOW</layout>
      <coverBoundOffsets>COMET_COVER_OFFSET_INFO</coverBoundOffsets>
      <explosionInfo>EXPLOSION_INFO_DEFAULT</explosionInfo>
      <scenarioLayout />
      <cameraName>DEFAULT_FOLLOW_VEHICLE_CAMERA</cameraName>
      <aimCameraName>DEFAULT_THIRD_PERSON_VEHICLE_AIM_CAMERA</aimCameraName>
      <bonnetCameraName>VEHICLE_BONNET_CAMERA_NEAR_EXTRA_HIGH</bonnetCameraName>
      <povCameraName>DEFAULT_POV_CAMERA</povCameraName>
      <FirstPersonDriveByIKOffset x="0.000000" y="-0.055000" z="0.020000" />
      <FirstPersonDriveByUnarmedIKOffset x="0.000000" y="0.000000" z="0.000000" />
      <FirstPersonProjectileDriveByIKOffset x="0.020000" y="-0.080000" z="0.000000" />
      <FirstPersonProjectileDriveByPassengerIKOffset x="-0.120000" y="-0.080000" z="0.000000" />
      <FirstPersonProjectileDriveByRearLeftIKOffset x="0.000000" y="0.000000" z="0.000000" />
      <FirstPersonProjectileDriveByRearRightIKOffset x="0.000000" y="0.000000" z="0.000000" />
      <FirstPersonDriveByLeftPassengerIKOffset x="0.000000" y="0.000000" z="0.000000" />
      <FirstPersonDriveByRightPassengerIKOffset x="0.000000" y="-0.055000" z="0.020000" />
      <FirstPersonDriveByRightRearPassengerIKOffset x="0.000000" y="0.000000" z="0.000000" />
      <FirstPersonDriveByLeftPassengerUnarmedIKOffset x="0.000000" y="0.000000" z="0.000000" />
      <FirstPersonDriveByRightPassengerUnarmedIKOffset x="0.000000" y="-0.120000" z="-0.025000" />
      <FirstPersonMobilePhoneOffset x="0.140000" y="0.230000" z="0.510000" />
      <FirstPersonPassengerMobilePhoneOffset x="0.136000" y="0.118000" z="0.443000" />
      <PovCameraOffset x="0.000000" y="-0.250000" z="0.630000" />
      <PovCameraVerticalAdjustmentForRollCage value="0.000000" />
      <PovPassengerCameraOffset x="0.000000" y="0.000000" z="0.000000" />
      <PovRearPassengerCameraOffset x="0.000000" y="0.000000" z="0.000000" />
      <vfxInfoName>VFXVEHICLEINFO_CAR_GENERIC</vfxInfoName>
      <shouldUseCinematicViewMode value="true" />
      <shouldCameraTransitionOnClimbUpDown value="false" />
      <shouldCameraIgnoreExiting value="false" />
      <AllowPretendOccupants value="true" />
      <AllowJoyriding value="true" />
      <AllowSundayDriving value="true" />
      <AllowBodyColorMapping value="true" />
      <wheelScale value="0.262900" />
      <wheelScaleRear value="0.262900" />
      <dirtLevelMin value="0.000000" />
      <dirtLevelMax value="0.300000" />
      <envEffScaleMin value="0.000000" />
      <envEffScaleMax value="1.000000" />
      <envEffScaleMin2 value="0.000000" />
      <envEffScaleMax2 value="1.000000" />
      <damageMapScale value="0.600000" />
      <damageOffsetScale value="1.000000" />
      <diffuseTint value="0x00FFFFFF" />
      <steerWheelMult value="1.000000" />
      <HDTextureDist value="5.000000" />
      <lodDistances content="float_array">
        15.000000
        30.000000
        60.000000	
        120.000000	
        500.000000	
        500.000000
      </lodDistances>
      <minSeatHeight value="0.881" />
      <identicalModelSpawnDistance value="20" />
      <maxNumOfSameColor value="1" />
      <defaultBodyHealth value="1000.000000" />
      <pretendOccupantsScale value="1.000000" />
      <visibleSpawnDistScale value="1.000000" />
      <trackerPathWidth value="2.000000" />
      <weaponForceMult value="1.000000" />
      <frequency value="30" />
      <swankness>SWANKNESS_5</swankness>
      <maxNum value="5" />
      <flags>FLAG_BOOT_IN_FRONT FLAG_SPORTS FLAG_SPAWN_ON_TRAILER FLAG_PARKING_SENSORS FLAG_RICH_CAR FLAG_NO_BROKEN_DOWN_SCENARIO FLAG_CAN_HAVE_NEONS</flags>
      <type>VEHICLE_TYPE_CAR</type>
      <plateType>VPT_BACK_PLATES</plateType>
      <dashboardType>VDT_BANSHEE</dashboardType>
      <vehicleClass>VC_SPORT</vehicleClass>
      <wheelType>VWT_SPORT</wheelType>
      <trailers />
      <additionalTrailers />
      <drivers />
      <extraIncludes />
      <doorsWithCollisionWhenClosed />
      <driveableDoors />
      <bumpersNeedToCollideWithMap value="false" />
      <needsRopeTexture value="false" />
      <requiredExtras />
      <rewards />
      <cinematicPartCamera>
        <Item>WHEEL_FRONT_RIGHT_CAMERA</Item>
        <Item>WHEEL_FRONT_LEFT_CAMERA</Item>
        <Item>WHEEL_REAR_RIGHT_CAMERA</Item>
        <Item>WHEEL_REAR_LEFT_CAMERA</Item>
      </cinematicPartCamera>
      <NmBraceOverrideSet />
      <buoyancySphereOffset x="0.000000" y="0.000000" z="0.000000" />
      <buoyancySphereSizeScale value="1.000000" />
      <pOverrideRagdollThreshold type="NULL" />
      <firstPersonDrivebyData>
        <Item>LOW_RAPIDGT_FRONT_LEFT</Item>
        <Item>LOW_RAPIDGT_FRONT_RIGHT</Item>
      </firstPersonDrivebyData>
    </Item>
  </InitDatas>
  <txdRelationships>
    <Item>
      <parent>vehicles_comet_interior</parent>
      <child>mycar</child>
    </Item>
  </txdRelationships>
</CVehicleModelInfo__InitDataList>

This package needs data/handling.meta with a <handlingName>MYCAR</handlingName> entry. Without it the car has no physics data.

Folder layout

mycar/
├─ fxmanifest.lua
├─ vehicle_names.lua
├─ data/
│  ├─ vehicles.meta
│  ├─ carvariations.meta
│  └─ handling.meta   ← yours, not generated here
└─ stream/
   ├─ mycar.yft
   ├─ mycar_hi.yft
   └─ mycar.ytd

How to use Vehicles.meta Generator

  1. 1Type the spawn name exactly as the .yft file is named (lowercase). Auto-fill sets the texture name, handling ID and GXT key.
  2. 2Pick the body template closest to your model. It supplies the seat layout, drive-by data, cameras and every other field from that stock vehicle.
  3. 3Adjust class, engine sound, wheels, dashboard, plates and flags if the stock values do not fit, then set the colour combos.
  4. 4Download all four files. Add the mod's handling.meta (or tick the stock handling option), arrange the folder as shown, and verify with the Resource Inspector.

What is vehicles.meta?

It registers a model with the game: spawn name, texture dictionary, handling entry, class, seat layout, engine sound and behaviour flags. Names such as the layout and drive-by entries must already exist in the game, which is why this generator copies them from a stock vehicle instead of making them up.

Why carvariations.meta?

It defines the colour combinations the car spawns in, its mod kit and its light and siren settings ids.

Display name shows as NULL?

The in-game name comes from a GXT entry matching gameName. The generated vehicle_names.lua adds it with AddTextEntry, so keep client_script in your manifest.

What the generator creates and when you need it

An add-on car needs more than model and texture files. vehicles.meta registers the model, carvariations.meta sets its colours and kit, a small client script supplies the display name, and the manifest mounts all of it. This generator writes those four files from a form.

A vehicles.meta entry is full of names that must already exist in the game: the seat layout, the first-person drive-by entries, cover offsets, cameras, the shared interior texture dictionary. Inventing them from the spawn name does not work, so the generator starts from a body template instead. Each of the 29 templates mirrors one stock GTA V vehicle (a Comet for a two-seat sports coupe, a Baller for an SUV, a Bati for a sport bike and so on), and every field you do not type is copied from the game's own entry for that vehicle. You then set the spawn name, texture dictionary name, handling id, GXT key and display name, make, vehicle class, engine sound, wheel type, dashboard, plates, swankness, behaviour flags, colour combinations, mod kit name and light and siren ids.

You need it when a mod ships only .yft and .ytd files, when you are turning a replace mod into an add-on (see add-on vs replace), or when the supplied metas are broken and starting clean is quicker than repairing them. Cars converted through the converter on the homepage normally arrive with their metas already, so check what you have before generating new ones. The tool is free and has no paid tier.

Using the generated files

The output panel has a tab per file with copy and download buttons. Place vehicles.meta and carvariations.meta in the data folder, vehicle_names.lua and fxmanifest.lua in the resource root, and the model and texture files in stream/, as shown in the folder tree on the page.

The generator does not create handling.meta. By default the handlingId you enter has to match a handlingName in a handling file you add to the data folder, normally the one that came with the mod, which you can tune in the Handling Editor. If the mod has no handling file, tick the stock handling option: the car then uses the handling entry of the template's stock vehicle and the manifest leaves handling.meta out.

Values that depend on the shape of your model, such as wheel scale and the first-person camera offsets, also come from the stock vehicle. They are valid, but a model with very different wheels or seats may need them adjusted by hand. The page warns when the spawn name is empty, when the GXT key is longer than 11 characters and when the texture dictionary name differs from the model name.

Before you put the resource on a server, check it with the Resource Inspector, which confirms that every name in the metas points at a file that exists.

Common mistakes

  • A spawn name that does not match the .yft file name exactly. It is case sensitive in practice; keep everything lowercase.
  • Picking a body template with a different number of seats or doors than the model, which shows up as peds sitting in the wrong place or clipping through doors.
  • Typing a mod kit name that no carcols.meta defines. Keep the generic stock kit unless the mod ships its own carcols.meta.
  • Leaving the default handling id without adding a handling.meta that contains it.
  • Removing the client_script line for vehicle_names.lua, after which the car's name shows as NULL. The NULL name fix covers the other causes.

Frequently asked questions

Is the vehicles.meta generator free?

Yes. All four files can be generated, copied and downloaded without an account or payment.

Where do the layout, drive-by and camera values come from?

From the stock vehicle the chosen body template mirrors. Those fields are copied unchanged from the game's own vehicles.meta entry, so they refer to layouts, drive-by data and texture dictionaries that exist in the base game.

Does it generate handling.meta too?

No. It references a handling id but does not write the physics data. Use the handling file from the mod, or tick the option to use the stock template vehicle's handling.

Why does my car show NULL as its name?

The game looks up the gameName as a text label. The generated vehicle_names.lua registers that label with AddTextEntry on the client, so the script has to be loaded by the manifest as a client_script and the gameName has to be 11 characters or fewer.

What are the colour indices in carvariations.meta?

Each colour combination lists GTA palette indices for primary, secondary, pearlescent and wheel colour. The form lets you pick them, and the car spawns in one of the combinations you define.

Can I use it for bikes or emergency vehicles?

Yes. There are templates for sport, chopper, dirt and scooter motorcycles, a quad, a police sedan, a police SUV and an ambulance, among others. Emergency lighting itself is configured elsewhere, in carcols.meta or an ELS file.

More answers about conversions, limits and plans are in the general FAQ.

Need another car converted?

Paste a gta5-mods.com vehicle link into the converter and download a FiveM resource, then bring it back to this tool.

  • 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