> For the complete documentation index, see [llms.txt](https://support.rendered.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.rendered.ai/development-guides/ana-software-architecture/package-volumes.md).

# Package Volumes

Volumes are used to store large asset files to keep the Docker images for channels small, which translates to faster startup times for the channel. Volumes are specified in a Package using the *package.yml* file. The below package.yml file is from the example package in the example channel.

```yaml
volumes:
  example: 'e66b164e-8796-48aa-8597-636d85bec240'

objects:
  YoYo:
    filename: example:YoYo.blend
  BubbleBottle:
    filename: example:BubbleBottle.blend
  Skateboard:
    filename: example:Skateboard.blend
  Cube:
    filename: example:Cube.blend
  Light Wooden Box:
    filename: example:Containers/LightWoodenBox.blend
```

When specifying a volume, you must use a key, value pair where the key is a unique name used locally for the volume and the value is the Volume ID on the platform. Volume ID’s are generated when the volume is created via anatools' create\_managed\_volume(name, *organizationId*) SDK call or through the web interface. See the[ anatools SDK documentation](https://sdk.rendered.ai/) or for more details on creating and volumes.

Files are referenced from the volume using the `get_volume_path(package, rel_path)` function where package parameter is the name of the package, i.e. “example”, and the rel\_path is the volume:pathinvolume. To get the file path for the blender file containing the Yoyo object this call would be `get_volume_path('example', 'example:LowPoly.blend')`. Anatools has a helper functions for creating object generators from blender files, this is an example of loading the YoYo object from the blender file and wrapping it in a YoYoObject class: `get_blendfile_generator("example", YoyoObject, "YoYo")`.

Volumes can be mounted during local development using the *anamount* command. Calling anamount from the workspace directory of the development container will mount the package volumes in the workspace directory at “data/volumes/\<volume-id>”, but only if the user has read or write permissions to the volume. For an example of how to mount and develop with a volume locally, review the [Add a Generator Node](https://dadoes.atlassian.net/wiki/spaces/DG/pages/1693876225) tutorial where we create a new volume then add a Blender file to it.


---

# 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://support.rendered.ai/development-guides/ana-software-architecture/package-volumes.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.