Initializing... drag & drop files here
Supports: 3GPP
This tool turns a .3gpp clip from an old GSM-era phone into an AVI file that VirtualDub-era Windows editors and other tools that reject .3gpp will accept. .3gpp is the same MPEG-4 container as .3gp — two spellings of one format — so a file named .3gp works on the 3GP to AVI page instead. AVI is Microsoft's RIFF-based container from 1992, and xconvert writes the video as MPEG-4 with MP3 audio by default; that re-encode is honest about its limits, covered below.
.3gpp videos. Batch is supported, so a folder of old phone clips can run in one job.| Property | 3GPP (source) | AVI (output) |
|---|---|---|
| Defined by | 3rd Generation Partnership Project (ETSI TS 126 244) | Microsoft (Video for Windows, Nov 1992) |
| Base format | MPEG-4 Part 12 (ISO/IEC 14496-12) | RIFF (chunked container) |
| Typical video codec | H.263, MPEG-4 Part 2, or H.264 | MPEG-4 (xconvert default), also H.264 / Xvid / DivX |
| Typical audio codec | AMR-NB, AMR-WB, or AAC | MP3 (xconvert default) |
| Designed for | GSM / UMTS phones, MMS, feature-phone video | Desktop playback and Windows editing |
| Resolution it carries | Small phone-era frames | Whatever the source had — re-encoding can't add detail |
| Best when | Sharing over a mobile network | A Windows editor or player won't open .3gpp |
Both formats are dated. If your goal is a clip that plays on modern phones, browsers, and editors, MP4 is the better target — 3GPP to MP4 re-wraps to H.264 and is the honest modern pick. Choose AVI specifically when an older Windows tool demands it.
Yes. .3gpp and .3gp are two filename extensions for the identical MPEG-4 Part 12 container that 3GPP defined for GSM and UMTS phones — same structure, same codecs, same content. This page accepts .3gpp; if your file is named .3gp, use 3GP to AVI instead. Note that .3g2 is a genuinely different format (3GPP2, for CDMA2000 phones), not just a different spelling.
No. The phone recorded the video as H.263 or MPEG-4 at a small resolution, and re-encoding it into MPEG-4-in-AVI is one more lossy generation, not an upgrade. The output keeps the source's frame size unless you deliberately scale it up, and upscaling adds pixels without adding any detail the camera never captured. AVI is the right pick for compatibility with an old Windows editor, not for making an old clip look better.
Because 3GPP was built to be tiny for mobile networks, while AVI carries less aggressive compression and adds RIFF container overhead. Re-encoding the same footage to MPEG-4-in-AVI typically lands larger than the heavily compressed phone original. If size matters more than Windows-editor compatibility, MP4 is far more space-efficient — see 3GPP to MP4.
The 3GPP soundtrack is usually AMR-NB, a narrowband speech codec, and xconvert re-encodes it to MP3 for the AVI. MP3 preserves what AMR captured but cannot add fidelity that was never recorded — AMR-NB only holds roughly telephone-quality audio (around 200–3,400 Hz), so the MP3 will sound the same as the tinny original, just in a format AVI and Windows editors handle natively.
Files are uploaded over an encrypted connection and processed on our servers — no sign-up and no watermark. They are deleted automatically a few hours after conversion and are never shared or made public.