Asset Library

Manage brand, product, and campaign assets with type, dimensions, usage rights, tags, collections, and recent activity. This example brings All assets and Images together so content and product teams can find the next task without losing context.

It includes representative records such as Launch hero video and Product screenshots. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Asset Library
Use this template in Figr

Template facts

Screen

Table

Primary action

Add asset

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to add asset while keeping assets, collections and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: All assets gives users an obvious place to start.
  • Supporting view: Images keeps the related context close.
  • Primary action: Add asset stays visible when people need it.
  • First signal: Assets shows a useful value (1,284).
  • Second signal: Collections gives additional context (24).
  • Sample record: Launch hero video.
  • Next record: Product screenshots.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

All assets → Images → Add asset → Review outcome

Patterns used

Table, All assets, Images, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to all assets and images. People need to distinguish Launch hero video from Product screenshots. Keep assets visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Add asset”. Make error recovery as clear as the happy path.

Related screen examples to explore next: File Browser, Media Upload, Version History.

Start from this in Figr

Design a asset library screen inside our existing product. Use our current components, tokens and content language. Include All assets and Images views, credible records like Launch hero video, and a clear “Add asset” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr