Large files that survive a bad connection
A normal upload has to arrive in one unbroken request. Lose the connection at ninety per cent and there is nothing to do but start again. Here the file is sent in parts, each acknowledged on its own, so an interruption costs one part rather than the whole transfer.
- An interrupted upload continues from where it stopped
- Pause on purpose and pick it up later — even after closing the tab
- Parts that fail are retried on their own, without your attention
- Up to 1 GB on Pro, unlimited on Business
Upload a file
Large files are sent in parts automatically. Nothing to switch on.
Drop your file here, or click to browse
Supports all major formats
How a resumable upload works
- 01
The upload is announced first
Before a single byte moves, the file name, its size and the format you want are sent ahead. That is when the size is checked against your plan — so a file that is too large is refused in a moment rather than after you have waited for it to transfer.
- 02
The file is sent in parts
The file is cut into parts of about 8 MB, and each one is confirmed as it arrives. A part that fails is the only thing that has to be sent again. Very large files use bigger parts so the count stays within the ten thousand the storage service allows.
- 03
An interruption is not a restart
The parts already stored are remembered on the server, not just in your browser. When the upload continues it asks what arrived, and sends only what is missing. Closing the tab is not different from losing the connection.
- 04
The parts become one file
When the last part is in, the storage service joins them itself — the file is never sent twice or reassembled through your connection. From that point it is an ordinary conversion, with the same queue, the same limits and the same automatic deletion.
What this does and does not do
It does not make the upload faster. The same bytes travel the same connection; what changes is what an interruption costs. On a stable connection you will not notice the difference, which is the intention.
A part that fails is retried by itself, with a growing pause between attempts. A refusal is not retried — if the server says the file is too large for your plan, sending it again cannot change that answer.
An upload has twenty-four hours to finish. Parts of an upload that is never completed are discarded, so an abandoned transfer does not quietly hold storage.
Size limits are the same as any other upload: 50 MB on the free plan, 200 MB on Starter, 1 GB on Pro, and no practical limit on Business. Results are deleted automatically — after 24 hours on the free plan, after 7 days on paid plans.
When it matters
Video on a home connection
A film that takes twenty minutes to send is twenty minutes during which anything can go wrong. Losing the last part costs seconds instead of starting the twenty minutes again.
Working on mobile data
Signal that comes and goes turns a single-shot upload into a coin toss. Parts wait for the connection to return rather than failing the whole file.
Uploading while doing something else
Pause deliberately when you need the bandwidth for a call, then continue afterwards from the same place.
Large scans and archives
A long scanned document or a big archive is exactly the size where a failed upload is most expensive and most likely.
Questions
Do I have to turn this on?
No. Large files are sent in parts automatically, and small ones are not — splitting a two-megabyte file would add work without protecting anything worth protecting.
Can I close the tab and come back?
Yes, within twenty-four hours. Which parts arrived is recorded on the server, and your browser remembers which upload was yours, so returning to the page continues rather than restarts. After twenty-four hours the parts are discarded and the upload begins again.
Does pausing lose the parts already sent?
No. Pausing stops after the part in flight finishes, and everything already stored stays stored. Resuming sends only what is still missing.
Is it faster than a normal upload?
No, and it does not claim to be. The same bytes cross the same connection at the same speed. What changes is the cost of an interruption: one part instead of the entire file.
What is the largest file I can send?
The limit is your plan's, not the upload method's: 50 MB free, 200 MB on Starter, 1 GB on Pro, and no practical limit on Business. The size is checked before the transfer starts, so you are told immediately rather than at the end.
Is a resumed upload treated differently once it finishes?
Not in any way. It becomes the same kind of conversion as a direct upload, in the same queue, under the same limits, with the same automatic deletion — 24 hours on the free plan, 7 days on paid plans.