Initializing... drag & drop files here
Supports: TS
.ts file or click "Add Files". This converter accepts MPEG Transport Stream files — the kind a PVR, IPTV box, or HLS download produces. Batch is supported: drop in several recordings and each converts in parallel.TS stands for MPEG Transport Stream, standardized as ISO/IEC 13818-1 (MPEG-2 Part 1, Systems, also published as ITU-T Rec. H.222.0) and first released on 10 July 1995. It was designed for one job: carrying audio and video reliably across channels where data can be lost or corrupted — digital TV broadcast (DVB and ATSC), satellite, IPTV, and live streaming. To survive a noisy channel it breaks the stream into fixed 188-byte packets, a size originally chosen for compatibility with ATM telecom networks. That packetized, error-tolerant design is brilliant for transmission and exactly why a .ts file lands on your drive in the first place — but it's a poor fit for everyday playback, editing, and sharing.
You typically end up with .ts files from a few sources: a TV tuner card or PVR that records broadcast, an IPTV or set-top box capture, or an HLS (HTTP Live Streaming) download, where the video arrives as a string of small .ts segments referenced by a playlist. Converting solves the real problems those files create:
.ts. VLC plays them, but the moment you want the file in Photos, on an iPad, or embedded on the web, you need MP4. The streams inside are usually H.264 already, so TS to MP4 keeps that same H.264 video family and re-encodes it into a container every device recognizes..ts chunks. Drop them in together and the converter stitches them into one continuous MP4 or MKV instead of leaving you with fragments.| Format | Standard / Origin | Native playback | Typical codecs | Best for |
|---|---|---|---|---|
| TS (source) | ISO/IEC 13818-1 / ITU-T H.222.0 (1995) | VLC, MPC-HC; not most phones/TVs | MPEG-2, H.264, HEVC + AC-3/AAC/MP2 | Broadcast, IPTV, HLS segments |
| MP4 | ISO/IEC 14496-14 (2003) | Windows, macOS, iOS, Android, all browsers | H.264, HEVC + AAC | Universal playback, sharing, web |
| MKV | Matroska (open, 2002) | VLC, MPV, Plex, Jellyfin; not Safari/Roku | H.264, HEVC, AV1, multi-track | Multi-audio/subtitle libraries |
| MOV | Apple QuickTime File Format (1991) | macOS, iOS, QuickTime, VLC | H.264, HEVC, ProRes + AAC | Final Cut / Apple editing |
| WebM | Google / WHATWG (2010) | Chrome, Firefox, Edge; Safari 17+ for AV1 | VP9, AV1 + Opus | HTML5 web embeds |
| AVI | Microsoft (1992) | Windows native, VLC | DivX, XviD, MPEG-4 + MP3 | Legacy Windows editors |
xconvert always re-encodes when it converts a .ts — there is no stream-copy pass-through — so the codec you land on decides the output's size and where it plays. A broadcast capture is often heavy MPEG-2, and moving it to a modern codec is where most of the size savings come from. For TS output the codec dropdown offers H.264, H.265, MPEG-2, and MPEG-4; VP9 and AV1 become available when the target is WebM, MP4, or MKV.
| Codec | Size vs H.264 | Where it plays | Best for |
|---|---|---|---|
| MPEG-2 | ~2x larger | Broadcast/DVD gear, VLC, most editors | Matching a legacy broadcast workflow |
| H.264 (AVC) | baseline (100%) | Effectively every device since ~2010 | The safe universal default for a .ts |
| H.265 (HEVC) | ~50-60% | Safari 11+/14.1+, Chrome 107+, Edge, recent Android | Shrinking a capture while keeping HD detail |
| VP9 | ~50-70% | Chrome, Firefox, Edge, Android; not Safari | Royalty-free web delivery inside WebM |
| AV1 | ~30-50% | Chrome 70+, Firefox 67+, Edge; Safari 17+ (partial) | Smallest files; slow encode, newest decoders |
A .ts file is an MPEG Transport Stream — a container built for broadcast and streaming, not for storage on a device. It carries the same kind of H.264 or MPEG-2 video you'd find elsewhere, but it wraps the data in 188-byte error-tolerant packets meant to survive a TV broadcast or a flaky network. Most phone galleries, the Photos app, and smart-TV players simply don't register .ts as a video file, even though VLC opens it fine. Converting to MP4 re-encodes those streams into a container every device recognizes.
xconvert always re-encodes — there is no bit-for-bit stream copy — but that does not mean visible quality loss. When your .ts already holds H.264 (true of most modern IPTV and HLS captures) and you convert to MP4 without changing the codec, the H.264 + AAC codec family is kept and the default Very High preset encodes at the visually-lossless tier, so the result is indistinguishable from the source in normal viewing. A larger change happens only when the source is older MPEG-2 broadcast video re-encoded to H.264, or when you deliberately change the codec, resolution, or quality preset. In our testing, a 5-minute 1080p H.264 transport stream converted to MP4 at the default preset kept the same H.264 video family and looked identical to the source in side-by-side frame checks.
HLS downloads arrive as many small numbered .ts files (segment0.ts, segment1.ts, and so on) that a playlist normally ties together. Upload all the segments in order and convert to MP4 or MKV — the converter joins them into one continuous file instead of leaving you with fragments. If the segments came from different renditions (different resolutions or bitrates), keep only one rendition's set, since mixing resolutions in a single output causes glitches.
Pick MP4 if the goal is broad playback and sharing — phones, browsers, TVs, and editors all speak it. Pick MKV (Matroska) if your broadcast capture carries several audio languages or subtitle tracks you want to keep, since MKV holds an unlimited number of tracks in one file while MP4 is happiest with one video and one or two audio streams. MKV is great for a Plex or Jellyfin library but isn't supported natively by Safari, Roku, or most smart-TV browsers, so it's a download-and-play target rather than a web-embed one. See TS to MKV for that route.
Quality only takes a visible hit when the codec actually changes or you lower the resolution or preset; keeping the same codec family — for example H.264 into MP4 or MOV — at the default Very High preset stays visually indistinguishable from the source, even though the streams are re-encoded rather than copied bit-for-bit. Audio is the bigger thing to watch: a broadcast .ts can hold multiple tracks (for example a main language and a described-audio track) plus AC-3 surround. MP4 keeps one or two audio streams cleanly, so if you need every track preserved, choose MKV instead, which carries them all.
PVRs and tuner boxes usually start recording a little before the scheduled time and stop a little after, so the capture bookends your show with a few seconds of the adjacent program or channel padding. There's nothing wrong with the file — it's just recorder behavior. Set the Trim control to a Time Range and enter a start offset and duration to clip those ends off during conversion, so you don't need a separate editing step.
Both are transport-stream containers, but they come from different worlds. A plain .ts is a raw MPEG-2 Transport Stream — what DVB/ATSC broadcast, IPTV boxes, and HLS segments produce — and it usually carries MPEG-2 or H.264 with MP2, AC-3, or AAC audio. A .m2ts (often .mts straight off the camera) is the AVCHD/Blu-ray flavor of the same transport-stream idea, introduced by Sony and Panasonic in 2006 for camcorders and Blu-ray discs; it wraps H.264 with AC-3 or LPCM audio and tags each packet with an extra timestamp, making its packets 192 bytes rather than the plain 188. xconvert treats them as separate inputs — use TS to M2TS if you specifically need the camcorder/Blu-ray variant, or M2TS to MP4 if you already have the camcorder file and want a universal one instead.
Yes. Files are uploaded over an encrypted (TLS) connection, processed on our servers, and deleted automatically after a few hours. There's no sign-up, no watermark on the output, and files are never shared or made public. Because conversion runs server-side, the practical limit on a big broadcast capture is upload time and your connection speed, not your device — multi-gigabyte recordings are routine.