Sending files gets all the attention, but the harder half of most working relationships is receiving them. The client has the logo files, the accountant needs the receipts, the contributor has the photos - and the default way any of it arrives is email, which is where the trouble starts.
Why collecting over email goes wrong
Attachments scatter. The brief arrives Tuesday, the revised brief Thursday, the “final” assets across three replies the following week. Assembling the actual current set means archaeology through a thread.
Size limits bounce the important ones. The files worth collecting are frequently the ones email refuses to carry, at which point the sender improvises - a compressed version, a random transfer service, a link that expires before you open it.
Versions multiply. logo_final.png, logo_final2.png,
logo_final_USE_THIS.png, each in a different message, none marked superseded.
And the sender does the filing - badly. Every attachment lands in your inbox, not your project folder. Moving it is manual, so it happens inconsistently, so the project folder is never quite the truth.
The shapes of a fix
A shared folder works when the relationship is ongoing and the other side is willing to hold an account. The cost is setup friction and a permissions decision: a folder someone can add to is usually also a folder they can see into, which may be more visibility than the situation wants. Our guide to folders, roles and permissions covers getting that right for a team.
A transfer service in reverse - asking clients to send you a link - just relocates the scatter and adds an expiry date to it.
An upload link is the shape that fits: a URL you create that lets anyone put files into a folder you chose, without an account, and without seeing anything else there.
What a good upload link does
We support these as file requests, and the properties below are worth demanding wherever you collect files:
No account for the uploader. The person with the files clicks, drops, done. Every step you add is a follow-up email you will send.
Files land where you decided. The request points at a folder in your
storage - Clients/Acme/incoming, say - so arrival and filing are the same
event. Nothing to move, no inbox stage.
Uploaders see nothing. A request link accepts files; it does not show the folder’s contents or anyone else’s uploads. The client cannot browse, which means you can point requests at real project folders instead of quarantine areas.
It closes. A deadline or a manual off-switch, so the link from March is not quietly accepting files in November. The reasoning behind expiring share links applies with equal force in this direction.
The file requests overview shows the setup, which is genuinely a two-minute job.
Patterns that work in practice
One request per client, per engagement. Acme - onboarding documents beats
a single eternal inbox link; when the engagement ends, close it.
Name the ask in the request. A title like “Q3 receipts, PDF preferred” does more filing than any follow-up email.
Pair it with delivery going the other way. Collecting via a request and delivering via a share link keeps the whole exchange out of everyone’s inbox - the full loop for client work is covered in our gallery delivery workflow, which generalises well beyond photography.
Mind the sensitive cases. For material with real consequences - identity documents, contracts, medical anything - the collection point deserves the same care as sharing sensitive documents outbound: a closed link once collection ends, and access to the folder reviewed like any other permission.
The change that actually sticks
The habit shift is small: when you need files from someone, send them a place instead of requesting an attachment. One link in your standard kickoff email, one folder that fills itself, and the thread archaeology simply stops being part of the job.
Frequently asked questions
How can clients send me large files without creating an account?
Use an upload link, also called a file request. The client opens the link, drops their files, and everything lands in the folder you chose. They never create an account or see anything else in your storage.
What is a file request link?
A URL that accepts uploads into one folder you control. Uploaders cannot browse the folder or each other's files, and the link can close on a deadline or whenever you switch it off.
Why not just ask for email attachments?
Attachments scatter across threads, bounce above roughly 25 MB, and leave the filing to you. A request link collects everything in one place at full size, already in the right folder.
