Optimize Clothing
Recompress ped clothing/prop packs (mpClothes / EUP / dlc-side props) and split oversized .ytd archives - lean pack, same fxmanifest, same drawable/texture IDs.
Start here
Run Optimize Clothing on a copy of your source files
PulseConvert → Optimize
Open the workflow: PulseConvert → Optimize. If the tool is locked, check its access notice instead of assuming it is available to your account.
Prepare the exact kind of input listed for this feature: Bring an existing resource or compatible asset for clothing optimization. Keep an unchanged backup and ensure you have permission to reuse the assets.
Open the tool page and provide the requested source files and any displayed options. Check that the detected file types match the input requirement; do not replace unrelated files just to make an upload succeed.
Review the resulting files or job details. Expected outcome: Output is one FiveM resource with the same fxmanifest, plus a report of exactly which files (if any) are still oversized after optimizing.
Compare the result with your original in a local editor. For resources that load in FiveM, start with an isolated test server; inspect the first client/server console error and test the asset in game before installing it for players.
Practical example
Texture dictionaries above the streaming-memory target get downscaled against progressively smaller mip caps - drawable/component IDs are never touched. Keep the original file beside the result so you can compare what changed.
Before you begin
- Bring an existing resource or compatible asset for clothing optimization.
- Keep the untouched original, especially when downscaling textures.
- Sign in if prompted to submit the optimization job.
Overview of the setup
Prepare and select
Open Optimize and choose Clothing. Keep the original available to compare size and appearance.
Apply optimization
Recompress ped clothing/prop packs (mpClothes / EUP / dlc-side props) and split oversized .ytd archives - lean pack, same fxmanifest, same drawable/texture IDs. Select options appropriate to the target FiveM resource.
Compare and test
Read the optimization report, compare texture quality and file sizes, then validate the resource in a test server before replacing a live resource.
Features explained
What each feature does and what to check before publishing or installing the result.
Downscales oversized .ytd
Texture dictionaries above the streaming-memory target get downscaled against progressively smaller mip caps - drawable/component IDs are never touched.
Splits what still won't fit
Ped clothing .ytds that exceed FiveM read limits even after downscaling are split into multiple dictionaries with the original references relinked, instead of leaving the pack broken.
Rescan and report
Output is one FiveM resource with the same fxmanifest, plus a report of exactly which files (if any) are still oversized after optimizing.
If it still does not work
- If the tool rejects the input, compare your file extension and the files inside the archive to the input requirement above. Source files inside nested folders may need extra review.
- If the tool reports success but the result does not function, do not assume the file is compatible: inspect warnings, actual output names and their references, manifest files, and version compatibility.
- Review warnings and test the output before putting it on a live FiveM server.
Troubleshooting and safety checks
- An output remains oversized? Review the remaining file warnings rather than assuming every texture can be compressed indefinitely.
- Unexpected visuals or missing textures? Restore from the original and compare referenced dictionaries, material mappings and generated file paths.