Skip to content

Upload to multiple file hosts at once

Why people mirror a file across several hosts, what it actually buys you, and what it does not.

Updated

A single file host is a single point of failure: accounts get closed, free files expire, and links rot. Mirroring the same file to several hosts means the link you shared keeps working when one of them stops.

One upload, not ten

Your file leaves your machine once. From there we push copies out to each host in parallel, so adding a tenth host does not cost you a tenth upload.

One link to share

You get a single page listing every copy. Sending that beats pasting ten links, and it stays correct when one of them dies.

You see which copies are alive

Each mirror is rechecked when someone opens your share page, so a dead link shows as dead instead of looking fine until someone clicks it.

What mirroring does not solve

When an upload counts as done

Sending one file to many hosts rarely ends with every host saying yes. So instead of a single pass/fail, each upload ends in one of three states.

Completed means every host that could take the file did. Partially completed means at least one copy is live but some hosts did not accept it. Failed means not a single copy made it.

Hosts that turned the file down on purpose — a type they do not accept, a file they refuse — are not counted against you. Out of ten hosts, if one refuses the format and the other nine succeed, the upload reads as completed, and the refusal stays visible next to that host's name with its reason.

Copies appear on your share page one by one, as each host confirms it. Visitors only see copies that actually arrived; hosts still working or ones that gave up are not shown to them. While the upload runs, your own view lists every host with its current state: queued, uploading, verifying, retrying, waiting for the host, succeeded, not accepted, or failed with the reason.

From the website, one working copy is enough for the share link to go out. Through the API you can ask for more before the job counts as a success.

Why a host gets skipped

Some hosts are left out before anything is sent. That is deliberate: sending a file to a host that is certain to refuse it only produces a failed copy and a wasted transfer. Each skip comes with a reason, and the rest of the hosts go ahead as normal.

The common reasons:

  • Too large for that host. The size compared is the one we have measured for that host, not only the number on its homepage.
  • Wrong file type. Video-only hosts skip everything that is not a video, and some take only specific formats.
  • It needs an account. As a guest, hosts that only work with your own key are skipped.
  • Temporarily off. A host in maintenance is skipped until it is back.
  • Already tried. Asking again for a host that already failed this file does not start a new attempt.

If none of the hosts you picked can take the file, nothing is sent and you are told why for each one.

Hosts that pass this check can still refuse at upload time. Temporary problems such as timeouts or rate limits are retried automatically; a refusal that will not change is recorded with the host's own message. A daily quota on the host account, for example, is shown as exactly that, not as a broken connection.

Your account on a host, or ours

There are three ways a copy can reach a host, and the catalogue shows which one applies.

As a guest of the host. 40 hosts accept an anonymous upload, so the file goes there with no key at all.

Through your own account. The other 90 hosts need you to connect your own key or sign-in on the Connections page. The copy then sits in your account on that host, under that host's rules for your plan. That often means bigger files: when your account reports its own size limit, we use it instead of the free one. It also means the host's quotas are yours — a daily API limit on your account stops uploads there until it resets.

Connecting an account is optional for the hosts that work without one. Most of those also accept your own key, if you would rather the copies be yours.

How many hosts to pick

A single upload can reach many hosts — the current maximum is shown below. More is not automatically better.

Every extra host adds a copy that can outlive the others, but it also adds a copy that needs to be checked and a row on your share page. Two things matter more than the count:

  • Different kinds of hosts. Several hosts that delete files after a short idle period will tend to disappear around the same time. Mixing in hosts that publish a longer keep period, and hosts where the clock restarts on every download, spreads the risk.
  • Hosts that work today. The status page shows each host's measured success rate. A host that fails most uploads adds noise, not safety.

For a file people will download soon, a handful of reliable hosts is enough. For something that needs to stay reachable for months, pick more, and expect some copies to drop out along the way — the share page will show which ones.

Doing it from a script

Everything above is also available through the API, with an API key from your account.

A script uploads the file in parts, then starts the distribution with the list of hosts it wants. The reply says how many hosts were actually queued and lists the skipped ones with their reasons, so a script can tell at once whether the plan changed. A host that cannot take the file is reported as skipped, not as a failure.

You can also set how many hosts must accept the file before the job counts as a success, and give the share page a password or an end date in the same call. To find out when it is done, either poll the job or register a webhook: there are events for the whole upload (completed, partially completed, failed) and for each host that accepts or gives up on the file.

The API docs have the full flow, with examples in curl, Python and JavaScript.

Where this stands right now

130 hosts are supported and 40 of them take a file with no account at all. One file can go to up to 50 of them in a single upload, up to 5.00 GB per file; 100.0 MB when fetched from a URL that does not report the file size. See the full list · Measured success rates · Try it

  • File hosting without registration — the hosts that take uploads with no account, with their limits and how long they keep files.
  • How to share large files — which hosts take the biggest files, and why the published limit is not always the one you get.
  • 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.