GIF Optimizer
Choose a color count and an optional delay.
About this tool
Frames are quantized locally. This does not use gifsicle.
Fewer colors change the picture. A delay of 0 keeps each frame’s existing delay.
How to use it
- Open this page and provide the input it asks for.
- Set the options that are visible, then use Optimize GIF.
- Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.
Limitations
- Fewer colors change the picture. A delay of 0 keeps each frame's existing delay.
Palette size and frame delay, still a GIF
Colors and delay, in milliseconds
Each frame is composited to RGBA, then quantized to a palette. The color count is clamped between 2 and 256. The field starts at 128. A lower count forces more pixels to share entries, which changes the picture: gradients band, and antialiased text picks up hard edges. The delay field is labeled in milliseconds and starts at 0. Zero keeps each frame’s existing delay. A positive number replaces the delay on every frame with that many milliseconds. The decoder had converted GIF centiseconds into milliseconds before this choice, so the kept delay is already in milliseconds. This is not a JPEG quality scale. There is no 0-to-1 quality slider and no DCT quantization. The only “how much” controls are the palette size and the optional delay.
The output is a GIF. Dimensions stay the GIF’s width and height. Frames stay frames. A still GIF stays a one-frame GIF with a new palette. The encoder writes the quantized indices and the palette you just built. It does not run gifsicle, and it does not do a global optimization across frames beyond quantizing each composited frame.
What gets worse as colors drop
At 256 colors a photographic GIF may look close to its already limited source. At 32 colors, large areas posterize. Transparency follows the quantizer’s palette, so a soft shadow that the GIF had already reduced can shift which index is clear. Preview the result before you replace the file you publish. Delay changes timing without changing pixels. A delay of 100 milliseconds on a GIF that used to hold different per-frame timing makes every frame equal. Use zero when only the palette should change.
A second pass
Running the optimizer again quantizes the already quantized frames. You cannot recover colors the first palette threw away by asking for 256 the second time. The second palette is chosen from the damaged frames. Pick the color count once. If the delay was wrong, you can run again for timing, but the pixels will be quantized again too. Keep the previous download if the first palette was the one you wanted and you only needed a timing fix from the original.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

