Convert 3GPP to M2TS — Free Online Tool
Convert 3GPP mobile video files to M2TS (Blu-ray MPEG-2 Transport Stream) format, re-encoding the video with H.264 and audio with AAC to meet the higher-quality, broadcast-grade standards of the M2TS container. This tool is ideal for upscaling archival mobile footage into a format compatible with Blu-ray authoring software and AVCHD workflows.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your 3GPP file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
3GPP files are a compact, low-bitrate container designed for 3G mobile devices, typically carrying H.264 video and AAC audio at very modest resolutions and bitrates. M2TS is a transport stream container used on Blu-ray discs and AVCHD camcorders, designed for high-definition, broadcast-grade playback. Because both formats can carry H.264 video and AAC audio, the codecs themselves are compatible — but the containers are structurally very different. FFmpeg must fully decode the 3GP stream and re-encode it into the MPEG-2 Transport Stream packet structure that M2TS requires. The video is re-encoded using libx264 at CRF 23, which controls quality rather than bitrate, and the audio is re-encoded to AAC at 128k — a significant upgrade from the 64k default typically found in 3GPP files. The result is a properly structured .m2ts file that Blu-ray authoring tools, media servers, and AVCHD-compatible players can read natively.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool, which handles all decoding, re-encoding, and container remuxing. In the browser-based version of this tool, FFmpeg runs via WebAssembly (FFmpeg.wasm) entirely on your local machine — no data is sent to a server. |
-i input.3gp
|
Specifies the input 3GPP file. FFmpeg reads and demuxes the 3GP container, extracting the video and audio elementary streams for decoding before re-encoding into the M2TS format. |
-c:v libx264
|
Sets the video encoder to libx264 (H.264), which is the standard video codec for AVCHD and Blu-ray-compatible M2TS files. Since the source 3GP likely also uses H.264, this re-encodes the stream into the transport stream packet structure required by M2TS. |
-c:a aac
|
Sets the audio encoder to AAC, transcoding whatever audio codec was in the 3GPP source (typically low-bitrate AAC or AMR) into a fresh AAC stream at the higher bitrate specified by -b:a, suitable for the M2TS container. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 video encode to 23, which is a balanced quality setting. Lower values (e.g., 18) produce higher quality at larger file sizes, which may be preferable for Blu-ray archiving, while higher values compress more aggressively. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second — double the 64k default of a typical 3GPP file. This upgrade improves audio clarity noticeably, especially for speech and music content from the original mobile recording. |
output.m2ts
|
Specifies the output filename with the .m2ts extension, which instructs FFmpeg to wrap the encoded H.264 video and AAC audio streams into an MPEG-2 Transport Stream container, the standard format for Blu-ray discs and AVCHD camcorder recordings. |
Common Use Cases
- Incorporating old mobile phone footage (recorded in 3GPP format) into a Blu-ray disc project using authoring software like Encore or Sony Vegas
- Archiving 3G-era video content into M2TS for long-term storage in a broadcast-compatible format on a media server
- Preparing mobile-captured event footage for editing in AVCHD-compatible video editors such as Final Cut Pro or Premiere Pro
- Upscaling 3GPP clips for use in a professional video production pipeline where the delivery format requires MPEG-2 Transport Stream
- Converting a collection of legacy mobile videos to M2TS so they can be played back on a Blu-ray player via USB or disc
- Standardizing mixed-format video libraries by converting 3GPP files to a uniform M2TS format alongside other HD sources
Frequently Asked Questions
No — converting from 3GPP to M2TS does not recover quality that was lost when the original video was recorded on a mobile device. 3GPP files are encoded at low resolutions and bitrates suited for 3G networks, and re-encoding to M2TS with H.264 at CRF 23 produces a higher-quality encode of the same source material. The output will be a cleaner, less compressed version of the original low-resolution content, but the source resolution and detail cannot be invented during conversion.
3GPP files are deliberately compressed to very small sizes for mobile transmission, often using audio bitrates as low as 12–32k and video resolutions as low as 176x144. When re-encoded to M2TS with a CRF of 23 and 128k audio, the encoder allocates significantly more data per frame to maintain quality, and the M2TS transport stream container itself adds overhead through its packet structure. Expect the output file to be several times larger than the source 3GP file even at the same resolution.
M2TS does support subtitles and multiple audio tracks as a container format, but standard 3GPP files do not carry subtitle streams or multiple audio tracks. This conversion will produce a single-video, single-audio M2TS file reflecting what was actually present in the 3GP source. If you need to add subtitles or additional audio tracks to the M2TS output, that would require separate steps beyond this conversion.
Yes, the .m2ts output uses H.264 video and AAC audio inside an MPEG-2 Transport Stream container, which is the standard structure for AVCHD and Blu-ray video. Most Blu-ray authoring tools and AVCHD-compatible editors will recognize and import this file. However, strict Blu-ray specification compliance may require the video to meet specific resolution (1080p/720p) and bitrate requirements — if your source 3GPP video is low resolution, you may need to scale it during conversion to meet those requirements.
To change video quality, modify the '-crf 23' value: lower numbers (e.g., '-crf 18') produce higher quality and larger files, while higher numbers (e.g., '-crf 28') reduce quality and file size. To change audio bitrate, modify '-b:a 128k' to a value like '-b:a 192k' for higher quality or '-b:a 96k' for a smaller file. For example: 'ffmpeg -i input.3gp -c:v libx264 -c:a aac -crf 18 -b:a 192k output.m2ts' would produce a noticeably higher quality output suitable for more demanding Blu-ray authoring use cases.
Yes. On Linux or macOS, you can loop over files in a directory with a shell command like: 'for f in *.3gp; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.3gp}.m2ts"; done'. On Windows Command Prompt, use: 'for %f in (*.3gp) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.m2ts"'. This is especially useful for converting large archives of legacy mobile video files where individual browser-based conversion would be impractical.
Technical Notes
The 3GPP container is derived from the MPEG-4 Part 12 base format (closely related to MP4), while M2TS is based on the MPEG-2 Transport Stream specification — these are structurally incompatible containers requiring full remux rather than a simple stream copy. The 3GPP format's '-movflags +faststart' optimization (which relocates the moov atom for streaming) is irrelevant to M2TS output, which uses a packet-based transport stream structure instead. The audio bitrate upgrade from 3GPP's typical 64k default to 128k in the M2TS output is meaningful and audible, particularly for speech and music content in the source file. Note that 3GPP does not support transparency, subtitles, chapters, or multiple audio tracks, so none of these features will be present in the output M2TS file regardless of the container's support for them. If the source 3GPP file contains only audio (no video stream), the FFmpeg command will need to be modified accordingly. Additionally, very old 3GPP files may carry AMR (Adaptive Multi-Rate) audio rather than AAC — FFmpeg handles this transparently by decoding and re-encoding to AAC, but users should be aware the audio fidelity of AMR-sourced files will be limited by the original codec.