Initializing... drag & drop files here
Supports: 3GPP
This walks you through rescuing a .3gpp clip — the kind a GSM-era phone recorded for MMS — into MKV, the open Matroska container that desktops, VLC, and editors actually open. .3gpp and .3gp are two spellings of the same MPEG-4 Part 12 file (3GPP defined it in ETSI TS 126.244), so a file named .3gp belongs on the 3GP to MKV page instead. By the end you will know which settings to leave alone, which to change, and where re-encoding can and cannot help.
.3gpp videos. Batch is supported, so a folder of old phone clips can run as one job.MKV is a container, not a codec — it just holds whatever video and audio streams you mux into it, which is why the codec choice matters more than the wrapper. By default xconvert writes the video as H.264 and the audio as AAC, a pairing that opens in VLC, mpv, and every recent desktop and mobile player without extra work. Your source almost certainly arrives as H.263 or MPEG-4 Part 2 video with AMR-NB speech audio, so this is a re-encode, not a passthrough — covered honestly below.
If the clip is DRM-protected or partially corrupted — a half-finished MMS download, a truncated transfer — re-encoding cannot reconstruct missing data, and the job may fail or produce a short, glitchy MKV. There is no honest way to recover frames that were never fully written. In that case, try playing the original in VLC first to confirm it decodes at all; if VLC stalls too, the source file itself is damaged. For clips you simply want playing on a modern phone rather than archived, 3GPP to MP4 is the device-friendly target instead of MKV.
Yes. .3gpp and .3gp are two filename extensions for the identical MPEG-4 Part 12 container that 3GPP standardized in ETSI TS 126.244 for GSM and UMTS phones — same structure, same codecs, same content. This page accepts .3gpp; if your file is named .3gp, use 3GP to MKV instead. Note that .3g2 is a genuinely different format (3GPP2, for CDMA2000 phones), not just another spelling.
MKV is a royalty-free open container (announced in 2002, published as IETF RFC 9559 in 2024) that holds an unlimited number of video, audio, and subtitle tracks in one file, which makes it a strong choice for long-term archiving and for clips you want to bundle with subtitles. MP4 is the better pick if your goal is a file that plays natively on phones and shares easily — see 3GPP to MP4. Choose MKV when you want the open, future-proof wrapper.
No. The phone recorded the video as H.263 or MPEG-4 Part 2 at a small resolution, and re-wrapping it into H.264-in-MKV is one more lossy generation, not an upgrade. The output keeps the source frame size unless you deliberately scale it up, and upscaling adds pixels without adding detail the camera never captured. MKV is the right pick for an open, multi-track archive, not for making an old clip look sharper.
The 3GPP soundtrack is usually AMR-NB, a narrowband speech codec, and by default xconvert re-encodes it to AAC for the MKV. AAC preserves what AMR captured but cannot add fidelity that was never recorded — AMR-NB only holds roughly telephone-quality audio (about 200–3,400 Hz at an 8 kHz sample rate), so the AAC track will sound the same as the original, just in a codec every player decodes natively.
MKV the container supports unlimited audio and subtitle tracks, which is one of its main advantages over the single-track 3GPP source. That said, your phone clip almost certainly contains just one video and one audio stream, so the conversion produces a one-track MKV — there are no extra subtitles or languages to recover that the source never had. The benefit is forward-looking: the open container is ready to hold added tracks later in an editor.
In our testing, re-encoding a small feature-phone clip to H.265 produced a meaningfully smaller MKV than H.264 at a comparable visual setting, but on a source this low-resolution the absolute file sizes are tiny either way, so the practical saving is small. We default to H.264 because it decodes on the widest range of hardware; reach for H.265 only when storage space genuinely matters and you know your players support it.
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.