Send 5GB free: transfer links vs cloud storage (what to use and when)

If you need to send 5GB free, you have two realistic choices: a transfer link (upload once, send a download link) or cloud storage sharing (upload into Drive/Dropbox/OneDrive, then share access). The best option depends on one thing: are you delivering a file (final export to a client), or collaborating on a file (ongoing edits and versions)?

This guide compares the two approaches, shows what to pick in common creative scenarios (video exports, RAW folders, project zips), and includes a quick checklist so you can send the file tonight without a second attempt.

Transfer link vs cloud storage: the simplest rule

Use a transfer link when your job is “Here’s the file, please download it”, especially for client delivery. You upload once, send one link, and it expires so it does not live forever in someone’s inbox.

Use cloud storage sharing when your job is “We will keep working on this”. Shared folders, version history, and ongoing permissions are what Drive/Dropbox/OneDrive are built for.

Fast answer: what to use to send 5GB free (by situation)

• You are delivering a final export to a client tonight: use a transfer link with expiry and (if needed) a password.
• You are sending to multiple reviewers: transfer link (one link), plus a clear file name and a ReadMe.
• You and the client will both edit the files: cloud storage shared folder.
• You are sending a 5GB folder of photos or assets: either works, but transfer links avoid permission issues and “request access”.
• You have flaky Wi‑Fi: a service with resumable or multipart uploads helps. If it fails, switch networks or upload from wired internet.

Option 1: Transfer links (the “delivery” tool)

A transfer link is designed for exactly this moment: you have a large file (say a 5GB ProRes export or a zipped project folder) and email refuses to cooperate.

Why transfer links feel easier for clients

• No account hurdles: the recipient clicks and downloads. Less “What password?” and fewer “It says I need access”.
• Cleaner handoff: one link, one payload, one deadline.
• Expiry is normal: you can set expectations like “This link works for 7 days”.

How LetsSend handles a 5GB free transfer (and why it matters)

We build LetsSend, so here’s the plain, non-mystical version of how it works. Files upload straight from your browser to encrypted object storage, rather than bouncing through a middle server. In practice, that can mean fewer moving parts and less waiting around for a second hop.

As of September 2026, LetsSend Free includes:

• Up to 5GB per transfer
• 5GB daily allowance (and up to 10 files per day)
• Links expire after 7 days
• Password protection

What we do not do: we do not sell your files or contact details, and expired transfers are deleted rather than quietly archived. If you want to read the details, see how we handle your data, and if you want to know who is behind the advice, meet the team behind LetsSend.

When transfer links are the wrong tool

• You need long-term hosting: a 7-day expiry is great for delivery, not for an evergreen asset library.
• You need collaborative editing: transfer links are not a shared workspace.
• You need strict enterprise controls: some teams need SSO, audited access, and retention policies. A dedicated enterprise platform can be a better fit.

Option 2: Cloud storage share links (the “collaboration” tool)

Cloud storage is brilliant when the file is part of an ongoing relationship: you will keep adding versions, you want the same link to keep working, or multiple people need to drop files into the same place.

Where cloud storage wins

• Shared folders for back-and-forth collaboration
• Version history (especially helpful for documents and design files)
• Longer-lived links when you need an asset to remain available

The annoying real-world problems (and how to avoid them)

• “Request access” loops: before you send, open the link in a private window to confirm it actually downloads without you being signed in.
• Wrong permissions: pick viewer vs editor deliberately, and avoid “anyone with the link can edit” for client work.
• Preview traps on phones: some clients open the link on mobile, see a preview, then miss the download button. Put “Download (not preview)” in your message.

Option 3: “Just zip it” (when it helps and when it wastes your time)

Compression is useful for folders (so you can deliver one item), but it is often pointless for already-compressed media:

• Video exports (H.264, H.265, ProRes) typically do not shrink much with zipping.
• JPEGs rarely shrink meaningfully when zipped.
• RAW photo folders might zip a bit, but the main win is “single package” delivery.

If your only reason to compress is “maybe it will fit in email”, it will not. Email attachment limits are far below 5GB.

Send 5GB free in a way clients don’t mess up (a practical checklist)

This is the part most comparison posts skip. The transfer method matters, but how you package it decides whether you get the dreaded reply: “It didn’t work, can you resend?”

1) Name it like a deliverable, not like your desktop

• Good: ClientName_Project_Final_v03_4K.mp4
• Bad: final_final_reallyfinal2.mp4

2) Include a tiny ReadMe.txt for anything complex

One short file can prevent three emails. Include:

• What the recipient is looking at (final export, source files, alternates)
• How to use it (for example “Use the MP4 for review, ProRes is for final delivery”)
• The link expiry date (so nobody panics on day eight)

3) Use expiry on purpose

Expiry is not just security theatre. It reduces the chance a client downloads an out-of-date version months later. If you want a deeper buyer-style explanation of retention and deletion, see what happens to your files after you send them online.

4) Add a password when the content is sensitive

A password protects against a forwarded link being enough on its own. Send the password in a separate channel (for example, text message), not in the same email as the link.

5) Test the download like you are the client

Before you hit send, open your link on your phone over cellular. This catches the classic issue where everything works on your logged-in desktop, but the client sees a sign-in wall.

What about sending more than 5GB?

If your file is just over 5GB, you have three choices:

• Split the delivery into two transfers (for example, Part 1 and Part 2) if your workflow allows it.
• Use a cloud storage folder where size is limited by your available storage, not a per-transfer cap.
• Use a paid transfer plan if you do this often and want it to be boring and predictable.

On LetsSend Pro (as of September 2026), you can send up to 200GB per transfer, links can last up to 30 days, and you can add a download limit. Pricing is $12/month. You can confirm the current details on compare Free and Pro.

Quick recommendation (honest, not universal)

• Pick a transfer link if your main goal is one clean handoff, especially to a non-technical client.
• Pick cloud storage if this is an ongoing shared workspace with versions and shared folders.
• Pick physical delivery if you are moving hundreds of gigabytes and your internet makes you cry.

If you want the shortest path to done for a one-off delivery, you can send a file free with a 5GB cap per transfer on the Free plan. If you want to understand all the link controls (passwords, expiry, download limits), you can see all features. And if anything behaves oddly on your network, the Help Center is where we keep the step-by-step fixes.

A note on sign-in and privacy (because it affects real work)

Account friction matters when you are trying to deliver work on a deadline. LetsSend accounts are passwordless (you sign in with a short code emailed to you), so there is no password to leak. That does not make you invincible, but it removes one common failure mode: reused passwords.

If you have questions about a specific edge case (for example, a client’s compliance policy or whether an expired transfer is recoverable), you can contact us. We would rather answer a boring question now than watch you resend a 5GB upload later.