grzyClothTool builds GTA5 addon clothing packs in the open

A modding tool that is explicitly unfinished

grzyClothTool is a free tool to easily create and manage GTA5 addon clothing packs, and the first thing the documentation tells you is that the tool is still in a work in progress state, with the warning that you will likely encounter bugs, missing features or functionality issues. The project title itself carries the WIP marker. That framing is unusual and worth taking at face value rather than reading past. The stated premise is that you can now do almost everything you could do before with other available tools, but without spending any money, and the open source angle is part of the pitch, with the argument that you do not have to be scared about running obfuscated executables that nobody knows what they are doing in the background. The project is GPL-3.0 licensed, written in C#, and the last push to the repository was on 2026-08-14, with v1.3.0 released on 2026-07-14 after v1.2.1 in January 2026 and v1.1.3 in December 2025. The audience is narrow and obvious: a GTA5 modder making clothing for their own game or for the wider modding scene.

The 3D previewer and the CodeWalker dependency

The most interesting part of the tool is the preview, and the documentation is explicit about where it comes from. The Mentions section credits dexyfex, the author of CodeWalker, and states that the 3D Previewer would not be possible without him and CodeWalker, with a link to support the author on Patreon. The repository layout backs that up, since CodeWalker/ appears as a top level directory alongside the tool's own projects. The preview capability is what separates this from a file manager for addon folders. The feature list names easily preview your textures, easily preview ALL ped props, and the ability to preview multiple drawables at once. The prop preview in particular is the kind of thing you only discover you need after you have already exported the wrong thing once, because the geometry of a hat or a bag sitting on the wrong body part is invisible in a flat texture viewer. Two of the preview features are unusually specific and read like answers to reported problems. One shows how much your hair will shrink under hair in the 3D Previewer, and another shows how much your heels require height in the same view. Both are the kind of measurement that only makes sense once the model is on screen.

The 128 item limit, and why the tool splits packs for you

The other exclusive feature worth singling out is the handling of the addon size limit. The documentation states that you do not have to worry about the 128 items limit in one addon, because the tool automatically splits to multiple addons for you. This is a small implementation detail that removes a genuinely annoying class of problem, because the limit is a constraint of the game rather than of the editor, and a creator who does not know about it will produce a pack that silently fails to load for their players. The design here is defensive rather than clever. Rather than refusing the pack or warning about it, the tool reshapes the output into several addons that the game will accept. The repository structure is a Visual Studio solution, grzyClothTool.sln, with the main project in grzyClothTool/, a shared library in grzyClothTool.Shared/, a WPF test project named grzyClothTool.Tests.Wpf/ and a separate grzyClothTool.UnitTests/ project. The separation of a WPF test project from a unit test project tells you something about how the author works, since the WPF side needs a desktop to run against while the unit tests do not.

Building it from the repository

There is no installation section in the documentation and no packaged release described, so the practical route is building from source. The repository is a Visual Studio solution with a .gitattributes file, a .gitignore and a .github directory, and the primary language is C# with a WPF user interface, which means the tool is built and run on Windows. The documentation does not describe the build steps, the required .NET version or the runtime prerequisites, and it does not document a rollback or a release process, so anyone planning to depend on the tool should treat the build as undocumented and verify it on their own machine. The dev/ directory and the .github directory are the places to look for the intended workflow, since a project with a solution file and a CI directory usually encodes its build there. The CodeWalker/ directory is a dependency rather than a vendored copy of the author's own code, and it is worth understanding which version you are building against before you trust a preview result.

Support, sponsorship and the funding model

The support arrangement is unusual and is stated plainly. The documentation says to join the Discord for support, but because the tool is still work in progress, support is currently only for people supporting the author on ko-fi. The Donate section asks for sponsorship through the Sponsor button at the top of the repository so development can continue, and the Want to say thanks section asks for stars and for spreading information about the tool. The Mentions section credits JagodaMods with a lot of motivation and ideas, and ook3d with fixes and a contribution. The combination of a work in progress label and a paid support gate is a specific posture rather than a contradiction. The tool is free to use and the documentation says it always will be, but the time to fix the bugs that work in progress implies goes to the people funding it. If you are evaluating this as a dependency in a modding pipeline, the honest reading is that you are depending on a single maintainer whose capacity is tied to donations, and that the code is published in full so you can pick up the maintenance yourself if you need to.

Where grzyClothTool is the wrong tool

There are several boundaries and they are practical rather than technical. The first is scope. This is a tool for addon clothing packs for one game, and nothing about it generalises to a general modding pipeline, a different game, or asset work outside the GTA5 format. The second is the preview dependency, and it is the one that will decide your experience. If the 3D preview is the reason you want the tool, then the accuracy of that preview is entirely at the mercy of CodeWalker and of the game assets it reads, and a preview that is subtly wrong is worse than no preview because it gives you false confidence. The third is the maturity question, stated by the author rather than inferred, so there is no arguing with it. The fourth is licensing friction, since GPL-3.0 for a modding tool is unusual, and it means a derived tool has its own distribution obligations, which is one more reason the choice between using this and writing a small script against the game's files is not automatic. The fifth is platform, since a WPF application does not run on Linux or macOS, and the modding community is not exclusively on Windows. For a creator who publishes a handful of packs, the existing commercial tools and a manual workflow may cost less time than getting a work in progress build working on their machine.

Editorial conclusion

Adopt grzyClothTool if you are a GTA5 modder who publishes addon clothing and wants to preview a texture on the body before uploading it, since the 3D previewer and the automatic split of oversized packs address two specific pain points. Do not adopt it if you expect a finished, supported product, because the documentation labels the tool a work in progress and says support is currently only for people sponsoring the author on Ko-fi. Verify two things before you rely on it: that the item count in your pack is handled the way you expect, since the tool splits an addon that exceeds the 128 item limit into multiple addons rather than failing, and that the CodeWalker based previewer handles the drawable you are previewing, since the preview depends on a separate project and its own asset data. The practical first step is to build the solution and open the 3D previewer with a single texture, because that is where the value of the tool is concentrated and where the bugs are said to be.

Frequently asked questions

Official sources

1. grzybeek/grzyClothTool on GitHub
2. Issues
3. License: GPL-3.0
4. README
5. Releases