FAQ

Not in game. The same files stream to players either way, so memory use and frame rate stay the same. Merging saves ensure lines, keeps server.cfg short and gives you one place to look when something is missing.

No. The EUP Merger copies the clothing files as they are. A collection that is too large to load stays too large after merging; remove packs you do not use instead.

Yes. Both mergers are free, with or without an account. The public pages allow 3 merges per hour per connection.

In the app it is Merge into one on My assets, also listed as Resource Merger on the tools page. For ZIP files there is the public page.

Not usefully. Vehicle packs need their vehicles.meta, handling.meta and carvariations.meta loaded by their manifest, and the Resource Merger only carries the files in the stream folder. Keep car packs as their own resources. Livery Studio packs, which only replace vehicle textures, merge fine.

No. Both mergers take game files only. Lua files are left out, so script resources stay separate.

No. Escrowed files are encrypted, so the mergers cannot read them. Keep them as their own resources.

Separately. Emote clips go into the Resource Merger, clothing into the EUP Merger. You end up with two resources, never one with both.

No. Every collection keeps its own YMT inside the merged resource. That is what keeps the drawable numbers and collection names of each pack as they were.

Merge again with all packs, the old ones and the new one, and replace the merged resource. Keep the original downloads for this: a merged resource cannot be merged a second time in the app.

Yes. A merged resource is plain game files and does not depend on a framework.

No. FiveM streams the merged resource to players when they join, like any other resource.