Resource tools · Vehicle Editor guide
Vehicle Merger
Combine multiple FiveM vehicle resources into one organized output resource without moving the original sources.
Merger creates one output resource from multiple scanned vehicle resources. It does not move or delete the sources, but an existing output with the same name can be mixed with or overwritten. Use a new output name and directory.
Merge resources
- Scan every resource you want to combine.
- Open Merger.
- Enter Pack Name and choose Output Location.
- Select resources individually or use Select All.
- Click Merge N Resources and wait for completion.
- Open the result from the completion dialog and inspect
spawn_names.txtand the generated manifest.
FREE accounts are limited to three vehicles per merge. PRO and early-access accounts are not subject to that application limit.
Pre-merge validation
- Duplicate model names across selected resources stop the merge.
- A
.fxapfile at a resource root triggers an Asset Escrow warning. You must explicitly cancel or continue. Continuing does not decrypt the file and can break the resource or violate its license.
Output structure
data/<resource-name>/receives recognized standalone meta files.stream/combines stream content from every source.audioconfig/andsfx/are copied when present.- A new
fxmanifest.luais generated. spawn_names.txtlists the names recorded during merge.
Recognized standalone meta files are vehicles.meta, handling.meta,
carcols.meta, carvariations.meta, vehiclelayouts.meta, dlctext.meta,
contentunlocks.meta, caraddoncontentunlocks.meta, and shop_vehicle.meta,
from either the resource root or its data folder.
Important limitations
- Stream files with an identical destination path can overwrite an earlier file.
- The generated manifest registers standard meta patterns. Custom
data_filedeclarations require manual review. spawn_names.txtcan reflect source folder names instead of every model in a complex pack.- Audio prefixes are inferred from config filenames; custom audio manifests may still require correction.
Verify the result
Confirm that each spawn name is defined once, all required metadata is present, and manifest paths are correct. Disable the source resources while testing the merged pack to prevent duplicate definitions.