Convert GIF to MP4 without changing the timing

Why GIF to MP4 is nearly always the better trade

An animated GIF has no idea that one frame resembles the one before it. Every frame is a fresh picture, drawn from a table of at most 256 colors, packed with a compressor designed in 1987 for logos and line art. H.264 was built for the opposite job: it looks at what moved, describes only that, and predicts the rest. Handing the same twelve seconds of footage to each of them is not a close contest. A five megabyte GIF routinely leaves here at two hundred kilobytes, looking better than it went in, because the banding and the dithering noise that the palette forced on it are gone too.

The catch is not quality, it is behavior. GIF plays automatically, repeats forever and drops into any box that accepts an image. Video does none of those things without being asked. Everything below is about asking properly — and about the handful of things in a GIF that have no direct translation into video at all, each of which this page shows you rather than deciding quietly on your behalf.

GIF and MP4, in brief

GIF

Full name	Graphics Interchange Format
Extension	.gif
Format type	Lossless raster image, 256 colors, animatable
MIME type	image/gif

MP4

Full name	MPEG-4 Part 14
Extension	.mp4, .m4v
Format type	Video container — usually H.264 or H.265 with AAC
MIME type	video/mp4

Each frame carries its own delay

This is the detail that separates a conversion you can use from one you throw away. A GIF does not have a frame rate. It has a delay stored beside every individual frame, measured in hundredths of a second, and animators use that freely: eight quick frames, then a long hold on the punchline, then eight more. A converter that assumes a single frame rate has to average all of that away, and the result is an animation whose pauses have vanished and whose fast parts crawl.

Here each frame is written with the exact duration it had, into the timing table inside the MP4 that exists for precisely this purpose. The receipt states the running time so you can check it against the original before you download anything.

There is one place where the honest answer is not the literal one. A frame may ask for a delay of zero, or of a single hundredth of a second, and no browser on earth obeys that — every one of them plays such frames at a tenth of a second instead, a compatibility decision from the Netscape era that is now permanent. Copying the raw number into the video would produce a clip that races through sections the GIF played at a walking pace. So those frames are written at a tenth of a second, matching what you actually watched. When a file contains any, the tool says how many and offers you the literal reading instead.

Transparency, odd sizes, and the loop

Three things in a GIF do not survive the crossing, and all three are visible decisions rather than silent ones.

See-through pixels. H.264 has no alpha channel. If your GIF has transparent areas, something must sit beneath them, permanently, baked into the picture. White suits most documents, black suits most video players, and a color picker is there for the person whose page is neither. The choice only appears when the file actually contains transparency, because on an opaque animation it would change nothing. If the transparency is the point — a sticker, a logo loop, an overlay meant to sit on top of something — then video is the wrong target and the same animation as a WebP is the right one: it carries a real alpha channel, keeps every frame lossless, and still lands several times smaller than the GIF.

Odd dimensions. Video encoders store color at half resolution horizontally and vertically, so a width or height that is not even has nowhere to go — ask an encoder for 301 pixels and it refuses outright. A frame like that is widened by a single column, which repeats the edge rather than introducing a stripe of background, and no original pixel is resampled to achieve it. The panel shows you the coded size before you start.

The endless repeat. Looping is written into the GIF file itself. MP4 has no equivalent field, so the instruction has to live in whatever plays the clip. On a web page that is four attributes on a video element, and the two that look decorative are the load-bearing ones: without muted no browser will start playback unprompted, and without playsinline an iPhone hijacks the clip into fullscreen. The finished tag is handed to you on the receipt with a copy button, because it is the step every free converter leaves you to discover on your own. And since a GIF has never carried sound, there is no audio track in the result — that is not an omission, it is arithmetic. If the thing you need to publish is the shape of an actual soundtrack, start with an audio file instead: the audio waveform generator exports its measured peaks as SVG and PNG without inventing sound for a silent animation.

For a spoken soundtrack, removing dead air is its own audio-only job rather than an MP4 option. The audio silence remover takes WAV or MP3 and makes a locally encoded MP3; it deliberately refuses video because cutting only the soundtrack would move sound and picture out of sync.

Your browser is already a video encoder

Nothing is downloaded to make this work and no file is sent anywhere. The H.264 encoder used here is the one your browser ships for video calls, reached through WebCodecs, running on the same silicon that handles your camera. What this site adds is the container: the box structure that tells a player where each frame lives, how long it lasts and which ones it may seek to. That part is written here, byte by byte, with the index deliberately placed ahead of the picture data so the file starts playing before it has finished downloading.

The practical consequence is speed and privacy at the same time. A clip that a web service would queue, upload, transcode and hand back over a minute is finished here in a few seconds, and the material never left the machine it was on. That matters more than it sounds for this particular format, because an enormous share of GIFs are screen recordings of software, and a screen recording tends to contain whatever else was open at the time.

How big the MP4 will be

The quality buttons are shortcuts to a bitrate, and the rate they land on is written in the box beside them — type your own number there if a chat app or a CMS has told you exactly what it accepts. The size shown before you convert is a range rather than a single figure, because the encoder spends what each scene needs instead of a fixed amount: flat animation and screen recordings finish well under the target, while camera footage with grain and motion runs over it. The range is half to double the target rate times the running time. The receipt then states the size and the average rate of the file that was actually written, read from its bytes, so a number you asked for and a number you got can never be confused.

Tablets, phones, and the encoder that is already paid for

Converting video has always been desktop software's territory, and the territory shows the moment you are not at a desktop. Search an app store for a GIF converter on a tablet and the results are apps that stamp a logo across the output, ask for a subscription at the export step, or send the clip to a service and describe that as conversion. On a Chromebook or a school-managed device there may be nothing installable at all, and on a phone the clip is already sitting in the camera roll where the search started.

Meanwhile the hardware is right there. Anything sold in the last decade encodes H.264 in silicon because video calling requires it, and WebCodecs is simply the browser lending a page that encoder — Safari since 16.4, Chrome, Edge and Firefox for longer. An older browser is told plainly that it cannot do this, before you hand over a file rather than after. A current one finishes in the same few seconds a laptop would take, with no account made and the result written into the downloads folder of whatever you are holding.

When to reach for something else

If you need the output to stay a GIF — because the destination only accepts images, or because it has to animate inside an email — then converting is the wrong move and compressing the GIF to a target size is the right one. That tool spends colors, frames and resolution in that order and tells you which levers it had to pull.

If MP4 is accepted but must fit a stated upload ceiling, convert first and then use the video compressor with a measured byte target. It re-encodes H.264 only when the file is still too large and marks a pass from the actual output bytes.

Going the opposite way is a separate page, deliberately: making a GIF out of a video clip is a different job with different questions, because it has to ask which seconds you want and how many frames per second are worth paying for before it can begin. Expect the result to grow rather than shrink — that direction is the one this page exists to undo.

This one does not crop, trim, resize, add captions or change the speed. It does not re-time anything, and it will not silently drop a frame to make a number look better. It converts, honestly, and shows you every place where the two formats disagree about what is possible.