Documentation

Introduction to the Asset Library CLI

Understand how the Asset Library CLI finds and imports individual Asset Store assets, which assets you can use, and how asset versions and render pipeline variants work.
Read time 3 minutesLast updated a day ago

Note
The Asset Library CLI is experimental, so it's not ready for production use. Not all Asset Store assets are available through Asset Library yet. The commands, options, and documentation might change before release.
The Asset Library CLI works with individual assets, such as a single model, texture, or sound, rather than whole Asset Store packages. You can check an asset's details before you import it, and import only the files that asset needs.
This page explains how individual assets relate to Asset Store packages, which assets you can import, how to identify a specific asset version, and how to use the CLI from coding agents and continuous integration (CI) pipelines.
To install the CLI, refer to Install the Asset Library CLI.

Asset availability and ownership

The commands you can use with an asset depend on whether the asset is free and whether you own its package:
  • search
    and
    show
    work with free and paid assets.
  • import
    ,
    download
    , and
    package
    work with free assets, and with assets from paid packages you own.
Ownership applies to the whole package. If you own a package, you own every asset in it. To use an asset from a paid package you don't own, buy the package in the Asset Store, and then run the command again. The
show
command prints the package URL.
The Asset Library CLI uses your Unity organization to check which assets you own.

Asset IDs and versions

Commands that act on one asset take an asset ID in one of the following forms:
  • assetId
    : uses the latest version of the asset.
  • assetId@versionId
    : uses the specified version of the asset.
By default, the
search
command prints each ID in the
assetId
form. To print IDs in the
assetId@versionId
form, add the
--versions
option. An ID that you copy from those results uses that specific version.

Render pipeline variants

Some assets include a separate variant for each render pipeline. For these assets, the
import
,
download
, and
package
commands require the
--render-pipeline
option with one of the following values:
urp
,
hdrp
, or
builtin
.

Automation with coding agents and CI

The Asset Library CLI supports automated use from coding agents and CI pipelines:
  • Use
    --format json
    or
    --format ndjson
    for structured output.
  • Use
    --non-interactive
    so that a missing value causes an error instead of a prompt.
  • Use
    --dry-run
    with
    import
    and
    download
    to review changes before the CLI writes any files.
  • Use
    assetId@versionId
    IDs so that repeated runs get the same files.
  • Run
    unity skill install <client>
    to give your coding agent the Unity CLI skill.
To list the options of a command, run
unity assetlibrary <command> --help
. For the options that all commands accept, refer to Asset Library CLI command reference.

Additional resources