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.
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.
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.
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.