However, IIRC, Squoosh was built largely by Surma and Jake; or maybe they were just the "face" of the project. Either way, at one point it even had a CLI.
Since their departure from Google, the CLI project was abandoned and it feels like the web app is as well.
As is usual Google things, I think it's a matter of time until some PM discovers squoosh.app, and asks "What's this?" and then the thing gets killed.
Perhaps this HN post will be the thing that does it.
Why does setting the quality to 100% make the resulting image size bigger than original? And if there's a reason, I think it should simply just return the original smaller image in those cases.
+1 Whenever I create a favicon.png, I always run it through ImageOptim and I consistently get an optimised PNG that is about 30% to 40% smaller than the original.
I love squoosh! It’s been one of the few PWAs I have installed and actually use regularly.
Does anyone know if their optimization methods still best-in-class these days? It’s been good enough for all my practical needs, but I know it’s been around for a while and there may be better techniques for some file types now.
Depends on how you'd define success. It has been profitable since 2014. A few millions in revenue.
Upkeep is another story when you have thousands of customers using the API. It's not so easy to keep everyone happy, as image quality is highly subjective there's a quality tolerance spectrum which for the life of me I will never understand.
I just tested it with a PNG from Nano Banana, recompressed to JPG and even reduced palette to 256 colors. Gemini still says the image contains SynthID.
However, IIRC, Squoosh was built largely by Surma and Jake; or maybe they were just the "face" of the project. Either way, at one point it even had a CLI.
Since their departure from Google, the CLI project was abandoned and it feels like the web app is as well.
As is usual Google things, I think it's a matter of time until some PM discovers squoosh.app, and asks "What's this?" and then the thing gets killed.
Perhaps this HN post will be the thing that does it.
https://github.com/GoogleChromeLabs/squoosh/issues/1408
Does anyone know if their optimization methods still best-in-class these days? It’s been good enough for all my practical needs, but I know it’s been around for a while and there may be better techniques for some file types now.
https://github.com/sbcinnovation/squoosh-cli
Windows support may be iffy, any PR's are welcome.
https://news.ycombinator.com/item?id=26992277
https://news.ycombinator.com/item?id=21912480
https://kraken.io/web-interface
Upkeep is another story when you have thousands of customers using the API. It's not so easy to keep everyone happy, as image quality is highly subjective there's a quality tolerance spectrum which for the life of me I will never understand.