QUICK ANSWER
Converting a GIF to Clipy’s H.264 MP4 removes transparency and changes how the animation is encoded and played. The result is often smaller, but cannot restore detail already missing from the GIF. Check timing and edges, and configure looping in the destination player. Keep the GIF when transparency or an image-only destination matters.
TL;DR
- Transparency does not survive this conversion. GIF carries a one-bit transparent colour. H.264 inside an MP4 has no alpha channel at all, so every transparent pixel becomes an opaque one, usually black or white. If the transparency matters, the answer is not MP4.
- GIF measures time in hundredths of a second, MP4 does not. GIF supports different delays for different frames. MP4 also supports variable sample timing; a converter may preserve those timings or resample them. A constant frame rate is not required by MP4 itself.
- The loop lives in different places. GIF stores a loop count inside the file. MP4 has no loop flag, so looping becomes the player's decision. In HTML that means the
loopattribute, andmutedplusplaysinlinehelp with autoplay and inline playback, subject to browser policy. - Colour gets subsampled, and it shows on text. H.264 in 4:2:0 stores colour at half resolution in both directions. Many photographic scenes hide the difference. Thin coloured text on a contrasting background sometimes will.
- Odd pixel dimensions get nudged. Clipy rounds width and height down to even numbers for its H.264 output, so a 601 pixel wide GIF comes out at 600.
- Most of the time none of this matters and the MP4 wins. It is often smaller, but playback and autoplay depend on the destination. Conversion does not recover colours or details already lost in the GIF. Convert it free at the GIF to MP4 converter, up to 500 MB, no signup and no watermark.
There is plenty written about why to convert a GIF to MP4, including two posts here: why the file shrinks so much and how to convert one quickly. This post covers the other half: what changes inside the file when you convert, and which of those changes will bite you.
What does a GIF store differently from H.264 video?
A GIF is a container of images plus a little control data. Frames can use a shared global palette or their own local palette of up to 256 entries. Optional control blocks describe frame delay, disposal and transparency. Many animated GIFs include an application extension specifying a loop count; a loop count is not required in every GIF.
Clipy produces H.264 pictures in an MP4 container with timestamps for playback. Its output has no GIF palette or disposal method and does not retain transparency. GIF loop instructions are not carried over into a normal video player’s repeat setting.
So a converter is not just recompressing pixels. It decodes the animation into pictures and writes those pictures using a different compression and timing model. Four of those swaps are worth understanding.
Why does transparency disappear?
GIF transparency is binary. One palette index is flagged transparent, and any pixel using it shows whatever is behind. There is no partial transparency, no soft edges, no 50 percent shadow. That is why transparent GIFs so often have crunchy outlines.
H.264 has no alpha channel. Not a limited one, none. When ffmpeg converts a transparent GIF to H.264, the transparent pixels have to become some colour, and by default that is usually black. If your GIF was a white logo on nothing, you will often get a white logo on black, which is either exactly what you wanted or a complete disaster depending on where you were about to paste it.
There is no clever converter setting that fixes this, because the format cannot represent the data. The realistic options:
- Flatten deliberately. Decide the background colour yourself instead of accepting the default, then convert. If the MP4 is going somewhere with a known background, this is usually fine and nobody notices.
- Keep the GIF. For a transparent sticker, a logo bug, or an overlay that has to sit on an unknown background, GIF is still the pragmatic answer. If it is too heavy, shrink it in place with the GIF compressor rather than changing format.
- Use a format that has alpha. Animated WebP, VP9 in WebM, and HEVC with an alpha layer all carry real transparency, including partial transparency, which GIF never had. Support is patchier than MP4, so check the destination first.
Worth saying plainly, because a lot of pages are vague about it: "GIF to MP4 with a transparent background" is not a setting anyone is hiding from you. Check the codec and destination support before trusting that promise. MP4 is a container, so claims about every possible MP4 codec are broader than the ordinary H.264 conversion described here.
How do GIF frame delays affect MP4 timing?
Every GIF frame carries a delay value in hundredths of a second. That has two consequences most people never think about.
First, a GIF is inherently variable frame rate. Frame one can sit for 4 hundredths, frame two for 12, frame three for 4 again. Meme generators and screen recorders exploit this constantly.
Second, the achievable frame rates are quantised. Because the unit is one hundredth of a second, you get 100, 50, 33.3, 25, 20, 16.7, 14.3, 12.5, 11.1 or 10 frames per second and very little in between. A fixed delay cannot represent exactly 24 or 30 fps, but alternating delays can approximate those average rates. For example, repeating delays of 3, 3 and 4 hundredths gives three frames in a tenth of a second, averaging 30 fps. Individual frames still sit on the centisecond grid.
Viewers may impose a minimum delay on very short frames, and decoder settings can treat short delays differently. Do not assume one universal clamp across browsers or tools. Compare the original in its destination viewer with the converted video rather than treating a metadata rate as the complete playback experience.
If a converter requests constant frame rate output, it resamples the source timing onto that rate. MP4 itself does not require this. Frames that were held longer get duplicated, frames that were too close together get dropped. The visible result is almost always fine. When it is not, it shows up as one of these:
- The clip finishes very slightly earlier or later than the GIF did.
- A deliberately long held frame loses a fraction of its hold.
- A GIF viewer and the video converter may interpret very short delays differently, producing a speed difference that needs investigation.
A speed change is worth checking. Compare total duration and a recognisable held frame before deciding whether the viewer, decoder or conversion settings caused it.
How do you make the converted MP4 loop?
A GIF that loops forever says so inside the file, in an application extension block near the top. A GIF that plays three times and stops says that too. Looping is a property of the image.
MP4 has no equivalent. The video simply ends. Whether it repeats is entirely up to whatever is playing it, so the same converted file can repeat in one player and stop after one pass in another.
For self-hosted HTML, the attributes you want are:
<video src="clip.mp4" autoplay loop muted playsinline></video>All four earn their place:
looprequests repeated playback; the original GIF may have used a finite loop count.mutedis not cosmetic. Browsers commonly restrict audible autoplay. Muting helps, while a video with no audio track may already qualify for inaudible autoplay. User settings can still block it.playsinlinestops iOS Safari taking the video fullscreen, which is what turns a GIF replacement into an unwanted takeover of the page.autoplayrequests automatic playback but does not override browser policy or user preferences.
Coming from a GIF this is easy, because a GIF has no audio to strip. It matters when the MP4 came from a screen recording instead: a silent track is not the same as no track, and some autoplay heuristics treat them differently. The mute video tool removes it as a stream copy in seconds.
Where can an MP4 replace a GIF?
Chat and note tools can show an MP4 in an inline player, but automatic playback and looping depend on the application, user settings and upload context. An accepted MP4 is not a guarantee of GIF-like behaviour.
The exceptions cluster in two places: email, and anywhere that treats your file strictly as an image.
| Destination | Animated GIF | Short muted MP4 | Practical call |
|---|---|---|---|
| Slack, Discord, X, Notion | Plays inline | Video player behaviour varies | Try the MP4 and check size, quality and playback. |
| iMessage and most mobile chat | Plays inline | Plays inline | Test the actual recipient app and file size. |
| Email clients | Animates in most clients | Generally will not play, arrives as an attachment | Keep the GIF, or send a still image with a link. |
| Anywhere expecting an image file | Accepted | Rejected or treated as a download | Keep the GIF if the field only accepts images. |
| Self-hosted web page | Animates automatically | Configure video attributes and a playback fallback | Compare file sizes and test browser playback. |
Platform behaviour changes, so test the destination you actually care about. The rule underneath the table: if it has a video player, send the MP4. If it only has an image slot, you need a real GIF.
Why can coloured text look different after conversion?
H.264 for general distribution is encoded in YUV 4:2:0, which stores brightness at full resolution and colour at half resolution horizontally and vertically. This is one of its compression trade-offs, and it is often less noticeable in photographic footage than on sharp coloured text.
It is not always invisible on synthetic content. Thin, saturated, high-contrast edges are the worst case: red text on blue, a one pixel coloured border, a chart line in a bright accent colour. You can get slight colour bleed there that the GIF, with its exact indexed palette, did not have.
Dithering and palette limits may already affect the source GIF. Converting it does not restore the original image from before that loss. But if you are converting a screen recording that is mostly small coloured text, check the result at 100 percent zoom before you ship it.
One related mechanical detail: 4:2:0 requires width and height divisible by two, so an odd-sized GIF gets nudged by a pixel. A one-pixel change can matter for pixel art or exact layout dimensions, so check the result.
What determines the file-size difference?
The headline number varies wildly, which is why you see everything from "3x smaller" to "50x smaller" quoted online. Neither is a guarantee for your file. The ratio depends on dimensions, duration, motion, palette use, optimisation and encoder settings. GIF can store changed rectangles and use transparent areas to avoid redrawing unchanged pixels; it does not always store every frame in full. H.264 uses a different set of spatial and temporal compression methods.
| Source GIF | What GIF does | Typical shrink as MP4 |
|---|---|---|
| Screen recording, mostly static UI, cursor moving | May store only changed rectangles, depending on optimisation | Can shrink substantially; measure your own file |
| Talking head or live footage, heavy dithering | Dither noise defeats its own compression | Often smaller; source dithering cannot be recovered |
| Flat cartoon loop, few colours, small dimensions | Palette compression works well here | May already be efficient as GIF |
| Tiny icon animation, under 100 KB | Already efficient | Marginal, and MP4 container overhead can even lose |
These are qualitative considerations, not benchmark results or promised ratios. Compare the actual source and output. A tiny animation may still benefit from video playback controls, but file-size savings alone may not justify a format change.
If the GIF is huge specifically because it was made badly, converting is not the only lever. Duration, frame rate, width and palette size all matter, and the MP4 to GIF settings guide covers how those four interact when you are producing a GIF in the first place.
When should you keep the GIF?
Keep the GIF when one of these requirements applies:
- The animation needs a transparent background over unknown content.
- It is going in an email body and has to animate there.
- The destination field only accepts image formats.
- It is already tiny, so there is nothing to win.
- You need a specific finite loop count baked into the file, rather than relying on the player.
Elsewhere, compare the MP4 with the source before choosing. If the problem is just that your existing GIF is too heavy, shrink it with the GIF compressor and keep the format.
How do you convert a GIF with Clipy?
Drop the file into the GIF to MP4 converter. It accepts animated GIF, animated WebP and APNG up to 500 MB, encodes H.264 with server-side ffmpeg rather than in your browser tab, and returns the MP4 through CDN. There is no account, no watermark, and no paid export step. Treat the download as temporary and save the finished file rather than using a conversion URL as permanent hosting.
Related tools for the rest of the workflow: MP4 to GIF for the other direction, video to GIF to skip the MP4 step entirely, video compressor if the MP4 still needs to fit an upload cap, and resize video if the destination has pixel limits.
What else should you know before converting?
Does converting GIF to MP4 lose quality?
Yes, this is a lossy conversion. It may look very similar, but compression and colour subsampling can change edges and fine detail. Transparency is removed. Timing may also differ depending on conversion and playback settings. Colours lost when creating the GIF are not restored.
Can I convert a GIF to MP4 and keep the transparent background?
Not in MP4 with H.264. The codec has no alpha channel, so transparent pixels become a solid colour. If you need transparency, keep the GIF, or move to animated WebP, VP9 in WebM, or HEVC with alpha, all of which support it properly.
Why does my MP4 play faster than the original GIF?
Compare frame delays and total duration first. The GIF viewer and conversion decoder may treat short delays differently, or the conversion may resample frames. Neither playback speed should be assumed correct without checking the source timing and intended result.
How do I make the MP4 loop like the GIF did?
Looping is a player setting, not a file setting. In HTML use <video autoplay loop muted playsinline>. In chat and social apps, check the actual player settings; automatic looping is not guaranteed. In a desktop media player you turn on repeat.
What frame rate should a converted GIF end up at?
Whatever the source timing supports. GIF delays are in hundredths of a second, and alternating delays can approximate rates such as 30 fps. Forcing a higher number afterwards only duplicates frames and adds bytes without adding any motion.
Is there a file size limit?
500 MB per file on the converter. Encoding runs server-side with native FFmpeg.
Will the MP4 have audio?
No. A GIF has no audio track, so the converted MP4 is silent. That helps with embedding, because video without an audio track may qualify for inaudible autoplay, subject to browser policy.
Is this free, and is there a catch?
Free, no signup, no watermark, no paid export. Clipy is a screen recorder and these conversion tools sit alongside it as utilities.
How should you compare the original and converted file?
Keep the source GIF and download the MP4 to a separate filename. Open them at the same displayed size. A video player that stretches the MP4 to fill a window can make it seem softer even when the main difference is scaling. Start at the source dimensions, then test the size at which people will actually see the animation.
Pick three moments to inspect: a still frame with text, a frame with motion, and a held frame near the end. Fine text reveals edge changes. Motion reveals duplicated or dropped frames. A deliberate pause reveals whether the timing still communicates the same thing. A tutorial animation can be technically playable and still become harder to follow if the pause after a click is too short.
For transparent artwork, first decide what the output background should be. Open the source over both a light and dark background to see what relies on transparency. After conversion, those areas are fixed pixels. If you need the same animation to work over several unknown backgrounds, retaining an image format with transparency may be more useful than a smaller video file.
Compare durations as well as file sizes. A smaller output is not a useful saving if it accidentally contains fewer frames or ends before the final instruction. Watch the last frame and the transition back to the first when looping. A noticeable jump at that boundary may have existed in the source; conversion does not automatically create a seamless loop.
Finally, upload a test copy to the actual destination and view it from the recipient side. A local player cannot tell you whether a chat service will start the video automatically, add controls, recompress it or require a click. Check with the relevant device and user settings before replacing a GIF across a help centre or email campaign.
How do you make a web animation usable when autoplay is blocked?
A moving image should not be the only way to understand a necessary instruction. Add a short adjacent explanation of what happens, especially for a cursor demonstration. If the animation shows three steps, write the three steps in text too. That helps people who cannot see the motion, prefer reduced motion, or are reading on a connection where the media has not loaded.
For a self-hosted MP4, provide a way to start and stop playback. The compact autoplay example above illustrates the relevant attributes, but an actual page should also consider controls, a useful poster frame and a fallback link. When a browser blocks automatic playback, visitors still need an obvious way to view the clip.
A silent GIF conversion has no speech to transcribe, but it can still carry meaningful visual information. Describe the outcome in surrounding text. If you later add narration, provide captions for that audio and check that controls remain available. File conversion and accessible presentation are separate tasks, and a smaller file does not complete the latter.
Where can you check the timing and playback details?
The GIF89a specification defines image palettes, transparency and frame-delay fields. The MDN autoplay guide explains why browser policy still matters for video. Check your particular animation with the GIF to MP4 converter, then test the destination where it will be used.