Start
Resource and EUP Merger
Two free tools that turn many packs into one FiveM resource with one ensure line: the Resource Merger for props, maps and animations, the EUP Merger for clothing.
What the mergers do
A FiveM server often ends up with one resource per prop pack and one per clothing pack, and a long list of ensure lines in server.cfg. The two mergers put those packs into one resource each:
- Resource Merger: props, map packs, vehicle textures and animation clips into one resource.
- EUP Merger: clothing and EUP packs into one clothing resource, with clashing collection names renamed for you.
Both write a fresh fxmanifest.lua for the merged files, so you never edit manifest lines by hand, and both ship a report of what went in and what was left out.
Which merger to use
Pick the merger by what is in the pack, not by where it came from:
Props from the 3D Generator, GLB to FiveM, Prop Reskin or Prop Studio
Merger:Resource MergerWhere:Merge into one in My assetsProp and map packs you bought or downloaded (ydr, ytd, ytyp, ymap)
Merger:Resource MergerWhere:Upload pageAnimated props from Prop Studio
Merger:Resource MergerWhere:Merge into one in My assetsAnimation or emote packs with ycd clips
Merger:Resource MergerWhere:Upload pageLivery Studio packs
Merger:Resource MergerWhere:Merge into one in My assetsEUP Maker packs and any other clothing pack
Merger:EUP MergerWhere:EUP Merger page
These stay as their own resources, because they need manifest lines that no merger carries over:
- Scripts: Lua resources, menus, jobs. The mergers only take game files.
- Weapons from the Weapon Studio: they load their weapon meta files through their own manifest.
- Tattoo packs and interiors: see Assets to keep as their own resource.
- Car packs with vehicles.meta, handling.meta or carvariations.meta: the metas would be left out.
Clothing and props never go together
A clothing pack in the Resource Merger is refused with That looks like a clothing pack. Merge clothing and props separately, into two resources.
What changes and what stays
- Spawn names stay. Every file keeps its name, so scripts, ymaps and spawn menus that use a merged prop keep working.
- One manifest. The merged resource has one
fxmanifest.luaand needs oneensureline. - Clothing collections stay separate. Each clothing pack keeps its own collection inside the merged resource. Only a pack whose collection name is already taken gets a new one.
- Extras are left out. Test commands, readmes, previews and GLB files of the original packs do not come along.
Merging does not make your packs smaller and does not change how much the game streams to players. It saves ensure lines, keeps server.cfg short and gives you one place to look when an asset is missing.
What it costs
Both mergers are free. Nothing is charged, and no credits are held while a merge runs.
Account
Resource Merger in the app:Yes, your finished assetsResource Merger upload:Not neededEUP Merger:Not neededPer merge
Resource Merger in the app:2 to 20 assetsResource Merger upload:2 to 10 ZIPs, 64 MB eachEUP Merger:1 to 6 ZIPs, 48 MB eachMerges per hour
Resource Merger in the app:No hourly limitResource Merger upload:3 per connectionEUP Merger:3 per connectionKept afterwards
Resource Merger in the app:In My assetsResource Merger upload:Only while the tab is openEUP Merger:Only while the tab is open
Next steps
Your first merged resource
Seven steps from your assets to city_props, merged in about 6 seconds.
Merge clothing packs
Two EUP Maker packs into city_clothing, with a collection renamed.
Merge ZIP files
Packs you bought or downloaded, without an account.
Installing on your server
One ensure line instead of many.