![convert webm to still images to gif convert webm to still images to gif](https://i.ytimg.com/vi/zMuc-dXr78I/maxresdefault.jpg)
MaxServersideGIFUploadSize: 6MB (a bit of extra leeway) Remember that "images" can include animated gifs and the like, which can get quite big, but can compress down by an order of magnitude (AVIF). MaxServersideImageUploadSize: 1.5MB (a bit of extra leeway) No point to being more than ~5x larger than SizeLimitForConvertedImages, as the extra detail would just get lost. SizeLimitForNoCompression: 150k (if AVIF) / 180K (if WebP) The vast majority of images being JPEGs lazily pasted in or uploaded would fall under this category. SizeLimitForConvertedImages: 250k (if AVIF) / 300K (if WebP). Larger than the size limit for nonconverted image files, because (A) they're sparing the server work, and (B) to give users an option to upload "high quality images" where needed (artwork, professional photography, science imagery, etc) if they're willing to do more work on their end. SizeLimitForPreconvertedImages: 500k (if AVIF) / 600K (if WebP).
![convert webm to still images to gif convert webm to still images to gif](https://media.giphy.com/media/26AHG5WtHnb2G2voA/giphy.gif)
StorageFormat: None (native legacy formats only (JPEG/GIF/PNG)), WebP, AVIF The server can configure its preferred formats and conversion thresholds ( question: will lenient servers increase the load on stringent servers?).Old uploaded images ( which have already been quality-degraded) could be lossless or near-lossless compressed further in said idle thread, at even lower priority ( optional, if a non-legacy storage format is chosen).( if a non-legacy storage format is chosen) An idle thread running at low priority converts uploaded images to more compact formats and does database updates.imgproxy sits in front of Mastodon ( if a non-legacy storage format is chosen).caching/CDN sits in front of imgproxy ( optional).I think there's a general architecture lining up here. It's hard to say exactly what sort of load (disk space, CPU) imgproxy would add, but given the assumption that "new files are served frequently and old files rarely", probably quite insignificant compared to the savings. It autoconverts formats as needed for legacy clients. As per the other thread (I'm not sure why a new one was started), imgproxy solves this. Edge still doesn't support it and Safari support is extremely limited at this point. Likewise, AVIF will probably only ever be deliverable to select devices even though the bandwidth savings are quite good. macOS 11 dropped support for MacBooks released before 2015, which is not that old by current PC standards. With Safari, WebP support relies on OS capabilities, needing macOS 11 or later. Note that "legacy" JPEG support will probably be necessary for the foreseeable future, either as a storage format or with converting on the fly by nginx.