Convert 3GPP to MPEG Online for Free
Create an MPEG Program Stream delivery from 3GPP media only after checking codecs, PES timing, stream selection, and receiver expectations.
- Add a file Choose or drop it here
- Pick the format Change it whenever needed
- Download the result After conversion completes
3GPP-to-MPEG Changes a Sample-Table File into an MPEG Systems Multiplex
The word "MPEG" is broad, so a useful conversion starts by identifying the requested delivery. A .mpeg or .mpg file commonly means an MPEG Program Stream (PS), not simply any file that contains an MPEG-derived codec. A 3GPP file is structurally based on the ISO base media file format: movie and track boxes lead to media, sample descriptions, and sample tables. The source tells a player where samples are and when each track is presented.
An MPEG-2 Systems Program Stream is a different multiplex. It interleaves elementary-stream data as packetized elementary stream (PES) packets, with pack headers and system information for one program on a shared time base. It was designed for relatively error-free storage or processing environments. Creating PS therefore means constructing a new systems layer around selected video and audio streams; changing a filename cannot perform that mapping.
Inspect the source first. 3GPP can contain H.263, MPEG-4 Visual, AVC/H.264, HEVC/H.265, AMR, AMR-WB, EVS, AAC, timed text, and other metadata tracks. A legacy Program Stream receiver may expect a much smaller codec set, commonly MPEG video and MPEG Layer audio in a DVD- or appliance-oriented workflow. Container compatibility and codec compatibility are separate questions.
Program Stream Packs and PES Packets Carry One Program's Elementary Streams
MPEG Systems defines both Program Stream and Transport Stream, and both are built from PES packets plus other necessary system information. In a Program Stream, packs provide a systems-level grouping and can carry a system clock reference; PES packets identify and carry portions of an elementary stream such as video or audio. This is not equivalent to copying a 3GPP track box. The output multiplexer must choose stream identifiers, interleave packets, and produce a legal program layout for the target.
A source may hold more than one audio track, timed text, a hint track, or timed metadata. List each track's ID, type, language, codec/profile, rate, channels, dimensions, frame timing, duration, and protection state. Then decide what belongs in the Program Stream. Preserve alternate audio only when the target can select it; do not silently discard language information just because a simple player exposes one audio choice. Caption or timed-text support needs its own target-specific plan.
Do not confuse elementary-stream payload with a complete MPEG file. A raw video or audio stream lacks the Program Stream's interleaving, timing, and signalling. Conversely, a valid PS can contain compressed media that a particular receiver still cannot decode. Verify both the systems wrapper and the source codec/profile against the delivery device or authoring rule.
PTS and DTS Must Preserve Presentation Order Rather Than Storage Order
3GPP timing comes from track timescales, sample tables, composition offsets, sync-sample information, and sometimes presentation edits. MPEG PES timing can use a presentation timestamp (PTS) and, where decoding order differs, a decoding timestamp (DTS). The two are not interchangeable. With reordered video frames, a decoder may need one order while a viewer sees another; an output based solely on source file order can stutter, start late, or put audio out of sync.
Translate the intended source timeline, then test it. Check first visible frame, first audible sound, a scene cut, a middle point, a late point, and the final frame. Compare output duration and lip sync. If the source contains lead-in silence, non-zero presentation starts, alternate audio, or an edit list, determine whether that behavior should be retained or deliberately normalized for the receiver. State any trim rather than hiding it in the conversion.
When transcode is required, define the timing policy as part of the output specification: frame-rate conversion or preservation, keyframe interval, audio resampling, downmixing, and whether frames are dropped or duplicated. A new MPEG container cannot recover missing source samples, and a fresh encode adds a lossy generation. Retain the original 3GPP file for comparison and future targets.
Program Stream and Transport Stream Solve Different Delivery Problems. Program Stream and Transport Stream are not interchangeable spellings for an MPEG output. Both use PES, but Transport Stream supports multiplexing programs with independent time bases and is better suited to environments where errors are likely. Program Stream is generally more appropriate for almost error-free environments and one-program software or storage workflows. A broadcast, DVB-style, network, or hardware-ingest requirement may actually call for .ts, not an MPEG Program Stream.
Ask which receiver and transport rule matter before building the file. A DVD-era authoring application may want a tightly constrained PS; a streaming or broadcast chain may require TS program information; a browser might prefer neither. Delivering PS where TS was specified can fail even if the video and audio codecs themselves are suitable, because the receiver expects a different packetization, signalling, or recovery behavior.
Use the desired file extension only after the output family has been decided. "MPEG video" can describe a codec generation, while .mpg often signals a Program Stream container. Include the output container, codecs, geometry, audio layout, and intended receiver in a job record so another operator does not later mistake the target for an arbitrary generic MPEG file.
Codec Decisions Determine Whether 3GPP Packets Can Be Remultiplexed
A remultiplex, often called a remux, is appropriate only if the selected source codecs, profiles, packet form, and timing can be represented in the requested Program Stream and played by the target. 3GPP support for a codec does not prove PS support. AMR and AMR-WB, for example, are central to many mobile 3GPP uses but are not a safe assumption for a conventional Program Stream appliance. H.263, AVC, HEVC, AAC, and MPEG-4 Visual likewise require an explicit target capability check.
If the receiver requires MPEG-1/MPEG-2 video and compatible audio, decode the chosen source streams and encode those settings deliberately. Specify frame size, aspect treatment, frame rate, interlace/progressive behavior, audio codec, rate, channels, and bitrate or quality target. Preserve the source aspect and rotation intentionally; a mobile source that is displayed by orientation metadata can become sideways or stretched when that interpretation is not transferred.
| 3GPP source evidence | Program Stream decision | Result to test |
|---|---|---|
| Track IDs and languages | Select primary and alternate streams deliberately | Correct picture and audio language |
| Codec sample entry and profile | Remux only if target supports the mapping; otherwise encode | Decoder accepts full playback |
| Timescale and composition timing | Generate consistent PES PTS/DTS | No A/V drift or reordered-frame fault |
| Sync samples/keyframes | Preserve or create suitable access points | Receiver starts and seeks as required |
| Rotation and display geometry | Apply pixels or target display policy | Correct orientation and aspect |
| Timed text and metadata | Map only documented target equivalents or export separately | Required context remains available |
3GPP Timed Metadata, Text, and Mobile Context Need an Explicit MPEG Policy
A 3GPP file can contain more than picture and sound: timed text, location, orientation, quality metrics, title/language fields, and extension data may be meaningful. A Program Stream does not automatically reproduce every ISO media box or 3GPP timed-metadata feature. Treat each item separately. Map it only when the target specification and player have a documented compatible representation; otherwise preserve a source metadata export or sidecar record.
Static fields such as title, copyright, language, and creation context can also be handled differently by downstream software. Check what the receiving application actually reads rather than declaring that "metadata is preserved" because a tool copied generic tags. Do not carry sensitive location or author information forward automatically; a new delivery is an opportunity to intentionally remove data the recipient does not need.
Protected tracks are a boundary, not a normal format option. A generic conversion does not remove encryption, rights controls, or authorization requirements. Use an approved workflow if one exists; otherwise retain the authorized original and do not imply that choosing Program Stream changes access rights.
Validate the Finished MPEG File as a Systems Stream and as a Viewing Experience
A reliable delivery check has two layers. First inspect the finished container: selected streams, codec identifiers and settings, duration, packet timing, and any required system data. Second test the actual receiver: file acceptance, first playback, audio presence, orientation/aspect, a scene transition, any requested seek, ending duration, alternate audio, and metadata behavior. A tolerant desktop player is useful but cannot stand in for an appliance, authoring system, or transmission chain.
Record source checksum, chosen 3GPP track IDs, stream-copy or transcode decision, output container (PS or TS when relevant), encoded parameters, timing checks, and receiver version. That evidence makes later faults tractable: it separates a bad source, a missing PES timestamp, an unsupported codec, and a mistaken container request. It also prevents needless re-encoding when a remux would have met the stated target.
The best 3GPP-to-MPEG result is target-specific. For a target that truly requires Program Stream, build a valid PS and confirm it there. For mobile sharing, archive, browser delivery, or broadcast, a different container may be the correct answer even before codec decisions begin.
Answers Before Converting 3GPP Media into an MPEG Program Stream
Does MPEG mean that the output will be MPEG Program Stream?
Not always. Confirm whether the recipient means PS, Transport Stream, a specific codec, or another MPEG-family format before conversion.
Can I change the extension from .3gpp to .mpg?
No. 3GPP and Program Stream use different container structures. A valid output requires a systems-layer mux and, where needed, codec conversion.
Why are both PTS and DTS important?
PTS describes when media is presented; DTS can describe when it must be decoded. They can differ for video with reordered frames, so preserving only one timeline can break playback.
Will my AMR mobile audio play in an MPEG file?
Do not assume so. The target Program Stream receiver's codec support decides whether it can be remuxed or needs an approved audio transcode.
Is Program Stream the right output for broadcast or unreliable networks?
Often no. Transport Stream is designed for different delivery conditions and multi-program use; confirm the system's actual requirement.