FiveM Car Not Spawning?
9 Causes & How to Fix Each One

1. Missing data_file lines in fxmanifest.lua

The #1 cause in purchased and downloaded cars. The manifest lists the meta files under files { } but is missing the matching data_file declarations — so FXServer loads the files but never tells the game engine what they are. The model is never registered and you get "Invalid model".

Every meta needs its declaration:

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

Fix: add the missing lines, or regenerate the manifest automatically with the FiveMRides Converter, which writes a complete, validated manifest for any vehicle.

2. A Lua syntax error in the manifest

One missing comma inside a files { } block kills the entire resource silently — every entry after the error is ignored. We once traced a box-wide outage of sound-equipped cars to exactly this: a files block written with newlines but no commas.

files {
    'data/vehicles.meta'      <- missing comma!
    'data/handling.meta'
}

Fix: the console says Syntax error in fxmanifest.lua with a line number. Add the commas. When in doubt, paste the manifest into any Lua linter.

3. Stream/ instead of stream/ (Linux servers)

Windows file systems ignore case; Linux does not. A resource with a capitalized Stream/ folder works perfectly on your Windows test box, then silently fails to stream a single asset on the production Linux VPS — the classic "works on localhost, breaks on the server" case. The car registers (metas load) but the model never streams, so it spawns as a tanker/trailer or not at all.

Fix: rename the folder to lowercase stream/. Check data/ too, and make sure file names inside match any explicit paths in the manifest exactly, character for character.

4. Spawn name ≠ model name

The spawn name is the <modelName> in vehicles.meta — and it must match the YFT file name in stream/ (e.g. modelName m3mw requires m3mw.yft + m3mw_hi.yft + m3mw.ytd). If a reseller renamed the files but not the meta (or vice-versa), the game looks for a model that does not exist.

Fix: open vehicles.meta, copy the exact modelName, and verify every streamed file uses it as its base name. Spawn with that exact name, not the marketing name of the car.

5. Oversized YTD (>16 MB) — the "tanker bug"

FiveM has a hard 16 MB per-YTD streaming limit. A 68 MB uncompressed texture dictionary will register fine, then fail to stream — the engine gives up and substitutes whatever is in memory, which is how you end up with a tanker, a trailer, or an invisible car. We fixed a pickup truck doing exactly this by compressing its YTD from 68 MB to 13.5 MB; it spawned instantly afterwards.

Fix: run the resource through the FiveMRides Optimizer — it resizes oversized textures and applies per-type compression (BC5 normals, BC7 speculars, DXT diffuse), typically cutting YTD size 40–70% with no visible quality loss. Also read the texture loss guide — same root cause, different symptom.

6. The manifest references a file that does not exist

If files { } or a data_file points to data/carcols.meta and that file is missing (or in another folder), FXServer aborts loading the resource's data — and the model never registers. This commonly happens after manual "cleanups" or partial re-uploads over FTP.

Fix: cross-check every path in the manifest against the actual files on disk. Delete references to files that are intentionally gone, or restore the missing files.

7. Modkit ID conflicts (broken tuning, random parts)

Every vehicle's tuning kit has a numeric <id value> in carcols.meta. Two cars sharing the same ID — or an ID above 65535 — pollute the server-wide modkit table. Symptoms range from broken tuning menus and missing liveries to body parts that randomly appear or disappear after a server restart. In an audit of 832 vehicles we found 568 with meta defects like this — it is the most underdiagnosed problem in FiveM car packs.

Fix: give each vehicle a unique modkit ID below 65535, and make sure the kit name matches between carcols.meta and carvariations.meta. Our broken vehicle repair guide covers this step by step.

8. Spawns invisible / as a bare frame (extras & modular bodies)

Two distinct causes look identical in game. (A) The car was built with <requiredExtras> and your garage/spawn script disables extras — the body panels are extras, so the car appears see-through. (B) The body is split into modkit parts (a "modular body" build): without the right mods applied, the car spawns as a rolling chassis.

Fix: for (A), force extras on at spawn; for (B), apply the body mods via script — or run the car through our Converter, whose Spawn Doctor detects both patterns and ships a small Lua fix that handles them automatically.

9. The resource is simply not started

Obvious, but it closes a surprising number of tickets: the folder was uploaded but ensure yourcarname was never added to server.cfg; the resource name contains spaces or special characters; or it sits nested one folder too deep (resources/[cars]/carname/carname/). After config changes, restart the server — a plain refresh is not always enough. On the client side, a corrupted cache can also keep serving a stale broken version: delete %localappdata%\FiveM\FiveM.app\data\cache.

Fix: flat folder layout, no spaces in the resource name, ensure line present, full restart. New to this? Follow the step-by-step install guide.