# qb-inventory reskin: change the UI, not the item system

A **qb-inventory reskin** changes the inventory's appearance. Replacing server logic, item storage or the inventory resource itself is a migration, not merely a theme. This guide provides an original downloadable CSS example, installation steps and a behavioral test matrix.

**Baseline:** [qb-inventory dc3d07fc](https://github.com/qbcore-fivem/qb-inventory/tree/dc3d07fc60139de569df38c5ac178ed4cada4577). Inspect your installed fork before applying it. Source review and documentation-browser tests do not replace FiveM runtime testing; the manual checks below remain necessary.

## Locate the actual frontend

| Path | Purpose | Scope of this change |
| --- | --- | --- |
| `html/index.html` | Vue template and frontend imports | Add a stylesheet link only |
| `html/main.css` | Upstream appearance | Keep unchanged |
| `html/app.js` | Inventory state and interactions | Keep unchanged |
| `html/images/` | Item images | Keep filenames stable |
| `fxmanifest.lua` | Client asset packaging | Add the new CSS path |
| `client/`, `server/`, `config/` | Gameplay and integration | Do not overwrite for a reskin |

The [pinned manifest](https://github.com/qbcore-fivem/qb-inventory/blob/dc3d07fc60139de569df38c5ac178ed4cada4577/fxmanifest.lua) explicitly names `html/main.css` rather than a general CSS wildcard. A new stylesheet needs both an HTML link and a manifest entry.

Keep the [inventory API reference](/docs/resources/qb-inventory) available for shops, stashes and exports. A visual theme cannot make incompatible inventory APIs compatible.

## Review a downloaded reskin before installing it

Ask for its intended upstream commit and compare its complete file list with your installation. Separate these changes before proceeding:

| Package contains | Treat it as |
| --- | --- |
| CSS and compatible image replacements | A presentation patch, still requiring tests |
| Replacement HTML or JavaScript | A frontend integration change; compare bindings and callbacks |
| Lua handlers, SQL or renamed item keys | A gameplay/data migration requiring its own review and recovery plan |

A screenshot establishes none of those compatibility properties. Back up the resource and affected data before testing an unknown package. Do not import SQL to fix a color or spacing problem.

## Apply the design in small steps
