How Freelancers Can Share Client Files Without Asking Anyone to Sign Up

Client work has a delivery problem, and it's not the work itself. It's the handoff.

You finish a project — a set of design mockups, an edited video, a batch of photos, a final PDF — and then the annoying part begins. You email it, and Gmail bounces anything over 25 MB. You upload it to Drive, and your client gets a "request access" screen because they opened it with a different account. You use a transfer tool, and the client gets asked to create an account just to download the file you already made for them.

Freelancers live in this gap. We don't need enterprise file management with client portals and permission tiers. We need something that sits between "email is too small" and "another platform my client has to learn."

After a few years of juggling this on both sides — sending work out and receiving assets from collaborators — I've found the friction usually comes down to four things.

1. Clients who won't sign up for anything

This is the biggest one. A client pays you for a deliverable, not for an onboarding flow. Asking a busy founder or a marketing manager to create an account on a tool they'll use once, verify their email, and then find your file is a lot to ask. Plenty of them just won't do it. They'll reply "can you just email it?" and then complain when the email never arrives.

2. Files that outlive the project

Most sharing links never expire. That design file from a project that ended eight months ago is still sitting on someone's server, attached to a link you lost track of. For client work — especially work under NDA — that matters. A finished project shouldn't leave a permanent copy floating around on a third-party service you can't audit.

3. Email limits that make no sense in 2026

Gmail caps attachments at 25 MB. Outlook is similar. A short phone video in 4K can be ten times that. Raw photos from a shoot, a designer's layered file, an uncompressed audio export — none of these fit in an email, and compressing them just to satisfy an attachment limit means sending your client a worse version of your work.

4. The privacy middle ground

Chat apps aren't great either. Sending client files over WhatsApp or Telegram mixes work into personal messaging, and the files stay there indefinitely unless someone manually deletes them. What you really want is a share that behaves like a handoff: you give it, they take it, and then it's gone on your terms.

What a good freelancer workflow looks like

The ideal handoff has a specific shape. You upload the file. You get something short and easy to pass along — a short code, a QR code, a link. Your client opens it on whatever device they're using, downloads what they need, and never signs up for anything. You pick how long the share stays alive, and after that it deletes itself.

That last part is worth saying twice, because it's the one most tools skip. Expiry shouldn't be a premium feature. If you're sharing a contract draft, a set of medical forms, a brand asset, or anything time-sensitive, the link should have a built-in end date. One hour, a day, a few days, a week — you choose, and the file disappears when the time runs out.

I've started using nowiretransfer for exactly this kind of handoff. It's a free tool in the browser — no account on either side. You add a file or some text, get a six-character code or a QR, and your client opens it on any modern browser. Files go up to 250 MB each and are sent as-is, so nobody is compressing your deliverable into a blurry preview. The shares are unlisted and encrypted, and you pick the expiry: one hour, 24 hours, three days, or seven days.

It works well for the usual freelancer scenarios. Sending a video cut to a client for review? A short expiry means the review link stops working once the project wraps. Need to send large files without signup, share a contract, or pass along text that shouldn't live in an email thread forever? It handles all of that from the same page. Collecting raw assets from a client who doesn't want another login? They upload from their phone browser and hand you the code.

The phone part matters more than it sounds. A surprising number of client handoffs happen on phones — a client approving a design on the couch, a collaborator sending phone photos for a project. Anything that requires a desktop app or a download is friction. Anything that works in the browser on iOS, Android, Windows, or Mac is just a link away.

A small habit worth adopting

The real win isn't one tool, it's a rule of thumb: stop creating permanent shares for temporary work. Before you send a file, ask yourself two questions. Does the recipient need an account for this? And does this link need to exist next month?

If the answer to the first is "no, but the tool demands it," use a tool that doesn't. If the answer to the second is "no," set an expiry and let the file delete itself. Your clients get their files with less effort, and you stop leaving finished projects scattered across the internet long after you've been paid.

Client work is temporary. Your file sharing should be too.

Originally published on Hashnode: https://practicalprivacynotes.hashnode.dev/how-freelancers-can-share-client-files-without-asking-anyone-to-sign-up