Snapshot of ImageOptim/gifski: 5.6k★, Rust, Image Tools. GIF encoder based on libimagequant (pngquant). Squeezes maximum possible quality from the awful GIF format.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
gifski converts video frames to GIF animations using pngquant's fancy features for efficient cross-frame palettes and temporal dithering. It produces animated GIFs that use thousands of colors per frame.
It's a CLI tool, but it can also be compiled as a C library for seamless use in other apps.
Download and install
See releases page for executables.
If you have Homebrew, you can also get it with brew install gifski.
If you have Rust from rustup (1.63+), you can also build it from source with cargo install gifski.
Usage
gifski is a command-line tool. If you're not comfortable with a terminal, try the GUI version for Windows or for macOS.
From ffmpeg video
Tip: Instead of typing file paths, you can drag'n'drop files into the terminal window!
If you have ffmpeg installed, you can use it to stream a video directly to the gifski command by adding -f yuv4mpegpipe to ffmpeg's arguments:
Replace "video.mp4" in the above code with actual path to your video.
Note that there's - at the end of the command. This tells gifski to read from standard input. Reading a .y4m file from disk would work too, but these files are huge.
gifski may automatically downsize the video if it has resolution too high for a GIF. Use --width=1280 if you can tolerate getting huge file sizes.
From PNG frames
A directory full of PNG frames can be used as an input too. You can export them from any animation software. If you have ffmpeg installed, you can also export frames with it:
ffmpeg -i video.webm frame%04d.png
and then make the GIF from the frames:
gifski -o anim.gif frame*.png
Note that * is a special wildcard character, and it won't work when placed inside quoted string ("*").
You can also resize frames (with -W <width in pixels> option). If the input was ever encoded using a lossy video codec it's recommended to at least halve size of the frames to hide compression artefacts and counter chroma subsampling that was done by the video codec.
See gifski --help for more options.
Tips for smaller GIF files
Expect to lose a lot of quality for little gain. GIF just isn't that good at compressing, no matter how much you compromise.
Use --width and --height to make the animation smaller. This makes the biggest difference.
Add --quality=80 (or a lower number) to lower overall quality. You can fine-tune the quality with:
--lossy-quality=60 lower values make animations noisier/grainy, but reduce file sizes.
--motion-quality=60 lower values cause smearing or banding in frames with motion, but reduce file sizes.
If you need to make a GIF that fits a predefined file size, you have to experiment with different sizes and quality settings. The command line tool will display estimated total file size during compression, but keep in mind that the estimate is very imprecise.
Building
Install Rust via rustup. This project only supports up-to-date versions of Rust. You may get errors about "unstable" features if your compiler version is too old. Run rustup update.
Clone the repository: git clone https://github.com/ImageOptim/gifski
In the cloned directory, run: cargo build --release. This will build in ./target/release.
Using from C
See gifski.h for the C API. To build the library, run:
rustup update
cargo build --release
and link with target/release/libgifski.a. Please observe the LICENSE.
C dynamic library for package maintainers
The build process uses cargo-c for building the dynamic library correctly and generating the pkg-config file.
The cbuild command can be omitted, since cinstall will trigger a build if it hasn't been done already.
For WASM
To build the library for WebAssembly, you need to have wasm-pack installed. Then run:
wasm-pack build --target web --features wasm --no-default-features
License
AGPL 3 or later. I can offer alternative licensing options, including commercial licenses. Let me know if you'd like to use it in a product incompatible with this license.
With built-in video support
The tool optionally supports decoding video directly, but unfortunately it relies on ffmpeg 6.x, which may be very hard to get working, so it's not enabled by default.
You must have ffmpeg and libclang installed, both with their C headers installed in default system include paths. Details depend on the platform and version, but you usually need to install packages such as libavformat-dev, libavfilter-dev, libavdevice-dev, libclang-dev, clang. Please note that installation of these dependencies may be quite difficult. Especially on macOS and Windows it takes expert knowledge to just get them installed without wasting several hours on endless stupid installation and compilation errors, which I can't help with. If you're cross-compiling, try uncommenting [patch.crates-io] section at the end of Cargo.toml, which includes some experimental fixes for ffmpeg.
Once you have dependencies installed, compile with cargo build --release --features=video or cargo build --release --features=video-static.
When compiled with video support ffmpeg licenses apply. You may need to have a patent license to use H.264/H.265 video (I recommend using VP9/WebM instead).
gifski -o out.gif video.mp4
Cross-compilation for iOS
The easy option is to use the included gifski.xcodeproj file to build the library automatically for all Apple platforms. Add it as a subproject to your Xcode project, and link with gifski-staticlib Xcode target. See the GUI app for an example how to integrate the library.
Cross-compilation for iOS manually
Make sure you have Rust installed via rustup. Run once:
The build may print "dropping unsupported crate type cdylib" warning. This is expected when building for iOS.
This will create a static library in ./target/aarch64-apple-ios/release/libgifski.a. You can add this library to your Xcode project. See gifski.app for an example how to use libgifski from Swift.
TopGit's metadata for ImageOptim/gifski does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
What else is in the Image Tools space?
ImageOptim/gifski is tracked by TopGit under the Image Tools category, alongside 5 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is ImageOptim/gifski?
ImageOptim/gifski (ImageOptim/gifski) is a Rust project on GitHub. From the project's own README: GIF encoder based on libimagequant (pngquant). Squeezes maximum possible quality from the awful GIF format.
Where can I see ImageOptim/gifski in action?
The project maintains a homepage at https://gif.ski. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about ImageOptim/gifski?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/ImageOptim/gifski is the definitive source.
Why is ImageOptim/gifski categorized under Image Tools?
TopGit places ImageOptim/gifski in the Image Tools category based on its GitHub topics and description (tagged: "gif", "gif-animation", "gif-creator"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Still deciding about gifski?
One click hands the question to an AI along with this page — see what it says about gifski.