Pro · included with UnlimitedFree preview · full report with Unlimited

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

Structure checks

Manifest, data_file lines, stream layout, model/texture pairs, meta cross-references.

Asset memory

Reads each asset's header and reports the physical and virtual MiB FiveM checks, with the console warning it will print above 16 MiB.

Instant fixes

Every finding comes with the exact line or rename that fixes it. Pro gets a ready fxmanifest.

How to use Resource Inspector

  1. 1Drop the converted .zip (or the extracted folder) onto the upload area. Nothing is uploaded; the analysis runs in your browser.
  2. 2Read the score card, then fix red errors first. Each finding names the file and the exact line or rename that fixes it.
  3. 3A .ytd above FiveM's 16 MiB oversized-asset warning: open the Texture Optimizer with the same zip. Missing manifest lines: paste the suggested fxmanifest (Unlimited).
  4. 4Re-run after your fixes. Zero errors means none of the checked problems remain; then install it or add it to a pack.

Why do FiveM cars spawn invisible?

Common causes: the .yft model is not in the stream/ folder next to fxmanifest.lua, an asset uses so much memory that FiveM warns it can fail to load, 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 load 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 the root stream/ folder (sub-folders are fine, nested stream folders are not scanned), spaces and uppercase in names, duplicates
  • Physical and virtual memory of every streamed asset against FiveM's oversized-asset warning (above 16, 32, 48 and 64 MiB), read from the file header rather than the size on disk
  • Model ↔ _hi ↔ ytd pairs, vehicles.meta ↔ handling.meta ↔ carvariations ↔ carcols links
  • Mod kit ids colliding with the vanilla 0–1023 range

What the Resource Inspector does and when to run it

The Resource Inspector is a FiveM resource checker for vehicles: it reads a vehicle resource, either the .zip you downloaded or the extracted folder, and runs a fixed set of checks against it. It parses the fxmanifest.lua, lists everything in the stream folder, reads the meta files and cross-references them: does every model in vehicles.meta have a .yft, is the handling entry it points at actually defined, is each meta mounted with the right data_file type. It also reads the header of every streamed asset and reports the physical and virtual memory FiveM measures for it, which is what FiveM's oversized-asset warning is based on.

Run it right after converting a car, before you copy it to the server, and again whenever a car spawns invisible, without textures, or not at all. It is also worth running on resources you got from somewhere else, because a manifest that looks fine at a glance can still miss one line. The analysis happens in your browser; the files are read locally and are not sent anywhere.

What is free and what Unlimited adds

Free, no account

  • The 0 to 100 score for the resource
  • The first 3 findings
  • Analysis in your browser, nothing uploaded

With Unlimited ($15 one-time)

  • Every finding, not only the first 3
  • Per-model table: .yft, _hi.yft, .ytd and each meta present or missing
  • Largest files, with memory use and size on disk
  • Suggested fxmanifest.lua covering every meta that was found
  • Downloadable text report

Unlimited is a single $15 payment, not a subscription. It also removes the limit on conversions from gta5-mods.com and unlocks the full output of the other two Pro tools. Get Unlimited or compare plans.

Reading the report

The score from 0 to 100 is a quick summary: 85 and above is shown in green, 60 to 84 in amber, below 60 in red. The findings underneath matter more than the number. Errors are things that stop the car from loading or rendering, warnings are things that usually cause trouble under load, and info items are housekeeping.

Asset memory follows FiveM's own warning. The server reads each streamed file's header and works out two figures: physical memory, which is mostly texture data, and virtual memory, which is mostly model data. An asset above 16 MiB on either figure is an info finding, above 32 MiB a warning, and above 48 MiB an error, because from there FiveM itself adds that oversized assets can and will lead to streaming issues; above 64 MiB FiveM prints its strongest warning. Each finding quotes the console line the server will print, in the form Asset <resource>/<file> uses <N> MiB of physical memory. Size on disk is shown next to it for reference only: FiveM does not check it, and none of these warnings stop the file from being streamed.

The free preview shows the score and the first three findings. With any paid plan you see every finding, a per-model table (yft, _hi.yft, ytd, vehicles.meta, carvariations and handling present or missing), the largest files in the resource, a suggested fxmanifest.lua covering every meta that was found, and a downloadable text report. See pricing for what each plan includes.

What to do next depends on the finding. A .ytd above the 16 MiB warning goes to the Texture Optimizer; an oversized model file (.yft) has to be simplified in a 3D tool. Missing metas can be created with the Vehicles.meta Generator. Once a resource is clean, add it to the server or merge it with others in the Car Pack Builder.

Common mistakes

  • Zipping the parent folder so the resource sits two levels deep. Upload the folder that directly contains fxmanifest.lua.
  • Fixing the manifest but leaving model files outside stream/. FiveM only streams assets from that folder.
  • Renaming a .yft without renaming the matching _hi.yft and .ytd, or without updating modelName and txdName in vehicles.meta.
  • Treating a green score as proof the car drives well. The inspector checks structure, references and asset memory, not handling quality or model polygon counts.
  • Judging an asset by its size on disk. Streamed files are compressed, so a small .ytd can still need far more than 16 MiB of memory; go by the memory figures in the report.

Frequently asked questions

Is my resource uploaded to your server?

No. The zip or folder is read by JavaScript in your browser tab and analysed there. Nothing from the resource is transmitted.

What is included for free?

The overall score and the first three findings. The full list of findings, the per-model table, the largest-files view, the suggested fxmanifest.lua and the report download are part of the paid plans.

Does it work with replace mods or only add-on cars?

It checks any vehicle resource that has a stream folder and a manifest. The cross-checks between vehicles.meta, carvariations.meta and handling.meta need those files, which add-on cars have. A stream-only replace resource has none, so the inspector reports that vehicles.meta is missing; for a replace mod that keeps the stock model names you can ignore that finding.

Why does it flag a file that is under 16 MB on disk?

Because FiveM does not look at the size on disk. It reads the file header and measures the memory the asset needs once loaded, and streamed files are compressed, so a .ytd of a few megabytes can need more than 16 MiB. The inspector reports that memory figure: above 16 MiB is an info finding, above 32 MiB a warning and above 48 MiB an error. The 16 MiB line is a warning, not a limit; the file is still streamed.

Can it fix the problems automatically?

It does not modify your files. It tells you which file and which line to change, and paid plans get a corrected fxmanifest.lua to paste in. Textures are fixed in the separate Texture Optimizer.

More answers about conversions, limits and plans are in the general FAQ.

Need another car converted?

Paste a gta5-mods.com vehicle link into the converter and download a FiveM resource, then bring it back to this tool.

  • 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