How to collect files from clients without the email chaos

Every freelancer, studio, and creator team has hit the same wall: the file someone needs to send you doesn't fit anywhere clean. It either lives in an inbox where you'll lose it, on a cloud folder that needs an account, or behind a one-shot link that expires before the project even kicks off.

The frustrating part isn't the file size. It's that the intake step — the moment a client, guest, or collaborator hands you something — is the only part of the workflow that's still glued together with tape.

Let's break down why each common tool fails the intake job, then walk through what to do instead.

Why the usual tools fail at intake#

Email attachments#

Email is where intake goes to die. The attachments work for tiny PDFs and screenshots, then everything else hits a wall:

• Gmail caps at 25 MB per message. Outlook is 20 MB unless your IT admin shipped a higher policy.
• A single 4K iPhone video (about 350 MB for two minutes) is fifteen times over the cap.
• Even when the file fits, the mental cost is high: you now have to drag the attachment somewhere, rename it so future-you can find it, and remember which client sent which version.

If you've ever searched your inbox for "the final logo" and turned up seven variants from four senders, this is the failure mode.

One-shot send tools (WeTransfer, Smash, Send Anywhere)#

These solve the size problem and nothing else. The link:

• Expires (WeTransfer: 7 days on the free plan, 30 days on Pro).
• Has no sender identity — the receiver gets a "someone sent you files" notification with no project context.
• Is point-to-point and disposable. Every project needs a new link, every team member needs to know which link is current, and reusing the same recipient address means hunting through history.

WeTransfer is great for a one-off send. It is not an intake system.

Cloud folders (Dropbox, Google Drive, OneDrive)#

Cloud folders are the opposite trap: they assume the sender is part of your workspace. For a tightly-knit team that already shares a Drive, fine. For a wedding photographer collecting guest photos? Every guest now has to:

1. Have a Google account
2. Be invited to the folder
3. Know how to upload, and to which subfolder