Addon to FiveM Converter for Add-On Cars

This is the addon to FiveM converter: paste the gta5-mods.com link of an add-on car and get back a resource with the car's own spawn name and meta files, leaving the base game vehicles alone. Add-ons are the best fit for a server and the most tedious to convert by hand, because everything is locked inside a dlc.rpf archive that FiveM cannot read. This page shows what you get and what to check when you run several add-ons.

  • Paste the mod's gta5-mods.com link; you do not unpack the dlc.rpf yourself
  • Models go to the stream folder, meta files become data_file entries
  • The spawn name is the modelName in vehicles.meta

What is inside a dlc.rpf

An add-on vehicle is packaged the way Rockstar packages its own DLC. The dlc.rpf is an archive with a fixed internal structure:

  • content.xml and setup2.xml, which tell the single-player game what the pack contains and when to load it
  • a data folder with vehicles.meta, handling.meta, carvariations.meta and usually carcols.meta, sometimes vehiclelayouts.meta
  • a nested vehicles.rpf holding the model files (.yft) and texture dictionaries (.ytd)
  • often a second nested archive with tuning parts, and a language file with the car's display name

How that maps to a FiveM resource

In single player you copy the folder into dlcpacks and add a line to dlclist.xml. FiveM uses none of that. content.xml, setup2.xml and dlclist.xml have no role on a server; their job is done by the resource's fxmanifest.lua.

The language file with the display name has no counterpart that FiveM loads. Its job is done by a client script that calls AddTextEntry. An add-on zip from the converter includes one as vehicle_names.lua, with a name derived from the key in the mod's vehicles.meta; edit the quoted text in it to rename the car.

Models and textures from the nested archives are placed flat in the resource's stream folder, and FiveM serves everything in it automatically. In the converted zip the meta files sit in a common folder. The meta files are listed under files and then declared with a data_file line each, which is the FiveM equivalent of the entries in content.xml:

  • data_file 'VEHICLE_METADATA_FILE' for vehicles.meta
  • data_file 'HANDLING_FILE' for handling.meta
  • data_file 'VEHICLE_VARIATION_FILE' for carvariations.meta
  • data_file 'CARCOLS_FILE' for carcols.meta
  • data_file 'VEHICLE_LAYOUTS_FILE' for vehiclelayouts.meta, when the mod has one

Doing it without OpenIV

The manual route is to open the dlc.rpf in OpenIV, extract every nested archive, sort the files into stream and data and write the manifest. The converter performs that extraction and packaging from the mod's link, so the usual mistakes (a forgotten _hi.yft, a meta file that is in the folder but not in the manifest) do not happen. Manual vs automated conversion compares the two routes. To check or rebuild a manifest yourself, the FXManifest Generator writes a valid one. Both routes are written out step by step in the dlc.rpf to FiveM guide, which is also the page for a dlc.rpf that only exists on your disk: the converter takes a link, not an uploaded file. If OpenIV is not an option because you work on a Mac, Linux or a Chromebook, see converting cars without OpenIV; for a free desktop converter on Windows, see how rpf2fivem compares.

Spawn names and clashes between add-ons

The spawn name is the <modelName> value in vehicles.meta. It is not the mod title, the folder name or the name of the dlc.rpf. Model names must be unique across the whole server: if two resources define the same one, only one of the cars will be reachable.

Add-ons can also clash in less obvious ways. Cars with tuning parts carry a mod kit id in carcols.meta, and two cars sharing an id get each other's bumpers and spoilers, or none. Handling names can collide in the same way. The Car Pack Builder checks spawn names, handling names and kit ids when you merge resources.

Not sure a mod is really an add-on? See add-on vs replace, or the page on converting replace cars for what to do with the other kind. Both are single-player formats; SP to FiveM explains what changes on a server.

