File Browser

Browse folders and files with ownership, type, size, modified date, sharing state, and fast bulk actions. This example brings My files and Shared together so content and product teams can find the next task without losing context.

It includes representative records such as Q4 product strategy and Design system assets. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

File Browser
Use this template in Figr

Template facts

Screen

Table

Primary action

Upload file

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 upload file while keeping files, folders and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: My files gives users an obvious place to start.
  • Supporting view: Shared keeps the related context close.
  • Primary action: Upload file stays visible when people need it.
  • First signal: Files shows a useful value (2,418).
  • Second signal: Folders gives additional context (126).
  • Sample record: Q4 product strategy.
  • Next record: Design system assets.

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

My files → Shared → Upload file → Review outcome

Patterns used

Table, My files, Shared, 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 my files and shared. People need to distinguish Q4 product strategy from Design system assets. Keep files 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 file”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Asset Library, Media Upload, Version History.

Start from this in Figr

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

Open Figr