GIF Maker

No. The frames are read with local object URLs, drawn onto an in-memory canvas, and encoded to GIF by a JavaScript encoder running in your browser tab. There is no upload, no queue, and no server-side copy of your images - the Network tab in DevTools stays quiet during encoding. This is different from our video-to-GIF converter, which needs a server because video decoding requires FFmpeg.

This tool starts from still images (photos, screenshots, rendered frames) and animates them. The video-to-GIF converter starts from a video file and extracts its frames on our server because browsers cannot decode arbitrary video codecs reliably. If your source is a set of images, use this tool and nothing leaves your device.

The delay is the time each frame stays on screen, in milliseconds. For a slideshow feel use 500-1000 ms. For smooth motion from a burst of photos use 50-100 ms. Note that browsers clamp very small values: delays under about 20 ms are rendered at roughly 100 ms by most browsers, so the tool enforces a 20 ms minimum.

The GIF format is limited to 256 colors per frame. The encoder builds an optimized palette for each frame with pairwise-nearest-neighbor quantization, which works well for screenshots, charts and flat graphics but visibly bands smooth photographic gradients. For photo-heavy animations a video format like MP4 or WebM preserves quality at a fraction of the file size.

No watermark, ever. The tool accepts up to 50 frames at up to 20 MB per image. The practical limit is file size: a 50-frame GIF at 800 px can reach tens of megabytes, so start with 480 px and increase only if you need the detail.

No. The output canvas takes its aspect ratio from the first frame, capped at your chosen maximum size. Every other frame is scaled to fit inside that canvas, centered, with white filling any leftover space. For the cleanest result, crop your images to the same aspect ratio first - our image cropper does that in a few clicks.