"Can you just email it to me?"
You've said it. Your clients say it back. And every time it happens, you're paying a tax you didn't budget for.
The "can you email it" tax
Email has a wall. Attachments top out around 25MB. Your client's 800MB reference video doesn't fit. So the file doesn't get sent by email. It gets sent by a round trip.
They try to email it. It fails. They ask you how to send it. You send them a link to some tool. They struggle with it. They send the wrong version. You ask for the right one. You wait.
That's the tax: chasing assets, wrong versions, and a 25MB wall that makes the obvious move (email) the one that never works. A single reference file can turn into three days of back and forth. And it's not a client problem. It's a setup problem. You're asking them to move a big file through a channel that was built for small ones.
There's a second, quieter cost. Every "can you email it to me" is a small moment where your client is doing work for you. They're figuring out how to get a file to you, and every time it goes wrong, it's on your name, not on the tool's. They don't file it under "the 25MB limit." They file it under "working with this studio is a bit fiddly."
Flip the direction
A file request is the opposite of a file send. Instead of you uploading and your client downloading, you hand your client a link and they upload to you.
They open the link, drop the file in, done. No account. No email attachment. No 25MB wall. The file lands in your workspace, not in some tool's queue that expires in 7 days.
The direction flips, and the tax disappears. You stop chasing. They stop asking how to send it. The file just arrives.
It's also the difference between "send me the file" and "here's where to put it." A request is an instruction that can't be misunderstood. The client knows exactly where the file goes and what happens to it next. There's no guessing, no wrong inbox, no "I thought you meant a different project." The link is the destination, and the destination is unambiguous.
For a studio that juggles several clients at once, that clarity is worth more than it looks. A request link per project means the files from client A never land in client B's pile.
Where file requests are gated
A lot of file-sharing tools treat receiving files as a premium feature. WeTransfer gates the top-tier receiving and recovery behind its Ultimate plan, the $19 to $25 a month one. So for most people, the tool that flips the direction is the most expensive subscription.
That's backwards. Asking a client to send you a file is a basic part of any client delivery. It shouldn't be the feature you need the top tier for. It's not a power-user capability. It's the everyday version of "I need this file from you."

File requests from $5
FileSplash gives you file requests from the $5 Personal plan. Your client gets a clean link, uploads to you, no account, no email, no 25MB wall. And because it's part of a no-expiry setup, the file they send you stays put instead of sitting on a 7-day clock.
The "can you email it to me" tax is one of the most expensive things in a client relationship, and it's the easiest to remove. You don't need a new process. You need a link that points at you.
If you want the step-by-step for setting one up, read how to request files from a client. And for the bigger picture on why the delivery experience is the product, see why FileSplash exists.
