You don't just send files to clients. You need things back: their high-res logo, the signed contract, the product photos, the raw footage, the final details before you lock the work. And getting those back is where a lot of projects quietly bleed a week.
The "can you email me that" loop
You know the exchange by heart. You: "Can you email me the high-res logo?" Them: "Oh, it's on my other computer." You: "Cool, whenever." …Three days later you're chasing. Then it's the contract. Then the product shots. Then the final payment reference.
Every "can you send that to me" is a tiny round-trip: a message, a wait, a re-message, a file in the wrong format, an "oops, wrong version." Across a project they add up to days you didn't budget for.
The root cause is the flow. You're asking the client to do a task — find the file, attach it, email it — through a channel built for messages, not files. And email's 25 MB ceiling means anything real — a product render, a short video, a batch of photos — can't even fit. So the file never comes, and the project stalls on a step that should take ten seconds.
It's not their fault, and it's not small
The client isn't being difficult. "Email me a 4 GB file" is an awkward ask, and a normal person doing a normal job will let it drift. The cost lands on you: you can't start the next step, you're the one holding the timeline, and the delay shows up as your project slipping.
The more files you need back, the more the engagement turns into "and where's that file again?"
Flip the flow with a request link
Instead of asking the client to find-and-email a file, give them a link that asks for the file. They open it, drop the file in, done. No account to make, no attachment limit to fight, no "which version." You get a clean upload into a place you control.
That's a file request — the reverse of a delivery. And it's a feature a lot of transfer tools reserve for their most expensive plan. WeTransfer, for example, only offers file requests on its top tier, not on the free or mid plans. With FileSplash, file requests are part of Personal ($5/month) — the same plan that gives you no-expiry delivery links and a branded page. So the whole client loop runs on one cheap plan: request the inputs, deliver the work back, keep everything in 500 GB of storage.
Making a request link land
A request link only works if the client knows exactly what to do with it. Three things make it land:
1. A naming convention on the request page. Put one line at the top: "Name files like brand_logo_highres, contract_signed, photos_batch1." A predictable name means you can find the file the day it arrives instead of guessing which of eleven downloads is the one you wanted. It also stops the "final_v3_REAL" problem before it starts.
2. A short brief on the request page. One or two sentences on what you need and in what form: "High-res logo (vector or 300dpi), please drop it here by Friday." The client doesn't have to remember the details from a week-old email. They see the ask, they do the ten-second upload.
3. Confirming receipt. The moment the upload lands, send a quick "got it, looks right — thank you." It closes the loop, it tells the client the step is done so they stop worrying, and it gives you a timestamp for the record. No chasing, because the confirmation replaces the follow-up.
Set up each request before you need it: a kick-off link for the inputs, a mid-project link for the assets the next phase depends on, and a close-out link for the signed approval. Each one is a link in an email — "here's where to drop the [X], no sign-up, just upload."

Stop chasing
You can't stop needing files from clients. But you can stop chasing them. A request link turns a back-and-forth email thread into a single upload and removes the 25 MB wall for anything big. It's the quiet feature that makes a project feel professional, because the client always knows exactly where to put the next thing.
See how the request fits the wider client loop in how to request files from a client, or start free and set up your first request link. Why it's built into the $5 plan: why FileSplash.
