@mtdowling Ok. I'll edit the pull request. I do think it is actually a quite popular use case... In our case, customers store the data locally as a hash to prevent data collisions. When it is shuttled to a service, the filename should be something nice. Example: ABC12345.pdf will become tickets.pdf. I cannot store multiple versions of tickets.pdf.