What you will end up with
A folder in your server's resources/ directory, one line in server.cfg, and a car that spawns with its textures and the handling the mod author shipped. An add-on zip also brings two things you would otherwise write yourself: vehicle_names.lua, a script that gives the car a name on the HUD instead of NULL, and a README with the car's vehicle entry filled in for QBCore, Qbox and ESX. Total time for one car is about five minutes; for a pack of twenty it is about twenty minutes because most of that is uploading.
Note
Everything below runs in your browser. Nothing you upload to the Inspector, Optimizer or Pack Builder leaves your computer; the only thing sent to a server is the gta5-mods.com link in step 1.
Step 1: Convert the mod
Open the converter, paste the page link of the vehicle (it looks like gta5-mods.com/vehicles/2015-bmw-i8, not the download button link) and click Convert. In about 30 seconds you get a download button. For an add-on mod the zip holds a resource folder with fxmanifest.lua, a common/ folder with the mod's own meta files and a flat stream/ folder with the models and textures. The converter extracts those meta files; it does not write or tune them. A replace mod comes back as a stream-only resource in a folder named replace_resources, with no meta files, and custom engine sound packs are not carried over.
An add-on zip has two more files. vehicle_names.lua sits next to fxmanifest.lua and is loaded by a client_script line in the manifest; for each name key in the mod's vehicles.meta that has no text yet, it registers one, so the car shows a name instead of NULL. The name is derived from the mod's key, not its title (the key MUSTANG becomes "Mustang"), so to change it you edit the quoted text in that file and restart the resource. README-gta5modsconvertor.txt has the install steps and the car's vehicle entry for QBCore, Qbox and ESX, filled in with its spawn name; price, category and shop are placeholders. A replace conversion has neither, and zips downloaded before 10 October 2026 do not have them: for those, see the NULL name fix.
Tip
If the converter says the page could not be fetched, open the link in a new tab to confirm the mod is still public, then try again. Failed attempts do not use up a free conversion. Script mods and a few other mod types cannot be converted at all; the compatibility guide lists what works.
Step 2: Inspect the resource
Drop the zip you just downloaded into the Resource Inspector. It checks the manifest, the folder layout, the meta files and the memory each streamed asset needs, and gives the resource a score. Read the red errors first: those are the ones that produce an invisible car or a server error. Each finding tells you the exact file and the exact line to change. With Unlimited you also get the corrected fxmanifest.lua to paste over yours (keep the client_script 'vehicle_names.lua' line from the original, because the corrected manifest lists no scripts) and a per-model table showing which car is missing its _hi model, texture dictionary or handling entry. The Resource Inspector tutorial explains every check.
Step 3: Fix oversized textures
If the Inspector reported a .ytd that uses more than 16 MiB of physical memory (it quotes the Asset … uses N MiB of physical memory line FiveM will print), open the Texture Optimizer and drop the same zip in. Pick 1024 px for interiors and most bodies, 2048 px for liveried show cars. Click Optimize; each file shows its physical memory before and after. The tool removes the top mip levels so the smaller version already inside the file becomes the new top; no pixels are re-encoded. Download the optimized .ytd (free) or the whole rebuilt zip (Unlimited) and replace the files in your resource. The full walkthrough is in optimizing .ytd textures in your browser, and what FiveM's size warning means is in the "16 MB limit" explained.
Step 4: Build a pack (optional, recommended for 5+ cars)
Once you have several converted resources, drop them all into the Car Pack Builder. Give the pack a name, keep "identical shared assets once" ticked, and click Build. You get one resource with a single manifest and every data_file line, plus a list of conflicts: duplicate spawn names, clashing handling entries, mod kit IDs used twice. Fix the red ones before you ship; the pack is downloadable either way. Every option is covered in the Car Pack Builder tutorial.
Step 5: Install
Copy the resource folder (or the pack folder) into resources/. Add ensure foldername to server.cfg. Restart the server, or run refresh then ensure foldername in the console. Hosting panels, category folders and load order are covered in how to install FiveM car mods.
resources/
└── my_carpack/
├── fxmanifest.lua
├── data/… (a single converted car has common/ here instead)
└── stream/…
server.cfg:
ensure my_carpackStep 6: Spawn and verify
Spawn the car with its spawn name (the <modelName> in vehicles.meta, listed on the Inspector's model table and in the pack README). To confirm the spawn command itself works, try a base game car from the FiveM car spawn codes list first. If it is invisible or black, the invisible car guide walks through the seven causes; nine times out of ten the Inspector already told you which one. If the game says the model does not exist at all, go to fixing 'Invalid Model' instead.
Next: add the car to your vehicle shop
A car that spawns by command is installed, but it is not for sale yet. For an add-on conversion the vehicle entry is already written out in the zip's README for QBCore, Qbox and ESX: set the price, category and shop, then paste it where the guide for your framework says. The last step depends on the framework your server runs:
- QBCore: the vehicles.lua entry and qb-vehicleshop
- ESX: the esx_vehicleshop database row
- Qbox: qbx_core's vehicle list and the shop categories
- txAdmin: the same install done from the panel, on any framework
Free vs Unlimited in this workflow
- Free: 3 conversions per IP (+2 with your email), the Inspector score and first three findings, one texture file at 1024 px, packs of up to 3 cars.
- Unlimited ($15 once): unlimited conversions, every Inspector finding with the fixed manifest, any texture size with whole-resource batch, packs of any size.
- Complete Bundle ($20 once): Unlimited plus Glory Optimizer, the desktop batch texture optimizer.
- Server Pack ($39 once): the bundle plus two team seats. See pricing.
Tip
Create a free account before you start. Every conversion you make while logged in is kept in My Garage, so you can re-download it after the upstream link expires.
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