You need a theoretical minimum of 92.6 Mbps sustained across a full day to move one decimal terabyte per day in one direction. Under the current calculator's 12% planning-overhead assumption, size the advertised connection at about 104 Mbps if the entire day is available and nothing else uses it. A half-day window needs about 208 Mbps; an eight-hour window needs about 312 Mbps.
Those are modeled minimums, not service recommendations or guarantees. Real circuit sizing needs headroom for competing traffic, slower periods, retries, storage, and maintenance. The sender needs upload capacity; each recipient needs enough download capacity.
Work backward from the transfer window
One decimal TB is 10^12 bytes, or 8 × 10^12 bits. At perfect line rate:
8,000,000 megabits / 86,400 seconds = 92.6 Mbps
The calculator models a 12% planning allowance by multiplying payload bits by 1.12. It does not claim that every path loses exactly 12%. With that assumption:
| Transfer window | Theoretical sustained rate | Calculator bandwidth input | |---|---:|---:| | 24 hours | 92.6 Mbps | 103.7 Mbps | | 12 hours | 185.2 Mbps | 207.4 Mbps | | 8 hours | 277.8 Mbps | 311.1 Mbps | | 4 hours | 555.6 Mbps | 622.2 Mbps | | 1 hour | 2.22 Gbps | 2.49 Gbps |
At 104 Mbps, the modeled one-way duration is 23 h 56 m. At 40 Mbps, it is 62 h 13 m—more than two and a half days. At symmetrical 1 Gbps, it is 2 h 29 m, leaving substantial calendar margin if the rate is actually sustained.
TB and TiB are different workloads
This article uses decimal units because the current calculator defines 1 TB as 1,000 GB. One TiB is 2^40 bytes, approximately 1.0995 TB. A workflow that produces one TiB per day moves about 10% more data than one TB per day.
Confirm the unit used by the camera, storage system, operating system, and transfer report. Windows may display binary capacity while labeling it “GB,” which can make a correctly measured package appear inconsistent with a drive vendor's decimal label.
Upload usually sets the daily ceiling
An internet plan's largest number is often download speed. A “gigabit” cable plan with 1 Gbps down and 40 Mbps up cannot send 1 TB per day continuously under this model, even though it can receive the same amount much faster.
The FCC's Thirteenth Measuring Broadband America report offers historical U.S. context, not current universal performance. Its panel used selected September–October 2022 measurement dates and documented upload asymmetry outside fiber. Separately, the FCC adopted 100/20 Mbps as a U.S. fixed-broadband policy benchmark in March 2024, using December 2022 deployment data. That benchmark is not measured throughput or a transfer guarantee. A 20 Mbps upload takes about 124 h 27 m in the calculator model.
Measure upload during the same hours the daily job will run. An idle midday speed test may not represent an overnight office backup, VPN path, or shared production network.
Account for the recipient side
If the workflow stages data in a service, the sender's upload and the recipient's download are sequential for the first complete copy. One TB uploaded at 500 Mbps and downloaded at 1 Gbps takes 7 h 28 m under the current model.
Additional recipients increase aggregate download volume. Each recipient still has an individual endpoint rate, while the service or direct sender must supply all copies. For three recipients, plan 3 TB of outbound delivery in addition to the original upload. Confirm whether repeated downloads, temporary storage, or internet egress affect cost.
Find the bottleneck beyond the circuit
Bandwidth is only useful when the rest of the path can consume it.
- Storage: the source must read and destination must write at the required rate.
- File count: hundreds of thousands of small files create more metadata and request work than a few large files.
- Latency and buffers: long high-rate paths need enough in-flight data to fill the connection.
- Packet loss: retransmission recovery can sharply reduce sustained throughput.
- Shared traffic: calls, backups, cloud sync, and other uploads consume the same capacity.
- Quotas and allowances: an ISP or provider may limit monthly data even when link speed is sufficient.
- Cloud ceilings: account, request, object, and regional targets are separate limits.
Azure documents standard storage-account ingress targets of 60 Gbps in listed regions and 25 Gbps elsewhere for the referenced account types. Those are high-end service targets scoped by region and configuration, not achieved throughput or a TeraAirlift speed claim.
Design a repeatable daily workflow
If 1 TB arrives throughout the day, stage completed camera cards, scan tiles, or project packages incrementally instead of waiting for one nightly batch. Reserve bandwidth with quality-of-service policy where appropriate, prevent workstation sleep, and monitor the actual sustained rate.
Define a cutoff: if the queue has not reached a stated percentage by a stated time, escalate, reduce the day's selected payload, extend the window, use another circuit, or ship an outlier. Keep a manifest and verify the destination before deleting the source. Daily capacity planning is an operating process, not just division.
Where TeraAirlift fits
TeraAirlift is a Windows-first desktop operations console for recurring large-file handoffs. Queue, progress and ETA, cancellation, retry-friendly operations, history, diagnostics, recipient-controlled delivery, and SHA-256 verification help operators answer whether last night's job completed. They do not promise a throughput or replace circuit planning. Schedule a demo after modeling the endpoints.
