FiveM Vehicle Shop Entry Generator
List your add-on cars and copy the entries that put them in the vehicle shop: QBCore vehicles.lua lines, Qbox entries and the ESX SQL insert. It runs in your browser; nothing is uploaded.
The defaults fill the rows where price or category is empty. They are starting values, not recommendations: set your own. An empty display name becomes the spawn name, an empty brand becomes Custom. Spawn names are written in lowercase.
One car per line: a spawn name alone, or spawn, name, brand, price, category separated by commas or tabs. Rows copied from a spreadsheet work as they are.
Paste inside the Vehicles list, before its closing brace, then restart the server. Format of qb-core 1.3.0. QBCore guide
{ model = 'gtr35', name = 'GT-R R35', brand = 'Nissan', price = 185000, category = 'sports', type = 'automobile', shop = 'pdm' },Converted cars come with these entries
An add-on car converted from a gta5-mods.com link on this site has a README in its zip with the QBCore, Qbox and ESX entries filled in for that car. Price, category and shop are placeholders you change. What the zip contains
What the Vehicle Shop Entry Generator does
An add-on car that is installed and started can be spawned, but a framework does not know it yet. Before players can buy it in a vehicle shop, and before garages show its name, the car has to be added to the framework's own vehicle list: a line in shared/vehicles.lua of qb-core, a keyed entry in shared/vehicles.lua of qbx_core, or a row in the vehicles database table that esx_vehicleshop reads.
This tool writes those entries for a whole list of cars at once. You give it the spawn name, a display name, a brand, a price and a category for each car, in the table or as a pasted list, and it shows the QBCore lines, the Qbox entries and one ESX INSERT statement, each with a copy button. It runs in your browser. Nothing is uploaded, and nothing is written to your server: you paste the result yourself.
The three formats are the ones this site's converter writes. They were read in the frameworks' repositories on 2026-10-10: qb-core 1.3.0 (commit 9b3cddc), qbx_core (commit 1825a3c) and esx_vehicleshop in ESX-Legacy-Addons (commit ccda737). An older or modified framework can use a different shape; if the entries already in your file look different, copy their shape and keep the values. A car converted on this site does not need this tool for its own entries: its zip has a README with the three entries filled in for that car, with the price, category and shop left as placeholders (what the zip contains).
How to use it, step by step
- 1Add one row per car, or open the list box and paste one car per line: a spawn name alone, or spawn name, display name, brand, price and category separated by commas or tabs.
- 2Check the spawn names. Each must be the
<modelName>of the car in itsvehicles.meta, written with letters, digits and underscores only. The tool writes it in lowercase. - 3Set a price and a category for every car. The default price and default category fill the rows where you leave those fields empty; they are starting values, not recommendations.
- 4For QBCore, set the shop to the key of a shop in the
Config.Shopstable of qb-vehicleshop. The stock dealership ispdm. - 5Choose the tab for your framework, press Copy and paste the result where the note above the code says. Then restart as described there.
Where each output goes
QBCore: every car is one line with model, name, brand, price, category, type and shop. Paste the lines inside the Vehicles list in qb-core/shared/vehicles.lua, before its closing brace, and restart the whole server, because qb-vehicleshop and qb-garages read the list from the core when they start. You do not write a hash; qb-core computes it. The steps and the checks for a car that does not show up are in the QBCore vehicle shop guide.
Qbox: every car is a keyed entry with a hash line, pasted inside the table that qbx_core/shared/vehicles.lua returns. The hash is the spawn name between backticks, and the backticks have to stay. There is no shop key: shops are assigned in qbx_vehicleshop, and a shop only offers the categories listed for it in qbx_vehicleshop/config/shared.lua. The stock PDM shop does not list sports or super, so a car in one of those categories needs the category added there. The Qbox guide shows how.
ESX: one INSERT statement for the vehicles table with a row per car. The name column holds the brand and the display name together, or the display name alone when you gave no brand or the two would be longer than the column's 60 characters. Run it on your server's database, then run restart esx_vehicleshop in the console. The category has to be a name that exists in your vehicle_categories table. See the ESX vehicle shop guide.
Texts are escaped for the language they end up in. A display name with an apostrophe, a double quote or a backslash is written so that the Lua string and the SQL string end where they should. Line breaks inside a field are turned into spaces.
Common mistakes
- Using the folder name or the mod's title as the spawn name. It is the
<modelName>value invehicles.meta, which is also the name of the main.yftfile. - Pasting the QBCore lines into Qbox or the other way round. The two frameworks do not share a format.
- ESX: a category that is not in
vehicle_categories, or one that differs only in upper and lower case. The row is saved but the car never appears in the shop. - ESX: running the statement twice.
modelis the primary key of the table, so the second run stops with a duplicate entry error. - Qbox: replacing the backticks on the hash line with quotes. That stores a text instead of a hash.
- Leaving the default price and category in place. They are there so the entry is complete, not because they suit your car.
Frequently asked questions
Which framework versions is the format checked against?
The formats in the repositories on 2026-10-10: qb-core 1.3.0 at commit 9b3cddc, qbx_core at commit 1825a3c and esx_vehicleshop from ESX-Legacy-Addons at commit ccda737. If your server runs an older or modified version and the entries already in your file look different, follow the shape your file uses.
Does the tool add the cars to my server?
No. It writes text for you to paste. Nothing is uploaded and nothing is changed on your server or in your database. The car resources themselves have to be installed and started separately.
Where do I find a car's spawn name?
It is the <modelName> value in the car's vehicles.meta, and the name of its main .yft file in the stream folder. The Resource Inspector shows it for an uploaded resource without opening any file.
What can I paste into the list box?
One car per line. A line can be a spawn name alone, or up to five fields in this order: spawn name, display name, brand, price, category. Separate the fields with commas or with tabs, which is what a copy from a spreadsheet gives you. Use tabs when a name contains a comma. Missing fields take the defaults.
My display name has an apostrophe or quotes. Is that a problem?
No. An apostrophe is written with a backslash in front of it in the Lua entries and doubled in the SQL statement, which is how each language expects it. Backslashes are escaped as well, in the form MySQL and MariaDB read by default.
Why does the ESX output have no brand or type?
The vehicles table of esx_vehicleshop has four columns: name, model, price and category. The brand is put in front of the display name in the name column, as in this site's ESX guide. A third-party shop script for ESX can use its own table or config file; check its documentation.
Do converted cars from this site need this tool?
Not for their own entries. The zip of an add-on conversion has a README with the QBCore, Qbox and ESX entries filled in for that car; you only change the price, the category and the shop. This tool is for cars from other sources, for whole lists, and for entries with your prices and categories already in them. What the zip contains.
Is it free?
Yes, with no account. The list is limited to 200 cars at a time.
More answers about conversions, limits and plans are in the general FAQ.
Related guides
Terms explained
Related tools
- Vehicles.meta Generatorvehicles.meta, carvariations.meta, display-name script and manifest from one spawn name.
- Resource InspectorFind out why a car spawns invisible: checks the manifest, stream files, asset memory and metas.
- Car Pack BuilderMerge many cars into one resource with a single manifest, deduped textures and conflict checks.
Have a gta5-mods.com link ready?
Paste it into the converter and download a FiveM resource with the stream folder, meta files and fxmanifest.lua in place.
- 3 conversions free, no account needed
- 2 more free if you leave an email
- After that: $15 once for unlimited conversions and the Pro tools. No subscription, 14-day refund policy