Every extra step between "here's the link" and "file received" loses you a percentage of clients. The two biggest offenders are email attachment limits and account sign-up walls — both are avoidable with a link that just asks for the file.
Why "just email it" breaks down
Gmail caps attachments at 25 MB — a single short video, a batch of high-resolution photos, or a design file with embedded assets clears that easily. When a client hits the limit, the two most common outcomes are both bad: they re-compress the file themselves, which is exactly the quality loss you didn't want, or they give up and send it through whatever app is already open on their phone, at whatever resolution that app defaults to.
Why sign-up walls lose clients too
Most client-facing file requests aren't blocked by bandwidth — they're blocked by friction. Asking a non-technical client to create an account, verify an email, and learn a new interface before they can send you one file is a real dropout point, not a minor inconvenience. The client who was going to send you footage today sends it three days late instead, after a reminder, through whatever app required the least effort.
What a good client-upload flow looks like
- One link, sent by email or chat — no separate invitation flow. Creating one takes about a minute.
- No account, no password reset email, nothing to install.
- A single page: drag files in, or pick them from the device. Nothing else to figure out.
- Files land somewhere you already control, at original quality — no recompression, no manual download-then-reupload step.
Collecting documents, not just files
Most client intake is documents rather than assets — statements, contracts, ID scans, signed forms — and documents bring a second problem behind the first. Receiving them is easy. Knowing what you received is not. A folder of files named scan_003.pdf tells you nothing about whose they are, what they are, or which of the eleven things you asked for is still missing.
The fix is to collect the context with the file rather than after it. Ask for the sender's name, the document type, and any reference number as fields on the upload page itself, while the client is the only person who knows the answer. A required dropdown naming the documents you expect does more work than any amount of chasing afterwards, and it lets each upload be filed into the right folder automatically as it arrives — the mechanics of that are in document collection software.
What this looks like by trade
- Freelancers and studios: one link per project for brand assets, raw footage, and revisions, with a size limit set for the largest realistic file rather than the average one.
- Accountants and bookkeepers: one link per client per period, with a document-type field so receipts, statements, and signed forms sort themselves instead of arriving as one pile at the worst time of year.
- Agencies: one link per client, so no client can ever see another's files, and a subfolder per submission so a repeat delivery does not merge into the last one.
- Consultants: a link per engagement with an expiry matched to the contract, so intake closes when the work does rather than staying open indefinitely.
- Recruiters: a link on the job posting for CVs and portfolios, from candidates who have no reason to create an account with you.
The common thread across all of them is that the client is not going to adopt your tooling. They will open a link. Anything past that is optional from their side, which means it is unreliable from yours — the access controls worth adding without adding steps for the client are covered in secure file upload portal.
Comparing the realistic options
| Shared Drive folder | Dropbox/Box file request | Dedicated upload link | ||
|---|---|---|---|---|
| Attachment size limit | ~25 MB | None | Plan-dependent | Set by you, or none |
| Client needs an account | No | No | No | No |
| Files private per client | N/A | No — shared folder | Yes | Yes |
| Lands directly in your Drive | No | Yes | No | Yes |
| Expiry / auto-cleanup | N/A | No | Sometimes | Optional |
Setting up a client-safe intake flow
- 01Create one link per client or per project — never reuse the same folder across unrelated clients. Drive File Request creates a separate Drive folder per link automatically.
- 02Set a file size limit that comfortably covers what you expect (raw video and RAW photos need more headroom than most defaults assume).
- 03Add a name and notes field if you need to know who sent what without opening every file — this matters more than it sounds once you're juggling more than two clients at once.
- 04Set an expiry date matched to the project timeline, so the link stops accepting files once the job is done instead of quietly staying open.
- 05Test the link yourself from a phone, since a meaningful share of clients will open it there first.
Handling recurring or multiple clients
The pattern that scales is a link per client with a subfolder created automatically for each submission, rather than one shared inbox for everyone. That keeps a repeat client's second and third deliveries organized without you manually creating folders each time, and it means a mistake by one client — wrong file, duplicate upload — never touches another client's files.
Before you send the link
- Confirm the file size limit covers your largest expected file type, not just the average.
- Decide whether you need the sender's name and email captured automatically, or whether the filename is enough context.
- Set an expiry date rather than leaving the link open indefinitely.
- Send a one-line instruction along with the link — most clients have never used a tool like this and a sentence of context prevents a confused reply. Three templates for that email cover the first request, the follow-up, and the final reminder.