Flawless Developer Hub · free tool

Vehicle Resource Validator

Checks FiveM vehicle resources for missing files, manifest mistakes, broken .meta references and damaged or oversized game files, then explains each problem in plain language.

Check a vehicle resource

For cars. Choose one car resource (the folder with fxmanifest.lua), a whole [category] folder, or your whole resources folder. With several resources it also finds clashes between them: duplicate cars, files and tuning kit numbers. You can also drag a folder onto this box.

Your browser may ask you to confirm the upload. That only gives this page read access on your computer; nothing is sent over the internet.

How to read the results

Must fix
Something is broken or missing, for example a car with no model file. Players will notice.
Check
Often a problem, but sometimes done on purpose. Tap "Why?" on an item to see when it is safe to ignore.
FYI
Good to know; does no harm.
Passed
The resource passed every check this tool runs.
Skipped
Part of the resource could not be checked, for example files protected by FiveM's asset escrow. They are left untouched.

Memory meter

Shows how much graphics memory the resource's heaviest game file needs once loaded in game. Too much is a common cause of texture loss (the "city bug").

Light
Up to 16 MiB. No concern.
Heavy
16–48 MiB. FiveM already prints an "Oversized assets" warning; many of these together cause texture loss.
Oversized
Over 48 MiB. Likely to cause texture loss; shrink its textures.

FiveM servers start warning at about 16 MiB (seen in real server logs); the 48 MiB level is community guidance. Neither is an officially documented limit.

This tool checks file structure, references and whether game files are intact. It cannot tell whether a model is built correctly, how a vehicle drives, or whether it looks right in game. Every finding lists its limits. See all checks.