FiveM fxmanifest.lua Generator

Build a resource manifest for a FiveM vehicle, script or NUI resource. Every key and data_file type it writes is taken from the FiveM resource manifest reference.

Tick only the files the resource really contains. Models and textures in stream/ need no entry.

fxmanifest.lua
fx_version 'cerulean'
game 'gta5'

version '1.0.0'

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

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

Want to skip the manual work?

Our main converter handles creating this file AND restructuring all your vehicle folders automatically.

What the fxmanifest generator does

Every FiveM resource needs a manifest in its root folder. fxmanifest.lua tells the server which game the resource targets, which files to send to clients and which scripts to run. Without it the folder is not recognised as a resource at all, and with a wrong one the resource starts but its contents are ignored.

This generator builds the file from a short form. You choose the fx_version (cerulean is the current one, see fx_version cerulean) and the game, fill in author, description, version and any dependencies, and tick what the resource contains: vehicle metas, a NUI page, client, server and shared scripts. The manifest updates as you type. Use it when a mod archive has no manifest, when you are still carrying an old __resource.lua, or when you start a new script and want a correct skeleton.

If you pick Red Dead Redemption 2, the generator adds the rdr3_warning line that a RedM server requires before it will start a resource, and leaves the vehicle meta lines out, because those data file types belong to GTA 5.

How to use it, step by step

  1. 1Leave fx_version on cerulean and the game on GTA 5 unless you have a specific reason to change them.
  2. 2Enter an author, a description and a version. All are optional but make the resource easier to identify.
  3. 3For a car, keep Vehicle Resource ticked and tick exactly the meta files the resource contains: handling.meta, vehicles.meta, carvariations.meta, carcols.meta, vehiclelayouts.meta.
  4. 4Set the folder the metas are in (data by default, or leave it empty if they sit in the resource root).
  5. 5Add Include UI or the script options only if the resource really has those files, then press Copy Code and save the text as fxmanifest.lua in the top level of the resource folder.

What the output means

For a vehicle the generator writes one files block that lists each ticked meta, followed by a data_file line for each with its type: HANDLING_FILE for handling.meta, VEHICLE_METADATA_FILE for vehicles.meta, VEHICLE_VARIATION_FILE for carvariations.meta, CARCOLS_FILE for carcols.meta and VEHICLE_LAYOUTS_FILE for vehiclelayouts.meta. Models and textures do not need to be listed; anything in the stream folder is picked up automatically.

The script and UI sections use placeholder paths such as client/main.lua, config.lua and html/index.html, which you replace with your own. The UI files are added to the same files block, because a ui_page has to be listed there too. The generator does not write lua54: the FiveM documentation marks that entry as deprecated.

If you would rather have the manifest derived from the files you actually have, the Resource Inspector suggests one for an uploaded resource on paid plans, and the Vehicles.meta Generator writes a manifest that matches the metas it creates.

Common mistakes

  • Putting the manifest inside data/ or stream/. It belongs in the resource root.
  • Keeping metas in the root while the manifest points at data/. Move the files or change the folder field so they agree.
  • Ticking a meta the resource does not contain, or forgetting one it does. Each meta needs both its files entry and its data_file line.
  • Shipping both __resource.lua and fxmanifest.lua. Delete the old one.

Frequently asked questions

Which fx_version should I use?

cerulean for anything new. bodacious and adamant are older versions that the generator offers for compatibility with existing resources.

Do I need to list .yft and .ytd files in the manifest?

No. Files in the stream folder are streamed automatically. The manifest only needs to list meta files and anything loaded by scripts or the UI.

My car has carcols.meta. Is that covered?

Yes. Tick carcols.meta and the generator adds it to the files block with a CARCOLS_FILE line. vehiclelayouts.meta is covered the same way with VEHICLE_LAYOUTS_FILE.

Can I use it for a RedM resource?

Yes. Choose Red Dead Redemption 2 as the game and the manifest gets game 'rdr3' plus the rdr3_warning line RedM requires. The vehicle meta options apply to GTA 5 only.

Is the generator free?

Yes, with no account and no limit. The manifest is generated in your browser.

Does the converter create a manifest for me?

Yes. Vehicles converted from a gta5-mods.com link on the homepage come back with a manifest already in place. This generator is for resources you assemble by hand.

More answers about conversions, limits and plans are in the general FAQ.

Need another car converted?

Paste a gta5-mods.com vehicle link into the converter and download a FiveM resource, then bring it back to this tool.

  • 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