FiveM vehicle classes: IDs 0–22 and Lua lookup

FiveM vehicle class ID list

The Cfx native reference lists the following engine classes. Use the numeric value when an API expects a class ID, and keep it separate from a model hash or entity handle. This reference concerns GTA V on FiveM; it does not establish GTA VI compatibility.

Inspect the vehicle you are sitting in

Place this example in a client script declared by your resource manifest. On a staging server, sit in a vehicle and run magnate_vehicleclass in F8. It prints the engine class ID and its localized label to the client console. Run it once outside a vehicle to check the empty-state message, then compare two known vehicle types.

This is a documentation-based diagnostic example, not a game-runtime test performed by Magnate. It reads information and does not spawn a vehicle, change handling, assign ownership or save a garage entry. Choose a unique command name if another resource already uses this one.

RegisterCommand('magnate_vehicleclass', function()
    local vehicle = GetVehiclePedIsIn(PlayerPedId(), false)
    if vehicle == 0 or not DoesEntityExist(vehicle) then
        print('Sit in a vehicle before running this command.')
        return
    end

    local classId = GetVehicleClass(vehicle)
    local label = GetLabelText(('VEH_CLASS_%d'):format(classId))
    print(('Vehicle class: %d (%s)'):format(classId, label))
end, false)

Entity handle, model hash and class ID are different inputs

GetVehicleClass expects a vehicle entity that exists in the game world. GetVehicleClassFromName expects a model hash, despite its name. Passing a display label, a class number or an entity handle into the model-hash API confuses different identifiers. Preserve the variable names and types as you trace a resource.

For a known model already available in your installation, a client-side expression such as GetVehicleClassFromName(joaat(knownModelName)) reads its class without requiring that specific vehicle entity. The variable knownModelName must contain the actual registered model name. Do not treat an arbitrary return value for an unavailable model as validation that a custom vehicle installed correctly.

A display label is another layer: GetDisplayNameFromVehicleModel returns the model’s gameName label, not a spawn command or class ID. When diagnosing a menu, record which field the menu uses instead of replacing several identifiers at once.

Why your dealership tier can disagree with the engine class

A server can organize its shop or race rules using its own categories. A label such as S tier, luxury or job-only is not one of the numeric engine classes above. Before editing a resource, identify whether its filter reads GetVehicleClass, a framework vehicle table, an allowlist or a database field.

For example, if the native returns 6 while a dealership places the same model in an expensive tier, those observations alone do not establish a bug. They may describe two independent systems. Trace the menu configuration and the gameplay restriction separately, then change the system that owns the behavior you intend to alter.

Do not use a client-side class check as the sole authorization for purchases, rewards or restricted vehicle access. Validate sensitive actions on the server against the server’s own rules and state. A cosmetic menu filter is not a permission boundary.

Troubleshooting a custom vehicle in the wrong category

Begin with a reproducible staging record: model name, resource version, game build, returned class ID and the menu category you expected. Compare the engine result with the resource’s category source. If only the menu differs, inspect its mapping before changing the vehicle package.

If the engine classification is unexpected, review the supplied vehicle metadata and check for conflicting resources defining the same model. Follow the package documentation, change one item at a time and repeat the diagnostic after the documented reload procedure. Avoid broad cache deletion as a substitute for identifying which configuration is being read.

• Test the current vehicle rather than accidentally reading the last vehicle.
• Confirm the model being tested matches the resource you changed.
• Keep a backup of the original metadata and configuration.
• Retest garage, dealership and job behavior separately after a change.
• Use the vehicle resource guide for manifest and package checks.

Questions, answered.