To transfer hundreds of gigabytes of video footage remotely, treat delivery as a scheduled production step: measure the package, check the sender's upload and recipient's download, use a wired connection and a transfer method with durable job visibility, then verify the received files. Start early enough to recover from an interruption.
The headline internet speed is not the schedule. A 300 GB package on a 100 Mbps upload takes about 7 h 28 m one way in the current calculator model. At 20 Mbps it takes 37 h 20 m. The model adds 12% to the payload for planning; that allowance is an assumption, not a law or measured promise.
Measure the package before promising a time
Camera format, resolution, frame rate, compression, audio, proxies, and shooting ratio all change the total. Do not estimate from “4K” or “8K” alone. Inventory the selected folders after offload and before the handoff.
Manufacturer figures show the range. ARRI's ARRIRAW FAQ lists ALEXA LF Open Gate ARRIRAW at 1.80 TB per hour and 1.08 TB per hour with lossless HDE encoding. Those are specified camera-mode rates, not typical project sizes. Your transfer input should be the measured package, including audio, reports, checksums, and any proxies the editor needs.
Decide whether the recipient needs all camera originals immediately. Sending reports, project files, audio, and editorial proxies first can start work while camera media follows. That is sequencing, not a substitute for preserving and delivering the originals required by the production.
Work backward from both endpoints
A remote handoff normally has at least two sequential legs: sender to service, then service to recipient. A 300 GB upload and download on symmetrical 1 Gbps connections take about 1 h 30 m in the current model. If the sender has 40 Mbps up and the editor has 500 Mbps down, the modeled end-to-end time is 20 h 10 m.
Check these inputs:
- measured upload at the source during the intended transfer window;
- measured download at every recipient;
- available hours before editorial needs the media;
- other traffic sharing either connection;
- source read and destination write performance;
- whether the workstation can remain awake and connected;
- package file count, not only total bytes.
The FCC's Thirteenth Measuring Broadband America report is historical U.S. context. Its selected measurements came from September–October 2022 and documented substantial upload asymmetry outside fiber. It is not a statement about global or 2026 performance. Test the actual endpoints.
Choose the transfer method by workflow
Cloud drive or sync
This can be convenient when both editors already share a workspace and the provider's storage, per-file, daily activity, and browser-versus-desktop limits fit. Confirm whether the recipient needs an account, how selective sync behaves, and whether moving a folder later will break the handoff.
Purpose-built transfer application
This is useful for recurring or deadline-sensitive deliveries where operators need queues, progress, ETA, cancellation, history, diagnostics, and retry-friendly behavior. Evaluate the actual delivery and retention workflow, not a “fastest” claim.
Object storage and a desktop client or CLI
Technical teams can gain control over concurrency, credentials, and destination layout. Azure documents high service targets for block blobs and standard storage accounts, but these are ceilings scoped by service version, region, account type, request pattern, and quotas. They do not guarantee the throughput of your workstation or internet path.
Direct site-to-site transfer
SFTP, VPN, NAS, and managed point-to-point paths can satisfy policies that rule out temporary third-party storage. They also put firewall rules, credentials, endpoint uptime, WAN tuning, and recipient support on your team.
Shipped media
Physical delivery remains rational when measured connectivity misses the deadline or the destination is disconnected. Include copy-on, packaging, carrier cutoff and transit, copy-off, verification, and risk. Microsoft currently positions Azure Data Box for limited connectivity and datasets above 40 TB, with next-generation 120 TB and 525 TB usable devices; that is Microsoft product guidance, not a universal crossover point.
Make overnight jobs recoverable
Prefer a wired source. Prevent sleep, keep adequate free space, and avoid changing source files after the job begins. Send a manifest with folder names, byte counts, and the expected destination structure. Many small files can add metadata and transaction overhead, so test a representative folder rather than one large benchmark file.
Verification is separate from transport. PowerShell's Get-FileHash computes SHA-256 by default; matching sender and recipient hashes confirm matching contents for the checked files. Preserve the source copy until receipt and verification are complete.
Keep logs and identify who owns exceptions. “The upload window stayed open” is not evidence that every file arrived. A production handoff should end with a manifest check, integrity verification, and explicit recipient acknowledgment.
Where TeraAirlift fits
TeraAirlift is a Windows-first desktop operations console for large file and folder delivery. It provides queueing, progress and ETA, cancellation, retry-friendly operations, transfer history, diagnostics, recipient-controlled delivery, and SHA-256 integrity verification. It does not guarantee speed or remove endpoint constraints. See the post-production workflow or schedule a demo after sizing the job.
