MP4 to GIF Converter

Why most video to GIF converters look bad

A GIF can only hold 256 colours per frame. A single frame of normal video can hold millions. So every converter has to throw colours away, and how it does that decides whether your GIF looks fine or looks like it was printed on a fax machine.

The lazy way is to use one generic palette, the same 256 colours for every clip. Skin tones go blotchy. Blue skies turn into stripes. Dark scenes get a layer of crawling grain on top. You've probably seen GIFs like that and assumed it's just how GIFs look. It isn't.

The better way takes two passes. First, look at your actual clip and work out which 256 colours it really uses. Then build the GIF from that custom palette. A sunset clip gets lots of oranges and purples. A screen recording gets crisp greys and the exact blue of your app's buttons. Same file format, a very different result.

How this one works

That two-pass palette approach is what runs here, every time, with no setting to find. FFmpeg reads the part of the video you picked, builds a palette from it, then encodes the GIF with light ordered dithering. It also only redraws the parts of each frame that changed, which keeps screen recordings and talking-head clips noticeably smaller.

The other thing I wanted was a way to find the right moment without guessing timestamps. When you choose a file, it plays in a small player on this page. That preview runs from your own device. Nothing is sent anywhere until you press convert. Scrub to where the good bit starts, click the button under the player, and the start time fills itself in.

Once the GIF is ready, it plays on the page right away, with its file size underneath. If it's too big or starts a beat too early, change a setting and run it again before you download anything.

Picking the settings

Start time and length

The start time is in seconds, and decimals work, so 12.5 means twelve and a half seconds in. Length can be anything from half a second up to 15 seconds. That cap is deliberate. A GIF stores every frame as a full image, more or less, so a 30-second GIF at a decent size easily runs past 20 MB and most chat apps won't even preview it.

Honestly, most good GIFs are two to five seconds long. A reaction, a product doing its one clever thing, a bug happening on screen. Shorter loops also feel smoother because the restart is less noticeable.

Frames per second

Video is usually 30 or 60 frames per second. A GIF doesn't need that. 10 fps is the default and it's fine for most things. Go to 15 or 20 if there's fast motion, like a sports clip or a quick UI animation, and the jerkiness bothers you. Drop to 5 or 8 for slow screen recordings, where the page barely moves and you'd rather have a tiny file.

Width

Height follows automatically so nothing gets squashed, and portrait phone clips stay upright. 480 px is the default. It looks sharp in a chat window or a README file and keeps the size sane. 600 or 800 is for when the GIF sits in a blog post or documentation page and people will actually look at the detail. 240 and 320 are for thumbnails and emoji-sized reactions. If your video is narrower than the width you pick, it's left at its own size rather than blown up.

Keeping the file size down

GIF is an old format and it's not efficient. Size grows with width, frame rate and length all at once, so doubling the width roughly quadruples the pixels per frame. When a GIF comes out too heavy, here's the order I'd try things in:

• Cut the length first. Trimming two seconds off a six-second clip saves a third of the file, and you rarely miss them.
• Lower the frame rate. Going from 15 to 10 fps cuts a third of the frames, and most people don't notice on a short loop.
• Then the width. 480 to 400 doesn't sound like much, but it's about 30% fewer pixels.
• Pick a calmer moment. A static background compresses far better than a shaky handheld shot where every pixel changes every frame.

As a rough guide, a five-second screen recording at 480 px and 10 fps often lands under 1 MB. Five seconds of handheld phone footage at the same settings can be 3 to 5 MB, because so much of the picture changes.

Where people actually use these GIFs

If it's the audio you're after, a GIF won't keep it, but the MP4 to MP3 converter pulls the soundtrack out in one go.

A few situations come up again and again. Developers drop a short GIF into a GitHub pull request or issue to show a bug or a new feature, since GitHub plays GIFs inline and a video link means another click. Support teams paste them into help articles and emails, where video often won't embed at all. Marketers use them in newsletters, because most email clients show an animated GIF but block video.

Then there's the fun stuff. Reaction GIFs from your own clips for a group chat or a Slack channel. A pet doing something ridiculous. A few seconds of a goal from your kid's football match. For all of those, the custom palette makes a real difference, because faces and grass are exactly where generic palettes fall apart.

What happens to your video

Need the full clip in a format that plays everywhere instead? The MOV to MP4 converter copies iPhone video into MP4 without re-encoding when it can.

The preview player only reads the file locally. When you press convert, the video is uploaded over HTTPS, cut and encoded on our server with FFmpeg, and the uploaded video is deleted as soon as the job is done, or straight away if it fails. The GIF is kept just long enough for you to download it. No account, no watermark and no logo stamped in the corner.

MP4 is the obvious input, but MOV from an iPhone, WebM from a screen recorder, MKV, M4V and AVI all work too. Sound is dropped, because a GIF has no way to store audio.

When a GIF is the wrong choice

If the clip has to stay a video and only needs to be smaller, the Video Compressor does that and keeps the sound.

I'll be straight about it: for anything longer than about 15 seconds, or anything where sound matters, a GIF is the wrong format. A short MP4 will be a tenth of the size with better picture quality, and every social network converts uploaded GIFs to video behind the scenes anyway. GIF still wins where video can't go, like email, README files, older forums and anything that needs to autoplay without a play button. Use it for those and keep everything else as video.