Dropbox file transfer limits for sending to people without Dropbox (and the best alternatives)

You searched for Dropbox file transfer limits because you are trying to get a large file to someone who does not have Dropbox, and you want it to work the first time. The practical answer is: Dropbox can send files to non-Dropbox users using Dropbox Transfer, but the limits that matter are usually transfer size, link expiry, and how much friction your recipient hits (sign-in prompts, “request access” confusion, or a link that quietly expires before the client downloads).

Below is a clear comparison of Dropbox Transfer versus other common ways to send to clients and collaborators who do not have accounts. Where competitor limits vary by plan or change over time, I call that out so you can verify before you promise a deadline.

Dropbox Transfer vs Dropbox shared links: which one you actually mean

Most “Dropbox limit” frustration comes from mixing up two different Dropbox behaviours:

• Dropbox shared links are for collaboration. You share a file or folder that lives in your Dropbox. Great when you want ongoing updates, comments, or a living folder.
• Dropbox Transfer is closer to WeTransfer. It sends a copy of files so the recipient can download, usually without needing a Dropbox account.

If your goal is “deliver this export tonight and be done”, you usually want Transfer, not a shared folder that triggers access requests at 11pm.

Dropbox file transfer limits that matter when the recipient has no Dropbox

Dropbox does not have one universal set of limits that applies to everyone. In practice, the limit you hit depends on your plan, your admin settings (on team accounts), and sometimes region. Instead of memorising numbers that may be wrong by next quarter, focus on the limits that cause failed deliveries.

1) Transfer size cap (the “my export is 6GB” problem)

The most common failure mode: you finish a 6GB ProRes export, try to send it, and discover your plan’s transfer cap is lower than your file.

Fix: If you need a predictable “this will take up to X GB” rule for client delivery, use a transfer tool with a clear cap. For example, LetsSend Free allows 5GB per transfer (as of November 2026), and Pro allows 200GB per transfer. You can also use storage-share tools (Drive/OneDrive/Dropbox folders), but then you trade size clarity for permissions friction.

2) Link expiry (the “client downloads next week” problem)

Expiry is great until it is not. In creative work, people download late. The client is on set. The PM is travelling. The person who needs the files is not the person you sent them to.

Fix: Decide on an expiry that matches reality. If you need a short window for sensitive work, pick a transfer tool with a clear expiry policy. LetsSend Free links expire after 7 days, Pro links can be set up to 30 days (as of Nov 2026). If you need longer, a shared-folder approach might be a better fit.

3) Recipient friction (the silent killer)

Even when “no account required” is technically true, recipients still get stuck on:

• Opening a link on a phone, then failing to download over mobile data.
• Confusing a shared folder with a transfer and trying to upload changes back.
• Being prompted to sign in, create an account, or request access (especially with shared links and team policies).

In our own support inbox, the most expensive problem is not bandwidth. It is the extra round-trip messages: “It says I need access” or “The link is gone”.

When Dropbox is the best choice (and when it is not)

Dropbox is best when…

• You and the recipient are genuinely collaborating on a folder over time.
• You want version history and a long-lived workspace rather than a one-off handoff.
• Your recipient already lives in Dropbox and you want everything in one place.

Dropbox is not ideal when…

• You need a clean download link for someone who does not use Dropbox.
• You do not want “request access” messages or account prompts derailing delivery.
• You want predictable, explicit expiry and straightforward password protection for a one-time send.

Best alternatives for sending to someone without Dropbox (quick verdicts)

You have a few realistic paths. Pick based on what you are optimising for: speed, simplicity, security controls, or ongoing collaboration.

1) A dedicated transfer link (best for client delivery)

If your job is “deliver files, not manage a shared workspace”, a transfer link is usually the cleanest experience.

• LetsSend is built for this workflow. Files upload straight from your browser to encrypted object storage (not relayed through a middle server), then you share an expiring link. Links can be password protected, and on Pro you can add a download limit. Free is 5GB per transfer and Pro is 200GB per transfer (as of Nov 2026). If you want to see the exact link controls, you can see all features.
• WeTransfer is the familiar option many clients recognise. It is often smooth for recipients, but exact free limits and features (passwords, expiry length) can change, so check before you build it into a repeatable workflow.

