You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
The right way to send large (>100GB) files via Dropbox to a client with no Dropbox subscription?
Hi,
I have Dropbox Pro myself, so uploading files should be no problem. The key question is: What is the optimum ZIP file size is so that a client who does not have a Dropbox subscription can downl...
khkannisto wrote:
Some years back it was impossible for a client to download anything over 2GB without signing up for Dropbox.
No, that's not true. If you invited someone to a shared folder they would be required to have a Dropbox account. If they had a free account, their storage space would be 2GB to start. That means they wouldn't be able to join a shared folder containing more than 2GB of data. Sending someone a shared link never had a 2GB download limit.
I am currently generating a split ZIP file with 50GB chunks. It will take 6 hours to generate the ZIP file and maybe 20 hours to upload. I really hope that that can be downloaded at the other end.If you're using a view-only shared link, they should be able to download the files, dependent on your own bandwidth limits.
To prevent abuse, Dropbox accounts have the following limits:- Basic accounts and accounts on a trial of a Dropbox team: 20 GB of bandwidth and 100,000 downloads per day
I take that to mean that if the recipient has a basic account they will only be able to download 20 GB per day
No, that refers to the bandwidth available to shared links and files requests used by people they share with. If someone on a Basic account shares a link to a file, or they send someone a File Request to receive files, the bandwidth limit applies to their account. If they're just downloading from someone else, they don't even need an account.
The exception here is if you send a Basic user a link to a file and they try to save it to their own Dropbox account instead of downloading it. In that case, they wouldn't be able to save it because it exceeds their space limit (assuming a 2GB free account). They can still download the file to their computer.
Some years back it was impossible for a client to download anything over 2GB without signing up for Dropbox.
Last year I couldn't transfer a file over 20GB or 50GB (I don't remember which one). The recipient couldn't download anything larger.
It had nothing to do with what I could upload, as I can upload a 2TB file. It had everything to do with what the recipient could download.
Which is why I am asking what the current limits are and how to best proceed.
Rich
Super User II
Super User II
khkannisto wrote:
Some years back it was impossible for a client to download anything over 2GB without signing up for Dropbox.
No, that's not true. If you invited someone to a shared folder they would be required to have a Dropbox account. If they had a free account, their storage space would be 2GB to start. That means they wouldn't be able to join a shared folder containing more than 2GB of data. Sending someone a shared link never had a 2GB download limit.
I am currently generating a split ZIP file with 50GB chunks. It will take 6 hours to generate the ZIP file and maybe 20 hours to upload. I really hope that that can be downloaded at the other end.
If you're using a view-only shared link, they should be able to download the files, dependent on your own bandwidth limits.
To prevent abuse, Dropbox accounts have the following limits:
- Basic accounts and accounts on a trial of a Dropbox team: 20 GB of bandwidth and 100,000 downloads per day
I take that to mean that if the recipient has a basic account they will only be able to download 20 GB per day
No, that refers to the bandwidth available to shared links and files requests used by people they share with. If someone on a Basic account shares a link to a file, or they send someone a File Request to receive files, the bandwidth limit applies to their account. If they're just downloading from someone else, they don't even need an account.
The exception here is if you send a Basic user a link to a file and they try to save it to their own Dropbox account instead of downloading it. In that case, they wouldn't be able to save it because it exceeds their space limit (assuming a 2GB free account). They can still download the file to their computer.
Hi Rich,
Thank you, that was helpful information.
From that my conclusion is that I should upload those 50GB files, generate individual read-only file links for each (there will be about 14 of them for 700 GB split into 50GB chunks), and NOT a folder link so that they don't try and add it to their free or basic or whatever version Dropbox they may or may not have.
Then I should send them a mail with a list of all those individual links and everything should be fine. As long as they download every one of them successfully and recombine the ZIP at their end. And since my (sender's) limit with Dropbox Pro is 1 TB per day, that should not be a problem.
And sharing a folder containing the ZIP files would not be the way to go (unless they have a Dropbox Plus or better).
Sending 14 transfers of 50 GB (or 7 transfers of 100 GB) would be another option, I gather, although that sounds more cumbersome.
Do I have that correct?
Best regards, Kalle
- Rich
khkannisto wrote:
Do I have that correct?
Yes.
If I give the recipient a link to the folder containing the files, they still cannot download individual files that are more than 2GB. Even 4GB mp4 files fail to download.
It may be that direct links to individual files allow downloading more than 2GB, but you still cannot download a individual file which is over 2GB (when zipped) if you only have a link to the containing folder. You have to give the recipient an individual link to each and every file which is over 2GB. Not very user-friendly.
It would be good to have this laid out clearly somewhere in the documentation.
Or, much better, fixed so that this counter-productive 2GB limitation is removed.
