GIF Maker
Turn Any Short Video Clip Into a Looping GIF

For most web use cases, 15 FPS is the sweet spot. Human perception of smooth motion begins around 12-15 frames per second, so a 15 FPS GIF feels fluid for everyday reaction clips, product demos, and social posts while keeping file sizes manageable. Jump to 24 FPS when your source footage contains fast-moving content like sports, particle effects, or dance clips where smoothness is critical to the message. Drop to 10 FPS for simple looping backgrounds, typography animations, or logo reveals where the slight choppiness is imperceptible and the bandwidth savings are significant - particularly for mobile users on constrained data plans. One important nuance: the GIF format does not support fractional frame timings the way video containers do, so 24 FPS is stored as approximately 41.6ms per frame delay, which most browsers round to the nearest whole millisecond. This is generally invisible to viewers.

Graininess in GIFs is caused by a process called dithering. When a conversion tool cannot accurately represent a color from your video using the limited 256-color GIF palette, it uses a checkerboard-like pattern of nearby colors to simulate the missing shade. With a poorly chosen palette, this dithering becomes visually coarse and distracting - especially in smooth gradients like sky backgrounds, skin tones, or motion-blurred objects.

The fix is a scene-specific palette generated by FFmpeg's palettegen filter. Instead of using a single universal palette, this filter scans every pixel in your chosen clip segment and applies a statistical algorithm (median-cut color quantization) to find the 256 colors that minimizes color error across the entire animation. When the paletteuse filter then applies this tailored palette, each pixel is mapped to its statistically nearest color, resulting in dramatically smoother gradients, richer saturation, and far less visible dithering noise.

Most online video conversion tools work by uploading your file to a remote server where the processing happens. This means your private video content - which may include personal footage, unreleased product demos, proprietary brand materials, or sensitive event recordings - is transmitted over the internet and temporarily stored on hardware you have no control over. Many of these services retain files for days or longer for compliance reasons, and their privacy policies may allow use of content for service improvement or advertising purposes.

This tool uses WebAssembly (WASM), which compiles the FFmpeg video processing engine into a format that runs natively inside your browser's secure sandbox. No network request containing your file is ever made. Processing happens entirely on your own CPU using allocated browser memory, and when you close the tab that memory is released. This is the same privacy guarantee as offline desktop software, achieved entirely in-browser. It is the technically correct approach for any scenario where file confidentiality matters.

A GIF file's byte size is proportional to the total number of pixels it must store across all frames. A 640px wide GIF contains exactly 4x as many pixels per frame as a 320px wide GIF (640 x 360 = 230,400 pixels vs 320 x 180 = 57,600 pixels). Multiply this across every frame in a 5-second, 15 FPS animation and you have 75 frames - meaning the 640px version must encode roughly 17.3 million pixels versus only 4.3 million in the 320px version. LZW compression (the algorithm GIF uses internally) helps reduce redundancy but cannot compensate for raw pixel count at scale. For blog embeds, social media thumbnails, or email newsletters where recipients may be on mobile data, a 480px output delivers a visually sharp result at a fraction of the bandwidth cost. Reserve 640px output for hero images on high-resolution desktop layouts where the full pixel density is actually visible to viewers.

WebAssembly is a low-level binary instruction format standardized by the W3C that allows code written in C, C++, Rust, and other compiled languages to run inside a web browser at near-native CPU speed. Traditionally, JavaScript was the only language browsers could execute, which limited the computational complexity of browser-based applications. WebAssembly removes that barrier.

FFmpeg is the world's most widely used open-source multimedia processing library, written in C and used by YouTube, VLC, HandBrake, and thousands of other professional tools. The ffmpeg.wasm project compiles the entire FFmpeg engine to WebAssembly so it can run directly in your browser. When you click "Generate GIF" on this page, the browser loads the FFmpeg WASM binary (cached after first load), mounts your video file into a virtual in-memory filesystem, executes the same powerful filtergraph commands a professional engineer would run on a terminal, and writes the output GIF back into that in-memory filesystem where JavaScript reads it and hands you the download. No servers. No uploads. No waiting.