squoosh
libavif
Our great sponsors
squoosh | libavif | |
---|---|---|
266 | 44 | |
20,820 | 1,358 | |
1.3% | 3.6% | |
6.2 | 9.7 | |
7 days ago | 7 days ago | |
TypeScript | C | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
squoosh
- Jpegli: A New JPEG Coding Library
-
Optimizing Images for Developer Blogs
Squoosh: A webpage that allows you to quickly optimize images for your blog.
-
Building an online image compressor
One of the most complete image compressor out there, squoosh.app by Google, uses web assembly for decoding/encoding images and it works pretty well.
-
Improve performance of Go serving a React frontend
First off you want to shrink your images. Every mb your page is the more it will hurt your score. I use https://squoosh.app/
-
Power Consumption of JPEG, WebP, and AVIF
https://squoosh.app/
Having a quick look at squoosh, it uses lossy compression of webp by default.
-
What makes a page rank well?
Size images appropriately (https://squoosh.app/ can be used for this). Ideally, the size of the image should be kept below 100 KB.
-
my live site keeps jumping back to the top of the page while I'm using it
if your images a large file size, remove them from the page, reduce file size, and place new reduced file size images in their place - publish the site to bring the new pics live - clear your cache - go the page and test it (good tool to reduce image file size is Google Squoosh - https://squoosh.app/ )
-
Can anyone recommend any decent plugins that let me adjust jpg quality on export for web,
I'm just exporting normally from Figma, but then using squoosh.app (browser based) to adjust quality/compression and even for making sure png files are optimized for prod.
-
Clan creating invalid photo [HELP]
Hey I see your friend made a clan, but this guy found a workaround here if you still need it. I just used https://squoosh.app/ to basically save a new copy of the image and that worked
- Squoosh – Simple image optimizer that does all the work locally
libavif
-
CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
It's 2023, surely this is not yet another bug related to memory unsafety that could be avoided if we'd stop writing critical code that deals with extremely complex untrusted input (media codecs) in memory unsafe languages?
Yep, of course it is: https://github.com/webmproject/libwebp/commit/902bc919033134...
I guess libwebp could be excused as it was started when there were no alternatives, but even for new projects today we're still committing the same mistake[1][2][3].
[1] -- https://code.videolan.org/videolan/dav1d
[2] -- https://github.com/AOMediaCodec/libavif
[3] -- https://github.com/AOMediaCodec/libiamf
Yep. Keep writing these in C; surely nothing will go wrong.
- Libavif 1.0 Released
-
Is there any clear documentation on how to make avif collections and how to read them?
As far as I understand you are talking about this plugin. I don't know c++ and half of the code was like a black magic, but if I get it correctly, it encodes your images with libavif, and adds custom metadata ([solar/time of day] -> json -> base64).
-
FSF Slams Google over Dropping JPEG-XL in Chrome
So a few dozen comments, but so far it doesn't look like any mention the immediate thing that jumped out at me which was the claims vs AVIF:
>"In turn, what users will be given is yet another facet of the web that Google itself controls: the AVIF format."
Huh? I'll admit I haven't been following codecs as super ultra closely as I used to, but I thought AOM was a pretty broad coalition of varying interests and AV1 an open, royalty free codec that was plenty open source friendly? I've heard plenty of reasonable arguments that JPEG XL has some real technical advantages over AVIF and as well as superior performance is much more feature rich and scalable. So I could see people being bummed for that. But this is the first time I've heard the assertion that it's somehow a Google project? I mean, AOM's libavif reference is BSD too [0]? I'd love some more details on that from anyone who has been following this more closely. I can even understand if AOM isn't as community friendly and an accusation that it's dominated by big corps, but in that case why single out Google alone? From wiki:
>The governing members of the Alliance for Open Media are Amazon, Apple, ARM, Cisco, Facebook, Google, Huawei, Intel, Microsoft, Mozilla, Netflix, Nvidia, Samsung Electronics and Tencent.
Like, Google is certainly significant, but that's a lot of equally heavy hitters. And interesting that Mozilla is there too.
----
-
JPEG XL support has officially been removed from Chromium
> You have a good point that AVIF layered image items can act like such P/B-frames. Do libavif (or other AVIF implementations if any) make use of them?
Seemingly. As search for "libavif progressive encoding" shows several issues about this, and a search for "progressive" in https://github.com/AOMediaCodec/libavif/blob/main/include/av... shows an enum for avifProgressiveState, appears to show support for it.
-
Wavif discussion
I mean, it already has it: https://github.com/AOMediaCodec/libavif/commit/570c42c2c10a878c8cc896f1c5daf1a955274142
-
Animated AVIF and JXL tools for Windows
Apart from mpv and ffplay, the only software I currently have installed that can play animated AVIF is Chromium. And from what I've read from this libavif bug report, I'm not sure if looping animated files in general is something that's just done by default by a lot of software regardless of whether the file is marked as a loop or not.
-
How to create progressive AVIF images?
The support for progressive AVIF decoding has landed in libavif and in Chromium. But are there any docs on how to create and test progressive AVIF images?
-
The Case for JPEG XL
The "for example" is the key here, because AVIF does support multi-layer coding per the spec now (though not currently implemented in libavif from what I can tell).
-
Google Outlines Why They Are Removing JPEG-XL Support From Chrome
libavif is at version 0.11.1, see https://github.com/AOMediaCodec/libavif/tags
What are some alternatives?
sharp - High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, AVIF and TIFF images. Uses the libvips library.
rav1e - The fastest and safest AV1 encoder.
oxipng - Multithreaded PNG optimizer written in Rust
cavif-rs - AVIF image creator in pure Rust
ImageOptim - GUI image optimizer for Mac
av1-avif - AV1 Image File Format Specification - ISO-BMFF/HEIF derivative
go-unsplash - Go Client for the Unsplash API
libjxl - JPEG XL image format reference implementation
Mono - Mono open source ECMA CLI, C# and .NET implementation.
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
devilbox - A modern Docker LAMP stack and MEAN stack for local development
benchmarks - Test images and results of compression benchmarks.