Upload limits and large files
How big a file you can upload, how quickS3 splits large files into parts that upload side by side, and where Azure works differently.
The Upload files panel always shows the largest file you can upload to that folder. That number already takes every limit below into account.
How files are uploaded
Files up to 256 MB go up in one piece, straight from your browser to the storage provider.
Files over 256 MB are split into parts that upload side by side. That’s faster, and if the upload is interrupted, only the missing parts need sending again. See pause, resume, and retry. This works on every provider except Azure.
On Azure, every file goes up in one piece, so the largest file is 5 GB.
Size limits
| Limit | Size | Set by |
|---|---|---|
| Largest file, most providers | About 5 TB | quickS3 and your provider |
| Largest file, Azure | 5 GB | quickS3, because Azure uploads aren’t split into parts |
| Largest file with backend upload fallback on | 100 MB | quickS3 |
| Connection upload limit | Whatever the Owner set | The connection’s Upload size limit setting |
The connection’s upload limit applies to Admins and Members. Owners can always upload up to the other limits.
Your provider may have its own rules too, and the smallest limit always wins.
Backend upload fallback
Normally, files never pass through quickS3’s servers. If an Owner can’t get CORS working for a connection, they can turn on Allow uploads through quickS3 in its settings. Uploads then go through quickS3, which is less private and limited to 100 MB per file. The Upload files panel says so when it’s on.
Fixing CORS is almost always better. When a connection test finds that CORS works, quickS3 turns the fallback off again by itself.