I thought you might have been on to something, Kraynic. I renamed a map image from JPG to JPEG and uploaded it and it was upscaled to a PNG just as Alan describes. But then I uploaded a JPG as JPG and it was also upscaled to a PNG. I went back to the map I had looked at when I made my earlier post and it was still a JPG in Roll20. So it looks like this is new behavior by Roll20 to convert JPGs and JPEGs to PNGs when uploaded. To truly test I uploaded the same map JPG with a different name, and looked at it and the one I already had in my Art Library. On my PC, the filesize is 6,745,250 bytes. Old JPG (shows as 7,119,230 byte JPG on Roll20, so some file inflation was going on before this): New JPG (shows as 37,527,146 byte PNG on Roll20): Thankfully, it seems to be counting the original, smaller filesize against my Storage Quota, but still. Anyone from Roll20 want to weigh in on what is happening here? Now is not a good time to be inflating filesizes and eating bandwidth...