Video to GIF Converter
Turn a video into an animated GIF right in your browser. Choose the frame rate and size, nothing is uploaded.
- Free, no account
- No watermark
- No usage limit
About the Video to GIF
Drop in an MP4, WebM, or MOV, pick a frame rate and a width, and you get an animated GIF back in a few seconds. It's free, there's no sign-up, no watermark, and your video never leaves your computer, because there's no server to send it to.
Nearly all the other GIF sites push your video up to a server and drop you in a queue, so every single attempt costs another upload and another wait. People settle for whatever comes back on the first try, and that first try is almost always too big. This tool converts right on your device, so a retry is basically free. Change the frame rate, hit Create again, check the size, tweak again. That back-and-forth is the whole game, because small is the whole target, and the only dependable way to get there is to try a setting and try another.
How to use
- Drop your video on the box or click to browse. MP4, WebM, and MOV all load.
- Set the frame rate. 12 is a sane default that works for most clips. Leave it there unless the result looks choppy.
- Set the width in pixels. 480 is fine for chat, 640 for a demo. You rarely want more than that.
- Click Create GIF. You'll see it pull frames one at a time, and that counter is worth a look, because the number of frames it lands on is basically your file size.
- Check the preview and the size it reports. Too big or too rough? Change one number and convert again.
- Download when you like it. Nothing was uploaded and nothing sits on a server.
Why your GIF is too big (it's the frame count)
Almost every oversized GIF traces back to a single cause: too many frames. GIF stores each frame as its own little picture with no memory of the frame before it, so the file grows in near lockstep with how many frames there are. That one fact tells you which knobs actually matter.
Trimming the clip is the biggest lever, even though this tool doesn't trim for you. Length and frame count move together, so a ten second clip is a third the size of a thirty second one at the same settings. Before you convert, cut the source down to the few seconds that tell the story, then bring that shorter clip here. Most GIFs only need three to ten seconds anyway. A bug repro, a UI interaction, a reaction, none of them need to run half a minute.
Frame rate is the next lever, and it's the one people get wrong. Your source is probably 30 or 60 fps, but a GIF almost never needs that. At 12 fps a screen recording or a talking-head clip still looks smooth, and you've just cut the frame count in half versus 30. Slow footage, a gentle pan, a two-step click, is fine at 10. Push above 15 only when the motion is genuinely fast, and if it's that fast, honestly a video is the better format. Dropping the frame rate costs you almost nothing, since the file shrinks, conversion speeds up, and nobody watching tends to notice.
Width matters too, but only up to a point. Nobody views a GIF at full resolution. Slack, Discord, GitHub, and most chat apps render it around 400 pixels wide no matter what you feed them. Export a 1080 pixel wide GIF that gets shown at 400 and you've paid for a much heavier file that looks identical on the screen. Cap it at 480 for chat, 640 for a demo, and match the width to where the GIF is going rather than to your source. If your result looks soft, a wider setting is almost never the fix. That's the color palette, which the FAQ covers.
A recipe that works for most screen recordings and social clips: trim to five to ten seconds, set 12 to 15 fps, and cap the width around 480 to 640. That combination usually lands a small, sharp GIF instead of a bloated one that stutters while it loads. And if you do feed it something long at a high frame rate, the tool caps the total frames it will pull and samples evenly across the clip, so you get a usable GIF instead of a frozen tab or a two hundred megabyte download. Better to trim first, but the guardrail is there.
When a video beats a GIF
A lot of oversized-GIF problems are really "this should never have been a GIF." Before you fight the settings, ask whether you need a GIF at all.
A GIF wins in one narrow situation: a short, silent, looping clip going somewhere a video player is awkward or missing, like a chat message, a GitHub issue, inline docs, or an email. There the automatic loop and the play-anywhere behavior are worth the size cost. Everywhere else a plain MP4 is the better pick. It's far smaller for the same footage, it keeps full color instead of crushing down to 256, it stays crisp, and it can carry sound. On a web page a muted autoplaying MP4 looks exactly like a GIF to the viewer at a fraction of the weight. Reach for a video once the clip runs past fifteen seconds or so, or when you need audio, full color, or you're posting to a page rather than a chat box.
Frequently asked questions
Is my video actually private?
Yes. The whole conversion happens on your device, so the file is never sent anywhere and nothing is stored on a server. There's no account, no logging, no "our end" that ever sees your footage. That makes it fine for internal work recordings or personal clips you would rather not hand to a website. It does not work offline, though, and that is a separate claim worth keeping apart from this one rather than folding into it. Two pieces arrive only when you press Create, the video reader at 632,175 bytes and the GIF writer at 30,101, and checking the built page confirms neither one is among the scripts that load with it. Press Create with nothing connected and you get an error instead of a GIF. After both have arrived they stay in your browser, so a second conversion really does run with the wifi switched off.
Which video formats can I feed it?
MP4, WebM, and MOV are the safe bets, with MP4 the most universal. The tool leans on your browser's own decoders, so the rule of thumb is simple. If your browser can play the file, it can usually convert it. Got an odd format that refuses to load? Run it through any basic video converter to MP4 first, then bring it back here.
Can I trim the clip inside the tool?
Not yet. It converts whatever video you hand it start to finish, so the cleanest way to control length is to trim the source before you drop it in. Your phone, your computer's built-in clip editor, or any free video app can cut it down in a few clicks. Since length drives file size more than any other setting, that extra step is usually the one that saves you the most.
It told me my browser isn't supported. Now what?
The tool needs a modern video engine that older browsers lack, so instead of failing quietly it tells you. The fix is to update your browser or open the page in a current version of Chrome, Edge, or desktop Safari. On an up-to-date desktop you're almost certainly covered.
Why does my GIF look grainy or washed out?
That's the 256-color limit, and it's baked into the GIF format, not something the tool got wrong. A full-color video has to be squeezed down to 256 shades, which shows up as banding in gradients, skies, and soft shadows. Flat footage like an app recording survives it well. Photographic or colorful clips suffer the most, and for those a video will always look cleaner. Keeping the clip short and the motion simple helps a little.
Does the GIF keep the sound from my video?
No, because GIF has no audio track at all. Whatever sound was in your source is dropped, and only the picture carries across. So you never need to mute anything first, and if a clip only makes sense with its audio, that's your cue to keep it as a video.
Is there any cap on size or number of conversions?
None on file size, and none on how many times you convert. No watermark, no daily limit, no sign-up, because the work runs on your own machine instead of a metered server. There is one real ceiling, and it's on frames rather than seconds: a single GIF tops out at 300 of them. Feed it something longer and the tool samples evenly across the whole clip instead of stopping partway, then tells you underneath the preview which frames it kept and what frame rate that leaves you with. The GIF still runs at the speed the video did. Everything else that limits you is practical rather than imposed. A very long or very large clip makes a very large GIF that's slow to process and awkward to share. If you're wrestling a 40 second video into a GIF, trimming it down first is the honest answer.