> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voyager.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Voyager assets on cloud machines

> Find models, materials and HDRIs in the Voyager asset library, record them in a lock file on your computer, and put them in place on a cloud machine without uploading them.

The Voyager asset library has thousands of ready-to-render models, materials and HDRIs. On a cloud machine you never upload them: you record which ones you want in a small lock file, push that, and the machine fetches the files itself.

> [!NOTE]
>
> **Before you start:** the `voyager` CLI ([quickstart](https://docs.voyager.so/api/machines/quickstart.md)) and a leased machine (`m=$(voyager cloud lease render-lite --wait --yes)`). Searching the library needs no sign-in and no machine.

## Find, lock, sync

**1. Search the library**

```sh theme={"system"}
voyager cloud assets search "brass telescope" --kind model
```

Each hit shows its id (`vy.model.telescope-on-tripod-05@1`), score, size in metres, triangles, texture sizes, licence and the command that adds it. `--kind` is `model`, `material` or `hdri`. "No good matches" means the library has none; it names the closest.

**2. Record the assets you want**

In the folder you will push:

```sh theme={"system"}
mkdir -p scene && cd scene
voyager cloud assets add vy.model.telescope-on-tripod-05 vy.hdri.story-studio-02:res=1k --lock-only
cd ..
```

`--lock-only` writes `voyager-assets.lock.json` with the exact versions and downloads nothing here. Options after `:` are that asset's own: here the HDRI at 1k, the model at its only size (2k).

**3. Push the lock**

```sh theme={"system"}
voyager cloud push $m scene/ scene
```

One small file goes up.

**4. Sync on the machine**

```sh theme={"system"}
voyager cloud exec --cwd scene $m -- voyager-cloud assets sync
```

The machine puts each asset in `scene/assets/<id>@<version>/`: the model as glTF with its textures, the HDRI as one EXR. This took 12 seconds for both. The machine image ships the CLI as `voyager-cloud`, so on the machine you run `voyager-cloud assets …`, not `voyager cloud assets …`.

Your scene loads the files from `assets/…` like any others. Run `voyager-cloud assets sync` again on any other machine to get the same versions there.

## Know what you're using

| Command | What it does |
| - | - |
| `voyager cloud assets show <id>` | Files, licence and credit, preview images, pivot and a kit's pieces |
| `voyager cloud assets categories` / `list --category <path>` | Browse the library by category |
| `voyager cloud assets packs` / `packs show <pack>` | Sets of assets made to be used together |
| `voyager cloud assets outdated` | Locked assets with a newer version (the lock doesn't change until you add the new one) |
| `voyager cloud assets credits --out CREDITS.txt` | One credit line per asset, required ones first |

Licences differ by asset, and some require a credit: check `assets show` before you deliver, and add the `assets credits` file to anything you hand over.

Models are glTF in metres, Y up, with the pivot at the bottom centre. Materials are PBR maps with a `.material.json` giving their real-world tile size. HDRIs are equirectangular; `assets show` gives an HDRI's sun direction and the matching Blender sun rotation.

## Keep asset files out of pushes

Never push library asset folders from your computer: a sync on the machine is faster. Add `assets/vy.*` to a `.voyagerignore` in the folder you push, or pass `--exclude 'assets/vy.*'`. `push` warns when it sees library asset files.

## Next

> [card] [Render with Blender](https://docs.voyager.so/api/machines/blender.md)
>
> Scene templates that build a shot from library assets in one command.

> [card] [Render with Vork](https://docs.voyager.so/api/machines/vork.md)
>
> The Vork render loop on cloud GPUs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.