Initializing... drag & drop files here
Supports: 3GP, 3G2
A .3g2 is a 3GPP2 file — the container CDMA2000 handsets recorded to, built on the ISO base media file format and specified by 3GPP2 in C.S0050. Xvid is the open-source MPEG-4 Part 2 encoder that DivX-certified DVD decks, in-car head units and 2005-era media boxes were built around. Converting between the two is a legacy-to-legacy job with a specific destination in mind: hardware that reads Xvid from a USB stick or a burned disc.
This tutorial covers the three decisions that change the result — resolution, audio codec and compression mode — and it is direct about the two things that catch people out on this route: the extension you get back is not a container anyone recognises, and the phone soundtrack ends up in an MP3 variant that old hardware often refuses. This page accepts .3gp uploads as well as .3g2.
.3gp works here too and several clips can queue together.Handsets of the CDMA era recorded small: QCIF at 176x144, QVGA at 320x240, occasionally CIF at 352x288. Those numbers are the whole picture that exists. Setting Video resolution to 720p produces a 720p file containing the same detail, softly interpolated, at several times the size — the encoder has nothing extra to encode.
There is a second reason to leave it alone. Keeping the resolution on "Keep original" preserves whatever pixel aspect ratio the source declared; any rescale flattens the pixels to square. On a clip recorded anamorphically that is exactly what makes the output look stretched or squashed, and it is a change you did not ask for. If a device genuinely needs a specific frame size, use Width x Height and type the display dimensions you want rather than taking a preset — the Preset Resolutions list sets the height only and lets the width follow the source, which is rarely what a fixed-raster device wants.
The one case for changing resolution is the opposite direction. Some certified players cap out at standard definition and stutter on anything larger; if you have an unusually large source and the deck struggles, dropping to 720x480 or 720x576 helps and shrinks the file at the same time.
A 3G2 from a CDMA handset usually carries AMR-NB speech at 8 kHz mono, or one of the CDMA voice codecs. None of those can go into an AVI, so the audio is re-encoded — and there is no sample-rate control on this page, so whatever the encoder negotiates is what you get. We fed an 8 kHz mono source through each codec and read the output back:
| Audio Codec you pick | Sample rate in the output | Why it matters on old hardware |
|---|---|---|
| MP3 (pre-selected) | 8000 Hz, kept as-is | 8 kHz MP3 is MPEG-2.5 Layer III, an extension many hardware decoders never implemented — a common cause of silent playback on DivX-certified decks |
| MP2 | Resampled to 16000 Hz | Inside the MPEG-2 Layer II rate set; broadly safe |
| AC3 | Resampled to 32000 Hz | A rate Dolby Digital decoders expect; safe where the device lists Dolby Digital |
| AAC | 8000 Hz, kept as-is | Fine in software players, but AAC in AVI is an unusual combination for old hardware |
So the practical rule is the opposite of the default: if the clip has AMR-NB speech and the target is a hardware player, choose MP2 or AC3 rather than leaving it on MP3. If the destination is VLC or a computer, MP3 at 8 kHz is fine and nothing will complain.
| Property | Value |
|---|---|
| Bytes written | AVI (RIFF) — we read the header back and it opens RIFF … AVI |
| Extension you receive | .xvid, which is not a registered container anywhere |
| Video coding | MPEG-4 Part 2 Advanced Simple Profile, FourCC xvid |
| Video Codec choices | Xvid only |
| Audio codec written by default | MP3 |
| Rename before playing? | Usually yes — change .xvid to .avi and players recognise it immediately |
| Alpha channel | Not supported by MPEG-4 Part 2 in AVI |
| Typical size change | Larger than the source. Reproducing what the Very High preset asks for — 1.32x the source video bitrate — on a 670 KB, 10-second QVGA 3G2 whose video ran at about 517 kbps produced a 963 KB Xvid file |
.xvid to .avi. The file is already an AVI; players match on the extension and .xvid means nothing to them..3gp" — that is fine, this page accepts both extensions and treats them identically..xvid when Xvid is a codec?Because the extension names what people search for rather than what the file is. Xvid encodes MPEG-4 Part 2 video, and that video has to live in a container — here it is AVI. The bytes begin RIFF, the form type is AVI , and the video stream carries the FourCC xvid. Renaming to .avi changes nothing inside the file and makes every player recognise it, which is why it is the first thing to try when something refuses to open.
No. The conversion always re-encodes: the handset's video is decoded and encoded again as Xvid, and the speech track is decoded and encoded again into whichever audio codec you selected. Nothing is copied through untouched. That is one lossy generation on top of a source that was already compressed hard for a 2000s cellular network. Keep the .3g2 if you might need it again.
Rarely. Both encode MPEG-4 Part 2 Advanced Simple Profile and a file from either normally plays wherever the other does; the difference is which FourCC ends up in the stream header. This page writes xvid. If a specific player's firmware lists DivX and rejects Xvid-tagged files, use the DivX route instead. If you would rather have an extension every player already knows, 3G2 to AVI is the same conversion under the name AVI understands.
The label is shared across every codec the site supports, and it is inaccurate here. Xvid uses a fixed quantiser from 1 to 31, and the slider is wired straight to it — lower means finer quantisation and a bigger file. It works; it is just named after a different codec's control. It opens at 5, which is a high-quality setting; for a small phone clip that is fine, and 8 to 12 is plenty if you want the file smaller.
It sets a bitrate target rather than a quality target, because Xvid has no constant-quality mode of the kind H.264 has. The converter reads your clip's existing video bitrate and scales it: the pre-selected Very High rung asks for 1.32x, and the ladder runs from 1.5x at Highest down to 0.3x at Lowest. Because everything is anchored to the source, a low-bitrate phone clip stays a low-bitrate clip at every rung — the preset changes the size, not the amount of detail that was captured.
Yes, and it is the most effective way to keep the output small. The Trim group opens on "Unchanged"; switch it to Time Range and enter a Start time and a Duration in seconds or as HH:MM:SS.sss. Removing frames costs nothing in quality, unlike lowering the bitrate. For a visual cut with a scrubber instead of typed timecodes, the Video Cutter accepts .3g2 directly.
On "Keep original", yes — the source's pixel aspect is preserved as-is. On any resize it is not: the pipeline flattens pixels to square whenever a scale filter runs. For most phone footage that makes no difference because the pixels were already square, but a clip recorded anamorphically will visibly change shape. When in doubt, convert once at the original size, look at the result, and only then decide whether a resize is worth it.
Only for old certified hardware. If the destination is a phone, a computer, a browser, a smart TV or an editing timeline, 3G2 to MP4 is better on every axis — H.264 fits more quality into fewer bytes, the container is understood everywhere, and nothing needs renaming afterwards. Xvid earns its place when a DivX-certified deck or an in-car unit lists MPEG-4 Part 2 and nothing newer.
Your 3G2 is uploaded over an encrypted connection, converted on our servers, and both it and the Xvid file are deleted automatically after a few hours. Nothing is shared or made public and no account is required. Clips from CDMA handsets are usually well under 10 MB, so this conversion normally finishes about as fast as the upload does.