FiveM Resource Inspector
Drop a converted vehicle resource (ZIP or folder) and get a full diagnosis: missing files, broken manifests, oversized textures, handling mismatches and everything else that makes cars spawn invisible. Runs 100% in your browser, nothing is uploaded.
Drag & drop your resource here
.zip archive or the extracted resource folder
22 checks
Manifest, data_file lines, stream layout, model/texture pairs, meta cross-references.
16 MB limit
Flags every asset above FiveM's streaming limit before your players see missing textures.
Instant fixes
Every finding comes with the exact line or rename that fixes it. Pro gets a ready fxmanifest.
How to use Resource Inspector
- 1Drop the converted .zip (or the extracted folder) onto the upload area. Nothing is uploaded; the analysis runs in your browser.
- 2Read the score card, then fix red errors first. Each finding names the file and the exact line or rename that fixes it.
- 3Files over 16 MB: open the Texture Optimizer with the same zip. Missing manifest lines: paste the suggested fxmanifest (Unlimited).
- 4Re-run after your fixes. Zero errors means the car will spawn; then install it or add it to a pack.
Why do FiveM cars spawn invisible?
Nine times out of ten the .yft model is not in the stream/ folder, the texture dictionary is over 16 MB, or vehicles.meta points at a model or handling name that does not exist. The inspector checks all three, plus the manifest lines that tell FiveM to mount your meta files.
What does it check?
- fxmanifest.lua: fx_version, game, files {}, data_file lines
- Every meta file declared and mounted with the right type
- Assets outside stream/, spaces and uppercase in names, duplicates
- Files over the 16 MiB streaming limit and heavy textures over 8 MB
- Model ↔ _hi ↔ ytd pairs, vehicles.meta ↔ handling.meta ↔ carvariations ↔ carcols links
- Mod kit ids colliding with the vanilla 0–1023 range