~/guides/fivem-multicharacter-setup
FiveM Multicharacter Setup
-- setup · updated november 2026 · var fivem team
-- 1 license, several rows · esx: char prefix · qbcore: citizenid
Multicharacter lets one player hold several separate characters on your FiveM server, each with its own money, job, inventory and appearance. This guide explains what the system actually changes in your database, how ESX and QBCore each store characters, and the setup order that works: prerequisites, server.cfg, slots, spawn, deletion, selling extra slots, and the fixes for the black screen after selection.
What multicharacter actually changes
Without multicharacter, a framework maps one player to one character: the Rockstar license identifier is the key, and money, job, inventory and skin all hang off it. A multicharacter resource breaks that one-to-one link. The license still identifies the person, but it now points to several character rows, and the player picks which one to load before spawning.
In practice the resource does three things. It holds the player on a selection screen instead of letting them spawn. It reads every character row tied to their license and shows them, with the empty slots. Then it tells the framework which row to load, or sends the player to a character creator when the slot is empty. Everything else on your server (jobs, garages, housing, banking) keeps working because it is keyed to the character, not to the person. If you are still choosing which script to run, the FiveM multicharacter script comparison covers the free and paid options. This page is the how.
How ESX and QBCore store characters
ESX keeps one row per character in the users table and tells them apart inside the identifier itself. With esx_multicharacter running, the identifier becomes a slot prefix followed by the license, so the same player owns char1:abc123, char2:abc123 and so on. The prefix is the Config.Prefix value of the resource. Every table that stores an owner (vehicles, properties, billing) stores that prefixed string, which is why the prefix must never change on a live server.
QBCore was built multicharacter-first. Each character is a row in the players table with its own citizenid, a short unique code that every other resource uses as the owner key. A separate license column holds the Rockstar license, and that column is what links several citizenids to one person. qb-multicharacter simply lists the rows that share the connecting license. Qbox follows the same citizenid model. The full picture of how the two frameworks differ is in ESX vs QBCore.
Step 1: check the prerequisites
Three things have to be in place before any multicharacter resource will behave. First, a working framework: ESX Legacy or QBCore, started and connected to its database. Second, oxmysql, because character rows are read and written on every connection. Third, exactly one skin manager, since the selection screen has to dress each ped and the spawn has to reapply the appearance. The four common ones are esx_skin, qb-clothing, fivem-appearance and illenium-appearance. Running two at once is the single most reliable way to get peds loading as the default model.
On ESX you also need esx_identity, which collects the name, date of birth and height for a new character. Take a database backup before going further: enabling multicharacter on a server that already has players changes how their rows are looked up.
Step 2: disable the default spawn flow
A fresh server spawns the player automatically the moment the game loads. A multicharacter resource needs the opposite: the player must wait, hidden, until a character is chosen. If both flows run, you get a double spawn, or a player dropped at the default location before the selection screen appears.
Both frameworks already handle this when you use their own multichar. ESX detects esx_multicharacter through its Config.Multichar setting and stops spawning players by itself, and the stock QBCore recipe hands the first spawn to qb-multicharacter. The step matters when you add things: a custom spawn selector, a second multichar left in the resources folder, or a loading screen that keeps the screen covered. Keep one resource in charge of the first spawn and remove the others, do not just stop them.
Step 3: get the ensure order right
Start order is where most installs break. The rule is simple: database, then framework, then everything the multichar depends on, then the multichar. On ESX Legacy that gives:
# server.cfg | ESX Legacy, database first, multichar after its dependencies
ensure oxmysql
ensure es_extended
ensure esx_identity # name, date of birth, height
ensure skinchanger
ensure esx_skin # or the appearance resource you run instead
ensure esx_multicharacterAnd on QBCore:
# server.cfg | QBCore, same logic
ensure oxmysql
ensure qb-core
ensure qb-multicharacter
ensure qb-spawn # where the player lands after selection
ensure qb-apartments
ensure qb-clothing # or illenium-appearance / fivem-appearanceIf your server.cfg starts whole category folders like ensure [core] or ensure [qb], the dependencies declared in each manifest sort the order for you, and the lists above are what to verify when something fails. The general method for start order and dependencies is in how to install a FiveM script.
Step 4: set the slots and the spawn location
The slot count is a config value. esx_multicharacter exposes Config.Slots, four by default, and qb-multicharacter exposes Config.DefaultNumberOfCharacters, five by default, with a second table to override the number for a given license:
-- qb-multicharacter/config.lua
Config.DefaultNumberOfCharacters = 5 -- slots for everyone
Config.PlayersNumberOfCharacters = { -- per-player override
{ license = "license:xxxxxxxxxxxxxxxx", numberOfChars = 2 },
}Lower the default before launch rather than after. Removing a slot from players who already filled it is a support problem, adding one later is a gift. Two or three slots suits most roleplay servers.
The spawn location has two halves. A brand new character needs a first spawn point, set in the config of the multichar on ESX (Config.Spawn) or decided by the spawn and apartment resources on QBCore. A returning character should load at its last saved position, which the framework stores for you. Test both paths: create a character, walk somewhere, disconnect, reconnect.
Limiting and selling extra slots
A global number is enough until you want one player to have more than the others, for a supporter perk or a staff test character. That requires a slot count stored per player. On QBCore the override table above does it by hand, at the cost of a config edit and a restart of the resource each time. On ESX, check the README of your esx_multicharacter version for per-identifier slot commands before assuming you need another resource.
Selling slots follows from that. A Tebex package can run a console command on your server after checkout, so the only requirement is a command that writes a slot count for one identifier. Keep the offer honest: a slot is convenience, never an advantage. Where slot sales sit among other revenue ideas is covered in the FiveM server monetization guide.
Deleting characters safely
Deleting a character is more than removing one row. The character owns vehicles, items, properties, bills and outfits in other tables, all keyed to its identifier or citizenid. A proper deletion removes those rows in the same operation, otherwise the orphans pile up and can resurface when a slot is reused.
Decide two things before opening the server. Whether players can delete at all: esx_multicharacter has Config.CanDelete, and qb-multicharacter has an equivalent switch for its delete button. Many servers turn it off and handle deletions through staff, which also stops players wiping a character to dodge a roleplay consequence. And whether third-party resources that add their own tables are covered: if a housing or garage script is not in the list of tables the multichar cleans, add it or clean it yourself. Always back up before a manual deletion.
Common failures and their fixes
Almost every multicharacter ticket is one of these:
Black screen or endless loading after selection: the fade-in waits for the skin to be applied. Check that your skin manager is started, started before the multichar, and prints no error in F8. A loading screen with manual shutdown enabled that no resource closes gives the same symptom.
Player spawns twice, or drops into the world before the selection screen: another resource is still auto-spawning. Disable the default spawn flow so only the multichar decides when the player appears.
Characters are not saved, or the list is empty after a restart: oxmysql is not started first, the connection string is wrong, or the SQL that ships with the resource was never imported. The server console says so on boot.
Existing players lose their character the day you enable multicharacter on ESX: their row holds the bare license, the resource now looks for char1: plus the license. Back up, then migrate the identifier in users and in every table that references it.
Skin not applied, everyone loads as the default ped: the multichar is configured for one skin manager and the server runs another. Run exactly one, and point the multichar at it.
Characters gone after switching framework: ESX and QBCore do not share tables or identifier formats. Changing framework means a data migration, not a config change.
One more check on ESX: the identifier columns must be long enough to hold the prefix plus the license. If a third-party table was created with a short owner column, the value is cut and the character silently loses what it owns.
Setting up Var-MultiChar instead
The framework defaults are free and they work. Run them until you have a reason not to. The paid route we sell is Var-MultiChar, which replaces the list of names with the native GTA police line-up mugshot board scaleform and a rotating ped preview. It runs on ESX and QBCore, gives up to four slots by default, works with esx_skin, qb-clothing, fivem-appearance and illenium-appearance, includes its own character and skin creator, and asks for a typed confirmation before a character is permanently deleted.
The install follows the same logic as above, with one difference: it replaces the framework multichar rather than sitting next to it. On ESX you delete the esx_multicharacter folder and point Config.Multichar at the new resource. On QBCore you delete the qb-multicharacter folder. Both need a small SQL import that creates the per-player slots table and adds a disabled column, then ensure Var-MultiChar:
-- es_extended/config.lua | point ESX at Var-MultiChar (ESX only)
Config.Multichar = GetResourceState("Var-MultiChar") ~= "missing"
# server console, or a Tebex command | give one player 4 slots (ESX)
setslots 4 <identifier>Slots are managed per player by command, run from the console or from a Tebex package: setslots and remslots on ESX, addslots, setslots and removeslots on QBCore. disablechar and enablechar suspend and restore a single character without deleting it, and relog reopens the selector. To keep your own creator instead of the built-in one, edit the SendToCreator function in the shared creator files. The exact steps are in the docs: Var-MultiChar installation, commands and changing the character creator.
Frequently asked questions
How many characters can a player have on a FiveM server?
As many as the multicharacter resource allows, and the owner decides. esx_multicharacter gives four slots by default and qb-multicharacter gives five. Most serious roleplay servers settle between two and four, because every extra slot means more alt characters and more rows to carry in the database.
How do I add character slots for one player only?
You need a slot count stored per player instead of one global number. On QBCore, qb-multicharacter has a Config.PlayersNumberOfCharacters table where you add the player's license and a character count by hand. On ESX, check the README of the esx_multicharacter version you run for per-identifier slot commands. Var-MultiChar stores slots in a database table and changes them with setslots (ESX) or addslots and setslots (QBCore).
What is the difference between ESX and QBCore multicharacter?
The idea is the same, the storage is not. ESX keeps one row per character in the users table and tells them apart with a prefix in the identifier, char1:, char2: and so on, followed by the license. QBCore keeps one row per character in the players table, each with its own citizenid, and a license column that links the rows to the same person. That is why a resource written for one framework cannot read the other's characters without a bridge.
Why does the screen stay black after I choose a character?
The multicharacter resource fades the screen out, then waits for the framework to load the character and for the skin manager to apply the appearance before fading back in. If the skin manager is missing, started in the wrong order or throwing an error, that last step never fires. Open the F8 console right after selecting: a script error naming your skin or spawn resource is the usual culprit, followed by a loading screen set to manual shutdown that nothing ever closes.
Can I sell extra character slots on my server?
Yes. A slot is a convenience, not a gameplay advantage, which keeps it on the safe side of the Cfx.re monetization rules. The technical requirement is a per-player slot count that a console command can write, so your Tebex package runs that command after checkout. Var-MultiChar supports this as an option: its slot commands are built to be run from the console or from Tebex.
-- var-fivem.com
Var-MultiChar
Character selection on the native GTA mugshot board, ESX and QBCore, four skin managers, admin slot commands and optional Tebex slot sales. Available in escrow, partially open and open source.
Related: Best FiveM multicharacter scripts · Best FiveM character creator · How to install a FiveM script
Keep reading
- listicleBest FiveM Multicharacter Scripts in 2026A priced comparison of FiveM multicharacter scripts: the free ESX and QBCore options, 8 paid ones from 11 to 40 EUR, escrow vs open source, and how to sell extra character slots.read
- listicleBest FiveM Character Creator Script in 2026What a FiveM character creator has to cover: parent heritage, face sliders, overlays, clothing, camera and saving to illenium-appearance or fivem-appearance, with the free and paid options compared on August 2026 prices.read
- setupHow to Install a FiveM Script: Escrow, Keymaster & DependenciesThe full install path for a FiveM script: download the asset from the Cfx.re Portal, drop it in resources/[category]/, ensure it in server.cfg in the right order, wire ox_lib and oxmysql, import the SQL, add the items, and fix the seven errors that break every first attempt.read