To send a 1 TB file, first measure the sender's upload speed, calculate the one-way time, and choose a workflow that can resume after interruption without depending on one long-lived browser tab. General cloud storage can work when its per-file limit and desktop sync client fit. Purpose-built transfer platforms simplify delivery. Object storage plus a CLI or desktop client offers more control. If the online estimate misses the deadline, use physical media.
Under the current calculator's 12% planning-overhead assumption, one decimal terabyte takes about 2 hours 29 minutes at 1 Gbps, 4 hours 59 minutes at 500 Mbps, or 24 hours 53 minutes at 100 Mbps, one direction. The 12% allowance is a modeling choice, not a physical constant or guarantee. Upload speed—not the advertised download speed—is usually the first constraint to check.
General cloud storage
Cloud drives are strongest when the dataset belongs in long-lived shared storage and everyone already has access. At 1 TB, use the provider's desktop sync client when possible. A browser upload does not always fail, but a tab, session, workstation sleep event, or connection change has more time to interrupt a transfer that runs for hours or days.
Official limits checked August 10, 2026 illustrate why file layout matters:
- Microsoft documents a 250 GB maximum individual file size for OneDrive and SharePoint, including files inside ZIP archives, and recommends the sync app rather than website upload for files larger than a few gigabytes. A 1 TB folder can fit subject to quota, but one 1 TB file cannot.
- Google Drive documents a 5 TB maximum for non-Google-format files, subject to available storage.
- Dropbox documents a 2 TB maximum file size and warns that dropbox.com uploads above 375 GB may time out, recommending its desktop app or API instead.
These are per-file ceilings, not promises about account quota, transfer time, or plan eligibility. Verify the current official page and your account before staging the delivery.
Purpose-built transfer platforms
This category is designed around delivery rather than permanent shared storage: stage a package, assign access, send or surface it to recipients, monitor it, and let it expire under a retention policy. It can be the practical choice when the recipient should not navigate a shared drive or when delivery status matters.
As checked August 10, 2026, WeTransfer documents up to 1 TB per transfer on Ultimate. That ceiling is plan- and transfer-specific. MASV publishes 15 GB free per month, then $0.25/GB pay as you go, plus $0.07/GB/month after five free storage days per file. Those are the vendors' current published terms, not timeless prices or a recommendation. Check transfer limits, retention, recipient requirements, and the cost for every intended download.
Object storage plus a CLI or desktop client
Azure Blob Storage or Amazon S3 paired with a resumable CLI or desktop client gives a technical team high ceilings, parallel requests, explicit credentials, and control over retention. The tradeoff is setup: someone must configure the storage account, access policy, client, expiry, and recipient instructions.
Microsoft documents an Azure block blob ceiling of about 190.7 TiB, based on 50,000 blocks of up to 4,000 MiB. AWS documents up to 5 GB with a single PUT, 160 GB through the S3 console, and 50 TB through multipart upload. A 1 TB object therefore needs multipart upload in S3 rather than the console. These object ceilings do not override storage-account, request-rate, permission, or egress constraints.
Parallelism can help fill a fast path, but it needs testing. Microsoft's AzCopy guidance recommends benchmarking before tuning concurrency. More requests do not guarantee more speed.
Physical media
Copying the data to a drive and shipping it is valid when measured bandwidth makes online delivery impractical. At exactly 1 TB it is often slower than a good online path, but a weak upload, a hard deadline, or an offline handling requirement can reverse that result. Include the copy onto the drive, courier cutoff and transit, copy-off time, and verification—not just the shipping tier. Compare the complete paths in shipping a hard drive versus transferring files online.
Decide before you start
Check these items against the actual job:
- measured sender upload and recipient download speeds;
- time for every required upload and download leg;
- interruption recovery or resumability;
- per-file, per-transfer, account, and plan limits;
- whether recipients need accounts, apps, or permissions;
- retention period and what happens when it expires;
- number of recipients and whether each download adds cost;
- integrity verification, access control, and security policy;
- whether a browser tab or session is in the critical path.
Then run the delivery in a deliberate sequence:
- Inventory and measure: confirm total bytes, largest file, file count, available source copy, upload speed, and destination speed.
- Calculate: estimate each network leg and add realistic operational margin. The published 1 TB transfer-time guide explains the model.
- Choose: select cloud storage, a transfer platform, object storage, or physical media from the constraints above.
- Stage: confirm quota, permissions, retention, recipient identity, destination capacity, and a recovery copy.
- Send and monitor: keep the source available and watch progress, errors, ETA, and interruptions.
- Verify: compare sizes or cryptographic hashes rather than assuming “complete” means intact.
- Confirm access and receipt: have the intended recipient open or ingest the files before deleting the staged copy.
Where TeraAirlift fits
TeraAirlift is one purpose-built option: a Windows desktop transfer operations console with queue, progress, ETA, retry-friendly operations, linkless delivery to authenticated recipients, SHA-256 verification, history, and activity/error logging. It improves visibility and controlled handoff; it does not guarantee speed or replace archival storage. Review the security model or download the Windows client; Mac is coming soon.
The same decision process applies to post-production delivery, LiDAR data transfer, and construction file transfer.
Sources
- Microsoft — Restrictions and limitations in OneDrive and SharePoint
- Google — Files you can store in Google Drive
- Dropbox — What is the Dropbox file size limit?
- WeTransfer — Plan limits
- MASV — Pricing
- Microsoft — Blob Storage scalability and performance targets
- AWS — Uploading objects to Amazon S3
- Microsoft — Optimize AzCopy performance
