GIFs are bigger than equivalent MP4s, but they auto-play with no controls, render where videos can't, and read as part of the message. For short reactions, demo loops, and embed-hostile surfaces, they're still the right tool.
No play button, no codec negotiation, no autoplay policy fighting the browser. Drop a GIF in any chat, README, or email and it starts looping the moment it loads.
A two-pass palettegen / paletteuse encode picks the best 256 colors for your specific clip — far cleaner than single-pass converters that use a fixed web-safe palette.
The conversion runs in this browser tab using ffmpeg.wasm. Your video is never uploaded, never queued, never logged. Close the tab and nothing remains.
GitHub renders GIFs inline in markdown. Videos render as a download link. If you want your README to demo the feature instead of asking a reader to download a clip, GIFs are still the answer.
Most email clients block HTML5 video and strip half of any modern markup. An animated GIF is the lowest-common-denominator inline animation that still actually plays in Outlook, Gmail, and Apple Mail.
Reddit, Hacker News, Lobste.rs, and most forum software allow image embeds but not video. GIFs render where MP4 links sit unwatched at the bottom of a thread.
A 2-second reaction GIF carries the punch of an inline animation without dragging in a video player UI. For under-3-second clips, the file-size argument for MP4 mostly evaporates anyway.
Yes. There's no signup, no watermark, no daily limit, and no paid tier on this tool. The entire conversion runs in your browser, so the only cost to anyone is your CPU. We don't show ads on this page.
No. The conversion happens locally inside your browser tab using ffmpeg.wasm — a WebAssembly build of the same ffmpeg used by professional video tooling. Your file is never uploaded, never copied to our servers, and never logged. You can verify by opening DevTools → Network and watching the conversion: there are no requests for your file.
MP4, MOV (QuickTime), WebM, and MKV (Matroska) — the four most common video container formats. The tool magic-byte sniffs each file before starting, so renaming a non-video file to .mp4 is caught early instead of crashing the encoder.
GIFs auto-play with no controls, render natively in places that don't load video (GitHub READMEs, RSS readers, some email clients, older forums, embed-restricted comment threads), and feel like part of the message rather than a player widget. They're the right tool for short reaction clips, demo loops in documentation, and chats where the visual punch of an inline-playing animation matters more than file size.
There's no hard cap, but in practice browsers struggle past ~100 MB because the entire file has to fit in WebAssembly memory. For best results, keep clips under 20 seconds — GIFs grow quickly with duration, and short clips look more like animations than slow-motion sequences.
The output is 480px wide (preserving aspect ratio) at 12 fps. That's the sweet spot for size and smoothness — wider GIFs balloon in size without much perceived quality gain because the format caps at a 256-color palette regardless of resolution.
Two-pass. ffmpeg.wasm runs palettegen first to compute the optimal 256-color palette for your specific clip, then paletteuse with Bayer dithering to apply it. The result is dramatically cleaner than single-pass converters that use a fixed web-safe palette — colors look like the source instead of a 1995 desktop screenshot.
The first time you convert anything in this tab, the browser downloads about 25 MB of WebAssembly (the ffmpeg core). After that it's cached, and every subsequent conversion in the same session starts instantly. If you reload the page or open a private window, the download repeats.
We have a dedicated tool for that at vidsandgifs.com/tools/gif-to-mp4. Drop your GIF there and get a 480p MP4 typically 5–20× smaller than the source.
This converter is a free side-tool. The main vids&gifs product is a private, cross-chat library: upload your GIFs and short videos once, and send them inline from any Telegram chat (@vidsandgifsbot) or any Discord channel (/gif) — no copy-pasting links, no rebuilding folders per platform.