Initializing... drag & drop files here
Supports: TS
.ts transport stream — or click "+ Add Files" to browse. Multiple files queue and convert in one batch with the same settings..3g2 lands on our servers — no watermark, no sign-up.TS (MPEG-2 Transport Stream, ISO/IEC 13818-1) is a packet-based container designed in 1995 to carry MPEG video, audio, and PSI tables over lossy broadcast links — DVB, ATSC, IPTV, HDHomeRun captures, and the recorded chunks Blu-rays ship in .m2ts form. It's robust but bulky and not natively playable on legacy mobile devices. 3G2 (officially 3GPP2, spec C.S0050-B) is the CDMA2000 sibling of 3GP. Defined by 3GPP2 in January 2004, it's a slim ISO base media container tuned for handsets with limited storage and bandwidth.
.3g2 files for archival, embedded, or repurposed use..ts capture frequently runs 800 MB-1.5 GB; the same content re-encoded to 3G2 at 320x240 with H.263 and AMR-NB audio typically lands at 30-60 MB, useful when SD-card space is tight..3g2 over .mp4.| Property | TS (MPEG-2 Transport Stream) | 3G2 (3GPP2) |
|---|---|---|
| Standard | ISO/IEC 13818-1 (1995) | 3GPP2 C.S0050-B v1.0 (latest Sep 2024; initial Jan 2004) |
| Container family | MPEG-2 Systems (packet stream) | ISO base media file format (like MP4) |
| Designed for | Broadcast, satellite, IPTV, error-prone links | CDMA2000 mobile handsets |
| Typical video codec | MPEG-2, H.264, HEVC | H.263, MPEG-4 Part 2, H.264 |
| Typical audio codec | MPEG-1 L2, AC-3, AAC | AMR-NB, AMR-WB, AAC-LC, HE-AAC v1, EVRC, QCELP |
| Typical bitrate | 5-19 Mbps (SD broadcast) to 40 Mbps (ATSC HDTV) | 30 kbps-512 kbps |
| MIME type | video/MP2T |
video/3gpp2 |
| Native browser playback | Limited (HLS via .m3u8) |
None — needs conversion |
| Best for | Live recording, broadcast capture | Legacy CDMA mobile, MMS, archival |
| Setting | What it means | When to pick it |
|---|---|---|
| H.263 + AMR-NB | Original 3G2 baseline pair | Maximum compatibility with pre-2008 CDMA handsets |
| MPEG-4 Part 2 + AAC-LC | Mid-era profile | Slightly better quality at the same bitrate; widely supported on feature phones |
| H.264 Baseline + AAC-LC | Newer profile inside 3G2 | Smartphones, emulators, and modern players that read .3g2 |
| Constant Bitrate (CBR) | Fixed kbps throughout | Streaming over a known-bandwidth CDMA link |
| Constant Quality (CRF) | Quality target, variable size | Best quality-per-byte for offline playback |
| Specific file size | Pick MB or % of source | Hitting an MMS or carrier cap (often 300 KB-1 MB) |
For a more modern container, see TS to MP4 — H.264/H.265 in MP4 is the right choice for anything newer than a feature phone. If your target accepts GSM-era 3GP instead of CDMA-era 3G2, use TS to 3GP. To go the other way and bring a 3G2 archive into something current, try 3G2 to MP4.
Three reasons we see most often: archival of CDMA-era content (matching the original collection's format), keeping a legacy embedded device working (an old POS terminal, an in-vehicle DVR, a feature-phone-style media player), or testing/validating tooling that targets the 3GPP2 spec. For general mobile playback today, MP4 with H.264 or H.265 is the right call.
No — 3G2 doesn't allow HEVC video or AC-3 audio. We transcode video to H.263, MPEG-4 Part 2, or H.264 (your choice) and audio to AMR-NB, AMR-WB, or AAC-LC. That's a lossy re-encode, so pick a Quality Preset that matches your tolerance: Very High for the smallest visible loss, Low for the smallest file.
3GP (.3gp, video/3gpp) was developed by 3GPP for GSM/UMTS networks — what most of the world outside North America used. 3G2 (.3g2, video/3gpp2) was developed by 3GPP2 for CDMA2000, primarily Verizon, Sprint, and US Cellular in the US plus a handful of Asian and Latin American carriers. The containers are very similar (both based on ISO base media), but 3G2 adds 3GPP2-specific audio codecs (EVRC, EVRC-B, QCELP, SMV) and notably excludes HE-AAC v2 and AMR-WB+ that 3GP supports. If your target device is GSM-lineage (almost everywhere outside the US), prefer 3GP.
The 3GPP2 video spec was written for QCIF (176x144) and QVGA (320x240) class screens, but the container itself doesn't impose a hard ceiling — modern H.264 in 3G2 will hold 720p or even 1080p, it just stops being playable on the legacy hardware the format was made for. Pick a Preset Resolution at or below 480x360 if your goal is genuine feature-phone playback; pick something higher only if you're targeting a modern player that happens to read .3g2.
A typical broadcast TS uses MPEG-2 at 5-19 Mbps for SD or up to 40 Mbps for ATSC HDTV — those bitrates are wildly higher than anything a CDMA handset needs. Re-encoding to H.263 at 64-128 kbps and AMR-NB at 12.2 kbps cuts the file by 50-100x. The visible quality drops accordingly, which is expected for the format — 3G2 was never a quality container, it was a "playable at all on this phone" container.
.m2ts Blu-ray clips?If you rename .m2ts to .ts it will upload, but the smarter path is M2TS to MP4 followed by an MP4-to-3G2 step if you genuinely need 3G2. M2TS is the BDAV variant of MPEG-2 TS with extra 4-byte timestamp headers; our decoder handles it, but you lose nothing by converting to a modern container first.
Yes — drop multiple .ts files in the queue and they convert in parallel with the same Quality Preset, Codec, and Resolution settings. Each TS produces one .3g2; we don't concatenate inputs into a single output. For broadcast captures that were split across two or three files, convert them individually and play them in sequence.
Files process on our servers and upload to our processing servers. There isn't a hard megabyte cap for typical broadcast captures, but very long single recordings (several hours of HDTV at 19 Mbps) will be slow to upload and re-encode — split with Video Cutter first if you only need a segment. For 3G2 output the practical size is tiny regardless of input length.