Exactly that for an enterprise web app that attached all the physical paperwork of an order to the digital record. Original dev just shoved all 30,000 in the w

Exactly that for an enterprise web app that attached all the physical paperwork of an order to the digital record. Original dev just shoved all 30,000 in the webroot as multipage tiffs, average size 25Mb-30Mb. End users couldn't easily view attached scans (multipage tiff isn't that prevalent), converting to pdf with jpeg compression took the first set from 76.8Gb to 6Gb with far less traffic on the network and much easier handling (PDF is far better supported).