First identify what stopped the send. A per-file or per-transfer cap calls for a larger-capacity workflow; a rolling plan quota may call for waiting or upgrading; a retention rule may make the service unsuitable for the recipient's schedule. If the size is allowed but a long browser session is unstable, use a desktop or command-line client with recovery behavior. If the real problem is that the transfer cannot finish before the deadline, switching services will not create bandwidth—calculate the transfer window first.
Check which WeTransfer limit you reached
According to WeTransfer's linked documentation as of August 2026, Free accounts can send up to 10 transfers or 3 GB total in a rolling 30-day window, and each Free transfer can be up to 3 GB. Starter allows up to 10 transfers or 300 GB total in the same rolling window, while Teams documents unlimited transfers. WeTransfer's current official pages conflict on Ultimate: the plan-limits page describes a 1 TB per-transfer limit, while its file-size resource says Ultimate removes the per-transfer cap. This article does not choose one statement as definitive. WeTransfer's help center also does not specify a per-transfer size for Starter or Teams.
These are separate from account storage: WeTransfer documents a default of up to 2 TB for live and recoverable transfers, with Teams at up to 5 TB and extensions to 30 TB on request. The 30-day usage window is rolling, not a calendar month. Limits, wording, and plan terms can change, so check the current plan page, file-size documentation, and your account before committing to a delivery.
Calculate the transfer window before changing tools
Use measured upload bandwidth, not the advertised download speed. The current calculator models:
seconds = (bytes × 8 × 1.12) / bandwidth bps
This matches the current site calculator's 12% planning-overhead model: it multiplies theoretical payload bits by 1.12. The allowance is a planning assumption, not a standard, measured constant, or guarantee. Under that model, 100 GB takes about 15 minutes at 1 Gbps or 2 hours 29 minutes at 100 Mbps; 500 GB takes about 1 hour 15 minutes at 1 Gbps; and 1 TB takes about 2 hours 29 minutes at 1 Gbps or 24 hours 53 minutes at 100 Mbps. Add the recipient's download leg and operational margin.
Choose a practical route
Split or package the dataset. Multi-part archives can get under a per-file cap and may be reasonable for a one-off delivery. Keep an untouched source copy, use clear part names, and provide a checksum or manifest. This approach multiplies recipient steps, and one missing part can block extraction. Re-compressing already-compressed video may consume time for little reduction and can affect quality.
Use general cloud storage. A cloud drive fits when the files should remain in shared storage and everyone already has accounts and permissions. As of August 2026, Google Drive documents files up to 5 TB, Dropbox documents files up to 2 TB, and OneDrive and SharePoint document a 250 GB individual-file limit, subject to storage and plan constraints.
Use purpose-built transfer software. This category is designed for finite delivery rather than permanent collaboration: stage a package, monitor it, control access, and remove it under a retention policy. Compare per-transfer limits, total quota, recipient requirements, recovery behavior, retention, verification, and cost. Upgrading WeTransfer may be the simplest valid answer when its current limits and workflow fit. See the full WeTransfer alternative comparison for a broader operational comparison.
Use object storage with CLI or desktop tooling. Technical teams can combine object storage with multipart, parallel, or resumable tools. In official documentation consulted in August 2026, Microsoft documents Azure block blobs up to about 190.7 TiB, while AWS documents Amazon S3 multipart uploads up to 50 TB. These are platform capacity limits, not guarantees of account eligibility, throughput, completion, or delivery time. The tradeoff is ownership of credentials, access policies, retention, recipient instructions, storage cost, and egress cost.
Ship physical media. When measured bandwidth misses the deadline or the destination is disconnected, copying to a drive and using a courier can be rational. Include copy-on, carrier cutoff and transit, copy-off, verification, and the risk of loss or damage. The published guide compares shipping a hard drive with transferring files online; retain another copy throughout the shipment.
Browser versus desktop reliability
Browsers do not always fail on large uploads. However, a transfer that occupies a tab for hours or days has more exposure to session expiry, sleep, restarts, connection changes, and accidental closure. Dropbox warns that website uploads above 375 GB may time out and recommends its desktop app or API; Microsoft recommends the OneDrive sync app rather than website upload for files larger than a few gigabytes. Desktop and CLI tools are useful when they provide retry or resumability, but verify that behavior for the specific tool rather than assuming every installed client has it.
Decide with a complete checklist
Before starting, record:
- total dataset size, largest file, and file count;
- measured sender upload bandwidth and recipient download bandwidth;
- the deadline, including staging, download, and verification;
- recipient count and technical ability;
- resumability and what must restart after an interruption;
- account, application, link, identity, and permission requirements;
- retention period and deletion or recovery behavior;
- size, manifest, or cryptographic verification;
- privacy, security, location, and access-control requirements; and
- whether this is one delivery or a repeat workflow.
For a terabyte-scale job, the published 1 TB sending guide turns those checks into a delivery sequence. The same framework applies to post-production, LiDAR and reality capture, and construction.
Where TeraAirlift fits
TeraAirlift is one purpose-built option: a Windows desktop transfer operations console with queue, progress and ETA, retry-friendly operations, linkless access for authenticated recipients, SHA-256 verification, transfer history, and activity/error logging. These features support observable handoffs; they do not guarantee speed, completion, or another outcome. Review the security model or download the Windows client. Mac is coming soon.
Whichever route you choose, calculate first, preserve a recovery copy, and confirm that the intended recipient can access and verify the result before removing the source or staged delivery.
Sources
- WeTransfer — Plan limits
- WeTransfer — How big a file can you send with WeTransfer?
- Google — Files you can store in Google Drive
- Dropbox — What is the Dropbox file size limit?
- Microsoft — Restrictions and limitations in OneDrive and SharePoint
- Microsoft — Blob Storage scalability and performance targets
- AWS — Uploading objects to Amazon S3
