A common use case is to have a folder with several dozen to several hundred pictures and to download them to more quickly access the photos. When downloaded, the first step is almost always to decompress the folder because if you open the photos within the compressed folder, you cannot navigate between the photos with the arrow keys without decompressing the files first.

When download files to file with the court, again, the first step is almost always to decompress the files. Most court filing systems only allow the filing of pdfs. I know of at least one court in particular that wants the certificate of service filed separately from the motion and will reject the filing if you do not do this step. Thus, this creates a use case where you are again downloading multiple files and decompressing them immediately since if you try to upload individual pdfs before decompressing them, it can break the upload. Thus, again, you pretty much by default must decompress the files first.

Another use case is when sending a large batch of files, it can take so long to compress the files that they fail to send and you get the message to contact support. I have run into this problem when sending multiple videos whose total file size is 4gb, 10gb, 25gb or larger. This use case can be hit or miss, and I am not certain whether the compression is at fault, but this issue did not occur before automatic compression was introduced.

There are other examples, but the majority of cases, the automatic compression seems to simply slow down the workflow. It would be greatly appreciated if you could chose to not compress files by default when downloading or sending files. This setting could be implemented through either an option in a user's profile settings or as a separate option under actions.