Skip to main content

Game asset library

Manage game assets as production records, not loose files

The asset library is where generated candidates become searchable production records. It keeps variants, official outputs, source links, folders, tags, comments, and review state connected to the game project.

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

Official outputs can stay connected to source objects, briefs, references, and variants.

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

01

From image output to production record

A generated image is only one part of a production workflow. Teams also need to know why it was created, which brief guided it, what references were used, which candidates were rejected, and when the final asset became official.

Assets Studio keeps that surrounding context available so teams can search, compare, and reuse work after the generation run is over.

02

Useful for large content databases

Game teams often manage hundreds or thousands of entities: characters, enemies, items, skills, zones, rewards, props, decorators, and effects. A production library gives those visual records a home.

When assets are tied back to source resources, the art workflow stays connected to the game database instead of drifting into detached image folders.

03

A cleaner handoff

Approved assets can be exported or downloaded with clearer context. Reviewers can see comments and decisions, producers can see readiness, and developers can understand which output is official.

Workflow

How the production flow works

  1. 01Create or import a production asset record.
  2. 02Attach candidates, variants, references, tags, and source links.
  3. 03Promote the approved candidate to the official output.
  4. 04Export or download assets once they are production-ready.