Help

Sending files to a client

A delivery is one link for one job. Your client opens it, sees the files and downloads them. They need no account and nothing installed.

Uploading

Make a delivery against a project, then choose your files. They upload one at a time, straight into your own storage, with a progress bar for each.

Anything over 16MB goes up in pieces. If the connection drops, only the piece in flight is lost rather than the whole file, and choosing the same file again picks up from whichever pieces already arrived. This matters more than it sounds on venue wifi.

For photographs, your browser also makes a small preview and puts it in your storage beside the original, so your client sees the pictures rather than a list of filenames. RAW files and video get a file icon, since a browser cannot draw them.

Password, expiry and download limits

All three are optional. Leave them blank and you have a plain link that keeps working.

  • Password. Your client enters it once. Send it separately from the link.
  • Expiry. After this date the link stops working and says so.
  • Download limit. Counts downloads, not visits. Taking the whole gallery as one zip counts as one, not one per file.

Knowing whether they opened it

Every delivery keeps an activity log, and refused attempts are in it too. That is deliberate: "they never opened it" and "the password you sent them is wrong" look identical from the outside, and only one of them is yours to fix.

Revoking a link

Revoking stops the link immediately, including for somebody who already has it. Your files are untouched. Deleting the delivery also removes those files from your storage, which is the one action here that does.

What your client sees

Each file downloads under its own name, straight from your storage. There is a Download everything button for the whole gallery as a zip, which their browser builds. On very large galleries, browsers other than Chrome and Edge will suggest downloading individually instead, because they would have to hold the whole archive in memory.

Still stuck? Write to support@archivesend.com and tell us what you were doing when it went wrong.