How to Convert a Video to GIF Online — Quality Settings Explained
Animated GIFs are everywhere — in Slack messages, GitHub issues, Notion docs, and tweets. They loop automatically, play without a video player, and embed directly in any document. But creating a good GIF from a video involves a few decisions that affect both quality and file size. This guide explains the options and how to get the best result.
GIF vs Video: When to Use Each
Use a GIF when you need something that plays inline without a video player — embedded in a Notion page, attached to a GitHub issue, included in a marketing email, or shared in Slack. GIFs loop automatically and are universally supported without any plugin or player.
Use a video (MP4) when quality or file size matters. A 10-second clip at 480 px might be 1–2 MB as MP4 but 10–20 MB as GIF. For anything longer than 15 seconds, or anywhere that accepts video files, MP4 is almost always the better choice.
- Slack, Teams, Notion, GitHub — use GIF for inline playback
- YouTube, TikTok, Instagram — use MP4 (much smaller, much better quality)
- Email marketing — GIF works, but keep it under 5 MB to avoid spam filters
Choosing Frame Rate: Smoothness vs File Size
Frame rate is the single biggest lever for controlling GIF file size. Each frame in a GIF is stored as a separate compressed image, so reducing FPS cuts the number of stored frames proportionally. A 10-second clip at 20 fps stores 200 frames; at 10 fps it stores 100; at 5 fps it stores 50.
For most reaction GIFs, memes, and product demos, 10 fps is the sweet spot — smooth enough to read clearly, small enough to share comfortably. Use 5 fps for slow-moving content like screencasts or slideshows. Use 15–20 fps only when smooth motion is essential, such as a cursor-heavy interface demo.
- 5 fps: screencasts, slides, slow motion — maximum compression
- 10 fps: default for most GIFs — good balance of quality and size
- 15 fps: product demos, animations with visible motion
- 20 fps: only when smoothness is critical — file size grows fast
Choosing Width: Resolution vs File Size
Width controls the pixel dimensions of the output GIF (height is scaled proportionally to maintain aspect ratio). Narrower GIFs have fewer pixels per frame, which dramatically reduces file size — halving the width roughly quarters the total pixel count.
480 px is the recommended default for most sharing contexts. It looks sharp on modern screens without being excessively large. Use 240–320 px for messaging apps or anywhere file size is tight. Use 640 px when the GIF will be displayed at larger size, such as embedded in a blog post or documentation page.
- 240 px: smallest files, good for mobile-first messaging contexts
- 320 px: compact but readable — a good choice for Slack or Teams
- 480 px: default — sharp on most screens, manageable file size
- 640 px: for larger embeds — use sparingly due to file size
Why This Converter Produces Better-Quality GIFs
Most simple GIF converters use a fixed 256-colour palette shared across the entire clip. This works adequately for simple graphics but produces obvious colour banding and dithering artefacts on photographic content.
MediaFormatter uses FFmpeg's two-pass palette approach. In the first pass, all frames in your clip are analysed to build a custom colour palette optimised specifically for the colours in your video. In the second pass, the GIF is encoded using that palette. The result has far less banding and more accurate colours than converters that use a generic palette.