Initializing... drag & drop files here
Supports: GIF
This tool turns an animated (or static) GIF into a 3G2 video — the small container 3GPP2 defined for CDMA2000 mobile services. 3G2 is the CDMA twin of 3GP: the same ISO base-media design, but aimed at a network family that has largely been switched off, since Verizon retired its 3G CDMA network on December 31, 2022. So pick 3G2 in one case only — an old CDMA-era handset, or a player or system that specifically demands a .3g2 file. For every modern use, GIF to MP4 is the right target: the same animation, far broader playback, and none of 3G2's small-screen baggage.
| Property | GIF (source) | 3G2 (3GPP2 / CDMA) | MP4 (H.264) |
|---|---|---|---|
| Defined by | CompuServe — GIF87a in 1987, GIF89a in 1989 | 3GPP2, for CDMA2000 multimedia services | ISO/IEC 14496-14 (MPEG-4 Part 14) |
| Built for | Looping images on the early web | 3G CDMA feature phones | General-purpose video, everywhere |
| Underlying structure | Its own chunked format | ISO base media (ISO/IEC 14496-12) | ISO base media (ISO/IEC 14496-12) |
| Video codecs | None — palettised frames | H.263, MPEG-4 Part 2, H.264 | Usually H.264 or H.265 |
| Colours per frame | 256 from a palette | ~16.7M (8-bit YUV) | ~16.7M (8-bit YUV) |
| Transparency | 1-bit, on or off | None — video cannot store alpha | None — video cannot store alpha |
| Typical resolution | Whatever the GIF is | Small; handsets often expect QCIF or CIF | Up to 4K and beyond |
| Temporal compression | Sub-rectangle frame updates only, no motion compensation | Yes — I/P/B frames | Yes — I/P/B frames |
| Audio from a GIF source | GIF has no audio | Silent output | Silent output |
| Plays in modern browsers | Yes, in <img> |
No native browser support | Yes, via <video> |
The headline: 3G2 and MP4 are close cousins — both sit on the ISO base media file format (ISO/IEC 14496-12), and 3G2 can carry the same H.264 video MP4 uses. The difference is intent. 3G2 was tuned for the storage and bandwidth limits of CDMA phones, so the devices that expect it lean toward small frames and codecs old handsets can decode. MP4 makes none of those compromises. The only reason to choose 3G2 today is a device or system that will not accept anything else.
.3g2 clips..3g2 extension and rejects modern containers.<video autoplay loop muted playsinline>, which 3G2 cannot do in a browser.| Control | Choices | Arrives on | Notes |
|---|---|---|---|
| Video Codec | H.264, H.263, MPEG-4, Xvid | H.264 | H.264 is the best-looking option a 3G2 file can hold; H.263 is the safest for the oldest handsets |
| Background Color | named colours, from Black and White through Navy, Teal, and Crimson | White | Video cannot store an alpha channel, so any transparent pixels in your GIF are painted this colour — and so are letterbox bars if you change the aspect ratio |
| File Compression | Quality Preset, Constant Quality, Constraint Quality | Quality Preset at Very High (Recommended) | Bitrate and target-file-size modes are deliberately not offered for image sources |
| Video resolution | Resolution Percentage, Keep original, Preset Resolutions (4320p down to 144p), Width, Height, Width x Height | Keep original | Aspect ratio is preserved on the Width and Height options; many 3G2 targets expect QCIF (176×144) or CIF (352×288) |
| Audio | No control appears | — | GIF carries no audio track, so nothing is there to encode and the output is silent |
Two things follow from the table that catch people out. First, Background Color matters more here than on most video pages, because GIFs so often have transparent backgrounds. A logo or sticker GIF with a transparent surround will come out on a white card unless you change it — pick Black, or any of the other 22 colours, to match where the clip will sit. Second, the per-frame Image Duration, merge, and trim controls you may have seen on other image-to-video tools do not appear here on purpose: an animated GIF already carries its own frame timing, and the converter reads and reuses that timing directly rather than assigning a fixed duration per image.
It keeps its motion. Every frame of the animated GIF is read and encoded in order as a real 3G2 video, so a looping GIF becomes a playable clip of the same length rather than a single held frame. The GIF's own frame delays set the timing, which is exactly why the "Image Duration" and merge controls are hidden for GIF input. A single static GIF simply produces a short still clip.
No. GIF has no audio stream at all, so there is nothing to carry over and the resulting 3G2 is silent by nature. That is also why no Audio Codec control appears on this page. The 3G2 container itself can hold audio — AMR narrowband and wideband, AAC, and the CDMA-specific EVRC, QCELP, SMV, and VMR-WB codecs — but with a GIF source there is no track to encode. Add narration or music afterwards in a video editor.
It is filled with the Background Color, which arrives on White. No video format can store an alpha channel, so transparency has to become a solid colour somewhere in the pipeline, and this control is where you choose which. If your GIF is a transparent sticker or logo destined for a dark screen, set Background Color to Black before converting — otherwise you will get a white card behind it that is very hard to remove later.
.3g2 and .3gp?They are sibling formats from different standards bodies for different mobile networks. 3GP is defined by 3GPP for GSM and UMTS phones; 3G2 is defined by 3GPP2 for CDMA2000 phones. Both are built on the same ISO base media file format (ISO/IEC 14496-12) that underpins MP4, and both carry H.263, MPEG-4 Part 2, and H.264 video. The practical differences are the target device's network family and the CDMA-specific audio codecs 3G2 adds. If your handset is GSM-era, convert to GIF to 3GP instead.
Only if you asked for it. Video resolution arrives on Keep original, so the output matches your GIF's dimensions unless you choose a preset or a custom size. People downscale here because the handsets and players that still want 3G2 were built for small screens and typically expect QCIF or CIF frames. If your target device rejects the file, a lower Preset Resolution is the first thing to try.
H.264 gives the best picture per byte and is the codec this page arrives on, but the oldest CDMA handsets predate it. If a device rejects the H.264 file outright, re-convert with H.263, which is the baseline codec of the 3GPP2 era and the most likely to decode on ancient hardware. MPEG-4 Part 2 and Xvid sit between the two. Pair a fallback codec with a small Preset Resolution for the best odds.
No — the output can match the source but never exceed it. Your GIF is already limited to 256 colours per frame and to whatever resolution and frame rate it was saved at. The 3G2's video stream can hold far more colour than that, so it will not add banding, but it cannot invent detail the GIF never captured. Upscaling the resolution just enlarges existing pixels. The file will usually still be much smaller than the GIF, because video codecs use motion-compensated inter-frame prediction that GIF has no equivalent of.
Yes. Use 3G2 to MP4 to bring a 3G2 clip into a web-friendly container. Bear in mind that re-encoding from an already-downscaled 3G2 cannot recover resolution or detail lost in the first pass — so if you still have the original GIF, converting that straight to MP4 gives a cleaner result than a GIF-to-3G2-to-MP4 round trip.