How to Make a GIF from a Video: Size, Frame Rate and Loop Tips

GIF is older than the web. CompuServe published the first version, GIF87a, in 1987 as a way to send still pictures over dial-up connections, and the 1989 revision, GIF89a, added the two features that made animation possible: a delay value for each frame and one transparent color. Looping came later, in 1995, when Netscape Navigator 2.0 started reading a small application extension that says how many times to repeat. Every animated GIF today is still a GIF89a file with that block inside, which is why it plays in practically every browser and mail client.

Inside, a GIF is a stack of indexed images. Each frame points at a color table of at most 256 entries, so a frame can show 256 different colors and no more, even though the video it came from had millions. The pixels are then compressed with LZW, a lossless dictionary method that works well on flat areas of a single color and badly on photographic noise, grain and gradients. Nothing is thrown away by LZW itself; the loss happens earlier, when millions of colors are squeezed into the palette.

There are two other things a GIF cannot hold. It has no audio track of any kind, so the sound in your video simply disappears. And its timing is coarse: delays are stored in hundredths of a second, and most browsers treat a delay of 0 or 1 hundredth as 10 hundredths, so a GIF built at 50 fps or faster plays slower, not smoother. In practice, 10 to 25 fps is the useful range.

A modern video codec such as H.264 stores a full picture only now and then and describes most frames as small changes from the one before. GIF can do a little of that by updating only a rectangle of the previous frame, but it has nothing like motion prediction. As soon as the camera moves, almost every pixel changes, and each frame is stored close to in full. That is why a 2 MB phone clip can become a 15 MB GIF, while a screen recording of a mouse moving over a still window stays tiny.

The size of a GIF is roughly width times height times frames, with a discount for how much stays still between frames. That makes the levers easy to rank. Length cuts frames one to one: four seconds instead of eight halves the file. Width cuts pixels quadratically: going from 640 px to 320 px leaves a quarter of the pixels in every frame. Frame rate cuts frames linearly again, and 12 fps holds up surprisingly well for gestures and faces. Fewer colors helps less than people expect, usually 10 to 30 percent, because LZW cares more about repeating patterns than about the palette size.

Dithering is the trade-off that confuses most people. It scatters dots of nearby palette colors to fake the shades the palette lacks, which hides banding in skies and skin but adds the kind of fine noise LZW compresses poorly. Turn it off for screen recordings, cartoons and UI demos, where flat color is the truth anyway, and keep it on for real footage. Cropping is the last lever: cutting away a static border or a black letterbox removes pixels without touching the subject.

Most GIFs that get shared are a single beat: a reaction, a goal, a button click and the screen that follows. Watch the video once with a stopwatch in your head and note the second where the beat starts and the second where it has clearly landed, then add a few frames on each side so the loop does not feel clipped. If the source is long, cut the range out first with a video trimmer and work on the short file;. On a converter, typing the times into Start at and End at in seconds or minutes:seconds does the same job without a separate step.

Think about where the GIF starts playing, too. Many chat apps and mail clients show the first frame while the file loads, and Outlook for Windows from 2007 to 2016 shows only the first frame and never animates. Start on a frame that makes sense as a still picture, not on a blur in the middle of a pan. If the message of the GIF is a caption or a result, hold that final moment for half a second by extending End at, so viewers can read it before the loop starts again.

Where the GIF is going sets the budget before any setting does. Discord lowered its free upload limit to 10 MB per file in 2024, and that is the number most people hit first; Nitro Basic raises it to 50 MB and Nitro to 500 MB. GIPHY accepts uploads of up to 15 seconds and 100 MB. X takes GIFs up to 15 MB and turns them into a looping video on upload, and Reddit accepts GIFs up to 100 MB but also serves them as video. Slack takes files of up to 1 GB, but custom emoji must stay under 128 KB, which means a tiny width, a short loop and few colors.

Email is the odd one out. Gmail allows 25 MB of attachments per message and Outlook.com 20 MB, but a GIF placed inline in the body of a newsletter or signature should stay well under 1 MB so the message opens quickly on mobile data. In chat, aim for half the limit rather than right under it, since the people receiving it may be on slow connections. The numbers below were current in 2025; check the service's help page when a file sits right on the edge.

The reason X converts every uploaded GIF into an MP4, and has done so since 2014, is bandwidth. The same five seconds that weigh 4 MB as a GIF typically fit in a few hundred kilobytes as H.264, with full color instead of 256 shades and no dithering noise. GIPHY and Tenor do the same: the GIF button in your keyboard usually fetches a small MP4 or WebP. So the honest question is not how to make the best GIF, but whether the place you are posting to needs a GIF at all.

Keep a real GIF when the destination shows images but not video: an email body, a GitHub README or issue, a Jira ticket, a wiki, an old forum, a slide deck that has to work in every viewer. Anywhere a video plays inline and muted, which covers most social networks and modern chat apps, an MP4 or WebM loop looks better and loads faster. On a web page you control, a <video autoplay muted loop playsinline> element behaves like a GIF and costs a fraction of the bytes.

Two image formats sit in between. Animated WebP, from Google, supports millions of colors and lossy compression and has played in Safari since version 14 in 2020, so it now works in every current browser, though many apps outside the browser still refuse it. APNG extends PNG with frames, keeps full color and real alpha transparency, and is what Apple and LINE use for animated stickers. If a GIF already exists and you only need it smaller for a site that plays video, turning the GIF back into an MP4 is usually the biggest single saving.

Phones can do it without extra apps. On an iPhone, the Shortcuts app has a Make GIF action that accepts a video or a Live Photo, and a Live Photo with the Loop or Bounce effect is a quick way to shoot the source. Samsung's Gallery app shows a GIF button while a video is playing, which records the visible section as a GIF. The GIPHY app and its web GIF Maker trim, caption and upload in one place, but the result is public unless you only save it. In Photoshop, File > Import > Video Frames to Layers brings in up to 500 frames, and Export > Save for Web (Legacy) writes the GIF with palette and dither controls.

For full control and batch jobs, ffmpeg's two-pass palette method gives the cleanest result: the first filter scans the clip and builds a 256-color palette from its actual colors, the second maps every frame onto it. The one-liner below cuts five seconds starting at 0:02, scales to 480 px wide, samples 12 fps and loops forever. In a browser, the video to GIF converter does the same palette step with Width, Frame rate, Colors and Dithering controls, and the MP4 to GIF page opens it with MP4 preselected. Phone clips in MOV work the same way; if an app rejects them, read converting MOV to MP4 first.

A GIF loops forever by default because the Netscape extension is written with a repeat count of zero, which means infinite. Setting a count of one makes it play once and stop on its last frame, which suits a GIF that ends on a message. The harder part is making the loop invisible. Look for a stretch where the start and end frames are nearly identical, such as a wave that returns to the same position, or play the clip forward and then backward with Boomerang, which removes the jump at the cost of twice as many frames.

Before you send it, open the GIF at its real size in a browser tab, not as a thumbnail, and watch three full loops. Check that text in the frame is readable at the chosen width, that faces have not turned into posterized blotches, and that the timing matches the video. Then compare the file size with the limit in the table above; if it is close, go back to the cutting order of length, width, frame rate and colors. For longer clips or anything with sound, compressing a video for Discord and email is the better route.