Sharing Packages

A .kct package is a self‑contained bundle of the clothing items you choose — their models, textures and settings — that you can hand to someone else, back up, or drop into another project. Think of it as a portable "mini‑project".

.kct is not the same as a FiveM build. A FiveM build (Building & Export) produces a server‑ready resource. A .kct package is for moving clothing between Cloth Tool projects — sharing with a teammate, reusing items across packs, or keeping a backup of a few pieces.

What's inside a .kct

A .kct is just a ZIP with a known layout, so it's easy to inspect:

• kct.json — a small header (format version, tool version, date, name, item count) used to recognise and preview the package on import.

• manifest.kctproj — the project data for only the items you selected, with asset paths rewritten to point inside the package.

• assets/ — the real files (.ydd, mesh physics, first‑person models, .ytd / .dds textures), de‑duplicated so nothing is stored twice.

Exporting a package

1

Click Pack to .kct

Enter packaging mode. Checkboxes appear next to every item and category header.

2

Select the items you want

Tick the items you want to include. Tick a category header to select the whole category at once. A counter shows how many items are selected.

3

Click Export N items → .kct

Use the bottom bar to start the export.

4

Choose where to save the .kct file

The package is written in the background with a progress bar.

Selecting nothing and exporting does nothing — you'll get a gentle reminder to pick some items first. Packaging mode doesn't change your normal selection or the editor; leave it any time with Cancel.

If an item is missing a source file (e.g. a texture was never imported), it's reported as a warning in the export summary — the package is still created, just without that file.

Importing a package

1

Click Import .kct…

Pick the .kct file.

2

Choose how to bring it in

Option	What happens
Add to current project	Appends the package's items to the project you have open. Each item gets fresh IDs and is re‑numbered into the right slot, and its assets are copied into the current project's cache. Requires a saved project — save first if prompted.
Open as new project	Creates a brand‑new project from the package (you pick a folder), just like starting fresh.
Cancel	Backs out, nothing changes.

Because the package carries its own assets, an imported .kct is fully self‑contained — the person you got it from doesn't need to send anything else.

Typical uses

• Share a few garments with a teammate without handing over the whole project.

• Reuse items — build a library of favourites and pull them into new packs.

• Back up a subset of a project before a big change.