Delivery is part of the work
A project may be finished for the team and still be pending for the client because final files are scattered across attachments, storage links, and forwarded messages. Transfers lets you prepare delivery in the same environment where the client and work are known. The file travels with a recognizable name, a defined recipient, and a date when it will stop being available.
Each transfer supports 20 files and 2 GiB per transfer at most. That limit encourages a concrete delivery instead of a permanent archive. If the client needs to consult materials for months, keep the master copy in Documents or Gallery and use a transfer for the moment it needs to arrive.
Prepare before sharing
Delivery starts by gathering the final files, confirming addresses, and choosing a proportionate expiration. While files upload, the transfer remains in preparation. It should not appear ready to the recipient until every file has finished and the screen shows its status. If an upload fails, retrying the same delivery is safer than creating several identical copies without knowing which one is active.
After upload, each file may be marked clean, not analyzed, blocked, or errored. “Not analyzed” does not mean clean. If analysis could not finish, the responsible person should decide whether to verify the file another way before sharing it. The feature makes uncertainty visible so a created delivery is not mistaken for a validated one.
A link you can review and cut off
The recipient opens a simple page, sees the list, and downloads without creating an account. You can send the link directly or add an address so the platform can attempt a notification. Delivery to the recipient's mail service only shows that the message was sent; download activity tells you whether someone actually accessed a file.
If the link reached the wrong person, replacing it invalidates previous access and creates new links. If the work should no longer be available, revoking the transfer cuts off downloads and begins cleanup. Expiration and revocation control access, although storage may take time to be released while cleanup finishes.
The right delivery for the right work
Transfers works well when closing a project, answering a ticket, or delivering artwork, backups, and work packages a client needs to download. It also helps the team use a shared naming practice and review who created a delivery. That basic traceability is more useful than depending on one person's mailbox search.
It is not a collaboration room, electronic signature, permanent archive, or folder structure for ongoing work. It also does not add a second password to the link. For sensitive text without files, Confidential Sends provides a different experience; for assets that need repeated use, Gallery is the right place. Choosing well keeps a temporary delivery from becoming a library substitute.
Control after sending
Responsibility does not end when the link is copied. Tell the recipient when it expires, check whether the files were downloaded, and act if a delivery remains pending or reached the wrong address. If mail is not delivered, review the address and retry; if it keeps failing, revoke and create a new delivery rather than leaving one tied to the wrong recipient.
The feature cannot know what someone did with a file after downloading it. Download activity is therefore a signal of access, not proof of responsible use. The organization still needs to review content, choose recipients, and keep a master copy when the material must remain available.