QBCore Frameworkqbcore.netCommunity docs
On this page

Updated 2026-10-11 · 4 min read

qb-clothing: appearance, outfits and persistence

qb-clothing is the QBCore appearance resource for character editing, clothing shops, barber shops and saved outfits. This guide follows upstream commit 8cca400; custom appearance replacements may expose completely different APIs.

Installation

  1. Start qb-core and oxmysql; the manifest also imports PolyZone client modules.
  2. Install qb-clothing with its bundled html, Lua files, config and locales. Do not copy only the UI folder.
  3. Import the upstream qb-clothing.sql into a backed-up staging database before replacing another appearance script.
  4. Test initial character creation, skin save/reload, job outfit selection, disconnect/reconnect and switching characters.

Actual database tables

TableRelevant columnsUse
playerskinscitizenid, model, skin, activeCharacter appearance data
player_outfitscitizenid, outfitname, model, skin, outfitIdNamed saved outfits

Both tables are present in upstream SQL. A generic clothing_stores, clothing_items or player_clothing migration is not part of this resource. It is unsafe to paste such a schema on top of existing player appearance data.

The server loads the active row from playerskins for the current citizen ID and sends the model/skin to the client. Outfit save/delete flows use player_outfits. The source uses parameterized queries.

Client exports: what actually exists?

From the client implementation:

ExportUsage / important boundary
reloadSkinRe-applies appearance through the resource's reload flow
IsCreatingCharacterReturns whether its character-creation UI is active
getOutfitsgetOutfits(gradeLevel, data) opens a job outfit UI; expects a compatible gender/grade outfit data table, not a plain return array

For example, an in-client guard can check whether the clothing creator is open:

if exports['qb-clothing']:IsCreatingCharacter() then
    print('Clothing creator is already active')
else
    TriggerEvent('qb-clothing:client:openMenu')
end

The upstream revision does not export OpenClothingMenu, SaveOutfit, LoadOutfit or GetPlayerOutfits. Do not replace the actual client event/exports with those invented wrappers.

Events and callbacks

These are implementation-defined handlers, not a promise of an external stable API:

SideNameRole
Clientqb-clothing:client:openMenuOpens appearance editing
Clientqb-clothes:client:CreateFirstCharacterOpens initial character creator
Clientqb-clothes:loadSkinApplies server-delivered skin
Clientqb-clothing:client:reloadOutfitsRefreshes outfit UI
Serverqb-clothing:saveSkinSaves character skin
Serverqb-clothes:loadPlayerSkinReads saved skin for a character
Serverqb-clothes:saveOutfitWrites an outfit row
Serverqb-clothing:server:removeOutfitDeletes an owned outfit row
Server callbackqb-clothing:server:getOutfitsLoads saved outfits for the caller

The historical qb-clothes prefix is used for some real events in this revision. Do not normalize all events to qb-clothing:... without checking their registration.

Configuration and compatibility

config.lua contains large Config.WomanPlayerModels and Config.ManPlayerModels lists plus appearance/shop settings. Compare the actual keys in your installed version before copying someone else's menu/store config.

A replacement like illenium-appearance or fivem-appearance may have a different database schema, creator API and character-login integration. Choose exactly one authoritative appearance implementation and plan a data migration before switching.

Troubleshooting

SymptomInvestigate
Skin resets after rejoinCharacter ID, active playerskins row, SQL import and qb-clothes:loadPlayerSkin flow
Outfits vanishplayer_outfits schema, caller citizen ID, save callback and SQL errors
Character editor fails to openClient event registration, NUI files and first-character flow
Error involving PolyZoneDependency loading and manifest imports
No such export OpenClothingMenuNot an export in this upstream; use a verified client event or a wrapper in your own resource
Appearance breaks after script replacementCompare schema, model/skin serialization and login lifecycle in a staging copy

Update checklist

  1. Pin the server's qb-clothing commit and installed appearance/inventory/character dependencies.
  2. Diff config.lua and the upstream SQL against local customizations.
  3. Test initial skin, outfit save/remove, job outfits and reconnect with two different characters.
  4. Never run an unrelated example CREATE TABLE over live player appearance data.

If you need more garments rather than a different clothing menu, compare clothing packs on RPScripts by the components and slot ranges they stream. RPScripts and qbcore.net are operated by the same owner.

Sources

Repository · Manifest · Client exports and events · Server handlers · SQL schema

For the login/spawn sequence see qb-multicharacter.

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website