Three file size limits can stop a deal file before it reaches the buyer: single-file upload limits, storage ceilings, and transfer caps. Check all three before you hit send — each lives in a different place and fails in a different way.
Key takeaways
- Single-file upload ceiling: the hard stop on any single file, which varies by surface — browser, desktop app, or mobile.
- Account storage total: everything already in the account counts toward the same pool, so a small file can still fail if the pool is full.
- Transfer ceiling: a link send has its own separate limit that can sit above or below the upload ceiling depending on the path.
- Surface matters: the same file behaves differently in a browser than in a desktop app or on a phone.
- Confirm before you send: check the expiration window and test the link on a different device yourself first.
What stops a deal file at the last minute
A deal file is the bundle you send to a buyer, your manager, or your board before quarter close. It usually holds the deck, the model, the signed contract, screen recordings, and supporting data extracts. The file goes out in a rush. Then a size limit you never checked kicks in.
The link expires. The recipient opens a file that will not download. You lose a day chasing it.
Three separate limits can block that handoff. Checking all three takes a few minutes. Skipping them can cost you the quarter.
Here is what to check before you hit send: the single-file cap on whatever tool you upload through, the total storage attached to your account, and the transfer ceiling if you are routing the bundle through a share link instead of attaching it.
Who this is for
This is for revenue leaders — VPs of sales, deal desk leads, and CFOs — who assemble a deal file and send it outside the company before quarter close. The recipient might be a buyer, your own manager, or a board member reviewing the quarter. The file is going out under time pressure.
Red flags. If your deal file is always a single PDF under a few megabytes, you can probably skim this and move on. If you routinely push screen recordings, data extracts, or a full contract set into the bundle, read the single-file section carefully.
Limit one: the single-file upload ceiling
This is the hard stop on any single file you try to push into a tool. For a fuller list of upload checks, see File size limits: 8 checks before evidence uploads.
Bitwarden sets its attachment ceiling at 500 MB or smaller for desktop, and 100 MB or smaller when the upload comes from mobile. That second number is the one that catches people. A screen recording that uploads fine from a laptop will fail from a phone on the way to the airport.
If your deal file lives in Bitwarden as an encrypted attachment, run the bundle past that line before you leave your desk. The mobile figure applies to anything you attach from the Bitwarden mobile app, regardless of how large your desktop uploads have been all week.
Bitwarden's attachment rule is worth reading closely, because the mobile and desktop cases sit in one sentence: a file of any type that is 500 MB or smaller, or 100 MB or smaller from mobile, can be attached to an item, and an account can upload up to 5 GB of total attachments unless more storage is added.
Note what that sentence covers: a file attached to an item. Match your send path to the right rule.
Dropbox splits its single-file ceiling by upload surface as well. Files uploaded through the desktop app or mobile apps must be 2 TB or smaller. Large files uploaded to dropbox.com — through the browser — must be 350 GB or smaller.
That gap matters if your deal file lives on a machine with the Dropbox desktop app running. A very large data extract can push through the app. The same file loaded in a browser tab will hit the web ceiling first.
If you are pushing anything near the top of a ceiling, check which surface you are on before you start. The file is the same. The ceiling is not.
What to check first
- Which tool holds the file.
- Which surface you are uploading from: browser, desktop app, or mobile.
- Whether a single file in your bundle crosses the line for that surface.
Keep the check short. Check every file in the bundle against the ceiling before you upload. If you compress or split the bundle before it goes out, confirm your recipient can reassemble it.
Limit two: your account storage total
The single-file ceiling is about one file. The storage ceiling is about everything you have already put in the account, plus what you are about to add.
Bitwarden gives paid users and members of paid organizations 5 GB of encrypted storage for file attachments. That is the account-wide pool. A new attachment on a Wednesday can fail because the pool was already full from Monday.
The Bitwarden page states the combined rule directly: "Paid users and members of paid organizations have 5GB of encrypted storage for file attachments." Attachments currently stored in the account count toward the same 5 GB.
For a deal file, this means two checks. First, how much of your current pool is in use. Second, how large the new bundle is on its own. Both have to fit.
Dropbox puts a different spin on the storage question when you use its transfer path rather than a plain upload. Dropbox Transfer sends files up to 100 GB, upgradable to 250 GB, without taking up space in your account. That wording matters: a Transfer-based send does not consume your Dropbox storage pool the way a direct upload would.
Dropbox states the capability this way: "With Dropbox Transfer, you can send files up to 100 GB (or larger files up to 250 GB with the Dropbox Replay Add-On)—without taking up space in your Dropbox account."
So the practical distinction is this: a plain upload draws on account storage, so the bundle must fit in the space that remains. Routing the same file through Transfer avoids that draw, because the transfer path is not drawing down your account pool.
For the shared-folder angle, see Dropbox shared folder quota: 3 rules for deal files.
Storage rules in one place
| Tool | Single-file ceiling | Storage or transfer ceiling |
|---|---|---|
| Bitwarden desktop | 500 MB or smaller | 5 GB account total for paid users |
| Bitwarden mobile | 100 MB or smaller | 5 GB account total for paid users |
| Dropbox desktop or mobile app | 2 TB or smaller | Uses account storage |
| Dropbox web upload | 350 GB or smaller | Uses account storage |
| Dropbox Transfer | 100 GB | Does not use account storage |
| Dropbox Transfer upgraded | 250 GB | Does not use account storage |
Limit three: the transfer ceiling when you send a link
A deal file often travels as a link, not an attachment. The link has its own ceiling, and it can sit above or below the upload ceiling depending on the path.
For Dropbox, the Transfer path runs up to 100 GB by default. The upgraded path runs up to 250 GB with the Dropbox Replay Add-On. Neither of those figures is the same as the 350 GB web upload ceiling or the 2 TB app ceiling. They are separate numbers for separate paths.
If your plan already puts the bundle near 100 GB, the Transfer default can cut you off even though a plain upload would have accepted it. If you are well under 100 GB, Transfer is usually the easier path, because the file does not draw down your account storage.
Which path matches your file
- A bundle under 100 GB going to a buyer: Dropbox Transfer handles it without touching your storage.
- A bundle above 100 GB but under 250 GB: you need the upgraded Transfer path before you send.
- A bundle above 250 GB: Transfer is out. Look at the upload ceilings instead.
- A bundle that must live in the account after the send: upload it, then share from storage.
Check the recipient's side as well. A link that expires before the buyer opens it is the same failure as a size cap, just wearing a different coat. Confirm the expiration window in the tool before you send.
How access control fits the same send
File size gets the file there. Access control decides who can open it once it arrives.
NIST Special Publication 800-63B describes the AAL3 requirement as follows: "To authenticate at AAL3, claimants are required to prove possession and control of two distinct authentication factors."
That wording applies to the person signing in, not to the file itself. For a board or buyer share, it points at one practical move: pair something the recipient knows with something they carry. A password plus a one-time code on their phone is two distinct factors. A shared link with no second step is one factor at most.
If your deal file contains pricing that has not been announced, or customer data, the link alone is thin protection. Add a second factor on the recipient side, or use a tool that lets you gate the download behind a login your recipient already has.
If the access question is still open after you check your tool's documentation, ask your security or IT lead which factor set your company requires for a file of this class. That answer belongs to your organization, not to a public page.
A working sequence before you hit send
Run this in order. It takes a few minutes and it catches the failures that cost a day.
1. List the bundle. Write down every file that will travel together. Note the largest one. Note the total.
2. Match the tool. Identify the tool holding the file and the surface you are on: browser, desktop, or mobile. The ceilings differ by surface.
3. Check the single-file line. Compare your largest file against the single-file ceiling for that surface. If it is over, compress or split before you upload.
4. Check the storage line. If you are uploading directly, confirm your account pool can hold the bundle on top of what is already there. If you are sending through a transfer path, confirm the transfer ceiling instead.
5. Check the transfer line. If you are sending a link, confirm the bundle fits under the transfer ceiling for your plan. Upgraded features cost extra and may need an add-on.
6. Check the access layer. Decide whether the link alone is enough. For anything sensitive, plan a second factor on the recipient's side.
7. Confirm the recipient window. Make sure the link lives long enough for the buyer, manager, or board member to open it. Confirm before you send, not after.
8. Send a test to yourself. Open the link on a different device. Download the bundle. Confirm every file inside opens. Then send it to the real recipient.
Common failure modes
The mobile surprise. A bundle that uploads cleanly from a desktop can hit a lower ceiling on mobile, as Bitwarden's 100 MB mobile limit shows. If you are attaching or uploading from a phone, apply the mobile figure, not the desktop one.
The full account. A file well under the single-file ceiling still fails because the account pool has no room left. Clear old attachments or route the send through a transfer path that does not draw on account storage.
The surface mix-up. The same file behaves differently in a browser than in a desktop app. Pick the surface with the higher ceiling before you start, not halfway through.
The transfer ceiling. A bundle that uploads fine as a file can exceed the transfer ceiling if you send it as a link. Check the transfer number separately from the upload number.
The expired link. The file went out fine. The buyer opened it two days late and the link was dead.
The thin access. A link to an unannounced price went out with no second factor. Anyone with the link could open it. Add a factor or a login gate for anything in that class.
Your next step today
Today, list every file in the bundle and note the largest one. Your own tool's current plan, your contract's overage terms, and your company's required access factor set all live inside your account or your policies. If any of those matter for your next send, ask your tool's account manager for the plan detail, and ask your security or IT lead for the access requirement. They can answer in a few minutes.
FAQ
What is the first limit to check when a deal file will not send?
Check the single-file ceiling for the exact surface you are uploading from. A file that fails in a browser may succeed in a desktop app, and a file that succeeds on a laptop may fail on a phone. The surface decides the number.
Does a transfer link use my account storage?
For Dropbox Transfer, the send does not draw on your account storage pool. That is the practical reason to prefer a transfer link when your account is already near full. A direct upload into your storage does use the pool.
What if my bundle is larger than the default transfer ceiling?
If the 100 GB Transfer ceiling is too small, the upgraded path allows files up to 250 GB with the Dropbox Replay Add-On. Check your plan before you promise a delivery window to the recipient.
How do I protect a link carrying unannounced pricing?
Pair something the recipient knows with something they carry. NIST's AAL3 requirement calls for two distinct authentication factors for the person signing in. A password plus a one-time code on their phone meets that shape. A bare link does not.
Should I test the link before sending it to the buyer?
Yes. Open it on a different device, download the bundle, and confirm every file inside opens. A link that works on your laptop and fails on a tablet is a failure you can catch in two minutes, before the buyer finds it.