Why do EXR frame sequences transfer so slowly?

Because a sequence is one image per frame — thousands of small files — and each file carries a fixed overhead to open, read, create and close. On one large file that cost is paid once; on 8,000 frames it is paid 8,000 times, and that overhead can dominate, so the folder moves at a fraction of the speed the same bytes would as a single file.

What is the fastest way to move a rendered shot between workstations?

Move the whole sequence folder as one operation over a wired gigabit LAN. For occasional sends, archiving (zip/tar) the sequence into one file removes the per-file overhead entirely. For daily handoffs, a direct LAN transfer like Oxolan streams the folder over one connection at 60–115 MB/s and resumes after an interruption, so a 60 GB shot is minutes, not an afternoon.

Should I zip a frame sequence before transferring it?

For a one-off transfer to the cloud or an external drive, yes — archiving into a single file removes the per-file overhead and copies at full speed, at the cost of compress/extract time. For frequent handoffs on the LAN, a transfer tool that pipelines the folder makes zipping unnecessary — you send the sequence folder directly and it behaves more like one large transfer.

How to Transfer EXR Frame Sequences Between Workstations Fast

Why Frame Sequences Are Slow to Move

An EXR render is not one file — it is one image per frame. A five-second shot at 24 fps is 120 files; a full shot with handles and multiple render passes is easily several thousand. The total might be 20–60 GB, which sounds like a quick copy on a fast network. It rarely is, and the reason is per-file overhead.

Every file in a transfer carries a fixed cost: opening it, reading its metadata, creating it on the destination, closing it. On one 20 GB file that cost is paid once. On 8,000 frames it is paid 8,000 times, and that overhead can dominate the transfer — a folder of frames often moves at a fraction of the speed the same bytes would as a single file.

This is why "the network is gigabit but the sequence still takes forever" is such a common complaint in animation and VFX.

What Makes It Worse

Cloud sync is the worst case. Sync clients (Dropbox, OneDrive, Google Drive) process files individually and round-trip each one through a server. Thousands of small files plus upload-limited bandwidth is a perfect storm — see local transfer vs cloud speed.
SMB over the network handles many files better than cloud but still pays per-file overhead, and a stalled copy restarts from zero.
Antivirus scanning each frame as it is written can halve throughput — a real factor with thousands of files.

How to Move a Sequence Fast

1. Move the folder as one job, not file by file. Whatever tool you use, transfer the whole sequence folder in a single operation so the tool can pipeline the work rather than treating each frame as a separate task.

2. For occasional handoffs, archive first. Zipping (or tar-ing) a sequence into one file removes the per-file overhead entirely — one big file copies at full speed. The trade-off is the time to compress and extract; worth it for a cloud send or an external drive, overkill for a quick LAN handoff.

3. For daily handoffs, use a direct LAN transfer. A tool that streams a folder over one connection avoids both the cloud round-trip and most of the per-file penalty. Oxolan sends a sequence folder directly between workstations at 60–115 MB/s on gigabit, and — the part that matters for a 60 GB shot — resumes after an interruption instead of restarting, so a dropped transfer at 80% continues from 80%.

4. Wire the machines. Frame sequences are the last thing you want on Wi-Fi. The wired-vs-Wi-Fi gap is largest exactly for big, sustained transfers.

5. Exclude the working folders from real-time antivirus. Scanning every frame on write is a hidden tax; exclude your render-output and cache folders on the destination machine.

A Quick Speed Reference

At a sustained 110 MB/s on wired gigabit (best case, sequence moved as a job):

20 GB shot (~4,000 frames): about 3 minutes
40 GB shot: about 6 minutes
60 GB shot: about 9 minutes

Use the transfer-time calculator with your own sizes. If you are seeing far worse than this, per-file overhead, a Wi-Fi hop, antivirus, or a slow drive is the cause — work through the slow-transfer guide.