Media Upload

Upload images and video with destination, naming, metadata, usage rights, and processing status visible before publishing. This example brings Upload and Metadata together so content and product teams can find the next task without losing context.

It includes representative records such as Select media files and Add metadata. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Media Upload
Use this template in Figr

Template facts

Screen

Form

Primary action

Upload files

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to upload files while keeping files selected, total size and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Upload gives users an obvious place to start.
  • Supporting view: Metadata keeps the related context close.
  • Primary action: Upload files stays visible when people need it.
  • First signal: Files selected shows a useful value (12).
  • Second signal: Total size gives additional context (842 MB).
  • Sample record: Select media files.
  • Next record: Add metadata.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Upload → Metadata → Upload files → Review outcome

Patterns used

Form, Upload, Metadata, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to upload and metadata. People need to distinguish Select media files from Add metadata. Keep files selected 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 “Upload files”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Asset Library, Version History, File Browser.

Start from this in Figr

Design a media upload screen inside our existing product. Use our current components, tokens and content language. Include Upload and Metadata views, credible records like Select media files, and a clear “Upload files” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr