ox_inventory Item Not Showing? Fix Items, Images and Metadata

Start with the item definition

When an ox_inventory item does not show, start with the data definition. The item name used by the script must match the item key registered in your inventory data. A label can be friendly and spaced, but the internal item key should stay predictable. If one script gives a player lockpick_advanced and your inventory defines advanced_lockpick, the item may fail or appear as an unknown object depending on the bridge and version. Copy the exact item key, label, weight, stack setting and any client metadata before changing code.

Next check where the item is registered. Some servers store item definitions in a shared items file, some in ox_inventory/data/items.lua, and some in a framework bridge. Do not add the same item in multiple places unless your setup requires it. Duplicate definitions create confusing behaviour because one resource may read one definition while another expects a different label, image or metadata shape.

item key:
item label:
image filename:
where it is defined:
script that gives the item:
console or F8 error:

Check image names and paths

If the item exists but shows without an icon, the problem is often the image filename. The image usually needs to match the item key and live in the image directory that your inventory UI expects. Watch for uppercase letters, spaces, hyphens, png versus webp, and cached browser assets. Restarting the resource may not clear every UI cache. Test with a private client session, refresh the inventory UI if your setup supports it, and verify that the image file is deployed on the live server, not only in your local folder.

Do not solve an image problem by changing the item key if the item is already used in shops, crafting recipes, job rewards or database records. Renaming the key can break existing players' inventories. Prefer correcting the image path or adding the missing image with the expected name. If you must rename an item key, plan a migration for old stored items.

Metadata and usable items

Metadata makes inventory items more powerful, but it also creates another failure point. A weapon attachment, ID card, evidence bag, phone, vehicle key or job item may require specific metadata fields. If the item appears but the action fails, copy the metadata object that is actually being stored. The giving script, usable-item callback and UI display must agree on field names. For example, serial, plate, owner, durability and description cannot be randomly renamed in one file without updating the consumers.

Ask Stellar AI to compare the item definition with the script that gives the item and the callback that consumes it. A good patch will not just “make it show”; it will preserve the server-side checks that decide who can create, use or transfer the item. Inventory systems are a common place for dupes and economy bugs, so the fix should be precise.

Restart order and bridge compatibility

ox_inventory should start before resources that register items, shops, stashes or usable callbacks through it. If you use QBCore or ESX with ox_inventory, also check that the bridge is active and compatible with your installed versions. A script written for qb-inventory can look similar but still fail under ox_inventory because exports, item metadata and callbacks differ. Mention your exact inventory resource and framework in the debugging prompt.

After patching, test three paths: giving the item from an admin command or test script, obtaining it through the real gameplay flow, and using or removing it. Also test an invalid path, such as a player without the job or a missing dependency. This proves the item exists, displays correctly and remains protected by the server.