File Hosting & Sharing

File Sharing

Definition

File sharing is handing a file to someone else without handing over a physical copy. In practice it takes one of three shapes: an attachment, which duplicates the file into their mailbox; a shareable link to a copy you host, which they fetch when they are ready; or an invitation to a folder, which ties access to their account. Links have largely won for anything above a few megabytes, because attachments hit mail server limits around 25 MB and folder invitations demand that the recipient has, and signs into, an account they may not want. The distinguishing question in sharing is never where the bytes live but who may read them, for how long, and whether you can take that back afterwards. Access control, expiry and revocation are what separate sharing from simply publishing.

Why It Matters

Sharing failures are quiet ones. A link forwarded out of a thread keeps working for whoever it was forwarded to, and nobody tells you. A 60 MB video attached to an email may be stripped by the recipient's mail server, leaving you certain you sent it and them certain you did not. Put concretely, a link with a seven-day expiry and a password turns an open-ended exposure into a bounded one, and lets you answer the question of who could have opened this with something better than a shrug. The cost of getting it right is about thirty seconds at upload time.

How It Works

You upload once, and the host gives the file an address. Sharing then layers conditions in front of that address, all of them evaluated before any bytes are released: a password-protected link that must be satisfied first, an expiring link that answers 410 Gone once its timestamp passes, a single-use token that is burned on first fetch, or a form that collects a name and an email before the file appears. Revoking access means deleting the object or invalidating the link — it does not reach the copies already downloaded, because once the bytes are on someone's disk they are theirs. Access logs close the loop by recording each successful fetch with a time and a country, so you can see that the contract was opened twice rather than guess at it.

Real-World Example

A solicitor needs a 12 MB signed contract to reach one client and nobody else. She uploads it to 99helpers as client-brookes-contract, sets a password and a fourteen-day window, then sends the address by email and the password by phone. The client opens it twice, and the analytics show both fetches came from one city on the same afternoon. On day fifteen the address stops serving, so the forwarded copy of that email sitting in somebody's archive is no longer a way in.

Common Mistakes

  • Sending the link and the password in the same message — anyone who reads the message has both, which is no safer than sending the link on its own
  • Believing revocation recalls the file — killing a link stops new downloads, it does nothing about copies already saved elsewhere
  • Using one open link where each recipient needed their own — with no record of who opened what, a leak cannot be traced back to anybody

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →