How to share large files
Which hosts take the biggest files — and why the number a host advertises is not always the number you get.
Updated
The advertised limit is a ceiling, not a promise
- A host's free tier is often smaller than the number on its homepage. Connecting your own account there usually raises it — and then the real limit is whatever your account allows.
- Cloud accounts are capped by space, not by file size. A drive with 15 GB free will not take a 20 GB file no matter what the API allows.
- Some hosts only accept video. A large archive is refused there for its type, not its size.
Biggest published limits
See all hosts49 more hosts do not publish a size limit, so they are not listed here. We do not guess.
Why the number here may not be your number
The sizes in the list above are not copied from host homepages. Each one starts as the host's stated limit and is then corrected by what we have actually seen: the biggest file that host accepted from us, and the smallest one it refused for size. If a host says 10 GB but turns away a few hundred megabytes, the list shows what it really took, not what it promised.
Those measurements come from uploads made without a personal account — as a guest, or with the account we run on that host. That is why the list describes the free path. It is the floor, not the ceiling.
If you connect your own account on a host, its limit can change in either direction. A paid plan on many hosts takes far bigger files than the free tier; when your account reports its own limit, we use that number for you instead of the one listed here. When your account does not report a limit, we do not apply the guest number to it — we treat it as unknown and let the host decide.
One thing your account cannot lift: a size we have seen refused on the way to the host itself. Some hosts sit behind a front end that caps a single request regardless of plan. When we have measured that wall, we stop sending files above it to everyone. A measured refusal is kept for 30 days and then tried again, so a host that raises its limit is not locked out forever.
Why big uploads fail, and what helps
A large upload is mostly a test of time. The longer a transfer runs, the more chances there are for something ordinary to interrupt it — a laptop going to sleep, Wi-Fi dropping, a tab closed by mistake.
Your connection drops. Files are sent to us in parts, and the server keeps count of every byte it has received. If the connection goes away mid-upload, the upload is paused rather than cancelled. When you are back online it resumes on its own, from the byte the server last confirmed — not from zero. You can also press Resume.
You close the tab. This one cannot be recovered: the browser only has access to the file while the page is open. While a file is still uploading, the page asks before you leave. Once the file has reached us, closing the tab is fine — sending it on to the hosts happens on our servers and finishes without you.
The host refuses it. Some refusals are temporary: a timeout, a busy server, a rate limit. Those are retried automatically. Others are not worth retrying. A file that is too large for a host, or the wrong type, is skipped before anything is sent, and you are told which host and why. And when a host refuses a file well below the size it is known to accept, we say so plainly: that usually points to a quota or a restriction on the host account, not to your file.
How long hosts keep a large file
Where a host publishes how long it keeps files, the list shows it as "kept ~N days". Treat that as the host's own policy, not a guarantee and not something we measure. 50 of the 130 hosts in the catalogue publish a figure at all.
The number also hides an important detail: what the clock counts from. On many hosts the countdown restarts every time the file is downloaded, so a link people keep using can stay up much longer than the number suggests, while a file nobody opens disappears on schedule. Other hosts count from the day of upload, whatever happens next. If a large file has to stay available for a long time, a host that counts from the last download — and a link people actually use — is the safer combination.
Because these figures are estimates, we do not declare a copy dead when its time is up. The share page shows what we have actually checked: whether each copy answered our last check, when that was, and which copies we could not check. Those checks run when someone opens the page.
Your share page has its own lifetime, separate from the hosts'. Guest links can be kept for up to 60 days, and a link nobody opens for 180 days is closed.
Video-only hosts
33 hosts in the catalogue accept only video. Several of them have some of the largest limits in the list above, which is why they show up there — but a large archive or disk image will be refused by every one of them, whatever its size. Some go further and accept only certain formats; where the catalogue says so, the card shows it, for example "MP4 only".
When you send a file to several hosts at once, this is handled for you: hosts that will not take the file's type are skipped before the upload goes out, with the reason shown. If we cannot tell what type a file is, it is not sent to hosts that restrict types at all — guessing would just produce a failed copy.
For anything that is not a video, look for cards without "video only".
Sending one big file to several hosts
You upload once (up to 5.00 GB per file; 100.0 MB when fetched from a URL that does not report the file size) and we push it out to the hosts you pick. Any host that will not take the file for its size or type is skipped, and you are told which ones and why — instead of finding out from a broken link later. All hosts and limits · Try it
Related guides
- Upload to multiple file hosts at once — what sending one file to many hosts costs, what it does not solve, and which hosts work best.
- File hosting without registration — the hosts that take uploads with no account, with their limits and how long they keep files.
- All supported hosts — the full catalogue, including the hosts that do not publish a size limit.
- Provider status — upload success rates for every host, measured from real uploads, bad numbers included.
- API docs — upload in parts, resume after a dropped connection and mirror to many hosts from your own scripts.