File upload

File upload is the control that moves a file off the reader's device: a target to drop on or a button that opens the system picker, then a row per file reporting what became of it. The six blocks work through that arc, from a dropzone stating its limits before the drop and an avatar well with Replace and Remove, to a manager where one stored file has failed and can be retried, a form field with a preview grid, a row playing its own progress, and a batch row speaking for everything in flight.

Drag and drop is decoration. The file input underneath is the control, and it has to stay reachable, because nobody on a phone, a keyboard or a screen reader drags anything. The other half of the work is failure. Choosing a file is not uploading one, and a dropped connection, a file over the ceiling and a type the server refuses are ordinary outcomes. Each needs a retry that does not send the person back through their file system to find it again.

18 blocks

Dropzone

Attaching files to a form: the zone, the live rows and the quota in one card

Dropzone, whole card

Attaching files where the files are the content: no permanent drop box

Dropzone, quota of files

A request with a total allowance, such as a 50 MB form upload

Avatar uploader

Profile and onboarding forms: one image with Replace, Adjust and Remove, over a single-file zone

Avatar uploader, in the circle

Onboarding where the photo is the star and the crop should look like the result

Avatar uploader, ring

Profile photos that upload in the background

Attachments manager

Files already uploaded: a calm list, one of them failed and retryable

Attachments manager, select

Managing many files at once

Attachments manager, failures first

Libraries where problems must not hide in the list

Upload field

A form that collects images: the zone and everything already attached, in one field

Upload field, one field

A form where photos and documents go in together, with a hard limit on how many

Upload field, slots

A listing or product form where the order of the photos matters and the first is the cover

Uploading file

The transport itself: one row playing its own progress, pause and failure

Uploading file, ring

A single large upload where the file itself is the control

Uploading file, parts

A big file sent in chunks, where a retry should visibly keep what arrived

Batch upload

A whole batch on one row: a status for everything in flight, not one file

Batch upload, stack

A batch where people want to see which files are in it

Batch upload, ink dock

Uploads that continue while the person keeps working elsewhere in the app

01

Using File upload

Reach for it when

  • Attaching documents to a form that is submitted as a whole
  • A single image that replaces whatever is currently there
  • Transfers long enough that pause, resume or cancel are worth having
  • A queue where several files each need their own state and their own retry

Reach for something else when

  • A short piece of text somebody would otherwise paste: a text area saves them a trip through their file system
  • Choosing something already stored in the product. That is a file browser, not an upload
  • Structured data that needs column mapping: the upload is one step of an import flow, and alone it strands the person
02

Where it shows up

01

Support ticket attachments

A form where screenshots and logs go up beside the description. The limits sit next to the zone before anything is dropped, so an oversized file is refused with an explanation rather than a silent nothing.

02

Profile photo

A single image replacing whatever is there now, with Replace and Remove as explicit actions. The well shows the current photo, which makes it plain that uploading is a replacement and not an addition.

03

Bulk media import

A batch going up together, reported as one row with a percentage and a bar for everything in flight, plus controls that pause or cancel the whole batch rather than picking through it a file at a time.

04

Document collection

Identity or compliance paperwork gathered across several fields, each with its own required mark and hint line, and a preview grid so the person can confirm they sent the right page.

03

Questions

Does a drag-and-drop upload zone need a click fallback?

Yes. Dragging is unavailable on touch screens, awkward with a keyboard and invisible to a screen reader, so the drop zone should be a label wrapping a real file input: focusable, activatable with Enter or Space, and opening the system file picker when it is. Treat the drop target as an accelerator for pointer users rather than as the control itself.

Should file size and type be validated in the browser or on the server?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.