Turn a stack of still pictures into a loop that plays by itself, or convert a single photo into a classic static GIF. Both jobs share one page: add frames and tune the timing in animated mode, or switch to static mode when an upload form accepts nothing but a single 256-colour image.
Every byte is written by a small GIF encoder built into the page, so frames never leave your device and the preview updates as you change delay, colours or width. All processing runs locally in your browser. Your data is not uploaded to any server. 100% Local
Pick animated mode whenever motion carries the message: a rotating product, a before-and-after flip or a short tutorial sequence. Static mode is the better answer when a portal or profile field only accepts the .gif extension, because the output is a normal single-frame picture that every browser can display. Switching modes keeps your uploaded files, so you can compare both exports without starting over. Remember that animated GIF always repeats a palette per frame, so a ten-frame loop costs roughly ten times the data of one still image.
File size grows with width squared, frame count and palette size. Going from 800 to 400 pixels wide cuts the pixel count by three quarters, which usually matters more than dropping from 256 to 128 colours. For chat stickers, 320 pixels wide and 64 colours is often enough. Turn dithering off for flat illustrations and text, because the added noise compresses badly. Long delays do not shrink the file; fewer frames do.
A three-second GIF that shows a drag-and-drop interaction explains more than five paragraphs of text. Export frames at 640 pixels wide with a 250 millisecond delay, keep the loop short and let it repeat. Documentation hosts often block embedded video but happily render GIF, so this format remains the practical choice for pull requests, internal wikis and bug reports.
Messaging apps and email clients still autoplay GIF while stripping most video. A 320-pixel sticker at 64 colours usually stays below a megabyte, which keeps it inside typical attachment limits. Use a slower delay around 400 milliseconds when the animation should read as a gentle loop rather than a flicker, and test on a phone before sending it to a group.
Older intranet portals, ticketing systems and avatar pickers sometimes accept only .gif regardless of the actual content. Static mode writes a regular 256-colour GIF from a JPG, PNG or WebP, so the picture passes validation while modern browsers still display it normally. Keep a PNG copy as well, because the GIF version loses transparency and fine gradients.
GIF stores at most 256 colours per frame, so every picture is reduced to a palette before encoding. Smooth skies and skin tones are the first to show bands. Raising the colour count to 256 and enabling Floyd-Steinberg dithering softens the transition, at the cost of a slightly larger file.
An animated GIF repeats a full palette and compressed frame for every image, and LZW compression is weaker than JPG or WebP. Ten photos at 800 pixels wide can easily reach several megabytes. Lowering the maximum width, reducing the frame count or dropping to 64 colours usually cuts the size the fastest.
No. Frames are painted onto a white background before quantization, so everything is opaque in the exported file. GIF only supports fully transparent or fully opaque pixels anyway, which makes it unsuitable for soft shadows, logos with anti-aliased edges or rounded avatars.
There is no fixed limit because nothing is uploaded, but each frame is decoded and quantized in memory. Large photos and long sequences slow the preview and can exhaust memory on phones. Keep frames near 800 pixels wide and below roughly 40 images for reliable results.
No. GIF has no audio, no real timeline and a delay resolution of one hundredth of a second, so playback looks choppy next to MP4 or WebM. It remains useful where autoplay video is blocked, such as documentation pages and chat previews. Check important exports yourself before publishing.