Large video transfer

How it works

Call it large when email and a single short POST are not credible, which for video is often above a couple of gigabytes. Use multipart or tus. Send a proxy separately if people must review before the master finishes. Do not make the proxy the only delivery.

An 18 GB master uploads in parts over two hours on a 25 Mbps up link. A 200 MB proxy goes first so notes can start. The master hash lands in the same thread. Editorial does not lock the cut until the master matches.

How it differs

Large video is the size-and-type case of large file transfer. The extra rule is codec. A short hash-matched file in the wrong codec is still a failed delivery.

Overnight desktop uploads die when the machine sleeps. A host that stays awake, or a resume the user can reopen, is part of the term.

Color pipeline LUTs that do not travel with the master make a perfect file look wrong in the grading suite.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• Count the finished object, not the first byte, before you close the ticket.