# Select, upload, and download files

Select the files or folders you want to act on. A selected folder can expand into many descendant entries when an operation is admitted, so a small selection count does not necessarily mean a small transfer. Check the operation limits before transferring a large folder tree.

## Upload from your computer

Choose the destination provider and folder, then use the available upload action. The file is uploaded to that storage location. Uploading to a storage provider and submitting a document to an App's File Upload control are different actions; use [Add to App files](/docs/storage/import-into-apps) when the goal is App ingestion.

A name collision can require a decision before the upload or transfer completes. Do not assume an existing file will be overwritten automatically. Review the destination and the applicable [collision policy](/docs/storage/collisions-and-replacement).

Browser multipart uploads have a 128 MiB request-body ceiling. This includes multipart overhead, so a file exactly at that size can exceed the request limit. A transfer job can have a different per-file limit; the larger transfer limit does not expand the browser upload request limit.

## Download

Use download to retrieve the selected original or provider-exported representation. Native cloud documents may be exported into a portable file rather than returning their editing format. Check the downloaded format before relying on it for a downstream process.

## Verify completion

An operation that was accepted can still be processing. Inspect its job progress and final results before deleting an original, closing a dependent process, or assuming every selected file arrived. If the response is uncertain, review the existing job first. Starting another operation can create a second copy even when the first completed successfully.

See [jobs and recovery](/docs/storage/jobs-and-recovery) for partial results, cancellation, and retry behavior.