Why is my GIF bigger than the video I made it from?

Because GIF stores every frame as a complete image, with none of the motion-based compression video codecs use. A video mostly stores the differences between frames; a GIF stores the whole picture over and over, which is why it is routinely five to ten times the size of the equivalent MP4 despite having fewer colours and no audio.

What frame rate and width should I pick for a GIF?

For screen recordings and UI demos, 10-12 frames per second and a width around 480 pixels is a solid default. GIFs do not need the 30 or 60 frames per second of the source video, and frame rate multiplies directly into file size. Raise either dial only if the result visibly stutters or text is hard to read.

Do GIFs lose quality when I convert a video?

Yes, but not the way JPEG does. GIF compression is lossless within its palette - pixels are stored exactly - but each frame is limited to 256 colours, so the conversion itself throws colour information away. Screen captures and diagrams barely suffer because they use few colours; camera footage with gradients and skin tones shows banding and dither speckle.

How do I turn an animated GIF back into a video?

Not with a generic image conversion - converting an animated GIF to another image format keeps only the first frame, so the animation is lost. Many platforms sidestep this by converting GIFs to video on upload automatically. If you still have the original video the GIF came from, use that: compress it with compress-video instead of round-tripping through GIF.

Are my videos and images uploaded when I convert them?

No. FileTinker's video-to-gif, images-to-gif, and compress-video tools run entirely in your browser. The file is processed on your own device and offered back as a download - nothing is sent to a server, and there is no signup.

GIF vs Video in 2026: When a GIF Is the Right Call (and When It Is 10x Too Big)

July 5, 20267 min read

The GIF turns forty next year, and by every technical measure it should be dead. It stores moving pictures the way a flipbook does, one complete frame after another, with a colour palette capped at 256 shades and no sound at all. A modern video codec delivers the same clip at a fraction of the size with millions of colours. And yet GIFs are everywhere: in chat threads, README files, support docs, forum posts. That is because the GIF holds one trump card no video format has taken: it plays everywhere, instantly, with no play button and no unmute step. This guide explains when that is worth the enormous file size, when it absolutely is not, and how to convert in both directions without making a 40MB monster out of a ten-second clip.

Why a GIF is so much bigger than the same clip as video

The GIF format dates from 1987, and it shows. An animated GIF is a stack of complete images played in sequence, compressed with a scheme designed for the modems of the late eighties. There is no concept of motion: if a person waves their hand in front of a static background, the GIF stores that unchanging background over and over, frame after frame.

Video codecs like H.264, VP9, and AV1 work the opposite way. They store a full picture only occasionally, and for the frames in between they store just the differences: this block of pixels moved left, that region did not change at all. For typical footage, where most of each frame matches the one before it, this is dramatically more efficient. The same ten-second clip that makes a 2MB MP4 can easily become a 15-20MB GIF, and it is common for the GIF version of a clip to be five to ten times the size of the video it came from - sometimes more.

The size gap comes with a quality gap, and it points the wrong way. Despite being far larger, the GIF also looks worse, because each frame is limited to a palette of at most 256 colours. Smooth gradients turn into visible bands and dithering adds a grainy speckle to hide the damage. Video has none of these limits and carries audio too, which GIF simply cannot. Bigger file, worse picture, no sound: on raw specs, the GIF loses every category.

The one thing GIF still does better than anything

So why does the format refuse to die? Because a GIF is treated as an image, and images just appear. Drop a GIF into a chat message, a GitHub README, a forum post, or a wiki page, and it starts moving the moment it loads - no play button, no controls, no click. The reader never has to decide to watch it; it is simply already playing, and it loops forever.

Video cannot reliably promise that. An embedded video usually renders as a player with controls, and whether it autoplays depends on the platform, the browser's autoplay policy, and whether it is muted. A GIF in a GitHub README animates inline; an uploaded video in the same README is a player the reader has to click. In many chat and forum contexts a video attachment is a thumbnail and a download link, while a GIF is a moving picture right there in the thread.

This is why the GIF's niche in 2026 is not entertainment - it is guaranteed, frictionless motion. A three-second loop showing where a button lives, a cursor performing the exact steps of a fix, a before-and-after that plays without being asked. When the whole point is that the reader sees the motion without doing anything, the GIF's terrible bytes-per-second ratio buys you certainty.

