We Need to Save The Bytes
We Need to Save The Bytes
47 评论
-
Webp sucks especially when you're downloading porn
-
Fuck webp, use JPEG XL. It supports lossless and lossy compression, and it's compression is on par or better than webp. It also isn't entirely designed by Google.
With JPEG fallback. Google, being Google, blocked the addition of JXL decoding in Chrome and Android.
-
Only Apple supports JPEG XL.
Neither Chromium nor Firefox supports it (Chromium needs an extension and in Firefox you have to configure a variable in Nightly).
-
-
no
-
The pict-rs backend can be configured to automatically convert images to webp. So if an instance admin cares about the "bytes" they can do so.
-
-
Now if only Windows and Linux supported it out of the box...
-
-
No
-
I usually crop, resize, and/or reduce quality before I post images anymore. I aim for images to be less than 500 kB before uploading unless it's that worthy of a zoom or the extra detail.
I don't think there's that much perceptible quality loss between an original 16 MP image and resizing it to 4 MP and 80%, but the image ends up around 90% smaller. This was basically how I had my digital point and shoot camera set up in 2008. My mom gave me a 256 MB SD card for it, and that went fast sometimes.
-
When you copy and paste an image from a web browser (an image, not the original file), it often puts it in the paste buffer as a png.
So it's not impossible for someone, without realising, to paste a 50MB image in a reply.
With a decent internet connection, you might not even twig.
And if the server isn't set with filesize limits and transcodes, you can end up with a very small number of images taking up a very large amount of space.
Common examples are hi-res paintings/movie posters with grain, or poor quality (but high resolution) photos with lots of sensor noise.
-
I'm a caveman with a computer, can this be automated somehow,
-
One convert Vs 1000s makes sense to pipe it into the upload process
-
...more like 1 vs 300k, but you're right. 👍
-
-
-
Better yet, host elsewhere:
-
I love how Tesseract has the automatic conversion to webp option when posting.
I tested converting my png profile picture on mastodon and the size went down from 350 kb to 70 kb.
-
I use Switcheroo which has convenient options to downscale as well.
-
-
I usually compress my images now. Or zoom out and take a screenshot.
-
In my limited testing, exporting as a JPG can sometimes lead to a smaller file size than exporting to WEBP. Not always. I'm not sure if there is just some "point of diminishing returns" or whatever where JPG actually becomes more efficient or what.
-
WebP can be either lossless or lossy. These two modes achieve objectively better compression than PNG or JPEG, respectively. Obviously, you need to pay attention to the settings to get the best file size for your use case.
-
That is actually something I really dislike. Lossless and lossy formats should be immediately distinguishable.
-
-
I’m not sure if there is just some “point of diminishing returns” or whatever where JPG actually becomes more efficient or what.
There is, but it's at high quality levels. If you're using WebP for thumbnails or other lower quality situations (Which was the original intended use) then WebP will give you better quality than JPEG for a given filesize.
For lossless uses it's even better, the format is much more limited than PNG, but in the common cases it beats it.
-
-
Is there a client that automatically converts/optimizes images (locally) when uploading? Preferably on IOS
47 评论