Who this suits: photographers delivering a gallery export, editors sending a review cut, designers sending packaged artwork, agencies handing off final assets.

2) Cloud storage share links (best for ongoing access)

Google Drive, OneDrive, and Dropbox shared links are good when you want files to live somewhere long-term, with permissions and updates.

The trade-off is that “simple download” can become “permissions support”. If you go this route, create a dedicated folder per client and set permissions deliberately (viewer vs editor). Also consider whether you actually want a link that never expires.

Who this suits: teams collaborating over weeks, clients who need a permanent library, and internal handoffs where everyone already uses the same ecosystem.

3) Pro media delivery platforms (best for huge, time-critical deliveries)

For very large projects, tight deadlines, and professional delivery workflows (think: camera originals, episodic, ad agency finishing), platforms like MASV can be a better fit than consumer file-sharing.

Who this suits: post houses, broadcast workflows, and anyone who needs enterprise-grade delivery and is comfortable with pay-as-you-go pricing.

A practical checklist: how to send to a non-Dropbox recipient without the back-and-forth

1. Decide: transfer or collaboration? If you do not need edits back, prefer a transfer link.
2. Pick an expiry that matches your client’s behaviour. If they download late, do not set a 24-hour link and hope for the best.
3. Add a password for client work. Send the password in a separate message channel. If you want to understand the security model and trade-offs, read how LetsSend protects your files.
4. Name the files like a human. “FINAL_v7_REALFINAL.mov” is funny until it is not. Use “Client_Project_Deliverable_2026-11-05.mov”.
5. Warn them about mobile downloads. If the recipient opens on a phone, tell them to download on desktop or Wi-Fi. This one sentence saves you support time.
6. Include one line of instructions. Example: “This link expires in 7 days. Download the ZIP, then unzip before opening.”

What to do when uploads fail (hotel Wi-Fi edition)

Real-world detail: the most cursed place to upload a 20GB folder is a hotel Wi-Fi network that drops every few minutes. You see the progress bar restart, your laptop goes to sleep, and you lose an hour.

• Use a wired connection or a reliable hotspot if you can.
• Keep the browser tab awake and disable sleep until the upload finishes.
• Send one folder, not 400 tiny files if your workflow allows it. Packaging into a ZIP can reduce overhead (but do not expect big compression on H.264 video or JPEGs, they are already compressed).
• Try a different browser if the upload is unstable. It sounds silly, but browser networking stacks differ in edge cases.

Privacy and retention: what happens after the link expires

With client work, “Where do my files end up?” is a fair question. Different products handle expired links differently. Some behave like storage (the file sticks around until you delete it). Others behave like delivery (the file is removed after expiry).

LetsSend is a delivery tool. Expired transfers are deleted rather than quietly archived, and we do not sell your files or contact details. You can review who we are and how we think about this on the team behind LetsSend and in how we handle your data.

So, should you use Dropbox Transfer or something else?

If your recipient does not use Dropbox and you want the fewest “how do I download this?” messages, use a dedicated transfer link.

• Use Dropbox Transfer if you already pay for Dropbox, your file fits your plan’s cap, and you are happy with the expiry and controls available to you.
• Use LetsSend if you want a simple, predictable transfer link with clear caps and automatic expiry. Free is 5GB per transfer with links expiring in 7 days, Pro goes up to 200GB and up to 30 days expiry (as of Nov 2026). When you are ready, you can send a file free in your browser.
• Use Drive/OneDrive if you want a long-lived shared library and do not mind managing permissions.

Disclosure: LetsSend is our product. We build and run a file transfer service, so we are opinionated about what reduces delivery friction, but Dropbox and cloud storage are still the better fit for some collaboration workflows.

If you want a fast way to decide between Free and Pro based on file size and expiry needs, compare Free and Pro.