When a GIF is the right call

The pattern is short, small, silent, and embedded. A GIF earns its size when every one of these boxes is ticked:

It is a few seconds long. Two to six seconds of loop is the sweet spot; every extra second multiplies the file size.
It needs to play inline with zero interaction - a README demo, a bug report showing the glitch happening, a step-by-step in support docs, a forum post.
Sound does not matter. GIF has no audio track, so if the clip needs sound, the decision is already made for you.
The content survives 256 colours: screen recordings, UI captures, diagrams, and text-heavy clips look fine, because interfaces use few colours to begin with.
The destination treats images and videos differently. If a video would show up as a click-to-play box or a bare attachment where you are posting, a GIF keeps the motion visible.

When video wins, and it usually does

Everywhere else, send a video. The moment any of the following is true, a GIF is the wrong container and you are paying a 5-10x size penalty for nothing:

The clip is longer than about ten seconds. GIF sizes grow brutally with duration; a thirty-second GIF is almost always a mistake.
It is real-world footage. Camera video is full of gradients, noise, and subtle colour, which is exactly what a 256-colour palette destroys and what video codecs compress brilliantly.
You need audio. Full stop.
You are sending it to a person rather than embedding it in a page. Messaging apps and email handle video attachments fine, and the recipient gets a smaller file at better quality.
The platform converts it anyway. Twitter has quietly converted uploaded GIFs to video for years, and GIF-sharing services mostly deliver MP4 behind the scenes, because serving actual GIFs would waste everyone's bandwidth. If the platform will turn your GIF into a video, you may as well upload the better-quality video yourself.

Converting video to GIF without making a monster

When a GIF is the right call, spend its bytes only on the part that matters. FileTinker's video-to-gif tool runs entirely in your browser: load the clip, pick the exact segment with a start-time and duration slider, choose a frame rate and output width, and get a looping GIF back. Nothing is uploaded anywhere.

Because GIF stores full frames with a 256-colour palette, output size grows fast, and the three dials you control multiply together. Duration is the big one: converting six seconds instead of twelve halves the file before you touch anything else. If the moment you want is buried in a longer recording, cut it out first with the video trimmer, or just use the segment slider to grab only those seconds. Frame rate is the next lever - ten to fifteen frames per second reads as perfectly smooth for a UI demo, and dropping from 30 to 10 cuts the frame count, and roughly the size, to a third. Width is the third: a 480-pixel-wide GIF has a quarter the pixels of a 960-pixel one, and for something viewed inline in a chat or README, 480 pixels is usually plenty.

A good starting recipe for a screen-capture demo: the shortest segment that shows the action, 10-12 frames per second, width around 480 pixels. Then only raise a dial if something specific looks wrong - the frame rate if fast motion stutters, the width if text is hard to read.

Going the other direction: shrinking video, building GIFs from stills

Sometimes the honest answer to a GIF question is to not make a GIF. If you reached for GIF only because the video felt too big to send, compress the video instead. FileTinker's compress-video tool re-encodes a clip in your browser at a capped bitrate, producing an MP4 where the browser supports writing one and a WebM otherwise (Firefox, for example). You keep full colour, audio, and a far smaller file than any GIF of the same clip - and a clip already under your target size is left alone rather than re-encoded for nothing.

One conversion trap is worth calling out. Converting a still image to GIF with a generic image converter gives you a single-frame GIF - a normal picture that happens to have a .gif extension, with no animation. The reverse trap is worse: converting an animated GIF to another image format keeps only the first frame, silently throwing away the animation. If you have ever converted a GIF to PNG and wondered where the motion went, that is where.

To make a GIF that actually animates from still images, you need a tool that stacks them into frames. FileTinker's images-to-gif does exactly that: give it two or more images and it builds a looping GIF, showing each image for the same number of seconds. The first image sets the canvas size - it is never enlarged - and images with different proportions are letterboxed onto a background colour of your choice. It is the quick way to turn a handful of screenshots into a before-and-after loop or a step-by-step that plays itself.