MOV to GIF Converter

How to Convert MOV to GIF Online

1. Upload Your MOV File: Drag and drop or click "Add Files" to select a MOV. iPhone clips, QuickTime screen recordings, ProRes exports, and DSLR/mirrorless MOV files all work. Batch conversion is supported.
2. Set the Frame Rate and Resolution: Pick a framerate from 1-50 fps (10-15 fps is the sweet spot for shareable GIFs — 50 fps is the maximum any browser will play). Choose a preset resolution, scale by percentage, set width with kept aspect ratio, or enter a custom width × height. Lower fps + smaller width = much smaller file.
3. Tune Image Quality and Color Reduction (Optional): Adjust Image Quality (1-100%) or enable "By Color Reduction + Dither" to cap the GIF palette at 2-256 colors. 64-128 colors is plenty for screen recordings; 256 for photographic content. Lower palette = smaller file with mild banding.
4. Pick a Time Range and Convert: Choose a specific frame, extract multiple frames as a sequence, or convert the full clip. Click Convert and download the animated GIF — no sign-up, no watermark, processed on our servers.

Why Convert MOV to GIF?

MOV is Apple's QuickTime container — it's what iPhones record by default, what macOS screen recordings export, and what most Apple-ecosystem cameras and editors output. The video inside is H.264 if your iPhone is set to "Most Compatible" or HEVC/H.265 if it's set to "High Efficiency" (the iOS default for recent devices). GIF is the opposite of all that: an 8-bit, 256-color, 1987-era image format that nonetheless plays inline on every device, every browser, every chat client, every email reader, every README on GitHub. The conversion exists because the universal-playback property of GIF is still uniquely valuable for short, soundless loops. Common reasons to convert:

• iPhone clips for messaging and social — iMessage, WhatsApp, Discord, and Twitter all render GIFs inline. A 3-second iPhone MOV becomes a tappable reaction GIF that auto-plays in every client.
• QuickTime screen recordings for GitHub READMEs, pull requests, and docs — GitHub renders animated GIFs inline in markdown; it does not render MOV. A 5-second QuickTime capture of a bug, feature, or UI flow embeds directly in a PR description.
• Slack, Notion, Confluence demos — Embedded video requires a player widget. A GIF plays in the message body, in mobile, and even when previewed in a notification.
• Reaction GIFs and memes for Reddit, Discord, X — Twitter/X transcodes uploaded GIFs to its own video player, but every other client still wants a real GIF.
• Archival of short loops — Every image viewer made since 1990 can decode GIF. MOV still requires a codec-aware player (H.264 is universal; HEVC isn't on older or Windows systems without the paid extension).
• Email-safe motion — Most email clients block embedded video but render animated GIF inline. A short product demo or bug repro can land in an email without an attachment-download step.

MOV vs GIF — What You're Trading

A 2 MB HEVC clip from an iPhone can easily become a 20 MB GIF at full resolution. This is normal — GIF stores every pixel of every frame with a 256-color palette and basic LZW. Drop resolution, frame rate, and palette size to bring it down. If you want short loops that stay small AND look good, MOV to WebP compresses 5-10× better than GIF for animated content (though support is browser-only).

Settings Cheat Sheet — Match Your Platform's Cap

Discord publishes a 10 MB free-tier upload cap, but anything over ~256 KB stops auto-playing inline. Slack custom-emoji uploads must fit in 128 KB total and animated emoji are limited to 50 frames. Twitter/X documents up to 15 MB for GIFs on desktop and around 5 MB on mobile clients.

Frequently Asked Questions

Will this work on iPhone HEVC (.mov) recordings, not just H.264?

Yes. iPhones set to "High Efficiency" record HEVC/H.265 inside a MOV container; iPhones set to "Most Compatible" record H.264 inside a MOV container. The converter decodes both and writes out a standard animated GIF. If the HEVC clip won't play on a Windows machine before conversion, the GIF will still play everywhere afterward — that's part of the appeal.

Why is my GIF so much larger than the MOV?

Because GIF was never designed for video. HEVC and H.264 use inter-frame compression (each frame references the previous), motion vectors, and 24-bit color. GIF stores every frame as an independent 256-color image compressed with LZW — a lossless algorithm from 1987. A 2 MB iPhone HEVC clip routinely becomes a 20 MB GIF at full resolution. The fix is to reduce width to 480-720 px, drop framerate to 10-15 fps, and cap the palette at 64-128 colors. Those three changes typically shrink the output 5-10× with little perceptual loss.

What frame rate should I pick — and why is 50 fps the ceiling?

GIF stores inter-frame delays in centiseconds (1/100 sec) as whole integers, so the format's theoretical maximum is 100 fps. In practice, Chrome, Firefox, and Edge clamp delays below 0.02 sec (50 fps) — anything faster is forced to ~10 fps by the browser. So 50 fps is the real-world ceiling. For shareable content, 10-15 fps is the sweet spot: smooth enough to read motion, half the file size of 30 fps. 8-10 fps is fine for UI demos. 24-30 fps only helps for slow-motion or sports content.

How do I make the GIF small enough for Discord auto-play (256 KB)?

Drop width to 320-480 px, framerate to 10 fps, palette to 32-64 colors, and trim to 2-3 seconds. For shorter clips, you can keep the width and lose the palette; for longer clips, the opposite. Discord's documented free-tier upload cap is 10 MB, but inline auto-play stops working above roughly 256 KB. If the source is longer than a few seconds, trim with video cutter first.

Will the GIF preserve transparency from the MOV?

Almost never. MOV files from iPhone or QuickTime screen recording don't carry an alpha channel — they're opaque. ProRes 4444 MOVs do support alpha, but GIF supports only 1-bit transparency (a pixel is either fully transparent or fully opaque, no antialiased edges). Soft / feathered edges in the MOV will look hard-edged in the GIF if any transparency is mapped at all.

Can I extract a single frame instead of converting the whole clip?

Yes. The "specific frame" option grabs one still at a chosen timestamp; "multiple frames" extracts a sequence at a chosen framerate (every 1, 2, 3, 4, 5+ seconds, or a set count). If you only need still frames, MOV to JPG and MOV to PNG give you better quality than a one-frame GIF — full 24-bit color instead of a 256-color palette.

Should I just convert to MP4 or WebP instead of GIF?

If the recipient can play it, yes. MOV to MP4 keeps full color, frame rate, and audio at a fraction of GIF's size — Twitter/X actually transcodes uploaded GIFs to MP4 internally for this reason. MOV to WebP produces animated images 5-10× smaller than GIF with full 24-bit color, and modern Chrome / Firefox / Safari / Edge all render it inline. Stick with GIF when the destination is GitHub markdown rendered outside a browser, an older email client, Slack custom emoji, or any context where you can't guarantee a video player.

Can I batch convert multiple MOV files at once?

Yes — drop in as many MOV files as you want. Each converts in parallel withon our servers. Download individually or as a ZIP. Frame rate, resolution, and palette settings can apply to all files or be set per-file. There's no file count cap and no watermark.

What about audio in the source MOV?

GIF has no audio track, so any sound in the MOV is silently dropped during conversion. If the clip relies on audio, convert to MOV to MP4 or MOV to WebM instead. If you want a silent visual loop AND a separate audio file, convert twice — once to GIF for the loop, once to MP3 with MOV to MP3 for the audio.