-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebP support #194
Comments
Also any mobile app can implement WebP support, which makes it even more worthwhile. |
Firefox released version 65 early 2019, now providing WebP support too. |
Agreed, browser support is good enough and the benefits plenty, please support! |
libwebp is 1.0 now, so we can support it. |
Are there any news about WebP support? |
Not yet, although we had a big breakthrough today that should free up more dev effort towards webp and rewriting the webserver. |
I'm maintaining bindings if you need them: https://lib.rs/crates/libwebp-sys |
@kornelski Perfect! I'll use those. Do you have any suggestions for output tuning or presets? The array of options seems dizzying.
|
I haven't looked into tuning these options yet. |
Thanks! I've just used the simple encoder API for now. WebP support can be activated using the webplossy {quality} and webplossless encoder presets or using &format=webp&webp.quality=x or &format=webp&webp.lossless=true respectively. This is in master. |
Update: you now use &webp.lossless=true|false and &webp.quality=0..100 to adjust compression rather than reusing the jpeg quality command. |
While WebP is only supported by Chrome, its dominance of market means that about 70% of the users will able to load that format.
WebP is a good compromise between JPEG and PNG, in terms that it can perform lossy compression while not destroying alpha properties. It simply compresses better, too.
The text was updated successfully, but these errors were encountered: