Vehicle Registrar Free FiveM vehicle registrar for QBCore, Qbox and ESX
Drop your vehicle resources, set a price, category and shop for each car, and copy or download the entries your framework needs — every file is checked before you download it. Also makes a small resource that fixes "NULL" car names in garages.
This tool is in beta, so you may hit bugs or rough edges. If something breaks or looks wrong, please report it in the GXD Discord with what you did and a screenshot. Every report helps us fix it faster.
Drop a vehicle resource, a pack, a .zip or vehicles.meta files
Every vehicle in the metas becomes a row: display name and brand are filled from gameName and vehicleMakeName, category from the vehicle class, hash from the spawn code. Set prices and shops, then export to QBCore, Qbox, ESX or JSON — plus a names resource that fixes NULL in garages.
No files? Paste a vehicles.meta or type spawn codes
- Runs in your browser — nothing is uploaded.
- Only the .meta texts are read; models are never touched.
- Every export is read back and checked before you download it.
Everything runs in your browser. Your files never leave your computer.
Questions about Vehicle Registrar
What this free tool does, what it makes and how the files go into FiveM.
Drop the car's resource, a pack, a ZIP or its vehicles.meta, and every vehicle becomes a row with name, brand, price, category and shop. Copy the QBCore entries into the Vehicles list in qb-core/shared/vehicles.lua and restart qb-core. An older keyed format is there for qb-core builds that use QBShared.Vehicles['model'].
For ESX the Registrar writes SQL that adds the categories to vehicle_categories and the cars to vehicles; run it once in your database, and existing models are updated, not duplicated. For Qbox, paste the entries inside the return table of qbx_core/shared/vehicles.lua; Qbox sets shops in its vehicle shop config instead.
Garages and shops look up the car's gameName from vehicles.meta as a text label, and an add-on car often has no label for it, so the game shows NULL. The Registrar makes a small vehicle_names resource that calls AddTextEntry for every gameName and make; add ensure gxd_vehicle_names to server.cfg.
Yes. Every output is read back before it is offered: the Lua is parsed as data and each model, name, brand, price, category and type is compared with your table, and the SQL and JSON are checked the same way. There is also a neutral JSON list for other cores and custom vehicle shops.