Our great sponsors
mozjpeg | svgo | |
---|---|---|
19 | 29 | |
5,353 | 20,349 | |
0.8% | 0.9% | |
6.2 | 9.0 | |
4 months ago | 7 days ago | |
C | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
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.
mozjpeg
-
WebP is so great except it's not
[2] https://github.com/mozilla/mozjpeg
-
It's the future – you can stop using JPEGs
It would be nice if the author would add mozjpeg[1] to the comparison. At certain sizes, it can produce smaller sizes than WebP, and because it is still a jpeg, it has a much better compatibility story, which the author alluded to.
[1]https://github.com/mozilla/mozjpeg
-
Random Code Inspiration Volume 2
image-shrinker is a simple, easy to use open source tool for shrinking images. Under the hood it uses pngquant, mozjpg, SVGO, and gifsicle. You can also install these tools individually if you need to compress some images. I often use pngquantafter exporting PNGs for web projects from Figma or similar tools. I literally run it like this:
-
JPEG XL: How It Started, How It’s Going
> MozJPEG is a patch for libjpeg-turbo. Please send pull requests to libjpeg-turbo if the changes aren't specific to newly-added MozJPEG-only compression code.
https://github.com/mozilla/mozjpeg#mozilla-jpeg-encoder-proj...
-
Why there may never be a libjpeg-turbo 3.1
FWIW, Mozilla has been maintaining their own fork for quite a while now[1]
AFAIK most Linux Distros have been using libjpeg-turbo as a drop-in replacement for libjpeg, after some drama in ~2010 where libjpeg came under new management, decided to break ABI/API several times over and add incompatible, non-standard format extensions[2].
[1] https://github.com/mozilla/mozjpeg
[2] https://en.wikipedia.org/wiki/Libjpeg#History
-
Are all JPEG compression implementations the same?
No.
See https://github.com/mozilla/mozjpeg
Also, there is a fairly big problem with JPG that the ‘quality’ setting is not calibrated. That is you might look at one image and think it looks fine (which is subjective, depends on what you want to use the image for…) with a quality of 60%, but then you compress a million images at that rate, delete the originals, then you find that many of them look really awful. Not only that but there are images you could have compressed more and still been happy with the output.
If you are publishing images for the web consider using WebP which is consistently better, well supported now, and has a calibrated quality knob.
-
reduce the size of a bunch of jpg
https://github.com/mozilla/mozjpeg's cjpeg tool is the command line version of the mozjpeg library, itself a fork of libjpeg-turbo. Mozjpeg performs lossless JPEG optimization. There are plenty of others out there.
-
Lossy Image Compression with Dithering
Use the Mozilla JPEG Encoder, which implements several tricks for smaller file size / better visual quality. The result is still JPEG standard compatible that other software can decode.
-
Fighting JPEG Color Banding
Guetzli was already mentioned and roughly does what you are talking about.
MozJPEG [1] includes several quantization tables that are optimized for different contexts (see the quant-table flag and source code for specific tables[2]), and the default quantization table has been optimized to outperform the recommended quantization tables in the original JPEG spec (Annex K).
It's also worth noting that MozJPEG uses Trellis quantization [3] to help improve quality without a per-image brute force quantization table search. Basically rather than determining an optimal quantization table for the image, it minimizes rate distortion on a per-block level by tuning the quantized coefficients.
[1] https://github.com/mozilla/mozjpeg
[2] https://github.com/mozilla/mozjpeg/blob/5c6a0f0971edf1ed3cf3...
[3] https://en.wikipedia.org/wiki/Trellis_quantization
-
FFmpeg now supports JPEG XL
They're still being used. A newer, optimized JPEG encoder, mozJPEG[0], seems to use progressive encoding by default. I suspect with faster internet speeds, most images download and decode so fast that the cool 'enhance' animation doesn't happen anymore.
[0] https://github.com/mozilla/mozjpeg
svgo
-
Random Code Inspiration Volume 2
image-shrinker is a simple, easy to use open source tool for shrinking images. Under the hood it uses pngquant, mozjpg, SVGO, and gifsicle. You can also install these tools individually if you need to compress some images. I often use pngquantafter exporting PNGs for web projects from Figma or similar tools. I literally run it like this:
-
Dynamic SVG images using Next.js
In addition to the techniques we’ve discussed so far, there are optimization tools available that can further enhance SVG images. These tools, such as SVGO and ImageOptim, offer valuable features to reduce file size and clean up SVG markup, making it easier to standardize and optimize the overall performance of SVG assets.
-
Is it possible to save multiple files as optimized SVGs at once?
Open the terminal and cd to the folder containing your SVG files and run the command inkscape *.svg --export-plain-svg --export-type=svg And Inkscape is going to save your files as plain SVG and append the word "_out" to them. Note : Plain SVG files are not optimized for the web, you should use SVGO or any other Node.js tool, there are a lot of them on MPM
- F360 going crazy over a client supplies SVG. Anything to clean it up?
- What is the benefit of stripping viewBox?
-
Ask HN: FOSS Projects Worth Donating To?
Look at software you use and identify underlying libraries.
SVGO https://github.com/svg/svgo is used by many graphics software but hasn't seen donations commensurate with usage https://opencollective.com/svgo
- Создаем React-компоненты иконок с помощью Figma API и SVGR. Часть 2.
- Used an online SVG editor, this code got added to my file. I've already opened the file. How fucked am I?
-
Using SVGs in Common Lisp web apps with Djula
There are still a lot of things cl-djula-svg is capable of doing. For the immediate future, I am looking at adding optimization capabilities something like what svgo is doing for svgr. If you know anything else needs to be done to improve the package, please open an issue in the repository.
-
Is Rust a good first language to master?
Writing/patching JS/TS-based CLI tools like Prettier or SVGO
What are some alternatives?
squoosh - Make images smaller using best-in-class codecs, right in the browser.
svgomg - Web GUI for SVGO
guetzli - Perceptual JPEG encoder
svgr - Transform SVGs into React components 🦁
wazero - wazero: the zero dependency WebAssembly runtime for Go developers
svg-to-react - Tool to convert SVG files to React components
image-actions - A Github Action that automatically compresses JPEGs, PNGs and WebPs in Pull Requests.
Beatbump - Alternative YouTube Music frontend built with Svelte/SvelteKit 🎧
bimg - Go package for fast high-level image processing powered by libvips C library
easyeda-svg-import - Simple SVG Importer for EasyEDA PCB that doesn't convert everything to Comic Sans 😄
jpegoptim - jpegoptim - utility to optimize/compress JPEG files
xooks - General purpose react hooks collection