Skip to content

Asset Tags

Pro Asset Tags

Asset Tags are J2 tags on Content Browser assets. They are stored as asset metadata and exposed through Asset Registry values so assets can be searched, filtered, validated, and included in diagnostics.

A tag can be used as an Asset Tag when it comes from a TagSet and its effective scope allows Assets. Quick Tags cannot be used as Asset Tags.

Valid Asset scopes include:

ScopeAsset use
AssetsAsset-only tag.
Actors & AssetsActor and Asset workflows.
Components & AssetsComponent and Asset workflows.
Actors, Components & AssetsAll supported target types.
SituationUse Asset Tags for
Production stateReview status, approval state, or pipeline labels.
Content organizationAsset categories that should be searchable.
DiagnosticsProject-wide checks that include Content Browser assets.
BehaviorsAsset open/save validation or metadata actions.
  1. Select one or more assets in the Content Browser.
  2. Open the asset context menu.
  3. Use the J2 Tags section.
  4. Choose Add Tag, Remove Tag, Copy Tags, or Paste Tag.

Multi-selection is supported. The picker only offers tags that are valid for Asset workflows.

J2 Tags registers a Content Browser frontend filter named J2 Asset Tag under the J2 Asset Tags filter category. Use it to show only assets that carry J2 asset metadata tags.

J2 Tags writes an aggregate asset metadata value and display values for the Asset Registry. It also registers explicit Asset Tag keys for known Asset-scope TagSet tags so Content Browser search and filters can see them.

Asset Tags can be included in usage tracking and Diagnostics when Track Asset Tags is enabled:

Project Settings | Plugins | J2 Tags

Use Show in Diagnostics from supported asset context menus when you want to inspect selected asset tag issues directly.

Use Asset Tags for editor-side production information, not as a replacement for runtime gameplay data. For runtime gameplay, use Actor Tags, Component Tags, Gameplay Tags, or a dedicated runtime system.