Cut 3GP files by setting start and end times. Free, no quality loss.
Process files in seconds with our optimized servers
Frame-accurate cuts with intuitive timeline controls
Maintain original quality with smart re-encoding
.3gp or .3g2 clip onto the page, or click "Add Files" to browse. Batch uploads are supported, and old feature-phone recordings (often 176x144 or 320x240) work the same as 720p H.264 3GP from newer Android devices.HH:MM:SS.ms format (e.g., 00:00:08.500 start, 00:00:20.000 duration). For multi-segment edits, queue several cuts back-to-back instead of one large range.3GP (.3gp) is the 3GPP container that shipped with virtually every 2G/3G/early-4G feature phone and Symbian/early-Android handset. It wraps H.263, MPEG-4 Part 2, or H.264 video alongside AMR-NB, AMR-WB, or AAC-LC audio inside an MPEG-4 Part 12 base structure, optimized in the early 2000s for cellular bandwidth and tiny storage cards. Most cuts on 3GP happen because the source clip is a long, unedited camcorder roll from an old Nokia, Samsung, or Sony Ericsson handset and the user wants one usable segment.
| Property | 3GP (.3gp) |
MP4 (.mp4) |
|---|---|---|
| Standard body | 3GPP (ETSI TS 26.244) | MPEG / ISO/IEC 14496-14 |
| Base container | MPEG-4 Part 12 (ISO BMFF) | MPEG-4 Part 12 (ISO BMFF) |
| Typical video codecs | H.263, MPEG-4 Part 2, H.264 | H.264, H.265, AV1, MPEG-4 Part 2 |
| Typical audio codecs | AMR-NB, AMR-WB, AAC-LC, HE-AAC | AAC-LC, HE-AAC, MP3, AC-3, Opus |
| Designed for | 3G cellular, feature phones | Web, desktop, modern mobile |
| MIME type | video/3gpp |
video/mp4 |
| iOS Photos / share sheet | Limited; iOS 9 deprecated native record | Native |
| Typical bitrate range | 64-384 kbps | 1-50 Mbps+ |
| Common resolutions | 176x144, 320x240, 352x288, 640x480 | 360p to 8K |
| When to use it | Compatibility with old handsets, legacy archives | Default modern playback target |
| Goal | Preset | Codec choice | Approx. output |
|---|---|---|---|
| Smallest size, legacy phone playback | Lowest preset, 176x144 | H.263 + AMR-NB | ~50-100 KB / 10 sec |
| Balanced legacy compatibility | Medium, 320x240 | MPEG-4 Part 2 + AAC | ~200-400 KB / 10 sec |
| Best 3GP quality | Highest, 640x480 | H.264 Baseline + AAC | ~700 KB-1.5 MB / 10 sec |
| Lossless cut (no re-encode) | Original | Copy streams | Unchanged bitrate, exact source quality |
Not if the cut is stream-copied. When you keep the codec and resolution at their original values, the underlying H.263, MPEG-4 Part 2, or H.264 frames are not decoded and re-encoded — they're sliced at the nearest valid boundary and re-packaged into a new 3GP container. If you change the codec, resolution, or quality preset, a transcode does happen and quality depends on the settings you pick.
3GP video is typically GOP-coded (groups of pictures with one keyframe followed by predicted P-frames), and a clean cut can only land on a keyframe without re-encoding. For H.263 and MPEG-4 Part 2 sources, keyframes are often 1-3 seconds apart. If frame-exact cuts matter, allow the tool to re-encode (don't pick "Original" codec) — that produces a frame-accurate result at the cost of some quality.
.3g2 files from CDMA phones too?Yes. The accepted extensions are .3gp and .3g2. 3G2 is the 3GPP2 variant for CDMA2000 networks (older Verizon, Sprint, and KDDI handsets). It uses the same MPEG-4 Part 12 base but adds EVRC, QCELP, and SMV audio codecs. The cutter handles both; if you need to convert formats, see Convert 3GP to 3G2 or vice versa.
iOS deprecated native 3GP recording in iOS 9 (2015), and the Photos app may not preview 3GP cleanly on modern iPhones. For reliable iOS playback after cutting, transcode the result with Convert 3GP to MP4 — MP4 with H.264 + AAC plays everywhere from iOS 4 onward. Android and VLC on all platforms still play 3GP natively.
AMR (Adaptive Multi-Rate) is a narrowband speech codec sampled at 8 kHz (AMR-NB) or 16 kHz (AMR-WB), designed for voice over 3G. It sounds noticeably worse than music-capable codecs like AAC, but it cuts fine. If you plan to keep cutting and remixing, transcode to AAC during the cut by switching audio output away from AMR; once AMR audio is decoded it can't be losslessly upgraded, but the cut itself doesn't add new degradation.
Yes. Cuts run in your browser session, so the practical ceiling is browser memory rather than a server upload limit. 3GP files larger than ~200 MB are unusual (the format was optimized for small cellular files), but H.264-in-3GP from newer handsets can reach that range for 10-20 minute recordings. If your file is unusually large, consider running Compress 3GP before or after cutting.
Two common reasons. First, if you re-encoded and picked a higher quality preset than the source, the new file genuinely has more data per frame. Second, when you change the video codec from H.263 to H.264 the bitrate floor for "watchable" rises — H.264 at 64 kbps looks worse than H.263 at 64 kbps in many phone-resolution scenarios. To match the original size, pick the same codec family and choose a Target file size (%) of 100 or lower.
Cut first. Cutting a 30-second segment out of a 10-minute file before compressing means the compression step only has to process 30 seconds of frames, so it's faster and the bitrate-vs-quality math is simpler. Cut, verify the segment plays, then run Compress 3GP if you still need the file smaller for MMS or a low-storage device.
Not in a single pass on this page — the cut tool produces one continuous output from one Start + Duration. For multi-segment work, run separate cuts to produce N clips, then use a merge tool to concatenate them. Multi-cut workflows are most reliable when all output segments share the same codec, resolution, and frame rate.