Image Converter
Swap between JPG, PNG, WEBP, GIF, TIFF, ICO, CUR, and BMP with full metadata control and instant previews.
Transcoding batch...
Drop images here or click to browse
Supports HEIC, AVIF, common RAW, ICO/CUR, ZIP bundles.
Conversion queue
- Queue files to preview status, estimated weight, and output names.
Conversion preferences
Drop files to see live previews.
Files disappear from our servers right after we hand you the converted download links.
Converted files will land here with preview thumbnails, metadata, and download buttons.
Do you want to...
The GIF converter turns still images and animated WEBPs into GIF files in your browser. Upload JPG, PNG, WEBP, AVIF, HEIC, BMP, TIFF, or animated WEBP. The output is a GIF with a 256-color adaptive palette per frame, animation preserved when the source is animated, and original frame timing and loop count carried through. Up to 50 files per batch, 40 MB per file, no registration.
How GIF Conversion Works
GIF is a lossless format with one hard constraint: each frame is limited to 256 distinct colors. When the source is a graphic, screenshot, icon, or any image with a small color count, the conversion is effectively lossless because all the original colors fit in the palette. When the source is a full-color photograph, the converter quantizes the millions of source colors down to the best 256 using an adaptive palette computed per frame. The result keeps the overall image recognizable but may show visible banding in smooth gradients (skies, skin tones, soft shadows).
Animation is handled frame-by-frame. An animated WEBP input is decoded into its component frames with their original timing values and loop count. Each frame is independently quantized to its own 256-color palette and re-encoded into the GIF stream. The reassembled animation plays at the same speed and loops the same way as the source. Still-image inputs produce a single-frame GIF at the source dimensions.
When GIF Is the Right Output Format
GIF earned its place in two specific situations. First, when the destination environment cannot reliably play modern formats. Many email clients still strip or transcode WEBP and AVIF but always render GIF correctly. Slack, Discord, Reddit, and most chat platforms accept GIF without conversion. Documentation tools (Confluence, Notion, GitHub wikis) embed GIF reliably where embedded video requires a player. Second, when the visual content suits a 256-color palette: pixel art, simple animations, screen recordings of a UI, reaction images, memes, and any graphic that does not depend on photographic gradients.
For photographs, animated GIFs of camera footage, or any modern web destination, GIF is almost always the wrong choice. Converting to WEBP typically produces files that are 60 to 80 percent smaller than the equivalent GIF at the same visual quality, and most modern browsers and chat apps now render WEBP natively. AVIF goes smaller still. The right rule: pick GIF when you need it to play in a hostile environment, pick WEBP or AVIF when you control the destination.
Inputs the GIF Converter Accepts
- JPG and JPEG: typical photo formats. The conversion quantizes color to 256 levels per frame, so expect visible banding on smooth gradients.
- PNG: the most common conversion target. Logos, icons, screenshots, and UI elements convert losslessly when the source has 256 or fewer distinct colors, which is most of them.
- WEBP: both still and animated WEBP. Animated WEBPs are unpacked frame-by-frame with timing preserved.
- AVIF: still images only. AVIF animation is not yet a common input.
- HEIC and HEIF: iPhone photos. Converted through the same palette-quantization path as JPG, with the same gradient-banding tradeoff.
- BMP and TIFF: legacy and archival sources, often containing screenshots or scanned graphics that suit a 256-color palette well.
The output is always GIF. If you need to convert in the opposite direction (GIF to JPG, GIF to PNG, GIF to WEBP), use the main image converter with GIF as the source. To shrink an existing GIF without changing the format, use the image compressor; converting to animated WEBP usually halves the file size or better.
Batch Conversion and Privacy
Each conversion runs in memory on the server. Files are decoded, palette-quantized, encoded as GIF, and returned to the browser as base64 inside the JSON response. Nothing is written to disk, indexed, logged, or cached. As soon as the response is sent, the buffer is released and there is no copy of the file left to recover. The same applies whether you upload a single image or 50 at once, and whether the upload is direct files or a ZIP archive that gets unpacked server-side. Per-file size limit is 40 MB. Outputs are returned individually or packaged into a single download ZIP for batches above one file.
FAQ
GIF is limited to 256 colors per frame, while a typical photograph contains millions of distinct colors. The converter picks the 256 colors that best approximate the original using an adaptive palette, but smooth gradients (skies, skin tones, soft shadows) become visible bands because there is no longer a continuous range of intermediate values. This is a fundamental limit of the GIF format. For photographs, JPG, WEBP, or AVIF will look much better and the file will be significantly smaller.
Yes. When the source is an animated WEBP, each frame is decoded with its original timing and the animation's loop count is read from the source. After per-frame palette quantization the frames are reassembled with the same timing values, so the output GIF plays at the same speed and loops the same number of times as the original. Still images become single-frame GIFs at the source dimensions.
Two reliable ways. First, reduce the dimensions: a 600 by 400 GIF is roughly a quarter the size of a 1200 by 800 GIF with the same content, since pixel count scales the file size linearly. Use the image resizer before converting. Second, convert to animated WEBP instead of GIF: the same animation typically becomes 60 to 80 percent smaller with no visible quality difference, and modern browsers and chat apps render it natively. The image compressor handles the GIF to animated WEBP conversion directly.
Yes, with a caveat. GIF supports single-color transparency: one specific palette index is marked as "see through" and renders as the background. Smooth alpha gradients (a soft drop shadow, an anti-aliased edge against an unknown background) cannot be represented in GIF and end up either fully transparent or fully opaque depending on the threshold. If you need clean alpha for icons or logos with soft edges, PNG or WEBP is the better target. If you only need on/off transparency for a hard-edged graphic, GIF works fine.
Each file must be under 40 MB and each batch can include up to 50 files. ZIP archives are unpacked server-side and each entry inside counts against the same 50-file limit. Outputs are returned individually, and for batches above one file they can be repackaged into a single download ZIP. Larger jobs need to be split into multiple batches; the converter settings persist between batches.
No. Files are streamed to the conversion endpoint, decoded into a memory buffer, palette-quantized, re-encoded as GIF, and returned in the response. Nothing is written to disk, indexed, logged, or cached. The buffer is released as soon as the response is sent, so there is no copy left to recover. The free tools require no registration and do not track which images you have converted.
Use GIF when the destination cannot reliably play modern formats (email clients, older forums, certain chat platforms) or when the image content fits a 256-color palette naturally (pixel art, UI screen recordings, simple animations, reaction images, memes, icons). Avoid GIF for photographs, gradient-heavy graphics, and any modern web context where WEBP or AVIF will work. Those formats produce dramatically smaller files at much higher quality.