Initializing... drag & drop files here
Supports: MOV
3GP is the 3GPP mobile container — MDN lists its MIME type as video/3gpp and describes it as designed for audio and video transmission over cellular networks for consumption on mobile devices. Converting an Apple QuickTime MOV into it is a downgrade on purpose: a small file an old handset or a size-capped upload will accept.
This page covers the four steps, then goes deeper on the two settings that actually decide whether the result plays — the video codec (where H.263 behaves very differently from the rest) and the audio codec (where the narrowband options quietly rewrite your sample rate).
.mov onto the page or click "Add Files" to browse. Several clips can be queued and encoded with the same settings in one batch.Three of the four video codecs behave normally — H.264, MPEG-4 and Xvid all encode whatever resolution you asked for. H.263 does not, and it is the one people pick for maximum handset compatibility.
We reproduced the underlying constraint directly: asked to encode a 640x480 frame, FFmpeg's H.263 encoder refuses with "The specified picture size of 640x480 is not valid for the H.263 codec. Valid sizes are 128x96, 176x144, 352x288, 704x576, and 1408x1152." Rather than hand you that failure, our pipeline snaps the frame to a legal size before encoding.
mp4v — the same codec and tag as the MPEG-4 entry.The Audio Codec group on this page is configured with a default value that does not correspond to any of the three buttons shown, so nothing appears preselected. That is cosmetic rather than broken: if you convert without touching it, the server falls back to the container's default and writes AAC audio, which the 3GPP file format allows. Still, it is worth choosing deliberately.
| Property | MOV (QuickTime) | 3GP (3GPP) |
|---|---|---|
| MIME type | video/quicktime |
video/3gpp |
| Origin | Apple QuickTime | 3rd Generation Partnership Project |
| Video codecs in common use | H.264, HEVC, ProRes | H.263, H.264, MPEG-4 Part 2 (MDN also lists VP8) |
| Audio codecs in common use | AAC, PCM | AMR-NB, AMR-WB, AMR-WB+, AAC-LC, HE-AAC, MP3 (MDN) |
| Browser playback | None — MDN's compatibility table shows no support in Chrome, Edge, Firefox or Safari | None in mainstream desktop browsers |
| Typical role | Capture and editing master | Small mobile delivery file |
| Codec | What you get | Pick it when |
|---|---|---|
| H.264 | The starting selection; modern, efficient, best quality per byte | Almost always, unless the target device is genuinely ancient |
| MPEG-4 | MPEG-4 Part 2 Simple Profile, tagged mp4v |
A player accepts 3GP but chokes on H.264 |
| Xvid | Also MPEG-4 Part 2 Simple Profile, tagged mp4v |
No practical reason to prefer it over MPEG-4 here |
| H.263 | Oldest and most universally supported, but locks the frame to 128x96, 176x144, 352x288, 704x576 or 1408x1152 | Feature-phone playback, and you accept the forced frame size |
| AAC (audio) | Full-bandwidth stereo | Music, or any target from the last fifteen years |
| AMR Narrow Band (audio) | Forced to 8000 Hz mono | Speech-only clips headed for old handsets |
| AMR Wide Band (audio) | Forced to 16000 Hz mono | Speech where the device supports wideband |
3GP is a delivery format for hardware that is largely retired, so the honest failure mode is that you did not need it. If the goal is a smaller file for a modern phone or a messaging app, MOV to MP4 gives you far better quality at the same size and plays everywhere; if the goal is simply less data from the same file, compress MOV keeps the container. If the target device is on a CDMA network rather than GSM/UMTS, its container is 3G2 — use MOV to 3G2. And if the clip is long, trimming the source with video-cutter before converting is faster than uploading the whole thing.
Because H.263 accepts only five frame sizes and the pipeline picks one for you before encoding — the largest legal size that fits inside the source frame. A 1080p source therefore lands on 704x576. The resolution controls are applied for every other codec on this page; H.263 is the exception. Select H.264 if you want the size you chose.
H.263 video with AMR Narrow Band audio. That combination is the lowest common denominator of the 3GPP era, and it is what a device from that period was built to decode. Accept that you are getting a 4:3 frame at 8 kHz mono audio — on a phone from that generation, nothing better would have played anyway.
No. The group's configured default value does not match any of the three visible buttons, so the interface shows none of them highlighted. Converting anyway produces AAC audio, because the server falls back to the 3GP container's own default. Select AAC, AMR Narrow Band or AMR Wide Band explicitly if you want to be certain what you are getting.
They are sibling containers for different mobile networks. 3GP comes from the 3GPP, whose members standardised GSM and UMTS; 3G2 comes from 3GPP2, which standardised CDMA2000. ExifTool describes 3G2 as "3rd Gen. Partnership Project 2 a/v" and classifies it as QuickTime-based, the same lineage 3GP shares. MDN lists both under one entry with MIME types video/3gpp and video/3gpp2. If your handset is a CDMA device, convert to 3G2 instead.
No. The 3GP encode discards detail permanently, and if H.263 was involved the frame was also scaled down and reshaped. Converting 3GP back to MP4 re-wraps what survived; it cannot rebuild what was thrown away. Keep the original MOV if you may need full quality again.
Always a re-encode. Our servers decode the MOV's video and audio and encode fresh streams into the 3GP container — there is no stream-copy path, which is why the settings on this page have real effect and why the conversion takes proportionally longer on long clips.
Technically yes with H.264 and "Keep original" resolution, but it defeats the purpose. Devices that need 3GP cannot decode those resolutions, and anything that can decode them would rather have MP4. If you find yourself keeping full resolution, the container you actually want is MP4.
They are uploaded over an encrypted connection, converted on our servers and deleted automatically after a few hours — never shared, never made public, no sign-up and no watermark. The real-world limit on a long MOV is upload time rather than the encode; trimming to a Time Range or targeting a Specific file size keeps the job short.