How to Install ox_inventory on FiveM
ox_inventory is the de facto free inventory in 2026 — roughly 0.08 ms idle at 64 players, and it runs on ESX, QBCore and Qbox. Here is how to install it correctly, in the right start order, without breaking your existing items.
ox_inventory is free, open source and faster than almost every paid alternative. It replaces qb-inventory or your ESX inventory entirely — this is a swap, not an addition, so read the migration step before you start.
Do this on a test server first if you already have players and items. An inventory swap touches every item, shop and job on the server.
What you'll need
A quick checklist before you begin — have these ready and the rest is easy.
- A working FiveM server on ESX, QBCore or Qbox.
- oxmysql and ox_lib installed.
- The release build of ox_inventory (not the source zip).
- The correct bridge for your framework version.
- A full database backup before you migrate.
Install ox_inventory, step by step
Back up first — seriously
Back up your database and your resources folder. The inventory owns your players' items; a bad migration is not something you fix later. If you have live players, do this on a test server first.
Install the dependencies
ox_inventory needs oxmysql (database wrapper) and ox_lib (shared UI/library). Almost certainly you already run oxmysql. Download the latest releases and drop them in your resources folder.
Download ox_inventory
Take the latest release build from the official Overextended GitHub — not the source zip. The release includes the compiled web UI; the source does not, and a missing UI build is the classic "my inventory is a blank screen" cause.
Install the bridge for your framework
ox_inventory is framework-agnostic and talks to ESX/QBCore through a bridge. Follow the official docs for your framework version — this is the step that differs most between setups, and the docs are the source of truth, not a random YouTube video.
Fix your start order
Dependencies must start before the things that use them, or you get cryptic failures. In server.cfg the order is: oxmysql, then ox_lib, then your framework core, then ox_inventory, then everything else.
ensure oxmysql ensure ox_lib ensure es_extended # or qb-core ensure ox_inventory # ...your other resources after this
Remove the old inventory
Stop ensuring qb-inventory (or your ESX inventory) — do not run two inventories at once, they will fight over the same events. Comment it out rather than deleting, so you can roll back.
# ensure qb-inventory <- disabled, replaced by ox_inventory
Migrate your items
ox_inventory uses its own item definitions in data/items.lua. Your existing framework items need to exist there or they will not resolve. Follow the official migration notes for your framework, then start the server and watch the console for unknown-item warnings.
Test before you let players in
Give yourself items, open shops, use a stash, check a job that hands out items, and confirm weapons work. Then check resmon (F8, resmon 1) — ox_inventory should sit near 0.08 ms idle.
resmon 1
Getting it right
Use the release, not the source
The release build ships the compiled web UI. Downloading the source zip is the number-one cause of a blank inventory screen.
Start order is not optional
oxmysql, ox_lib, framework, ox_inventory — in that order. Most "won't load" errors are just this.
Trust the official docs
Bridges and item formats change between versions. The Overextended docs are current; the tutorial video from 2023 is not.
Check resmon after
Around 0.08 ms idle at 64 players is normal. Much higher means something is misconfigured or fighting it.
Common problems & fixes
Hit a snag? These are the issues people run into most — and how to solve them.
Inventory opens as a blank screen
You installed the source instead of the release build — the compiled web UI is missing. Download the latest release and restart.
Resource fails to start
Start order. oxmysql and ox_lib must be ensured before ox_inventory, and the framework core before it too.
Items exist in the framework but not in the inventory
They are not defined in ox_inventory data/items.lua. Add them or run the framework migration from the official docs; the console lists unknown items on boot.
Items duplicate or vanish randomly
You are likely still running the old inventory alongside it. Disable qb-inventory (or the ESX one) in server.cfg — only one inventory may run.
Skip the setup — host it with ESAGAMES
FiveM is single-thread bound, and an RP server with a full script list is demanding. Our FiveM hosting runs high-clock CPUs with txAdmin and MySQL ready, behind multi-Tbps Frankfurt filtering.
Frequently asked questions
Does ox_inventory work with ESX and QBCore?
Yes. ox_inventory is cross-framework and runs on ESX, QBCore and Qbox through a bridge. Qbox ships it as the default. Follow the official docs for the bridge matching your framework version.
Is ox_inventory better than qb-inventory?
On modern builds, yes — qb-inventory has been outperformed on essentially every metric. ox_inventory is free, faster (about 0.08 ms idle at 64 players) and actively maintained. The only reason to stay on qb-inventory is being locked in by old scripts.
Is ox_inventory free?
Yes, free and open source from Overextended. The paid alternative most people compare it to is qs-inventory (around 35-50 EUR), which is worth it mainly if you want built-in crafting and a more polished UI.
Why is my inventory a blank screen?
Almost always because you downloaded the source zip instead of the release build — the release contains the compiled web UI. Re-download the latest release and restart.
Can I run ox_inventory and qb-inventory together?
No. Two inventories fight over the same events and items. Disable the old one in server.cfg before starting ox_inventory.
Will I lose player items?
You can, if you migrate carelessly. ox_inventory uses its own item definitions in data/items.lua, so existing items must be defined there. Back up your database first and test on a copy before doing it live.
Keep reading
FiveM is a Cfx.re / Rockstar Games project. Grand Theft Auto V is a trademark of Rockstar Games / Take-Two Interactive. ox_inventory, ox_lib and oxmysql are projects of Overextended; ESX and QBCore belong to their respective authors. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by any of them. You must own a legitimate copy of the game and download resources from their official sources.
