Stop shipping drives when the complete online path—upload, recipient access, download, and verification—reliably fits inside the complete physical path—copy-on, packaging, carrier cutoff, transit, copy-off, and verification—at an acceptable cost and risk. There is no universal dataset threshold. Calculate the crossover for each route and repeat it when endpoints or deadlines change.
Compare two complete clocks
For one recipient:
physical elapsed = copy to drive + handling/cutoff + transit + copy from drive + verification
online elapsed = upload + availability/access + download + verification
The common mistake is comparing courier transit with upload alone. Shipping requires two local copies. Online delivery requires two network legs. Either path can also wait on an operator, an access issue, or an endpoint.
Microsoft's transfer guidance keeps offline devices in the toolkit for large datasets and limited connectivity. Its current Azure Data Box guidance positions the service above 40 TB and lists next-generation 120 TB and 525 TB usable devices. That is Microsoft product guidance, not a law saying every 39 TB job belongs online or every 41 TB job belongs on a device.
Build a physical baseline
Consider an illustrative 7.8 TB delivery. Assume sustained local copy speed of 200 MB/s, which equals 720 decimal GB/hour. Each copy takes about 10 hours 50 minutes, so the two physical copy passes consume about 21 hours 40 minutes before packaging, cutoff, transit, receiving, and verification. The 200 MB/s figure is an assumption, not a USB or drive guarantee.
USB-IF specifies USB 3.2 signaling rates of 5, 10, and 20 Gbps. Signaling rate does not establish sustained file-copy speed; media, enclosure, filesystem, file count, source storage, thermal behavior, and host all matter. Measure a representative package.
Carrier service is another input. UPS's 2026 U.S. Daily Rate guide, effective May 10, lists a 5 lb Next Day Air package at $54.75 in Zone 2, $129.93 in Zone 5, and $134.93 in Zone 6. Those are contiguous-U.S. published Daily Rate examples, not quotes. Account terms, billable weight, dimensions, surcharge, pickup, route, service, and negotiated discounts change the invoice.
FedEx offers multiple U.S. domestic service levels. Origin, destination, tender time, weekend or holiday, and service availability determine the commitment, so “overnight” is not a complete assumption.
Derive the network threshold
The current transfer calculator treats 7.8 TB as decimal, adds a 12% planning allowance, and adds sequential upload and one-recipient download legs. If both endpoints have the same effective bandwidth:
- fitting both legs into 72 hours requires about 539 Mbps, producing 72 hours;
- fitting both legs into 48 hours requires about 809 Mbps, producing 48 hours;
- fitting both legs into 24 hours requires about 1,618 Mbps, producing 24 hours.
These are derived planning thresholds, not observed speeds or service promises. They exclude access, notification, verification, and ingest. If upload and download differ, calculate them separately; the slower side can dominate.
The shipping-versus-online comparison explains the same two clocks, while the real shipping-cost guide itemizes media, labor, packaging, carrier, and risk.
Add labor, recipient count, and first-use time
Elapsed time is not the only decision. Shipping drives to three editors generally means three media copies and shipments. One online upload can support multiple recipient downloads, subject to platform terms, egress, and each endpoint.
Calculate active labor for staging, tracking, access, diagnosis, ingest, and verification. Then calculate blocked labor separately. The waiting-for-footage model shows why a slow overnight job can cost no idle time while a shorter daytime delay can block a session.
Also distinguish complete originals from first usable media. Apple lists 4096×2160/24p ProRes 422 Proxy at about 70 GB/hour and ProRes 422 HQ at about 339 GB/hour. A proxy-first handoff can let editorial begin while originals continue online or ship. Hybrid is often the decision threshold's practical middle, not a compromise to hide.
Clear “ship,” “send,” and hybrid cases
Keep shipping when a location has no dependable connectivity, measured transfer time misses the deadline, a very large one-time job already has a proven media shuttle, or policy requires an approved physical process. Retain another verified copy and plan for delay, loss, damage, and recipient ingest.
Move online when both endpoints are measured and repeatable, the full path beats copy-plus-courier, multiple recipients need the package, early file availability matters, and operations can support access and verification.
Use both when proxies, reports, audio, or urgent selects can start editorial while camera originals take the slower route. Define package identities so recipients do not combine mismatched versions.
Recalculate whenever the editor, facility, carrier lane, upload link, dataset, or delivery window changes. Use the remote-editor workflow and delivery-night checklist to keep either route controlled.
Where TeraAirlift fits
TeraAirlift is the online side of the decision: a Windows-first desktop operations console with queue visibility, progress and ETA, cancellation, retry-friendly operations, history, diagnostics, recipient-controlled delivery, and SHA-256 verification. It does not replace shipping for disconnected sites or guarantee throughput. Plans start with a 10 TB included allotment, but packages can be any size; volume above the allotment is overage, with details confirmed on a demo. See the post-production workflow.
