FiveM Car Invisible? 7 Causes and the Exact Fix for Each (2026)

Your add-on car spawns but is invisible, or you can hear it and sit in it but see nothing. Here are the seven real causes, how to tell which one you have in 60 seconds, and the fix for each.

Updated 5 min read9 sections

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

The 60-second diagnosis

An invisible car in FiveM is almost never a broken model. It is the game failing to find or load the model file, and there are only seven ways that happens. (If the game says the model does not exist at all, that is a different problem: see fixing 'Invalid Model'.) Before you touch anything, do this:

  1. Spawn the car and press F8. Look for lines containing the spawn name. Size warnings are printed in the server console when the resource starts, as Asset <resource>/<file> uses <N> MiB of physical memory. The Error Analyzer explains pasted console lines.
  2. Run the resource through the Resource Inspector. Drop the zip or folder in; it checks every cause below and names the file that is wrong.
  3. Keep the server console open while you ensure the resource. Errors about data_file or the manifest show up there, not in-game.

Tip

Failed spawns still consume the player's patience. Fix the resource on a dev server before pushing it to production.

Cause 1: The .yft is not inside stream/

FiveM only streams files inside the stream folder at the root of the resource. Subfolders inside it are fine; a stream folder nested somewhere else in the resource is not scanned. Converted mods from gta5-mods.com often arrive with the model next to the manifest, or inside stream/x64/levels/... from the original single-player structure. Both work on a local game and fail on FiveM. SP to FiveM sets the single-player and FiveM layouts side by side.

Fix: Move carname.yft, carname_hi.yft and carname.ytd into resource/stream/. Subfolders inside stream are fine.

Cause 2: An oversized model or texture dictionary

FiveM does not block large files, but it warns about any asset that needs more than 16 MiB of memory once loaded, and the bigger the asset the more likely it is to load late or not at all on a player's machine. A very heavy .ytd tends to show as a black or white car; a very heavy .yft as a car that stays invisible. High-poly showroom conversions are the usual offenders.

Fix: Start the resource and read the server console. Any file named in an Asset … uses N MiB warning should shrink, starting with the yellow and red ones. File size on disk is only a rough guide, because the files are compressed. Textures go down to 2048 px or 1024 px with Glory Optimizer; a model named in a virtual-memory warning has to be re-exported with fewer polygons or split into LODs. For a single dictionary, the in-browser Texture Optimizer is enough. Background: the "16 MB limit" explained. A black or white car rather than an invisible one is covered in FiveM missing textures.

Cause 3: The spawn name does not match the file name

vehicles.meta says <modelName>bmwm4</modelName> but the file is BMW_M4.yft, or bmwm4comp.yft. The game hashes the model name and looks for a file with that exact hash. Case matters on Linux hosts.

Fix: Make the file name, the modelName, and the txdName identical and lowercase. Rename the files rather than editing metas if you are unsure; fewer places to break.

Cause 4: vehicles.meta is not declared in fxmanifest.lua

The meta exists, but the manifest never tells FiveM to mount it. Without data_file 'VEHICLE_METADATA_FILE' the game has no idea the spawn name exists, so the spawn command either fails silently or spawns nothing.

Fix: Your manifest needs both the files entry and the data_file line for every meta:

lua
fx_version 'cerulean'
game 'gta5'

files {
  'data/vehicles.meta',
  'data/carvariations.meta',
  'data/handling.meta',
}

data_file 'VEHICLE_METADATA_FILE' 'data/vehicles.meta'
data_file 'VEHICLE_VARIATION_FILE' 'data/carvariations.meta'
data_file 'HANDLING_FILE' 'data/handling.meta'

The Inspector generates this block for the metas it finds in your resource (Inspector tutorial). If the resource has no vehicles.meta at all, generate one.

Cause 5: Missing or wrong handlingId

vehicles.meta points at <handlingId>BMWM4</handlingId> but handling.meta has <handlingName>BMW_M4</handlingName> or no entry at all. The car then has no valid handling entry, which can show up as wrong physics or a failed spawn.

Fix: Copy the handlingName from handling.meta into handlingId exactly. Use the Handling Editor if the handling file is missing entirely; mastering handling.meta explains what goes in it.

Cause 6: The _hi.yft is missing or the base .yft is a copy of it

Some conversions ship only carname_hi.yft. The base carname.yft is the model the game loads for the car; the _hi file is the close-up detail model. With only the _hi file the car usually does not render. With only the base file you usually get a lower-detail car that looks fine from far away and rough up close.

Fix: Ship both. If you only have one, duplicate it and name the copy accordingly; it is not ideal for performance but it renders.

Cause 7: A spaces-or-uppercase problem in the path

stream/BMW M4/bmwm4.yft fails on Linux servers. So does data/Vehicles.meta when the manifest says data/vehicles.meta.

Fix: Lowercase everything, underscores instead of spaces, and keep the manifest paths byte-identical to the real paths.

Still invisible?

Note

If the car is invisible for only some players, suspect Cause 2. Heavy assets fail first on machines with less memory.

Run the resource through the Resource Inspector. It flags every one of these causes with the exact file and the exact line to change, and the paid report includes a corrected manifest you can paste over yours. If you converted the mod by hand, try the automatic converter instead; it produces the stream layout and manifest correctly on the first try (manual vs. automated conversion compares the two routes).

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