Every editor and filmmaker hits this wall eventually: the project is done — or the footage just came off the card — and now a folder measured in tens of gigabytes has to get to another computer. Email laughs at you at 25MB. Free WeTransfer stops at 2GB. And the "proper" cloud route means watching an upload bar for hours so the other person can then watch a download bar for hours.
The thing is, for most of these handoffs the cloud was never actually necessary. Your files don't need to live anywhere — they need to move from your machine to one other machine. This article covers how direct transfer works, when the cloud genuinely is the better tool, and a concrete workflow for sending huge folders without touching either.
Why large video files are so painful to send
Three separate problems stack on top of each other:
- Size limits built for documents. Most sharing tools were designed around office files. Video laughs at those limits: a minute of 4K footage can outweigh a thousand PDFs.
- The double trip. Cloud transfer means your file travels twice — up from you, down to them — and the upload leg runs at your connection's upload speed, typically a fraction of your download speed. A 50GB folder on a 20 Mbps uplink is roughly 5–6 hours of uploading before the recipient can even start.
- Fragility. Many tools restart a failed transfer from zero. At hour four of six, a dropped connection isn't an inconvenience — it's an evening.
Add pricing (per-GB fees or monthly storage for files that only needed to exist in transit) and privacy (client footage parked on a third-party server), and the standard route starts looking like what it is: a workaround that became a habit.
The direct alternative: computer to computer
A direct transfer skips the intermediary entirely. Your machine connects to the recipient's machine and the data flows point-to-point — one trip instead of two, no server in the middle, no storage bill, no copy left behind anywhere.
This is what ClickandSend does. The receiving side picks a destination folder and gets a short connection code; the sender pastes the code, picks the files or folders, and sends. A few properties matter in practice:
- No size limit. There's no tier where a 50GB folder becomes a problem — the constraint is your connection, not a plan.
- Folders travel as folders. A project directory arrives with its structure intact — subfolders, relative paths, everything — not as a zip you have to rebuild.
- Transfers resume. If the connection drops at 80%, it continues from 80%, not from zero. For multi-hour transfers this is the difference between annoying and catastrophic.
- The receiver approves. Nothing lands on the destination machine without the recipient accepting it — no surprise 60GB appearing on someone's nearly-full drive.
- Nothing is stored server-side. The files go from disk to disk. There is no copy to expire, leak, or pay for.
On a local network (two machines in the same studio), a direct transfer runs at LAN speed — moving footage between edit bays at hundreds of megabits without a cable shuffle. Over the internet, it runs at the natural ceiling of the two connections, with no service throttle on top.
When the cloud is still the right call
Direct transfer is a point-to-point tool. The cloud earns its keep when the shape of the problem is different:
- One-to-many distribution. Ten stakeholders each need the deliverables — upload once, share a link.
- Long-lived shared assets. A logo pack the whole team pulls from for months belongs in shared storage.
- Both machines can't be online together. Direct transfer needs both ends running at the same time. If your recipient is asleep on another continent and the files must be waiting for them, a cloud drop is the honest choice.
The workflow rule we use across the modern editing pipeline: storage for things that need to live somewhere, direct transfer for things that need to move somewhere.
Sending a 50GB shoot folder: the actual workflow
- Receiver: open ClickandSend, choose the destination folder (put it straight on the edit drive — no "move it later" step), and start sharing. The app shows a short connection code/link.
- Receiver → sender: send the code over whatever channel you already use — a WhatsApp message is fine. The code is what pairs the two machines.
- Sender: open ClickandSend, drop in the folder (drag-and-drop works, structure is preserved), paste the code, hit send.
- Receiver: approve the incoming transfer. Data starts flowing disk-to-disk with live progress on both ends.
- Walk away. If either connection hiccups, the transfer resumes where it stopped. When it finishes, the folder is already in its final location — no unzipping, no re-organizing, no download step.
That's the entire process. No accounts for the recipient to create, no storage plan to size, no link that expires in seven days.
Common mistakes when moving big footage
- Zipping first. Compressing already-compressed video buys you almost nothing and adds an hour of CPU time on each end. Send the folder as-is with a tool that preserves structure.
- Sending to the laptop, then copying to the edit drive. Receive directly into the destination. Every intermediate copy of 50GB is another half hour and another chance for a half-copied folder.
- Using a method that can't resume. Ask one question of any transfer tool: what happens at a mid-transfer disconnect? If the answer is "start over," keep looking.
- Leaving client footage on a sharing service. If you did use a cloud link, calendar its deletion. Unreleased material with a long-lived public link is a quiet liability.
The bottom line
Sending large video files is only hard when the route includes a stop the files never needed to make. Point the two machines at each other, let the transfer resume through hiccups, and a 50GB handoff becomes a background task instead of an evening's project.
Download ClickandSend — it's a portable app (no installation), free for 20 transfers, with no file size limits. If your handoff is specifically footage between two editors, we've written up that exact scenario in How to Transfer Raw Footage Between Two Editors.
FAQ
How can I send a video file that is too big for email or WeTransfer?
Use a direct computer-to-computer transfer tool. Instead of uploading to a server, the file travels straight from your machine to the recipient's — no size limit, one trip instead of two, and nothing stored in between.
How long does it take to send 50GB directly?
It depends on the slower of the two connections. On a shared local network it can be minutes to tens of minutes at LAN speed; over the internet it runs at your natural connection ceiling — but unlike cloud transfer, it's one trip instead of an upload followed by a download.
Do both computers need to be online at the same time?
Yes — that's the trade-off of direct transfer. If the recipient can't be online, use a cloud drop for that handoff. For everything else, direct is faster and leaves no copy behind.
Is direct file transfer safe for client footage?
Direct transfer avoids the main cloud risk: there is no third-party server holding a copy of the material and no shareable link floating around. The receiver also has to explicitly accept each incoming transfer.
Can I send an entire folder with subfolders?
Yes — ClickandSend transfers whole folders with their structure preserved, and resumes per-file if the connection drops mid-way.
Ready to download?
Get CLICKandDOWN and save video from YouTube, Instagram, TikTok and more — your first 20 downloads are free.
download Start Free