Initializing... drag & drop files here
Supports: TS
TS (MPEG-2 Transport Stream, ISO/IEC 13818-1) is the container designed for broadcast and IPTV: 188-byte packets with error resilience for unreliable channels like satellite, cable, and over-the-air ATSC. It usually carries MPEG-2 or H.264 video at high bitrates because broadcast bandwidth is cheap relative to encode complexity. AV1 (released by the Alliance for Open Media in 2018) is a royalty-free codec aimed at internet delivery; independent comparisons typically place it 30-50% more efficient than H.264 and 20-30% better than H.265/HEVC. Re-encoding TS to AV1 inside an MP4 or MKV container produces a far smaller file that streams over residential connections without falling back to lower resolutions. Common reasons:
.ts chunks is awkward to play and share. Convert to a single AV1 MP4/MKV for normal playback in VLC, mpv, or Plex.| Property | TS (MPEG-2 Transport Stream) | AV1 in MP4/MKV |
|---|---|---|
| Layer | Container (typically wrapping MPEG-2 or H.264 video) | Codec (wrapped in MP4, MKV, or WebM) |
| Standard | ISO/IEC 13818-1 (1995, updated) | AV1 spec via AOMedia (Jan 2018); MP4 = ISO/IEC 14496-14 |
| Designed for | Broadcast, satellite, cable, ATSC, DVB, IPTV, HLS | Internet streaming, on-demand video, archive |
| Typical bitrate (1080p) | 8-20 Mbps (broadcast/DVR) | 1-3 Mbps (visually lossless to web-quality) |
| Compression efficiency | Baseline (MPEG-2) or moderate (H.264 inside) | 30-50% smaller than H.264, 20-30% smaller than H.265 |
| Error resilience | Excellent — 188-byte packets, PCR sync, designed for lossy channels | None at codec layer; container handles integrity |
| Royalty status | MPEG-2 patents largely expired; H.264 inside still pooled | Royalty-free (AOMedia Patent License 1.0) |
| Hardware decode | Universal (any TV, DVR, set-top box) | Chromecast 4K, Apple TV 4K (A15+), Shield TV Pro 2019, modern Intel/AMD/NVIDIA GPUs |
| Best for | Live broadcast capture, streaming segments | Archive, on-demand streaming, smallest watchable files |
| CQ value | Quality | When to pick |
|---|---|---|
| 18-23 | Visually lossless | Master archive, source for further editing |
| 24-28 | Excellent | DVR archive, Plex/Jellyfin libraries, default |
| 29-34 | Good | Streaming to phones, mobile uploads, casual sharing |
| 35-40 | Acceptable | Low-bandwidth distribution, preview clips |
| 41+ | Compressed | Thumbnail-size previews only |
AV1 encoding takes meaningfully longer than H.264 — even with modern SVT-AV1 a 1080p 30 fps source typically encodes at 1-5× realtime on a desktop CPU. The trade is one-time encode cost for smaller permanent storage and lower delivery bandwidth.
If you also want to keep the original H.264 or H.265 video tracks intact and just change containers, see TS to MP4 or TS to MKV. Want to shrink without changing codec? Use Compress TS.
AV1 is roughly 20-30% more efficient than H.265 at the same perceived quality, and it carries no patent royalties — H.265 is split across at least three competing patent pools, which is why Chrome held off on H.265 decoding until late 2022 and many web platforms still avoid it. Pick AV1 when storage or bandwidth matters and your playback devices are recent (post-2020 SoCs for hardware decode). Pick H.265 if every minute of encode time counts or your devices lack AV1 hardware support.
Hardware AV1 decode is now common: Intel Arc and 11th-gen+ iGPUs, AMD RX 7000+, NVIDIA RTX 40 series, Apple Silicon M3/M4 and A17 Pro / A18 chips, recent Chromecast / Shield TV / Fire TV / Roku Ultra. Software decode (dav1d) works in Chrome 70+, Firefox 67+, Edge 121+, and Safari 17+ on supported Apple Silicon — global browser support is roughly 94%. On older phones and laptops without hardware decode, AV1 plays but uses more CPU and battery; MP4/H.264 is friendlier on those targets.
AV1 trades encode speed for compression efficiency. Even with SVT-AV1 (the fastest open encoder, used by Netflix and Meta), expect single-digit-multiple-of-realtime on a desktop CPU for 1080p, and slower for 4K. XConvert runs server-side encodes with sensible defaults so you don't tune the encoder yourself. If you only need to clean up the container, use TS to MP4 — a remux finishes in seconds.
Yes. Under Trim, pick Time Range and enter start time + duration in seconds (12.5) or HH:MM:SS.sss format (00:18:30.000). Trim before the AV1 encode and you save proportionally — cutting an hour of content down to 45 minutes cuts roughly 25% off the encode time and the output size. For frame-accurate multi-segment cuts (removing several ad breaks individually), see Video Cutter.
Yes. TS commonly carries MP2, AC-3 (Dolby Digital), E-AC-3 (Dolby Digital Plus), or AAC audio. XConvert re-muxes the audio into the AV1 container — MP4 carries AAC, AC-3, E-AC-3, and Opus natively; MKV carries virtually any codec. The default keeps AAC if present and re-encodes other tracks to AAC for maximum compatibility. Multiple audio tracks (e.g., main + descriptive audio) are preserved.
XConvert handles large TS files including multi-hour DVR captures running tens of GB. the practical limit is upload size and connection speed and patience for the upload; there's no fixed per-file cap and no quantity limit on batch jobs. For very large archives, consider trimming or splitting the source into per-show segments before queueing.
TS is a streaming format — there's no global header announcing the total duration the way MP4 has. Players estimate it from the file size and bitrate, which is often wrong for variable-bitrate broadcasts. Re-encoding to AV1 in MP4 or MKV writes a proper duration into the container, so seek bars and time displays match the actual content.
In theory yes — the Alliance for Open Media published a draft spec for "Carriage of AV1 in MPEG-2 TS" — but the draft is not widely deployed and most consumer playback chains expect AV1 inside MP4, MKV, or WebM. XConvert outputs AV1 inside MP4 by default (best compatibility) and offers MKV via the TS to MKV page if you need to carry multiple subtitle/audio tracks.