> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/canvas/asset-packs.md).

# Asset packs

Pick the keyframes, videos, references, models and scenes to hand off, and package them into one downloadable ZIP, straight from the canvas.

The end of a project is a handoff: the keyframes and videos, and often the references and models behind them, for an editor, a client or the next team. An asset pack puts what you choose in one ZIP, built from the canvas.

## Make a pack

Click **Add an asset pack** in the bottom toolbar. The button is dimmed until the canvas has at least one asset on it. The pack appears as its own card after your outputs.

An empty pack reads "Drag images, videos, models, uploads or scenes here."

## Choose what goes in

A pack holds the items you choose. The pack card lists them in sections: outputs by scene and shot, references and models, and 3D scenes.

* **Add a card:** drag it onto the pack. Images and videos, models, uploads, references and scenes can go in; shots can't. Models include ones generated on the canvas and `.glb` files uploaded to it, once they finish generating; worlds can't go in. The card stays where it was on the canvas. Outputs show under their scene and shot, for example "Scene 1 · 03 The big bounce", with a count of images and videos.
* **Remove one:** click **×** on its tile. A tile for something you deleted from the project shows dimmed until you remove it.

While the pack's items differ from its last build, the header reads **Draft · Not generated yet** and the versions menu shows **Draft** at the top.

## Build and download

1. **Click Generate** on the pack card. Intangible builds the ZIP from the pack's items on its servers, so you can keep working. Generate is off when the latest version already has those items.
2. **Click Download** when the build finishes, either on the toast that says the pack is ready or in the pack card's header. A draft can't be downloaded until it is generated.

The ZIP has a folder per type (`images/`, `videos/` and so on), with files named by scene, shot and version, and a `manifest.json` that lists what is inside. It holds only the items you put in the pack: the references and models behind an output are not added for you, so drag them in too if the next team needs them.

Each build is a **version** of the pack. Open the chevron by the pack's title to see them. Pick an older version to view it, with **Back to latest** to return. Changing its items starts a new draft from that version, and Intangible asks first if that would replace a draft you haven't generated. Download acts on the version on screen.

To delete the version or the draft on screen, click the trash button in the pack's header. Intangible asks you to confirm.

A pack that holds a scene keeps Generate on, so a rebuild picks up any changes you made to the scene since.

Versions do not expire. Any editor or owner of the project can download them.

## Delete a pack

Select the pack card and click **Delete asset pack** in its toolbar. Intangible asks you to confirm first, and the pack's versions are deleted with it.

## Related

* [Deliver](https://help.intangible.ai/get-started/deliver.md) – where the pack fits at the end of a project.
* [Keyframes to video](https://help.intangible.ai/canvas/keyframes-to-video.md)
* [Edit media](https://help.intangible.ai/canvas/edit-media.md)
* [Share](https://help.intangible.ai/publish/publish.md) – share a published project instead of files.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/canvas/asset-packs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
