Skip to content
Orindle

How to Share Large Files Online: Secure Links, Permissions and Expiry

Email attachments stop working at about 25 MB. Here is what to use instead, and the four settings that decide whether the link you sent is safe.

Published 16 Nov 20265 min read
A large digital file transferring between two devices through a refined sharing link, with abstract permission and access-control indicators

Sharing a large file is easy. Sharing it *safely* is a question of four settings that most people leave at their defaults, because the defaults are chosen to reduce friction rather than exposure. This guide covers the methods, then the settings that matter more than the method.

The main ways to send a large file

MethodTypical size limitRecipient needs an accountLink can expireGood for
Email attachment~20–25 MBNoN/ADocuments and images, small teams
Cloud storage linkPlan-dependent, often very largeUsually notYesMost sharing, especially repeat or ongoing
Transfer service (upload-and-send)Often 2–5 GB on free tiersNoYesOne-off sends to someone without storage
Direct peer-to-peer transferUnlimited, both onlineNoN/ALarge one-off sends on good connections
Physical mediaDisk-dependentNoN/AArchives, offline delivery, very large volumes
Methods compared. Limits are typical rather than universal.

For almost everything, a cloud storage link is the right answer: the file is uploaded once, the link carries permissions you control, and you can revoke it later. Transfer services are better when you do not want the file to persist — they exist to move bytes and then forget. Email attachments are for things small enough that the question does not arise.

Access permissions: the decision people skip

Most sharing mistakes are permission mistakes. The four questions to answer before you send a link:

  1. Who should be able to open it?

    Anyone with the link, or only specific people? Link-sharing is convenient and means the URL is the credential — forward it and you have forwarded access. Per-person grants are stricter and survive forwarding badly, which is what you want for anything confidential.

  2. What should they be able to do?

    View, or edit? Read-only is the correct default for delivery; choose edit only when someone is genuinely collaborating. An edit link to a client is an invitation to a version-conflict problem neither of you asked for.

  3. For how long?

    An expiry turns a permanent decision into a temporary one. Project files, contracts and invoices rarely need to be accessible in a year, and an expiring link means a leaked URL stops being useful.

  4. Can you take it back?

    Revocation must actually cut off access, not just hide the link. With signed URLs that expire, revoking a grant stops new links from being issued; a link already downloaded cannot be recalled, which is a property of the internet rather than of any provider.

Expiry and revocation, and what they cannot do

Expiry is the cheapest security control available and the least used. A link that expires in seven days means a URL pasted into the wrong chat window has a bounded problem. Revocation handles the case where you noticed sooner.

It is worth being precise about the limit of both. Once someone has opened a file, they have a copy. Revoking access stops future access; it does not un-share what was already downloaded. This is why expiry and permission level matter more than revocation — they decide what can happen before it happens.

Common security mistakes

  • Sending an edit link when view is enough. Recipients change things by accident, and now there are two versions nobody can reconcile.
  • Links with no expiry for permanent projects. A URL created for a 2023 invoice is still live in 2026 because nobody revisited it.
  • Sharing a parent folder. Permissions cascade. Sharing the folder above the one you meant can expose everything beside it.
  • Putting sensitive data in the filename. Filenames can appear in previews, notifications and mail subjects. "Contract_Acme_Layoffs.pdf" is a disclosure before the file is even opened.
  • Forwarding a link instead of inviting a person. Once a link is out, you cannot tell who has it or revoke it for one person.
  • Assuming a private link cannot be found. Links get pasted into tickets, shared in group chats, and occasionally indexed. Treat a link as public unless it requires authentication.

A practical process for sending a file

  1. Decide whether it should be a file or a folder

    One deliverable: a file link. A set the recipient needs to browse or extend: a folder, with the narrowest permission that works.

  2. Upload, then set the permission

    In Orindle, open the share dialog on the file or folder. You can grant access to a specific email address, or create a link with a permission level and an expiry in days.

  3. Set an expiry that matches the project

    A day for something urgent, a week for a delivery, thirty days for an ongoing collaboration. If the work continues, a fresh link is a minute's work.

  4. Send the link, and the context, separately

    Where possible send the link by one channel and the password or context by another. For a confidential document this halves the exposure if one channel leaks.

  5. Revoke when done

    The help article on revoking a shared link covers the steps. Doing it at project close is the habit that keeps the number of live links small.

What Orindle's sharing actually offers

Being specific about this matters more than describing sharing in general terms, because a feature list is a promise. Orindle currently supports:

  • Per-person grants on a file, with a permission level, revocable individually.
  • Share links with a permission level and an expiry expressed in days.
  • Short-lived signed download URLs, so a file's location is not a permanent address and expires quickly.
  • Server-side authorisation on every request, backed by database row-level security, so a modified client cannot read rows it should not reach.

If your question is closer to whether any of this is safe at all, is cloud storage safe covers encryption, account security and where the responsibility actually sits.

Further reading

Orindle — How to share a link

Steps for the flow described above.

OWASP — Insecure direct object reference prevention

Why a link must be authorised server-side rather than trusted because it is hard to guess.

Frequently asked questions

What is the maximum email attachment size?
Commonly around 20–25 MB across major providers, though the exact figure varies and some corporate mail servers are stricter. Anything above that needs a link instead of an attachment.
Are share links safe?
A link with no expiry, no password and public access is a public URL — anyone who finds it can read the file, and it may be indexed or forwarded. Links are as safe as the four settings behind them: who can access, what they can do, whether a password is required, and when it stops working.
What Orindle sharing controls exist today?
Per-person grants with a permission level, and share links with a permission level and an expiry in days, which can be revoked at any time. Downloads are short-lived signed URLs, so no permanent public address to a file exists. Password-protected links are not currently available.
Should I send a file or a link to a folder?
A link to a file for one-off delivery — it is clear what is being shared. A folder when the recipient needs to browse or add things, with the permission level set to match: read-only unless they genuinely need to edit.

Written and reviewed by the Orindle team. This article is editorial content published by Orindle, which sells cloud storage. Where a competitor is discussed, the figures come from the provider's own published pages and are dated in the text. Prices and allowances change; re-check before relying on them.

All articles