Overview
CLO builds clothing the way clothing is actually built. You draw flat pattern pieces, define the seams between them, and the simulation sews them together and drapes the result on an avatar. Change a pattern piece and the garment on the avatar updates, which means fit problems appear on screen instead of on a sample that took two weeks to make and ship.
The simulation is the whole product. Fabric is defined by real physical properties: weight, thickness, stretch on both grain directions, bending stiffness, friction and shear. A silk behaves like silk and a heavy denim behaves like denim, and the difference shows in the drape, the way a seam sits and where a garment strains. Stress and strain maps overlay the garment to show where it pulls, which is fit information a flat pattern cannot give you.
Around the simulation sits everything a technical package needs: graded sizes, avatars with editable measurements and poses, trims and hardware such as buttons, zips, eyelets and topstitching, printed and woven texture mapping with placement on the pattern, and export of both the 2D pattern set for cutting and the 3D garment for rendering or a game engine. The tech pack output carries the measurement and construction detail a factory expects.
What it does well
Pattern based construction
Garments are built from flat pattern pieces and seam definitions, exactly as they would be cut and sewn.
Real fabric properties
Weight, stretch, bending, thickness and friction are physical values, so different materials drape differently.
Fit analysis
Stress, strain and pressure maps show where a garment pulls or gaps on the avatar before a sample exists.
Avatars and sizing
Editable measurements, poses and motion, with graded size runs simulated across the same pattern set.
Trims and texturing
Buttons, zips, eyelets, topstitching and printed or woven textures placed on the pattern rather than on the surface.
Changes in this build
- Simulation solver improved for layered garments, which previously needed manual separation.
- New fabric presets covering current technical and knit materials.
- Faster rendering with better cloth shading on translucent materials.
- Pattern tools gained better handling of curved seam alignment.
- Export updated for current interchange formats used by game engines.
What is in the package
- CLO Standalone installer, 64-bit
- Avatar library with editable measurements and poses
- Fabric preset library with physical properties
- Trim, hardware and topstitch libraries
- Multilingual interface files, 10 languages
System requirements
| Processor | Intel or AMD 64-bit, 6 cores or more recommended |
| Memory | 16 GB minimum, 32 GB for layered garments |
| Graphics | GPU with 6 GB VRAM and current drivers |
| Storage | 15 GB free plus library space |
| Display | 1920 x 1080 minimum, dual monitor useful for pattern and 3D views |
| System | Windows 10 or Windows 11, 64-bit |
Installation
- Extract the archive to a local drive.
- Run setup and install the avatar and fabric libraries alongside the application.
- Apply the included configuration step before the first launch.
- Open a sample garment so the simulation and shader caches build.
- Turn off the update check in preferences.
Before you start
Simulation quality settings matter more than machine speed, work at draft and raise it for final output.
Fabric presets are a starting point, real material behaviour needs the measured values from the supplier.
Garments saved by this release will not open in an older install.
Questions about this title
Does it simulate real fabric behaviour?
Yes, materials are defined by physical properties rather than a visual style setting.
Can I export the flat patterns?
Yes, the 2D pattern set exports for cutting alongside the 3D garment for rendering.
Are avatars included?
Yes, with editable measurements, poses and motion.
Can it show fit problems?
Yes, stress and strain maps overlay the garment and highlight where it pulls or gaps.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.