Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
TS (MPEG Transport Stream) is the digital container defined by ISO/IEC 13818-1, also published as ITU-T Recommendation H.222.0. It carries video, audio, and metadata in fixed 188-byte packets that include synchronization markers, so receivers can recover the stream even when packets are lost or arrive out of order. That packet structure is why TS underpins every major broadcast and streaming standard, and why a still photo turned into a TS file plays where a JPEG never could - inside a TV playout chain, an HLS playlist, or an IPTV head-end.
| Property | TS (MPEG-TS) | MP4 (ISO BMFF) | MXF |
|---|---|---|---|
| Standard | ISO/IEC 13818-1 (1995) | ISO/IEC 14496-14 (2003) | SMPTE ST 377 (2004) |
| Packet / chunk size | Fixed 188 bytes | Variable atom size | Variable KLV triplets |
| Designed for | Lossy broadcast / streaming | File storage and download | Professional post-production |
| Native HLS segment | Yes (legacy + supported) | fMP4 (HLS since 2016) | No |
| Error resilience | High - stream recovers after packet loss | Low - corrupted box can break file | Medium |
| Random-access seeking | Limited without index | Excellent (moov atom) | Excellent |
| Typical use | DVB, ATSC, IPTV, HLS, capture | Web, mobile, social, NLEs | Broadcast post, archive |
| Setting | When to pick it | Notes |
|---|---|---|
| H.264 (default) | Default for HLS, IPTV, modern set-top boxes | Highest device compatibility; supported in HLS since launch |
| H.265 / HEVC | 4K signage, bandwidth-constrained IPTV | ~50% smaller files at equal quality vs H.264; not supported by all legacy TS hardware |
| MPEG-2 | Legacy DVB / ATSC playout, older STBs | The original TS video codec; ~2-3x larger files than H.264 at equal quality |
| AAC audio (default) | HLS, modern IPTV, ATSC 3.0 | Mandated by HLS spec; LC profile is the safe choice |
| AC-3 (Dolby Digital) | ATSC 1.0 broadcast, North American DVRs | Required by ATSC for primary audio; license-encumbered |
| MP2 audio | DVB broadcast, European IPTV | Default in DVB; widest legacy receiver support |
| Quality: Very High (recommended) | Most HLS / IPTV use | Balanced bitrate; CRF ~20 internally |
| Quality: Highest | Master TS for re-encoding pipelines | Near-lossless; large files |
| Quality: Low / Very Low | Slate cards, channel fillers, test segments | Tiny files; visible compression artifacts on detail |
A .ts file is an MPEG Transport Stream container - the format standardized as ISO/IEC 13818-1 (and ITU-T H.222.0) in 1995. It wraps video, audio, and program metadata into 188-byte packets carrying Program Association Table (PAT) and Program Map Table (PMT) entries that tell a receiver which streams are inside. The same container drives DVB and ATSC TV broadcasts, IPTV delivery, and Apple HTTP Live Streaming segments.
MP4 cannot be inserted into a broadcast playout chain or an HLS .ts segment list without re-wrapping. Playout servers, DVB multiplexers, ATSC transmitters, and many IPTV head-ends ingest only TS. If your downstream system is one of those - or if you are building an .m3u8 playlist out of legacy .ts segments - converting straight to TS skips an extra ffmpeg pass. For web playback or social uploads, JPEG to MP4 is the better target.
Yes. VLC, ffmpeg, mpv, and most desktop media players read MPEG-TS natively because the format predates them all. The output produced here is standard-compliant TS with H.264 video and AAC audio by default, which is the same combination Apple HLS specifies, so it also plays in any HLS-capable player when listed in an .m3u8 manifest.
Effective frame rate is set by the Image Duration option. Choosing 1/60s gives a single frame at 60 fps; 1/30s gives a single frame at 30 fps; longer durations (1-10 seconds per image) produce a steady slideshow at standard frame rates. For HLS segments paired with other live content, match the duration to your existing segment length (commonly 6-10 seconds per .ts segment).
H.264 is the safer default - it is mandatory in HLS and supported by every modern STB, ATSC tuner, and HLS player. Pick H.265 / HEVC only when you control both ends of the pipeline (for example, a 4K digital-signage screen wired to a known HEVC-capable player) and need the ~50% bitrate reduction. ATSC 3.0 broadcast uses HEVC, but ATSC 1.0 hardware will not decode it.
The 188-byte size was chosen for compatibility with Asynchronous Transfer Mode (ATM) cells, which carry a 184-byte payload plus a small header. Keeping TS packets the same size meant a single ATM cell could carry one TS packet without padding - critical when MPEG-TS was designed in the early 1990s for satellite and cable distribution. Even though ATM is largely obsolete, the 188-byte packet stuck because every receiver, mux, and transcoder is built around it.
Not from this single converter - it produces .ts files, not the .m3u8 manifest that lists them. To build a playlist, run the resulting .ts files through an HLS segmenter (ffmpeg's hls muxer or a tool like Bento4) that emits the manifest. The TS output here is segment-ready: H.264 + AAC, standard packet structure, valid PAT/PMT.
Anonymous users can upload up to 1 GB per file; signed-in free accounts get higher limits. JPEG inputs are tiny (a 12 MP photo is typically 3-6 MB), so file caps almost never matter for this conversion - the output .ts file size is driven by your duration, resolution, and bitrate choices, not the input.
Yes. JPG, JPEG, and JFIF are all the same JPEG image format with different filename extensions, and the converter accepts all three. For other image inputs see PNG to TS or the generic Image to TS page; for the reverse direction, TS to MP4 extracts a playable MP4 from a transport stream.