Mods & customization Guide

grzyClothTool for FiveM: download, projects and build checks

Find the original grzyClothTool release, compare self-contained and external projects, understand documented drawable limits and plan a clothing-pack test.

Original Magnate concept artwork; not a GTA VI screenshot Original concept artwork · Not game footage

Find the original project and release

The grzyClothTool repository describes a free, open-source GTA V add-on clothing-pack tool and labels it a work in progress. Its README highlights drawable and prop previews, texture previews and automatic splitting into additional add-ons. Use the original repository to identify the project before choosing a download.

The latest upstream GitHub release returned on November 15, 2026 was v1.3.0, published July 14. Its notes describe project storage choices, embedded texture export, automatic gender detection from filenames and duplicate inspection. Record the release you actually install rather than assuming every wiki screen corresponds to that build.

This is an independent documentation review and proposed test plan. Magnate has not installed the tool, opened a clothing pack or generated a resource. We link original sources rather than distributing an executable or implying a successful compatibility test.

Choose how a project keeps its source assets

The grzyClothTool v1.3.0 release notes distinguish self-contained projects, which copy files into the project folder, from external projects, which retain existing paths. The grzyClothTool FAQ connects missing-file reports to moved files in external projects and describes a relinking workflow.

Choose the mode according to how you will move and back up the project. A project file referring to assets elsewhere is not a complete archive of those assets. Keep the editable project and the files it references together in your handoff record.

Before moving a large library, rehearse with one small project and an asset you have permission to use. Copy it to a separate staging location, reopen it and check which files are found. This is a proposed portability test; the expected result should be recorded before the move.

Original project-portability checklist
CheckWhat to retainAcceptance question
Storage modeRelease and selected project typeAre assets copied or referenced?
Source assetsOriginal models and texturesCan the project find every intended file?
Build outputGenerated resource in a separate locationIs it distinguishable from editable source?
BackupProject plus its required assetsCan a copy be reopened without the working folder?
PermissionsSource and license for each assetMay these files be shared with the recipient?

Resolve the documented drawable-limit difference by version

The v1.3.0 release notes advertise support for 256 drawables per type with a settings option retaining 128. The wiki FAQ reviewed for this guide instead states 255 per type and says another add-on is created automatically when a type is full. These are different published numbers; Magnate has not run a boundary test to reconcile them.

Do not translate either statement into a universal limit for every release, resource or server setup. Retain the installed version and settings, inspect the generated add-ons and test their intended items. Automatic splitting is a packaging behavior, not a guarantee that a downstream outfit system accepts every result.

When updating an existing pack, preserve a known-good export and an identity record for representative items. Compare the rebuilt result with the old one before replacing production files. A changed index or collection reference deserves its own verification rather than being dismissed as a visual-only change.

Keep drawable properties separate from list labels

The grzyClothTool drawable-properties reference distinguishes a display label from the game name derived from type and number. It describes changing drawable type or sex as a renumbering operation. Those settings matter when a project list looks correct but an external reference points at the wrong item.

The same reference documents a first-person alternate .ydd and a cloth-physics .yld as separate linked files. It also separates list grouping and tags from generated shop metadata. A useful filename or tag helps organization but is not a substitute for checking the exported model and metadata.

Pick a small representative set: one component, one prop and any asset requiring an alternate or physics file. Preserve their original names, intended ped and expected appearance. Review each relevant output rather than extrapolating from the first preview that opens successfully.

Understand which optimization step changes the originals

The wiki FAQ distinguishes applying optimization during a build from Apply now. It says the build-only path changes the built resource, while Apply now retains originals beside the files with a .grzy-backup suffix and can be reverted. Read the installed tool’s behavior before using an operation on your only source copy.

Keep an independent backup and test one original texture before applying changes across a collection. Record the source dimensions and appearance, operation selected and produced files. Compare the result at the intended viewing distance and on the intended model.

A smaller output is only one observation. It does not establish unchanged visual quality, correct UV placement or in-game behavior. Preserve both versions until the target-environment check is complete.

Test the generated clothing resource separately

Use the clothing templates guide for model-specific texture work and the clothing-pack guide for the server integration layer. A packing tool, a clothing selection menu and a saved-outfit system are separate parts of the workflow.

On staging, load the generated resource using its supported instructions. Check the representative component and prop on the intended ped, including texture variants and any first-person alternate. Save the intended outfit through your actual appearance resource, reconnect and compare the saved result.

Have a second test player observe the same asset where possible. Keep client observations separate from server resource state. Mark any untested target edition or appearance integration explicitly; this page establishes no GTA VI compatibility.

  • Record the tool release, storage mode and build settings.
  • Preserve original assets and a known-good export before rebuilding.
  • Inspect generated resources and the files required by representative items.
  • Check components, props, textures and linked alternates separately.
  • Verify saved outfits after reconnecting through the chosen appearance system.
  • Retain logs and a minimal project when reporting a reproducible issue.

Questions, answered.

Is grzyClothTool free?

The original repository describes it as free and open source, and also labels it work in progress. Review the original project and release notes for the version you intend to use.

Does grzyClothTool support 255 or 256 drawables per type?

The reviewed v1.3.0 release notes say 256, while the wiki FAQ says 255. This guide does not resolve the difference through testing. Check your installed version, settings and generated add-ons.

Why does an external project report missing files?

The wiki FAQ describes moved external source files as a cause and provides a relinking workflow. Preserve the project’s original paths and inspect which files are actually missing before rebuilding.

Sources & editorial notes

Source review: November 15, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.

  1. grzyClothTool repository Project source reviewed November 15, 2026. Release/wiki limit difference retained; no installation or export test.
  2. grzyClothTool v1.3.0 release Project source reviewed November 15, 2026. Release/wiki limit difference retained; no installation or export test.
  3. grzyClothTool FAQ Project source reviewed November 15, 2026. Release/wiki limit difference retained; no installation or export test.
  4. grzyClothTool drawable-properties reference Project source reviewed November 15, 2026. Release/wiki limit difference retained; no installation or export test.

Published by an independent editorial brand. Read our editorial standards.

Find your next move

Search the Magnate guide library.

Browse every guide