Why Is Sharing a File With a Client Still So Hard?

Q: What is the simplest way to share a file with a client?

Give the client one private link to a space that holds the file. No account, no signup. They open the link, see the file, and download it. The same link works again later, so you never have to resend.

Q: Can I make a shared file delete itself after a while?

Yes. On Droplana you set an expiration date on each file when you share it - a month, six months, or leave it. On the free plan files are kept for up to 90 days; Solo, Practice, and Studio have no retention cap.

Q: Can a client upload a file back to me without an account?

Yes. A good client portal lets the client upload into the same space using the link they already have. No account, no app, no separate transfer service to figure out.

Q: Why do WeTransfer links keep expiring before the client downloads?

Free WeTransfer links expire after seven days by design. They are built for one-off transfers, not an ongoing place a client can return to. A portal the client can return to at any time avoids the expiry problem entirely.

September 22, 2026

You want to share one file with a client. That's it. Maybe a short note attached, maybe not. You'd like some control over it - have it disappear in a month, or a year, whenever suits you. And you'd like the client to be able to send a file back without a fuss. So why does that simple thing still turn into a chore in 2026?

This post is about that exact frustration - and the small set of things that actually fix it.

Quick answer (TLDR)

Share files through one private link per client, not a fresh attachment or transfer each time
Set an expiration date on each file so it cleans itself up on your schedule
Let the client upload back through the same link - no account, no second tool
Skip anything that makes the client sign up, install, or hunt for a working link

The ask is tiny. The tools make it big.

Here is the whole job, written out plainly:

Get one file to one client.
Decide how long it should stick around.
Let them hand one back.

Three steps. Nothing exotic. Yet every common tool solves one of them and quietly breaks the other two.

Email sends the file, but it has no concept of "delete this in a month," and a 30 MB attachment bounces or lands in spam.
WeTransfer sends the file fast, then the link expires in seven days whether the client downloaded it or not - and there's no clean way for them to send one back.
A shared Drive folder keeps the file around forever, but now you're managing permissions, the client can see more than they should, and there's no per-file lifespan.
WhatsApp is easy to send through, but the file is buried under chat within a week and you've now mixed work with personal messaging.

None of them is wrong. Each just solves a third of the problem and leaves you stitching the rest together by hand.

The piece everyone forgets: control over the file's lifespan

Sending a file is the easy half. The half that gets ignored is what happens to it afterward.

Most tools give you two settings: forever, or gone-in-seven-days. Neither is what you actually want. You want to decide - per file. A signed contract might live for years. A rough draft or a one-time deliverable should clean itself up so you're not the unofficial archivist of every project you've ever touched.

That's a per-file expiration date. You set it when you share, and the file removes itself on that date without you remembering to go back and tidy up. It's the difference between a folder that grows forever and one that maintains itself.

This matters more than it sounds. Files you no longer need are files you're still responsible for - for storage, and for privacy. Letting an old draft expire on a date you chose is simpler and safer than letting everything pile up indefinitely.

The other forgotten piece: letting the client upload back

Sharing is rarely one-directional. You send a draft, they send a marked-up version. You send a contract, they send it back signed. You send a brief, they send the source photos.

With most setups, the return trip is a whole separate negotiation. "Can you email it?" "It's too big." "Try WeTransfer?" "What's the link?" The client ends up choosing their own tool, and now the file you need is in a third place.

The fix is unglamorous: the client should be able to upload a file back through the same link you already gave them. No account to create, no app to install, no transfer service to learn. They open the link, drop the file, done. One surface, both directions.

That covers one file coming back. It doesn't cover the more common case: you need several specific things, not one. A signed engagement letter, last month's bank statement, a copy of an ID, two receipts - each a separate ask, and asking for them one at a time over email is the same chase you were already trying to avoid, just repeated five times instead of once. This is what a document checklist is for. You list exactly what you need from that client, and they see the list from their side - what's still outstanding, what they've already provided. Nobody has to keep a mental tally or send a follow-up email just to ask "did you get the last one?" - the list itself shows it.

A real example

A freelance bookkeeper sends each client their quarterly reports as PDFs. The reports are sensitive, so she doesn't want them living in an inbox indefinitely - but she also doesn't want to chase clients to delete anything.

Her old routine: email the PDF, hope it didn't bounce, then field "can you resend last quarter's?" months later. When a client needed to send a receipt back, it arrived as a blurry phone photo in a reply three threads deep.

Her new routine: each client has one link. She uploads the report and sets it to expire in twelve months - long enough to be useful, short enough to clean itself up. When a client needs to send something back, they use the same link. She stopped being the archive, and the "can you resend?" emails stopped with it.

Nothing about that is sophisticated. It's just the three-step job, finally done in one place.

Where Droplana fits

Droplana is built for exactly this small job. Each client gets one private link - no account on their end. You upload a file, set an expiration date on it, and share the link. They can upload files back through the same link. If a file needs a note or a quick comment, that lives next to the file too, but it's optional - the point is the file, not a feature pile.

On the free plan, files are kept for up to 90 days and you get three clients. Solo, Practice, and Studio remove the retention cap and the client limit. Either way, all files are stored on EU infrastructure in Germany, which matters if you or your clients care about where the data sits.

Honest about the edges: Droplana is not a Drive replacement for your own long-term archive, not a project management tool, and not built for internal team collaboration. It does the client-facing file exchange - sending, expiry, and receiving - and stays out of the way otherwise. If your need is bigger than "share a file with a client and control what happens to it," it's the wrong tool.

Wrapping up

The reason this still feels hard isn't that the problem is hard. It's that the popular tools each solve one slice and ignore the rest - so you do the stitching. The whole job is small: one link per client, a lifespan you choose per file, and a return path the client can actually use. Once those three live in one place, sharing a file with a client stops being a task and goes back to being a click.

If you've been running this through email and feeling the friction, try the same flow with one client and one file. You'll know within a week whether it's better.