GTA V and FiveM file formats, plain English

GTA V runs on RAGE, Rockstar Advanced Game Engine. FiveM keeps that asset system and streams extra assets and metadata into the game.

Most server files are connected to another file. A .ytd feeds textures to a model. A .ytyp tells the game what a prop is. A .meta file tells the game how a vehicle, weapon, handling line, or other system should behave. Once you know those links, broken resources get easier to fix.

Quick format map

How the files connect

.ydr plus .ytd plus .ytyp

A prop usually starts as a .ydr. The .ydr carries the mesh and material references. The .ytd carries the texture names those materials ask for. The .ytyp defines the prop as an archetype so map placements know what it is.

If the model shows up white, grey, or invisible, check the texture dictionary first. The texture name inside the .ytd has to match the name the model expects. If the prop exists but will not place correctly in a map, check the .ytyp.

.yft plus vehicle metadata

A .yft is usually the vehicle model in a FiveM resource. Many vehicles also have a _hi.yft version for higher detail at close range. Textures live in a .ytd, and behavior comes from metadata files.

• vehicles.meta connects the model name, vehicle class, layout, audio, and other vehicle settings.
• handling.meta controls driving behavior.
• carvariations.meta links liveries, colors, extras, and variation data.
• carcols.meta often carries extra color and mod kit data.

.ydd plus .ytd

A .ydd is a dictionary of drawables. In most server-owner conversations, that means clothing. The geometry lives in the .ydd and the matching textures live in the .ytd. If a clothing item loads with the wrong fabric or a blank material, check texture names and component naming before rebuilding the whole resource.

.xml is usually the editable copy

Tools such as Codewalker often export .ydr, .yft, and other game files as .xml. That XML is easier to inspect and edit, but the game does not stream the exported .xml as the final asset. After editing, compile or import it back into the game format.

.ybn / .ybd collision

Collision is the part you notice when the art looks right but the world feels wrong. A .ybn or .ybd can define the physical shape around a prop, building, road, or other world asset. If players fall through a floor, hit an invisible wall, or drive through a visible object, check collision before you rebuild the model.

.ycd animation dictionaries

Animation data usually lives in .ycd files. Many FiveM scripts call existing game animation dictionaries, but custom assets may bring their own animation clips. If an animation request does nothing, check the dictionary name, clip name, resource path, and whether the file is being streamed.

Where the manifest fits

FiveM resources use fxmanifest.lua to describe scripts, data files, UI pages, dependencies, and files that clients should download. For exact manifest entries, use the official resource manifest docs.

fx_version 'cerulean'
game 'gta5'

files {
  'stream/props.ytyp',
  'data/vehicles.meta',
  'data/carvariations.meta',
  'data/handling.meta'
}

data_file 'DLC_ITYP_REQUEST' 'stream/props.ytyp'
data_file 'VEHICLE_METADATA_FILE' 'data/vehicles.meta'
data_file 'VEHICLE_VARIATION_FILE' 'data/carvariations.meta'
data_file 'HANDLING_FILE' 'data/handling.meta'

The manifest does not fix bad names inside a model. It only tells FiveM which resource files and metadata should be loaded. If the .ydr asks for a texture called sign_1 and the .ytd only contains sign1, the manifest can be perfect and the texture will still fail.

Source files vs game files

Creators also work with files that are not final streamed assets. A .png, .jpg, .psd, .glb, .fbx, or .obj can be the source you use to make the resource, but GTA V usually needs the result packed into the formats above.

Match the tool to the file

Fast debugging checklist

• Model is invisible: check the filename, stream folder, model name, and whether a .ytyp or metadata file is missing.
• Model is white or grey: check the .ytd and texture names the model expects.
• Vehicle spawns but has no liveries: check carvariations.meta and the livery texture names inside the .ytd.
• Clothing appears with the wrong texture: check component naming and whether the matching .ytd texture dictionary is present.
• Map prop exists but will not place correctly: check the .ytyp archetype and .ymap references.
• File works in OpenIV or Codewalker but not on the server: check fxmanifest.lua data_file entries and resource folder structure.

Related guides