Child Item

Download Zip limits

I am curently experimenting with the Download Zip and Download File APIs, but I'm running into issues with the two:

1. Download Zip works well since it preserves the file metadata, but quickly becomes unfeasible due to the limitations since we have many instances of files larger than 4GB or folders that are over 20GB.

2. Download File works but writing binary stream doesn't retain file metadata.

Is there any possibility to increase the Download Zip limits? Or, are there are creative work-arounds to use the API for large exports + retaining file metadata? I could use the server_modified timestamp and os.utime to modify the file after it writes, but that isn't the most ideal way.

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

There isn't a way to increase the limits on /2/files/download_zip, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

I'm afraid I can't offer any other good workarounds.

All comments

Greg-DB

There isn't a way to increase the limits on /2/files/download_zip, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

I'm afraid I can't offer any other good workarounds.

lostinlovephotography

Would LOVE to see the limit of downloadable zip files to 40GB so that we can store our backup work on dropbox and bulk download if we need to for clients or if we lose data on our harddrives.

Greg-DB

@lostinlovephotography Thanks for the feedback!