# Escrowed Resources

Some clothing you buy for a FiveM server is protected by **Cfx.re Asset Escrow**. Its files are encrypted and locked to the buyer's server key, so no tool can open, preview, edit or merge them. The Cloth Tool can still carry such a resource in your project and ship it next to your own pack, untouched.

**New in 2.0.8.** This is free.

## When to use it

Use it when a server's clothing is a mix of your own garments and escrowed packs you have bought, and you want one build that installs everything in the right order. The escrowed resource is never part of your pack's own collection. It is copied beside it, byte for byte.

:::hint{type="info" title="Escrowed files are not garments"}
If you drop an escrowed `.ydd` or `.ytd` into the project as an ordinary garment, it is refused with the reason: the file is protected by FiveM asset escrow and nothing can be done with it. Add the whole escrowed resource as described below instead.
:::

## Adding an escrowed resource

:::steps
### Open the import menu

On the item list, open the arrow next to **Import** and choose **Import a FiveM resource** → **Escrowed FiveM resource (kept as-is)…**. Once a project has an escrowed resource, the **Escrowed resources** section on the item list also has a **+** button (**Add escrowed resource…**).

### Pick the folder

Choose the resource's folder (the one with `fxmanifest.lua`). You can also pick a `[category]` folder: every escrowed resource inside it is added at once.

### Read the report

The tool copies each resource into the project unchanged and records every file. A report lists what was added. A resource already in the project with the same files is left as it is.
:::

The normal resource import (**Import a FiveM resource** → **Resource folder…** or **Downloaded .zip…**) also recognises escrowed resources among what it reads and keeps them the same way.

What can be refused, and why:

| Message | What to do |
| --- | --- |
| Not a FiveM resource — no `fxmanifest.lua` was found | Pick the resource's own folder. |
| The resource is not escrowed | Import it with the normal import, so its garments become part of your pack. |
| A different resource with that name is already in the project | Remove the old one first. An escrowed folder cannot be renamed. |
| No `.fxap` file | The copy would not start on any server. Download the original again from your Cfx.re account and add it again. |

## The Escrowed resources section

Escrowed resources appear in their own **Escrowed resources** section at the bottom of the item list. A project without any has no section. Each resource shows its garments, read from the file names, with a count of garments and textures. The garments are read-only and have no 3D preview, because the models are encrypted.

Right-click a resource to:

- **Reveal folder** — open the project's copy in Windows Explorer.
- **Remove from project** — delete the project's copy after you confirm. The resource you downloaded is not touched.

A resource with a problem says so in the section, in the build window and in the checks:

- **No .fxap file — it will not start on a server.**
- **Files missing or changed since it was added — it will not be shipped.**

## What the build does

Escrowed resources are FiveM resources, so they only go into a build with **FiveM** (or **Both**) selected under **Output**. The build window's **Escrowed resources** section shows how many will be copied. There is nothing to choose: every escrowed resource in the project ships.

When you build, the tool:

1. Checks every file of every escrowed resource against what was imported, before writing anything.
2. Copies each resource into the output folder as its own folder, next to your pack, under its original name.
3. Checks the copies again, file by file.
4. Writes `ESCROW-README.txt` and `server.cfg.snippet` into your pack's folder. The snippet holds the `ensure` lines in order: your pack's resources first (including any extra resources from an automatic split), then each escrowed resource.

The build refuses, and nothing of that resource is shipped, if:

- the `.fxap` file is missing,
- any file is missing or has changed since it was added,
- the output folder already has a different folder with that resource's name,
- the escrowed resource has the same name as one of your pack's own resources. Rename your pack instead.

:::hint{type="warning" title="Installing on the server"}
Copy every folder, **including hidden files**. The `.fxap` inside each escrowed folder must be there; some FTP programs skip hidden files, and the server then reports "Failed to verify protected resource". Do not rename or edit the escrowed folders. An escrowed resource only starts on a server whose licence key belongs to the Cfx.re account that bought it.
:::

## Limits

- **Legacy only.** Escrowed files cannot be converted for GTA V Enhanced (only their seller can), and FiveM for GTA V Enhanced does not support asset escrow yet. They ship with the Legacy resource only. See [GTA V Enhanced](/cloth-tool/about-the-tool/gta-v-enhanced).
- **Not in .kct packages.** A `.kct` export leaves escrowed resources out and says so. They are licensed to your own server and cannot be passed on; the recipient needs their own copy from the seller. See [Sharing Packages](/cloth-tool/about-the-tool/sharing-packages).
- **Not in a singleplayer dlc.rpf.**

## Related pages

- [Building](/cloth-tool/about-the-tool/building)
- [Importing](/cloth-tool/about-the-tool/importing)
- [Sharing Packages](/cloth-tool/about-the-tool/sharing-packages)
- [GTA V Enhanced](/cloth-tool/about-the-tool/gta-v-enhanced)
- [Validation](/cloth-tool/about-the-tool/validation)