Resource tools · Vehicle Editor guide
One-Click Export to FiveM
Collect recognized workspace files into one deployable FiveM resource and generate a fresh fxmanifest.lua.
Export collects recognized files from every workspace root into one output
resource and generates a new fxmanifest.lua.
Export a workspace
- Add and scan the workspace folders.
- Open Export.
- Choose Export Destination Folder.
- Enter Resource Name (default:
optimized_vehicles). - Click Export Now and wait for progress to finish.
- Open the result from the completion dialog.
File placement rules
| Input | Destination |
|---|---|
.yft, .ytd | stream/ |
| Recognized vehicles, handling, carcols, carvariations, or vehiclelayouts meta/XML | data/ |
.rel, .dat, .nametable | audioconfig/ |
.awc | sfx/, or sfx/dlc_<prefix>/ when its parent uses that pattern |
If a destination filename already exists, Export appends _1, _2, and so on.
Other file types are not copied. A standard manifest is generated from detected
files and audio prefixes.
Important limitations
- All workspace roots are combined and metadata folder structure is flattened.
- Collision renaming preserves both files, but internal references or the manifest may still use the old name.
- Audio prefixes are detected only from filenames ending in
_game.dat; some REL layouts require manual manifest fixes. - Scripts, configuration, licenses, README files, and custom assets are omitted.
- An existing output directory is not cleared before export.
“Export successful” means copying completed, not that the resource is valid. Review the output, remove stale files, correct the manifest, and test on a development server before deployment.