How to Receive Large Video Files From Clients Without Chasing Links
How I receive large video files from clients and outside editors in one project, and how statuses tell my team what actually arrived before the edit starts.
Client video files are where I made a really really silly mistake in my video editing agency, on the one job that sounds too boring to get wrong, which is how you receive large video files from clients, right. A client had shot an event on three cameras, and instead of giving them one place to put everything I said send it however is easiest for you. So they did exactly that, basically a transfer link from the camera operator, a shared drive folder from their marketing person and a few phone clips over chat.
The catch here is that one of those transfer links expired before anybody on my side downloaded it, and nobody noticed for days because we all assumed the footage was in. By the time my editor opened the project we were missing an entire camera angle, so I had to call the client, apologise and ask them to dig the card out again, which pushed the delivery back and, to be very honest, made us look like a team that did not have its house in order.
So this post is the reverse of sharing a cut, right, it's about how I now get footage and new versions coming into one project from clients and outside editors, and where PlayPause fits into that, including the parts where it honestly doesn't.
Why receiving files is harder than sending them
When I send a file I control everything, right, the export, the tool, the file name and the moment it's done, and I've covered that direction in my guide on sending large video files to clients. Receiving flips all of that around, because now the whole thing depends on somebody else's habits and somebody else's idea of what "the footage" means. Most clients are busy people who just want the files off their plate so they can get back to their actual job.
For instance, a client will send you the one clip they think is the good take and forget the other forty, or they'll export a compressed copy out of their phone gallery because the original felt too big, and so on. Nobody ever told them what you need, so the first real fix is on your side, which is giving them one obvious place to put things and telling them plainly what to send. If your clients shoot on phones, my post on sending full-quality iPhone video is worth forwarding before the shoot, because it saves you from receiving a squashed file in the first place.
The other half of the problem is knowing when it's actually done, right. A transfer email saying your files are ready tells you that something was sent, but it says nothing about whether it was everything or whether anyone on your team has opened it, and that gap between sent and received is exactly where my missing camera angle fell through.
Transfer links, drive folders and a file request for video
Before I moved everything into one project I tried pretty much every approach agencies use, and I'm pretty sure you've tried most of them too, and each one leaves a gap that usually bites you three days before delivery.
Transfer links are the default because clients already know them, but the file lands in one person's downloads folder and the link dies after a set number of days. Then someone has to upload it again into wherever the editing and review actually happen, so you end up moving the same heavy file twice. Shared drive folders feel more permanent, but the client often needs an account on the same service, permissions get messy, and three months later the folder is full of "final_v2_REAL" files that nobody wants to touch.
A file request for video is the smartest of the lot, basically a page where the client drops files into a folder you own without seeing anything else inside it, and I do like that idea. The catch here is that the files still sit outside the place where you review and approve, so your editor downloads them, cuts and uploads a review copy somewhere else, and the context of who sent what gets lost on the way, you see what I mean here.
Footage arrives through transfer links, drive folders and chat, then gets downloaded and uploaded again before anyone can review it
Guest uploads and your own bulk uploads land in the same project where review, versions and statuses already live
Guest upload without an account, name and email collected
On the Agency and Enterprise plans, PlayPause has guest version upload, which basically means someone outside your workspace can upload a version into your project without creating an account. While they do it their name and email are collected, so you always know who sent which file. For me this is the client upload link I was missing for years, right, because the client doesn't sign up or install anything and the file lands exactly where my team is going to review it.
Because it's a version upload, I mostly use it for things that naturally become a version on a card, like a client's own rough cut, a corrected master or a replacement export with the new logo. When a client has a whole shoot's worth of raw cards to hand over, I'd rather my own team brings those in, which I'll get to in the bulk upload section.
The name and email part sounds small, but trust me on any level, it matters once files come from the marketing lead and an outside photographer on the same shoot, because nobody has to send a group message asking who uploaded the vertical version.
On Agency and Enterprise, anyone you send the link to can upload a version without an account, and PlayPause collects their name and email so every file arrives with a sender.
Size is the other worry when you let clients upload video, right. On Agency and Enterprise there is no max upload size per file, so a long multicam export or a big ProRes master doesn't need to be split or compressed first. On Creator the max upload is 10 GB per file and guest version upload isn't included, so on that plan you or your editor do the uploading yourselves, which is fine for a solo editor but starts to hurt once clients send footage every week.
One practical tip from my side is to tell the client exactly what you want before you send the link, like the original export with no re-compressing and no renaming, because an easy upload only helps if it's the right file. For the opposite direction, where your client comments on a cut, my walkthrough on how to get a shareable review link covers that side.
Letting an outside editor add the next version
The same guest version upload works really well for people who are not clients at all, like a freelance editor you've brought in for one project or an in-house editor on the client's side doing the first pass. They open the link and upload their cut, and it stacks onto the same card as the next version, so what was MV1 yesterday now has an MV2 sitting on top of it and nobody emails you a file called "edit_new_new".
This matters because an agency workflow is really just a messy kind of version control, right, and the whole point is that everyone is looking at the same latest file with the full history underneath it. On Agency and up you also get side-by-side version compare, so when the outside editor uploads MV3 I can put it next to MV2 and see what actually changed before the client ever sees it.
If you're a freelancer on the receiving end of this from agencies, have a look at how PlayPause works for freelance editors, and if the handoff itself is the painful part, I've written separately about a proper raw footage handoff to editors.
Bulk uploading 100 plus files on your side
Receiving isn't always the client sending things in, right, because a lot of the time it's my own team coming back from a shoot with a few cards full of clips that need to land in the same project as everything else. Every plan supports batch uploads of 100 plus files at once, and there's a Mac and Windows desktop app as well as a mobile app that uploads straight from the camera roll.
Storage is a pool per workspace rather than per person, so adding someone who uploads doesn't cost you more, and it's 100 GB on Creator, 250 GB on Agency and 1 TB on Enterprise. The media storage page has the details if you keep a lot of raw footage around.
Marking what arrived with custom statuses
This is the part that would have saved me from my missing camera angle, right, because uploading is only half of receiving. The other half is somebody on your team confirming that they opened the file and that it's complete. PlayPause has custom statuses on every plan, so you can make your own set, something like Waiting on client, Footage in, Checked and In edit, and move each card along as it progresses.
It's basic project management, really, because you can see at a glance which cards are still waiting and which ones are safe for the editor to start on. A card that has sat on Waiting on client since Thursday is something you notice on Monday morning, long before it turns into a missing angle in delivery week. At the end of the day, the rule in my agency now is simple, a file doesn't count as received until someone has opened it and moved its status.
A file does not count as received until someone on my team has opened it and moved its status.
Statuses also help when extra material turns up after the brief is locked, because a fresh cut that lands with a name and a status of its own makes it very very easy to have the honest conversation about scope creep.
A worked example with a three-camera shoot
So let me put it together with the same kind of job that burned me, a half-day event on three cameras plus a separate audio recorder. Before the shoot I set up one project with a folder for each camera and one for the audio, right, and I send the camera operator a short note asking for the originals straight off the cards with no renaming, plus a rough clip count and total size per card once they've wrapped.
Then I do the storage math before the shoot rather than after it. Say each camera comes back with around 120 GB, which is an illustrative number and not a rule, so three cameras is roughly 360 GB, and that's already more than the 250 GB pool on Agency. On that plan I'd clear out finished projects first or look at Enterprise with 1 TB, and this is exactly the bit I used to discover halfway through an upload.
If the operator is in another city, I let them use whatever transfer tool they like for the raw cards, but my team downloads it the same day and bulk uploads it into the right folder, so the transfer link is never the place the footage lives. If the client's marketing lead then wants to send a corrected brand video for the end card, that comes in through the guest link on Agency with their name on it.
Before anything moves to Checked, somebody on my side compares the clip count with the operator's note and the total size with what we expected. Then they play the last clip of each camera right to the end, because a last file that stops early is the classic sign of a copy that died halfway, and only after that does the editor start.
- Tell the sender exactly what to upload before the link goes out
- Keep uploads in the same project as the review
- Match the clip count and total size against the sender's note
- Play the last clip of every camera to the end
- Move cards to Checked only after those checks
Frequently asked questions
Can clients upload video without creating an account?
On the Agency and Enterprise plans they can, through guest version upload, which lets anyone you send the link to upload a version into your project without signing up for anything. PlayPause collects their name and email while they upload, so the file arrives with a sender attached, right. On Creator, guest upload isn't included, so your own team handles the uploading.
Is there a file size limit when a client sends footage?
On Agency and Enterprise there is no max upload size per file, so long multicam exports and big masters go in as they are, while on Creator the max upload is 10 GB per file. Each plan also has a storage pool for the whole workspace, 100 GB on Creator, 250 GB on Agency and 1 TB on Enterprise, so plan around that pool and not just the single file.
Does PlayPause change the original file the client uploads?
Playback in the browser runs from a streaming copy and the original file stays untouched, so the client reviews something smooth while the full-quality version your editor needs is still exactly what came off the camera. To be very honest, this is one of the first things I'd check in any tool you use to receive footage, because a compressed copy quietly becoming your master is a painful discovery at the grading stage.
Can my own team upload a whole shoot at once?
Every plan includes bulk upload, which handles 100 plus files in one go, and the mobile app uploads straight from the camera roll for phone footage. Once everything is in, I'd check the clip count against the shooter's note and set a status like Footage in on each card, so everyone can see what has landed before the edit starts.
If you're tired of chasing transfer links and want new versions landing where your team already reviews them, have a look at the plans on our PlayPause pricing page, and remember that guest version upload sits on Agency and Enterprise. Every plan comes with a 7-day free trial, so set up one real project, send a client the link and see how it feels before you commit, does that make sense, right.
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