Initializing... drag & drop files here
Supports: MPEG2
Turn an MPEG-2 program stream into an MPEG Transport Stream — the fixed-packet, resync-friendly format that broadcast playout, IPTV multiplexers, PVR ingest and HLS segmenting all expect. Both sides of this conversion live in the same ISO/IEC 13818 systems standard, but they are built for opposite conditions: a program stream assumes a reliable disk, a transport stream assumes a lossy wire. The output here is a plain 188-byte-packet .ts — not the 192-byte BDAV framing that Blu-ray-style .m2ts files carry — with H.264 video and AAC audio by default. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours; no sign-up, no watermark, never shared or made public.
.mpeg2 file onto the page or click "+ Add Files" to browse. Queue as many clips as you like — they all convert with the same settings..ts. No sign-up, no watermark.| Property | MPEG-2 program stream (.mpeg2) |
Transport stream (.ts) |
|---|---|---|
| Standard | ISO/IEC 13818-1 systems layer | ISO/IEC 13818-1 systems layer |
| Packetisation | Variable-length packs | Fixed 188-byte packets |
| Framing written here | Program stream | Plain 188-byte TS — not the 192-byte BDAV framing used by .m2ts |
| Designed for | Reliable storage: DVD, local files | Lossy transmission: broadcast, streaming |
| Programs per file | One | Several, each with its own clock |
| Resync after data loss | Poor | Designed for it — packet headers carry sync bytes |
| Typical consumers | DVD players, desktop players, editors | DVB, ATSC, ISDB, IPTV, PVR ingest, HLS segments |
| Default codecs on this page | MPEG-2 video with MP2 or AC-3 audio | H.264 video with AAC audio |
For ordinary viewing or sharing, a transport stream is the wrong container — browsers and phone galleries do not handle raw .ts reliably. Use MPEG-2 to MP4 for that, or TS to MP4 if you already have the transport stream.
Every conversion here re-encodes; there is no stream-copy passthrough, so the codec you choose is the codec that gets produced from scratch. Some combinations are far better travelled than others:
| Combination | Verdict |
|---|---|
| H.264 + AAC (default) | The safe modern choice — what HLS segmenters and most IPTV stacks expect |
| MPEG-2 video + MP2 audio | The classic DVB/ATSC broadcast pairing; pick this when matching a legacy playout profile |
| MPEG-2 video + AC-3 audio | The ATSC pairing for surround; well supported by broadcast equipment |
| H.265 + AAC | Efficient, but check the decoder at the far end before committing a whole archive |
| DTS (DCA) audio | Avoid unless you have no alternative — the DTS encoder is experimental and unreliable; use AC-3 for surround instead |
| DivX / Xvid / MPEG-1 / MPEG-4 video, EAC3 or MP3 audio | Selectable, but well outside the codec set normally carried in a transport stream. Test one short clip on the target player before batch-converting |
Re-encoded, always. There is no stream-copy path here, so even when you set Video Codec to MPEG-2 — matching the source codec — the picture is decoded and encoded again rather than passed through untouched. That is worth knowing for two reasons: it costs a generation of quality, and it means the Quality Preset and bitrate controls genuinely apply no matter which codec you pick. If your only goal was to change the packetisation without touching the picture, this is not the tool for that.
No, and the distinction matters if you are feeding disc-authoring software. This page writes a plain transport stream with the standard 188-byte packets. The .m2ts extension gets BDAV framing instead — 192-byte packets, each a standard 188-byte packet with a four-byte arrival-timestamp prefix — which is what Blu-ray and AVCHD structures use. If the receiving system specifically wants BDAV timestamps, convert to MPEG-2 to M2TS rather than renaming a .ts file.
Because a transport stream is built to survive data loss. It chops each elementary stream into fixed 188-byte packets and interleaves them with regular sync bytes, so a decoder that misses data can find the next packet boundary and carry on — which is exactly what you need over the air, over IP multicast, or across segment boundaries in HLS. It can also carry several programs with independent clocks in one stream. A program stream assumes none of that goes wrong, which is fine on a DVD and unhelpful on a wire.
Yes. Set File Compression to Constant Bitrate and enter your target — that is usually what you want for transport-stream delivery, because a fixed rate keeps a multiplex predictable in a way variable bitrate does not. Constraint Quality is the middle ground: it holds a quality level while capping the peak with a Max bitrate, which suits adaptive-streaming ladders. Specific file size works backwards from a byte target instead, and both it and the bitrate modes offer an Auto Scale toggle that will reduce resolution if the target cannot be met at the source size.
VLC, mpv, FFmpeg-based tooling, broadcast monitoring gear and most IPTV set-top boxes open transport streams directly. Web browsers and phone photo galleries generally do not — a .ts is a delivery format, not a consumer file format. If someone needs to just watch the clip, give them an MP4: MPEG-2 to MP4 from the original source, or TS to MP4 if you only have the transport stream left.
Not unless you ask. Video resolution defaults to Keep original, so a 720×576 or 1920×1080 source keeps its frame dimensions and only the container and codec change. If you do rescale, note that the presets from 4320p to 144p set height and let width follow the source aspect, so they never distort the picture on their own. The exception is anamorphic DVD material: a widescreen disc stores 16:9 inside a 720×480 or 720×576 frame using non-square pixels, and any resize here normalises pixels to square. For those sources use Width x Height and enter the display dimensions you want.
No. Nothing in this pipeline deinterlaces, so 480i and 576i material keeps its woven fields and will comb on motion during progressive playback. For a broadcast chain that is often exactly right, since the downstream equipment expects interlaced content. For anything destined for web playback it is not, and you should deinterlace with a desktop tool before uploading.
No — use AC-3. The DTS encoder available to this pipeline is experimental and unreliable, and it is the wrong tool for producing a dependable surround track. AC-3 is both well supported by broadcast equipment and the pairing ATSC standardised on, so it is the right answer for 5.1 in a transport stream. AAC handles multichannel too and is the better fit for HLS and IP delivery.
There is no fixed per-file quota — with a long MPEG-2 capture the practical constraint is upload size and time over your own connection. Every file is sent over an encrypted connection, processed on our servers, and deleted automatically after a few hours. Nothing is watermarked, shared or made public, and no account is required.