Have the resource on disk already? The Resource Inspector checks its manifest, stream files, textures and metas in your browser and lists what is wrong. Open the Resource Inspector
What the Inspector does
It reads a FiveM vehicle resource the way the game does: it finds the manifest, checks which meta files are declared and mounted, walks the stream folder, and cross-references model names between vehicles.meta, handling.meta, carvariations.meta and carcols.meta. It also reads the header of every streamed asset and works out the memory FiveM measures for it. It then reports every problem with the exact fix. It never uploads your files. In the complete conversion workflow it is step 2, straight after converting.
Step 1: Upload the resource
Open the Resource Inspector. Drag the converted .zip onto the drop zone, or click "Choose folder" and pick the extracted resource folder. Nested zips (a zip containing the resource folder) are fine; the tool finds the folder with the manifest. RAR archives must be extracted first.
Step 2: Read the score card
You get a score from 0 to 100, the file count, total size, how much of it is streamed, and how many models were found. Below that: counts of errors, warnings and info. Anything with errors will not work correctly in game; warnings are quality problems; info is housekeeping.
Step 3: Fix errors top to bottom
Findings are sorted by severity. The most common errors and what to do:
- Not in stream/: move the file into
stream/. Only that folder is streamed. This is cause 1 of an invisible car. - "uses N MiB of physical memory": the asset is above FiveM's oversized-asset warning. Above 16 MiB this is an info finding, above 32 MiB a warning, and above 48 MiB an error, because from there FiveM adds "Oversized assets can and WILL lead to streaming issues". The finding shows the exact console line (
Asset <resource>/<file> uses <N> MiB of physical memory.). Physical memory is mostly texture data, so a.ytdgoes to the Texture Optimizer; virtual memory is mostly model data, and a model file has to be simplified in a 3D tool (what FiveM's warning means). - Meta not in files {} / no data_file line: add the lines the finding shows to
fxmanifest.lua, or paste the suggested manifest (Unlimited). - handlingId not found: copy the exact
handlingNamefromhandling.metaintovehicles.meta(what the handling file does). - Model referenced but no .yft: the spawn name in
vehicles.metaand the file name do not match; rename one. In game this shows up as an "Invalid Model" error.
Step 4: Check the per-model table (Unlimited)
Each spawn name gets a row: .yft present, _hi.yft present, .ytd present, listed in vehicles.meta, listed in carvariations.meta, and the handling ID with a red mark if it does not resolve. A row with all green ticks is a car that will spawn.
Step 5: Use the suggested manifest (Unlimited)
The bottom-right card holds a complete fxmanifest.lua generated from the meta files actually present in your resource, with the right data_file type for each. Copy it over yours when the original is missing lines. It does not include scripts, so re-add any client_script entries you had. For a zip from our converter that means the line client_script 'vehicle_names.lua': without it the car's name shows as NULL again. Without Unlimited, the free FXManifest Generator builds a manifest from a form.
Step 6: Re-check and ship
Apply the fixes, re-zip or re-select the folder, and run it again. Aim for zero errors; warnings about _hi models and assets above 32 MiB are worth fixing but not blocking. If the server runs FiveM for GTAV Enhanced, clear the errors before you run Cfx.re's Alchemist on the resource, because it carries mistakes over unchanged (Alchemist vs. mod converters). Then install it or pass it to the Car Pack Builder (tutorial). The rest of the toolkit is compared in best tools for FiveM server owners.
Every check, in one list
Manifest: fx_version, game, files {}, data_file lines, entries pointing at missing files, wrong data_file types. Layout: assets outside stream/, spaces and uppercase in names, duplicates, junk files in stream/. Asset memory, read from each streamed file's header as FiveM does (physical is mostly texture data, virtual mostly model data): above 16 MiB (info), above 32 MiB (warning), above 48 MiB (error, where FiveM adds its streaming-issues sentence), above 64 MiB (error, FiveM's strongest warning). Size on disk is shown as a secondary figure and is not what FiveM checks; a large file with no readable header is listed as info with its disk size only. Models: yft / _hi / ytd pairs (tuning-part .yft files named in carcols.meta are not treated as vehicles), vehicles.meta ↔ handling ↔ carvariations ↔ carcols links, mod kit IDs in the vanilla 0–1023 range, long or uppercase spawn names.
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