3GP is a multimedia container format defined by the 3rd Generation Partnership Project (3GPP) for storing and streaming audio and video on mobile phones and over cellular networks. Within video containers & formats, it belongs to the same family as MP4 and MOV, because it is built on the ISO base media file format and organizes media into boxes that describe tracks, timing and sample locations.
The format was designed in the early 2000s, when handsets had limited processing power, small screens and slow data links. It therefore favors low bit rates, small resolutions and simple codecs such as H.263, MPEG-4 Part 2 and AMR speech audio. Although modern phones record MP4 instead, 3GP files remain common in archives, legacy messaging systems and multimedia messaging service (MMS) workflows.
How the 3GP container is structured
A 3GP file stores media as a hierarchy of boxes, also called atoms, exactly as the ISO base media file format prescribes. The opening ftyp box declares the brand, such as 3gp4, 3gp5 or 3gp6, which tells a player which release of the 3GPP specification the file follows and therefore which features it may contain.
The moov box holds the metadata: track headers, timescales, codec configuration and sample tables that map every frame to a byte offset. The mdat box holds the compressed audio and video samples themselves. Because the structure is shared with MP4, many tools can remux a 3GP file into MP4 without re-encoding, simply by rewriting the brand and the surrounding boxes.
The following table summarizes the main boxes and what each one contributes to playback.
| Box | Role | Effect on playback |
|---|---|---|
| ftyp | Declares brand and compatible brands | Player decides whether it can open the file |
| moov | Holds track metadata and sample tables | Enables seeking and synchronization |
| mdat | Stores compressed media samples | Supplies the actual audio and video data |
| udta | Carries user data such as titles | Displays descriptive information |
| moof | Describes a movie fragment | Supports progressive and adaptive delivery |
When the moov box is placed before the mdat box, a phone can begin playback while the file is still downloading. This arrangement, often called fast start, was essential for early progressive download over 2G and 3G networks.
Codecs and profiles allowed in 3GP
3GP does not compress anything itself; it only defines which codecs a conforming file may carry. The permitted list grew with each 3GPP release, moving from basic speech and video codecs toward H.264/AVC and AAC, which brought quality close to that of desktop MP4 files.
The table below lists the codecs most often found in real 3GP files and their typical operating ranges.
| Codec | Media type | Typical bit rate | Typical use |
|---|---|---|---|
| H.263 | Video | 64 to 384 kbit/s | Early camera phones and video calls |
| MPEG-4 Part 2 | Video | 128 to 768 kbit/s | Mid-2000s phone recordings |
| H.264/AVC | Video | 200 kbit/s to 2 Mbit/s | Later handsets and streaming |
| AMR-NB | Audio | 4.75 to 12.2 kbit/s | Narrowband speech |
| AMR-WB | Audio | 6.6 to 23.85 kbit/s | Wideband speech |
| AAC and HE-AAC | Audio | 24 to 128 kbit/s | Music and general audio |
Typical 3GP video resolutions were QCIF at 176 x 144 and QVGA at 320 x 240, recorded at 10 to 15 frames per second on early devices and up to 30 frames per second later. These figures explain why many archived 3GP clips look soft and blocky on modern screens: the limitation lies in the capture settings and codec, not in the container.
3GP compared with 3G2, MP4 and other containers
3GP is best understood as a constrained profile of the MP4 family rather than an unrelated format. A sibling format, 3G2, was defined by 3GPP2 for CDMA2000 networks and adds support for codecs such as EVRC and QCELP. Both formats can usually be opened by the same players, yet they are not formally interchangeable.
The comparison below places 3GP among neighboring containers that video engineers meet in practice.
| Container | Standard body | Main strength | Main limitation |
|---|---|---|---|
| 3GP | 3GPP | Small files for mobile networks | Narrow codec list, dated profiles |
| 3G2 | 3GPP2 | CDMA network codecs | Even narrower device support |
| MP4 | ISO/IEC MPEG | Universal playback and streaming | Larger feature set to implement |
| MKV | Matroska project | Almost any codec and many tracks | Weak support on old phones |
| WebM | Open web project | Royalty-free web video | Limited to VP8, VP9, AV1 and Opus or Vorbis |
In practical terms, renaming a 3GP file to .mp4 often works because both use the same box structure, but strict MP4 validators may still reject brands or codecs such as AMR that MP4 profiles do not normally list. A proper remux or transcode is the reliable route.
Working with 3GP files today
Most current work with 3GP involves conversion, preservation or compatibility testing rather than new production. Editors and archivists need to decide whether to keep the original streams or re-encode them, and the right choice depends on the codecs inside and the destination platform.
The decision table below captures the usual options.
| Situation | Recommended action | Reason |
|---|---|---|
| H.264 video with AAC audio | Remux to MP4 | No quality loss, fast and lossless |
| H.263 or MPEG-4 Part 2 video | Transcode to H.264 or HEVC | Modern editors handle these poorly |
| AMR speech audio | Transcode audio to AAC | AMR is rarely supported outside phones |
| Archival master copy | Keep the original plus a converted copy | Preserves the authentic source |
| MMS delivery to legacy devices | Encode directly to 3GP | Gateways may expect 3GP brands |
Before converting, a technician should inspect the file with a media analysis tool to read the brand, codec identifiers, frame rate and duration. Variable frame rates were common on early phones, so an editor may need to conform the footage to a constant frame rate to avoid audio drift on the timeline.
Limitations and common mistakes
The main weakness of 3GP is its dated codec ecosystem. Many modern players, browsers and editing applications no longer decode AMR audio or H.263 video, so a file that played perfectly on a 2006 handset may open silently or not at all on a current computer.
- Assuming the container sets quality: the codec and capture settings determine image quality, while 3GP only packages the streams.
- Upscaling without care: enlarging QCIF footage to HD multiplies artifacts; mild denoising before scaling usually gives better results.
- Ignoring timestamps: missing or irregular timing in the sample tables can cause audio and video drift after conversion.
- Discarding originals: once transcoded, lost metadata such as recording date and device model cannot be recovered.
Stripped to the essentials
A 3GP file is a small box for video and sound that was made for old mobile phones. It does not decide how good the picture looks. It simply holds the compressed picture and sound together so that a phone can play them in the right order.
Think of it as a compact travel case packed for a slow journey. Everything inside was squeezed to fit early phone networks, which is why old clips look rough today. The key point is simple: 3GP is a close relative of MP4, so most old clips can be moved into an MP4 file or converted with little effort.
Where it is applied
A regional television newsroom receives a box of donated phones containing clips of a 2007 flood. The files are 3GP, recorded at 176 x 144 pixels and 15 frames per second, with H.263 video and AMR-NB audio at 12.2 kbit/s. The newsroom editing software opens the video track but plays no sound.
The archive technician first copies every original file to protected storage. Next, she inspects each clip to confirm the codecs, then transcodes the video to H.264 and the audio to AAC in an MP4 container, conforming the variable frame rate to a constant 15 frames per second. The result is a set of clips that play with synchronized sound in the edit suite, while the untouched 3GP originals remain available for verification and future preservation work.