Skip to main content

Game asset library

Manage game assets as production records, not loose files

The asset library keeps generated images in searchable production records. Each record can connect variants, source links, folders, tags, references, and the brief and visual identity behind the work.

Assets belong to the workspace and project, not just the user who generated them.

Images stay connected to source objects, briefs, references, and related variants.

Folders and tags make asset work easier to scan and revisit.

01

More than a folder of generated images

A useful image should not become an anonymous file. Teams need to find the brief that guided it, the references that shaped it, and the variants created from the same requirements.

Keep that context available so the team can find the asset later, compare alternatives, and continue from the same production record.

02

Useful for large content databases

Game projects can include hundreds of related entities: characters, enemies, items, skills, zones, rewards, props, and effects. A production library gives their visuals a shared home.

Linking assets to source objects keeps the visual work connected to the game project instead of scattering it across detached image folders.

03

Return to the work with its context

Open an asset later and find its source, brief, references, visual identity, and related variants. The project context is still there when it is time to continue or download the image.

Workflow

How the production flow works

  1. 01Create or import a production asset record.
  2. 02Add images, variants, references, tags, and source links.
  3. 03Compare related variants and keep their shared context together.
  4. 04Return to the production record when the asset needs another pass.