How to Request Files From Clients Without Making Them Sign Up
Most teams request files from clients through chat threads and expiring transfer links. Here is the no sign-up flow I use in my agency, the exact request message I send, and its honest limits.
Most editing teams I know request files from clients through a WhatsApp thread, an email chain and whatever transfer link the client found that morning, and to be very honest my own agency ran exactly like that for a long time. What it looked like in practice was an editor spending the first hour of every project digging through email for the logo the client swears they sent last Tuesday, right, and all of us calling that a process.
We put so much effort into the outbound side, the clean review link and the frame-accurate comments, and then the inbound side is basically chaos. The moment you ask a client or a freelancer to create yet another account just to hand you a file, some of them stall for days and the rest send a transfer link that expires on Friday.
So below is how I collect files from clients now, including the exact message my team sends on day one, because no tool fixes a client who doesn't know what to send, right, and that part is on us as the people running the project.
Why collecting files from clients is harder than sending them
Sending is easy because you control everything, right, you know the file and you're the one motivated to get it out the door. Receiving flips that, because now the person holding the file is the least motivated person in the chain, and they are definitely not reading your onboarding email about naming conventions.
In my agency the inbound files fall into a few buckets that each break differently. Raw footage is huge and arrives in pieces, and brand assets like logos, fonts, music licences and so on are tiny but somehow always the wrong version. Then there's the bucket most people forget, which is a new version of a video coming back from someone else, for instance a subcontracted colorist returning a graded cut, or a client's in-house social person sending their own trim of your edit.
That last bucket is where the real damage happens, because a version that arrives outside your review tool has no history attached to it, and I'm pretty sure most mix-ups about which version a client reviewed start at the moment a file comes in through the side door.
A cut that arrives over chat or email has no history, so nobody can say for sure whether it is newer than the one the client approved.
Common ways editors request video files from clients today
I've done every one of these myself, so no judgment here. The most common setup is email attachments for small stuff and a transfer link for anything big, and the catch here is that both land the file in your inbox rather than in your project, so somebody has to download it, rename it and upload it again.
Then there's the shared cloud folder, which is honestly fine for a one-time dump of raw footage, right, but used for cuts it works really really well for about a week, until the folder fills up with files called final, final2 and final real, which is basically the exact problem version control was invented to solve in software.
Some teams use the file request features inside storage tools, where the other person uploads into your folder without signing in. Those are genuinely better than email, but they stop at the folder, so the upload has no connection to comments or versions and you're back to moving files by hand.
The worst option is asking the client to create an account on the review tool before they can send anything, which is where a lot of projects quietly stall for three days because the invite went to spam.
Attachments, chat files and expiring transfer links that someone has to download, rename and upload again
One link where the outside person uploads the new cut, leaves a name and email, and it stacks on the same card
What a client file upload link should do
Here is the standard I use to judge a client file upload link, whatever tool it sits in.
- No account and no install for the person uploading
- Captures who sent the file with a name and email
- Lands the file in the project instead of an inbox
- Treats a new cut as a new version of the same video
- Accepts large originals without a size fight
- Can be password protected and revoked when the job ends
The first two points pull against each other, right, because the easiest way to know who uploaded something is to make them log in, and the easiest way to get them to upload is to not make them log in. What I've landed on is a name and an email at the moment of upload, which is enough to know the graded cut came from your colorist.
The third and fourth points are the ones most tools miss, and you see what I mean here, a file that lands in the project as the next version of the video is a file nobody on your team ever has to touch again, because the whole cost of inbound files is the handling in between.
The request message I actually send
The link only solves half of it, and the other half is telling people exactly what to send, in writing. On day one of a brand film my team sends something very close to this: "Hi, to start the edit we need a few things by Thursday. The original camera files from the shoot, not the copies you shared on WhatsApp, because those get compressed. Your logo as an SVG, or a PNG with a transparent background, plus any brand fonts. The licence or link for any music you want to use. Please keep one folder per camera, and if the footage runs past a few hundred gigabytes, tell us and we'll pick up a drive instead."
Every line in there exists because something went wrong without it, basically. A real date beats "whenever you get a chance", which in client language means next week. The WhatsApp line is there because I've watched footage that looked fine on a phone fall apart on a 4K timeline, and one folder per camera saves my editor from guessing which angle is which.
I keep that list in the creative brief, and for retainer clients it also goes into the statement of work, so our turnaround clock starts the day the files arrive rather than the day we asked. In PlayPause I put the same spec into a Playbook for the client on Agency, with a checklist that isn't done until it's ticked, shared as a no-login page they can reopen whenever they forget what we asked for.
Guest uploads that let clients upload without an account
This is the part I care about most. PlayPause has guest version upload on the Agency and Enterprise plans, and basically it means someone without a PlayPause account can open your link and upload a new version right there in the browser, with no install and no sign-up, while PlayPause collects their name and email.
The way I use it in my agency is pretty simple, right. When we send work to an outside colorist or a freelance editor, we create the card, upload our version as MV1 and send them the link, and when their cut is ready they upload it straight onto that same card. It works the same way when a client's in-house team sends back their own trim.
The people sending you files are exactly the people who will never create another account, and trust me on any level, they won't. A freelancer working with four agencies does not want four more logins, which is the same freelancer I had in mind when I wrote the Wipster alternative for freelancers piece.
Now the honest limit, because I don't want to oversell this. Guest version upload is built around versions, so it shines when the thing coming in is a new cut of something already in your project, and for a first-day dump of forty raw clips it is not a magic inbox, so raw footage still comes in the old way.
If your inbound files come from lots of people at once, I've gone deeper in collecting multi-cam footage from remote guests and the UGC creator submission workflow. Everything the client sees after that lives on the client review portal, so they open one link instead of hunting for five.
Frame-accurate note, everyone sees the exact same thing.
Landing new versions on the same card
Version stacks are on Creator and up, and they're the reason guest uploads are worth anything at all. A new file on the same card becomes MV2, then MV3, then MV4, and the client opens the same link as always and sees the newest cut with the older versions and their comments underneath.
On Agency you also get side-by-side version compare, which is really really useful when the version came from outside your team, because you can put your MV1 next to the colorist's MV2 and see exactly what changed. With who-watched analytics on top, I can see when the client actually opened MV2, which settles a lot of arguments before they start.
This is also where a lot of scope creep sneaks in, right, because when a client's in-house person uploads their own trim it's very very easy to treat it as another round of notes when it's actually a new direction. I've written about qualifying a revision versus a new project for exactly that conversation.
A file that lands on the right card as the next version is a file nobody on your team has to touch again.
Handling large files and bulk uploads
Large files are the other half of this problem, and your plan really matters here, right. Guest version upload lives on Agency and Enterprise, and both have unlimited max upload, so a colorist can send back a long graded master through the link without splitting or compressing it. Creator caps uploads at 10 GB per file, which is plenty for your own social cuts, but outside people can't upload through the link on Creator at all, so if subcontractors send you work, Agency is the plan to look at.
Whatever comes in, playback runs from a streaming copy and the original stays untouched, so a heavy ProRes file plays in the browser without anyone converting it. There's more on that in sharing ProRes files with clients, and the outbound side is in my guide on sending large video files to clients.
For your own side, every plan has bulk upload of 100+ files, so when a client hands over a drive with a whole shoot on it, one person on my team drops the entire folder into the project in one go, which you can see on the batch uploads page.
Keep link lifetime in mind too, because the freelancer needs the link alive for as long as the job runs, and Agency links last 90 days while Enterprise links never expire. Since outside people can upload through that link, I password protect it and revoke it instantly once the job is done, which works on every plan.
How review tools compare on guest uploads
I'll keep this fair, because Frame.io is a solid review tool, but it doesn't offer guest upload without an account and it's priced per seat, so every outside freelancer becomes either a paid seat or yet another account to create. PlayPause is flat per workspace and guests don't need to be members, and the full breakdown is on our PlayPause vs Frame.io comparison, with the Frame.io migration guide if you're switching.
The storage file request tools are good at getting a file into a folder without a login, but you still need a separate place for comments and versions, and a shared Google Drive folder has the same gap, which I went through in Google Drive timestamped video comments.
So at the end of the day, the test I run on any tool is whether a new cut from an outside person lands as the next version of the right video, with their name on it, without them signing up. If it doesn't, you'll be moving files by hand forever, which a two-person shop survives but an agency really can't, does that make sense, right.
Frequently asked questions
Can clients upload files to PlayPause without an account?
On the Agency and Enterprise plans, guest version upload lets someone open your link and upload a new version straight from the browser, without creating an account or installing anything. PlayPause asks for their name and email at the moment of upload, so you always know who sent it, and the file lands on the same card as the next version, right next to the earlier cuts.
Is there a size limit when clients upload video files?
Not on the plans where clients can upload, basically. Guest version upload is on Agency and Enterprise, and both have unlimited max upload, which is what I'd want if freelancers or colorists send back long ProRes masters. Creator has a 10 GB max upload, but that applies to your own team's uploads, because guests can't upload on Creator at all.
How do I collect raw footage from a client's shoot?
For a big first-day dump of raw clips, I'll be honest that guest version upload is built for versions rather than as a general inbox. My team sends the request message with the file list and a date, takes the drive or transfer link from the client once, then uses bulk upload of 100+ files to put the whole shoot into the project, and every new cut after that comes through the guest link.
Does Frame.io let guests upload without an account?
Frame.io doesn't offer guest upload without an account, and it's priced per seat from $15 per user per month, so giving outside people upload access costs you either seats or their patience. PlayPause pricing is flat per workspace, and guests uploading a version on Agency don't need to be members, which is the main reason I'd point an agency that leans on freelancers toward it.
If your inbound files still arrive through chat threads and expiring links, run your next freelancer handoff through one card and one link. You can compare the plans on the PlayPause pricing page, and every plan comes with a 7-day free trial, so you can test the guest upload flow on Agency with a real job.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free