Start here · Vehicle Editor guide

Safe workflow and resource structure

Learn the recommended FiveM resource structure, backup workflow, validation steps, and safe testing process before editing files.

Recommended resource structure

text
my_vehicle/
├── fxmanifest.lua
├── data/
│   ├── vehicles.meta
│   ├── handling.meta
│   ├── carcols.meta
│   └── carvariations.meta
└── stream/
    ├── model.yft
    ├── model_hi.yft
    └── model.ytd

Scanner also supports __resource.lua, meta files in subfolders, multiple vehicles.meta files, nested stream folders, and workspaces containing multiple resources.

Recommended editing sequence

  1. Duplicate the original resource into a working folder.
  2. Open Vehicle Editor and scan that working folder.
  3. Check the resource and vehicle counts in the status bar, then locate the target spawn name.
  4. Make one logical group of changes at a time.
  5. Save and inspect both the output and any generated backup.
  6. Rescan after a rename, split, merge, or directory-structure change.
  7. Start the result on a development server and check the console.
  8. Spawn the vehicle and test its model, textures, handling, siren/audio, LODs, and collision before moving it to production.

Features that write directly to source files

FeaturePrimary effectAutomatic backup
Meta Editor (Visual)Changes a vehicle item in vehicles.meta.bak
Meta Editor (Code)Replaces the entire XML fileNo
Handling (Visual)Changes one CHandlingData item.bak
Handling (Code)Replaces the entire handling.meta fileNo
CarcolsReplaces the selected fileNo
Bulk Engine SoundChanges one or more vehicles.meta files.bak
Vehicle RenamerRenames stream files and replaces meta referencesNo
YTD EditorRepacks over the original YTDNo
3D XML EditorWrites XML and can compile over a YFTNo
Resource OptimizerReplaces selected YTD filesOne-time .backup
CleanupDeletes junk files and can replace a legacy manifestNo

Merger, Splitter, Sound Pack Builder, RPF Unpacker, and Export write to an output location. Use an empty output folder to prevent stale files from mixing with the new result.

What an automatic backup means

  • A .bak file is created by copying the current file before a save. A later save may overwrite the same .bak.
  • Optimizer creates .backup only when that backup does not already exist, so the first backup is preserved.
  • Automatic backups are not version history. Use Git or separate ZIP archives to preserve multiple editing stages.

Asset Escrow

Vehicle Editor does not decrypt or bypass FXAP. Merger detects .fxap files at a resource root and displays a warning. Continuing may break the resource or violate its license. Only modify assets you are authorized to edit.

FiveM verification checklist

  • ensure resource_name produces no manifest or data-file errors.
  • The spawn name is correct and does not conflict with another resource.
  • Standard and _hi models render correctly at near and far distances.
  • Textures, transparency, normal maps, and liveries render correctly.
  • Collision, doors, glass, wheels, lights, extras, and sirens still work.
  • handlingId in vehicles.meta matches handlingName.
  • audioNameHash points to the intended sound and its sound resource is started.
  • Client and server consoles report no missing file or invalid XML errors.
Ready to work on a resource? Download Vehicle Editor