How to convert add-on cars with this site

  1. 1

    Copy the mod page link

    Open the vehicle on gta5-mods.com and copy the address of its page from the browser. It has to be the mod page itself (gta5-mods.com/vehicles/...), not the download button link or a search result.

  2. 2

    Paste it into the converter

    Go to the converter on the homepage, paste the link and start the conversion. The first 3 conversions are free; unlimited conversions are a one-time $15, listed on the pricing page.

  3. 3

    Install the resource

    Download the zip, extract the folder into your server's resources directory and add ensure folder-name to server.cfg. The Server.cfg Generator helps if you are setting up a server from scratch.

  4. 4

    Restart and spawn

    Restart the server, or run refresh and then ensure folder-name in the console. Spawn the vehicle with the <modelName> from common/vehicles.meta.

  5. 5

    Confirm the spawn name and the manifest

    Open vehicles.meta, note the <modelName> and spawn the car with it. If the car has tuning parts, check them at a mod shop; missing parts point at carcols.meta.

Got the mod page link copied? Paste it into the converter and carry on from step 3. Open the converter

Want every step with screenshots of the result? Follow the complete gta5-mods.com to FiveM workflow.

Common problems with add-on cars

The spawn name is not recognised

Use the <modelName> from vehicles.meta and confirm the resource started. More causes in invalid model fixes.

The car name shows as NULL

The display name was in the pack's language file, which FiveM does not load. An add-on zip converted here since 10 October 2026 includes vehicle_names.lua, which registers a name with AddTextEntry; check that the file and its client_script line in the manifest are still in the resource. A zip downloaded earlier, or one whose layout the converter did not recognise, has no such script: the NULL name fix shows the script and the manifest line, and the Vehicles.meta Generator can produce it.

Tuning parts are missing or belong to another car

A mod kit id in carcols.meta clashes with another resource, or carcols.meta is not declared in the manifest.

The car is silent

Its vehicles.meta references an engine sound from a separate sound mod. Install that sound or point the audio name at a stock vehicle, as shown in custom engine sounds.

The car drives like a default sedan

handling.meta is not being loaded, or its handling name does not match the one in vehicles.meta.

Seeing an error in the F8 console instead? Paste it into the Error Analyzer for the likely cause.

Addon to FiveM FAQ

How do I convert an addon car to FiveM?

Copy the address of the add-on car's page on gta5-mods.com, paste it into the converter and download the zip. It contains a resource folder with fxmanifest.lua, the mod's meta files, a stream folder and vehicle_names.lua, a script that gives the car a name in game. Put it in your server's resources folder and add an ensure line to server.cfg.

What does the addon to FiveM converter accept?

A link to a vehicle page on gta5-mods.com, for mods up to 300 MB. It does not take an uploaded dlc.rpf, a direct download link or a mod hosted on another site, and a custom engine sound pack inside the mod is not carried over.

Can FiveM load a dlc.rpf directly?

No. A FiveM server streams loose model and texture files from a resource's stream folder and loads meta files that are declared in fxmanifest.lua. The contents of a dlc.rpf have to be extracted and repackaged into that structure first.

Do I need OpenIV to convert an add-on car?

Not for the conversion. You paste the gta5-mods.com link and download a resource in which the archive has already been unpacked. OpenIV is only needed if you later want to edit the model or textures.

What is the spawn name of an add-on car?

It is the modelName value in the car's vehicles.meta file. The mod title and the dlc.rpf folder name are often different from it, which is the most common reason a spawn command fails.

What happens to content.xml and setup2.xml?

They are only used by the single-player game to register a DLC pack. On FiveM their role is taken by fxmanifest.lua and its data_file entries, so they are not needed in the resource.

Can two add-on cars conflict with each other?

Yes. The usual clashes are identical spawn names, identical handling names and identical mod kit ids in carcols.meta. Each of them has to be unique across all vehicle resources on the server.

Why does the converted car show NULL as its name?

The display name is stored in a language file inside the dlc.rpf that FiveM does not read, so a client script has to register it with AddTextEntry. An add-on zip converted here since 10 October 2026 includes that script as vehicle_names.lua, with a name derived from the mod's own key; edit the quoted text in the file to rename the car. If the name still reads NULL, the zip is older, the file or its client_script line was removed, or the converter left an unusual zip as it was. The NULL name guide has the manual fix.

Questions about limits, payments or downloads are answered in the main FAQ.

Guides and tools for this vehicle type

All free and Pro utilities are listed on the tools page.

Other vehicle and mod types

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