How to send a 20GB file: 9 steps that actually work (no compression)

If you’re trying to figure out how to send a 20GB file, the honest answer is: don’t fight email, and don’t waste time re-compressing something that’s already compressed (like H.264, HEVC, ProRes, ZIP, or RAR). Use a transfer link or cloud link that can handle large single files, and follow a workflow that prevents the two usual failures: unstable uploads and recipient friction.

Below is a step-by-step method you can use today, whether you’re sending a 20GB final export to a client, a folder of RAWs to a retoucher, or a project archive to a collaborator.

Before you start: pick the simplest “20GB-safe” method

At 20GB, you typically have three realistic options:

• A dedicated file-transfer link (fast, client-friendly, built for one-off delivery).
• Cloud storage sharing (good if you already store the files there and need ongoing access).
• Specialist delivery (best when you’re sending massive media daily and need acceleration, verification, or automation).

How to send a 20GB file in 9 steps

1. Confirm you’re really sending one 20GB file (or a folder)

   “20GB file” can mean a single .mov, or a folder that totals 20GB. That changes your prep:

   • Single file: keep it as-is. Re-zipping won’t shrink most video and can add hours.
   • Folder: bundle it into one archive (ZIP or RAR) so the recipient downloads one thing, not 4,000 tiny files.

   For folders, pick a format your recipient can open easily. ZIP is universal, RAR can be better for splitting (later step), but not everyone has an extractor preinstalled.

2. Do a 15-second “recipient sanity check”

   It’s very common to deliver a huge file successfully… and then the client tries to download it on a phone over mobile data.

   • If your recipient is likely on mobile, warn them: “Download on desktop, ideally on Wi‑Fi, needs ~25GB free space.”
   • If they’re non-technical, prefer a simple transfer link with minimal steps.

   This one message saves a surprising number of “it doesn’t work” follow-ups.

3. Choose a transfer method that can handle 20GB cleanly

   Email attachments are out (most providers cap attachments far below this, and even “send via Drive” flows often create permission headaches). For one-off delivery, a transfer link is usually fastest for both sides.

   If you’re using LetsSend specifically: Free allows up to 5GB per transfer (as of October 2026). For a 20GB file, you’ll need Pro (up to 200GB per transfer). You can compare Free and Pro before you commit.

4. Stabilise your upload connection (this matters more than the service)

   A lived truth from sending big edits on the road: the upload usually fails because of the network, not because the file is “too big”. Hotel Wi‑Fi that drops for three seconds can ruin a long upload.

   • Use wired ethernet if you can.
   • If on Wi‑Fi, sit close to the router and avoid public “captive portal” networks (the ones that kick you out).
   • Pause other heavy uploads (cloud sync, system updates).
   • Keep your laptop awake. Don’t let it sleep mid-upload.

   Many modern uploaders use multipart or chunked uploads (sending the file in pieces) so they can resume more gracefully, but an unstable connection can still break the session. Give yourself the best chance.

5. Prep the file so it downloads cleanly

   Do these quick checks:

   • Name it clearly: Client_Project_Final_v03_4K.mov beats final_final2.mov.
   • Check free space: keep at least 1.5x the file size free on the sending device during packaging and upload.
   • Export a checksum (optional but pro): if you and the recipient know how, generate a SHA-256 hash so they can verify integrity. This is useful when the stakes are high.

   If you’re sending video, do not convert codecs “just to make it smaller” unless you’ve agreed on a delivery spec. Re-encoding can add hours and can degrade quality.

6. Upload with a transfer link, then set the right controls

   When you create a transfer link, set controls that match the job:

   • Expiry: pick an expiry that covers the review window, then ends automatically.
   • Password (recommended for client work): share the password in a separate message channel.
   • Download limit (if available): useful when you want the link to stop after the client has it.

   LetsSend links expire automatically, can be password protected, and Pro links can carry a download limit. You can see these controls on see all features.

   Technical note (because it affects reliability): LetsSend uploads straight from your browser to encrypted object storage, rather than relaying through a middle server. In practice, that means fewer moving parts and a more direct path for large transfers.

7. Send the link like a pro (and prevent support emails)

   Don’t just send the URL. Send a short “receipt” message so the recipient knows what to do:

   • What it is: “Final 4K export (20GB)”
   • What they need: “Download on desktop, ideally Wi‑Fi, needs ~25GB free space.”
   • Expiry: “Link expires Friday.”
   • Password note: “Password sent in the next message.”

   This reduces the back-and-forth more than any feature.

8. If the upload fails: use this quick triage

   When a 20GB upload fails, don’t immediately restart and hope. Try this in order:

   • Switch networks (hotspot, different Wi‑Fi, ethernet). If it fails at a different point each time, it’s usually the connection.
   • Try a different browser (Chrome, Edge, Safari). Browser extensions can also interfere, so try an incognito/private window.
   • Reduce local contention: pause Dropbox/Drive sync while uploading.
   • Send overnight when networks are quieter, if your deadline allows.

   If you’re using LetsSend and you get stuck, the fastest next step is the visit the Help Center.

9. If you absolutely must stay on a free plan: split safely

   Sometimes you cannot use a paid plan, and you still need to deliver today. If your service caps transfers under 20GB, you can split the file, but do it in a way the recipient can recombine.

   • For archives: use a tool that creates a multi-part ZIP/RAR set (for example 4GB parts). The recipient downloads all parts, then extracts once.
   • For video: avoid splitting the .mov into chunks unless you really know what you’re doing. Many recipients will struggle to reassemble it. Prefer a folder archive split into parts.

   This works, but it increases recipient effort and increases the chance one part is missed. If client experience matters, a single-link transfer is usually worth it.

A simple “which tool should I use?” checklist

• You need the easiest client download: use a transfer link with expiry and an optional password.
• You need ongoing collaboration and shared folders: use cloud storage with clear permissions.
• You send huge media constantly: consider a specialist delivery service.

Privacy and security notes (honest version)

For client work, you want three things: encrypted transport (HTTPS), encrypted storage, and predictable retention (links expire, files get deleted).

LetsSend is encrypted in transit (HTTPS) and at rest in storage, and expired transfers are deleted rather than quietly archived. It is not end-to-end encrypted, so don’t use it as a zero-knowledge vault. For the details, see how LetsSend protects your files and how we handle your data.

When LetsSend is a good fit (and when it isn’t)

We build LetsSend, so here’s the straight trade-off.

• Great fit: you want a simple transfer link for a 20GB deliverable, with expiry, optional password, and minimal recipient friction.
• Not the best fit: you need end-to-end encryption, or you need a long-term synced workspace with complex role permissions and deep collaboration features.

If you want the fastest path to done, you can send a file free (Free up to 5GB per transfer, Pro up to 200GB as of October 2026). If you want to know who’s behind the advice, see the team behind LetsSend or contact us.

One last practical tip for 20GB deliveries

If you’re sending to a client who will “download once and forward to their team”, add a download limit only if you’re sure they won’t need multiple attempts. A 20GB download can fail on their side too, and re-downloading should be allowed unless you’ve planned otherwise.

If your delivery is a large video export, you may also want a dedicated workflow for codecs and client playback. Our guide on send large video files goes deeper on that side.