Initializing... drag & drop files here
Supports: 3GPP
Turn an old .3gpp (or .3gp) phone clip into WebM — the open, royalty-free format that plays inline in every modern browser, so you can embed feature-phone footage on a personal site or family-history page with a single HTML5 <video> tag. 3GPP is the GSM-era mobile container most desktop players refuse to open; WebM was built by Google in 2010 specifically for the web. The honest catch: those clips were recorded tiny and soft for 3G networks, and no converter adds detail that was never captured — the output stays small and low-resolution, and the win is playability, not sharpness.
.3gpp or .3gp clips — saved MMS attachments, Nokia / Sony Ericsson / early-Motorola recordings, or footage dumped off an old camera card. Batch is supported; drop several at once.| Property | 3GPP (.3gpp / .3gp) | WebM |
|---|---|---|
| Defined by | 3GPP, for 3G cellular phones | Google, 2010, for HTML5 |
| Container | Simplified MP4 / ISO base media | Matroska-based |
| Video codecs | H.263, MPEG-4 Part 2, H.264/AVC | VP8, VP9, AV1 |
| Audio codecs | AMR-NB, AMR-WB, AAC-LC, HE-AAC | Opus, Vorbis |
| Typical capture resolution | 176×144 (QCIF), 320×240 (QVGA), 352×288 (CIF) | Anything from 240p to 4K+ |
| Royalty status | H.263 / H.264 patent-encumbered | Royalty-free |
| Native browser playback | None — no browser plays 3GPP inline | Chrome, Firefox, Edge, Opera, Safari 14.1+ |
| Era | 2003-2012 feature phones | 2010-present web standard |
Because the source is already low-resolution, going above the original width just enlarges blurry pixels — keep "Keep original" or a matching preset. For device playback over iMessage / WhatsApp instead of web embedding, convert 3GPP to MP4 so H.264 plays natively on iOS and Android. If your clips are saved with the shorter spelling, the extension-twin page 3GP to WebM runs the identical workflow.
No, and no online tool can fix this. The source 3GPP was encoded at low bitrates for 2G / 3G cellular networks, typically at 176×144 or 320×240, so block artifacts and color banding are baked into the original. Upscaling the resolution doesn't add detail — it just enlarges blurry pixels. The conversion moves that footage into a modern, royalty-free container browsers can actually play; if you want it to look better on a big screen, run a separate AI upscaler after converting.
VP9 for almost everything — universal modern-browser support and more efficient than the H.263 inside most 3GPP files. AV1 when you want the smallest possible file and your audience is on 2022-or-newer devices; encoding takes longer but the result is meaningfully smaller. VP8 only for very old Android or extremely conservative legacy embeds, which is rarely needed now. All three are royalty-free, which is the main reason to choose WebM over the patent-encumbered codecs in the original 3GPP.
The audio survives but won't improve. 3GPP voice is usually AMR-NB (narrowband, 8 kHz, roughly 4.75-12.2 kbps) or AAC-LC on later clips; it's re-encoded to Opus (WebM's default) or Vorbis. Speech stays intelligible, but a speech codec already discarded the high frequencies during the original recording, so phone-quality audio stays phone-quality — re-encoding can't recover what was never stored.
.3gpp the same thing as .3gp?Yes — they're two extensions for the same container, defined by the 3rd Generation Partnership Project for GSM-based 3G handsets. The underlying ISO base media structure, codecs, and metadata are identical; .3gp is just the more common spelling. This tool treats them interchangeably. The separate .3g2 extension is the CDMA-network variant (3GPP2), a near-identical container with a few different voice codecs.
Because 3GPP files are tiny by design — they target cellular bandwidth, so a couple of minutes is often only a few megabytes. In our testing, a 30-second QVGA-source 3GPP at the default VP9 quality landed around 3 MB, larger than the 1-2 MB original. WebM reserves more bitrate for video and audio at default quality; to match the original footprint, drop the Quality Preset or set a target in Specific file size. You're trading a slightly bigger file for browser compatibility the original codec can't offer.