FiveM Clothing List

How ped clothing works in FiveM

A ped in FiveM wears two kinds of items. Components are clothing baked into the model, the torso, legs, shoes, mask and hair, set client-side with SetPedComponentVariation(ped, componentId, drawableId, textureId, paletteId). Props are attached accessories, hats, glasses, watches and bracelets, set with SetPedPropIndex(ped, componentId, drawableId, textureId, attach). The difference matters: a component slot is always present so you swap its drawable, while a prop can be attached or removed entirely. These are the two natives every FiveM clothing script, skin manager and character creator is built on top of.

The IDs come from the game, not from a framework, so the same FiveM clothing component IDs work on ESX, QBCore, Qbox and standalone. What changes between servers is the number of drawables available in each slot: that depends on the ped model and on any add-on or EUP clothing you stream. The freemode peds mp_m_freemode_01 and mp_f_freemode_01 carry the largest wardrobes, which is why almost every roleplay server spawns players as a freemode ped.

FiveM clothing component IDs (0 to 11)

There are 12 component slots. The table lists each ID, the engine's internal name (the value you will see in dumps and appearance exports), the slot it maps to on the freemode peds, and what it holds. Two rows are worth flagging because the internal name and the real usage disagree: component 7 is named TEEF internally but on freemode peds it is the neck accessory slot (scarves, chains, ties), and component 8 is named ACCS but is actually the undershirt worn under the top. Component 11 (JBIB) is the outer torso, the jacket or top most scripts think of as the shirt.

FiveM prop IDs (SetPedPropIndex)

Props are the accessories that sit on top of the ped. SetPedPropIndex uses its own set of slot IDs, separate from the component IDs above, and only five are used on the MP freemode peds. Slots 3, 4 and 5 exist in the enum but are unused. To remove a prop, call ClearPedProp(ped, propId) or set the drawable to -1. The final attach argument should stay true so the prop is parented to the correct bone.

Drawable, texture and palette IDs

The component or prop ID is only the first number. Inside one slot, the drawableId chooses which item you wear, and the textureId chooses that item's colour or material variant. A jacket slot might hold 30 drawables, and each drawable might have 4 textures, one per colourway. The paletteId is a further tint palette from 0 to 3 and is almost always 0. In short: component sets the slot, drawable sets the item, texture sets the colour.

Because those counts change per ped model, you never hardcode a maximum. You read it at runtime with the helper natives below, which is exactly what clothing menus do to build their catalog. These are all documented FiveM natives, listed by name.

Lua snippets: set an outfit and props

Dressing a ped is one native call per component. The snippet below sets a top, undershirt, arms, pants and shoes on the player ped. The drawable IDs are examples, the valid range for each slot depends on the ped model, so treat them as placeholders you replace with values from your own wardrobe or menu.

-- client.lua | dress the player ped with components
-- SetPedComponentVariation(ped, componentId, drawableId, textureId, paletteId)
-- drawable ids below are examples: valid ranges depend on the ped model
CreateThread(function()
    local ped = PlayerPedId()

    SetPedComponentVariation(ped, 11, 15, 0, 0) -- 11 JBIB  | top / jacket
    SetPedComponentVariation(ped, 8,  15, 0, 0) -- 8  ACCS  | undershirt
    SetPedComponentVariation(ped, 3,  4,  0, 0) -- 3  UPPR | arms / torso
    SetPedComponentVariation(ped, 4,  10, 0, 0) -- 4  LOWR | pants
    SetPedComponentVariation(ped, 6,  12, 0, 0) -- 6  FEET  | shoes
end)

Props take the extra attach boolean and are removed individually. This is how you put on a hat, glasses and a watch, then take the hat back off.

-- client.lua | props are attached accessories, not baked components
local ped = PlayerPedId()

-- SetPedPropIndex(ped, propId, drawableId, textureId, attach)
SetPedPropIndex(ped, 0, 5, 0, true) -- 0 hat
SetPedPropIndex(ped, 1, 3, 0, true) -- 1 glasses
SetPedPropIndex(ped, 6, 2, 0, true) -- 6 watch

ClearPedProp(ped, 0)                 -- remove the hat
-- equivalent: SetPedPropIndex(ped, 0, -1, -1, true)

To know how many items a slot actually has on the current ped, enumerate them at runtime. This loop prints every top drawable and its texture count, the same technique a clothing shop uses to populate its grid. If you would rather not build that menu yourself, a FiveM clothing shop script already turns these natives into a browsable catalog.

-- client.lua | count the tops (component 11) on the current ped model
local ped = PlayerPedId()
local component = 11 -- JBIB / tops

local drawables = GetNumberOfPedDrawableVariations(ped, component)
print(('component %d has %d drawables'):format(component, drawables))

for d = 0, drawables - 1 do
    local textures = GetNumberOfPedTextureVariations(ped, component, d)
    print(('  drawable %d -> %d textures'):format(d, textures))
end

Finding drawables on any ped model

This page lists every component and prop slot ID, because those are fixed by the game. The drawables and textures inside each slot are not fixed: they vary per ped model and grow every time you stream add-on clothing or EUP packs. So the reliable way to find what is available is to query it, not to memorise a list. Spawn the ped you care about, then loop GetNumberOfPedDrawableVariations across components 0 to 11 and the prop slots, exactly as the enumerate snippet above does, and you have the real, current range for that model on your server.

One caveat for DLC and add-on clothing: the classic global drawable indexes shift with each GTA title update, which can break saved outfits. FiveM added collection-based natives, SetPedCollectionComponentVariation and SetPedCollectionPropIndex, that address a component by a collection name plus a local index (an empty string for the base game, a named collection for DLC), so the indexes stay stable across updates. If your server relies heavily on add-on outfits, storing the collection name alongside the drawable is the durable approach.

Scripts that use these clothing IDs

If you would rather configure clothing than write the natives by hand, Var FiveM appearance scripts wrap the exact component and prop IDs on this page into ready menus. Var-ClotheShop V2 is a NUI clothing shop with 15 configurable clothing and prop categories, tops, pants, shoes, masks, glasses, helmets, chains, bags, watches, bracelets, vests and more, an image-based catalog and save, rename and delete outfits per player. Var-Creator is a FiveM character creator that sets face, hair, beard, makeup, clothing and props with a cinematic camera, and Var-BarberShop handles the hair and beard components (2 and 1) with a live in-chair preview. All of them auto-detect the skin manager, esx_skin, qb-clothing, fivem-appearance or illenium-appearance, so they drop into an ESX or QBCore server without touching these natives yourself.

Related: FiveM ped list · FiveM blips list · FiveM emote list