Initializing... drag & drop files here
Supports: XVID
.ts — no sign-up, no watermark.Xvid is an MPEG-4 Part 2 Advanced Simple Profile codec — an open-source counterpart to DivX, dating to 2001 and almost always shipped inside an AVI container. AVI's index-based structure is fragile under packet loss and was never designed for streaming or broadcast. TS (MPEG-2 Transport Stream, ISO/IEC 13818-1, standardized 1995) breaks the bitstream into 188-byte packets with continuity counters and a Program Clock Reference, so it can survive dropped packets, be cut at arbitrary boundaries, and multiplex multiple programs at once. Common reasons to move Xvid AVI into TS:
.ts as the original segment format. TS segments remain the most-compatible HLS payload, especially for older Smart TVs, set-top boxes, and pre-2016 iOS clients that predate fMP4 support.| Property | Xvid in AVI | TS (MPEG-TS) |
|---|---|---|
| Standard | MPEG-4 Part 2 ASP (codec) in AVI (container) | ISO/IEC 13818-1 / ITU-T H.222.0 |
| Container structure | Index-based, single-program | 188-byte packets, multi-program capable |
| Codecs supported | Xvid (MPEG-4 ASP) | MPEG-2, H.264, H.265, AC-3, AAC, MP3, EAC-3 |
| Error resilience | None — corruption can break the index | PCR + continuity counter, designed for lossy channels |
| Streaming-ready | No — designed for local file playback | Yes — HLS, DVB, ATSC, IPTV |
| Cuttable mid-stream | No | Yes — segments at any packet boundary |
| Native browser support | None | None — both need a media server / segmenter |
| Typical use | PC playback of legacy MPEG-4 files | Broadcast, HLS streaming segments, Blu-ray (M2TS variant) |
| Output codec | Relative bitrate vs Xvid | Where it plays | Best for |
|---|---|---|---|
| MPEG-2 video | ~150-180% | Every TS-aware decoder, broadcast hardware, Blu-ray | DVB / ATSC playout, hardware decoders that predate H.264 |
| H.264 (AVC) | ~50% (same quality) | Every modern player, all current HLS clients | HLS segments, IPTV, general-purpose TS |
| H.265 (HEVC) | ~30-35% | 2017+ TVs and phones, modern HLS clients | Bandwidth-constrained streaming, 4K archive |
| Resolution | Constant Bitrate (H.264 in TS) | CRF (Constant Quality, H.264) |
|---|---|---|
| SD 720×480 / 720×576 | 1.5-2.5 Mbps | 20-23 |
| 720p | 2.5-4 Mbps | 20-23 |
| 1080p | 5-8 Mbps | 20-23 |
| 4K UHD | 15-25 Mbps (H.264) / 8-12 Mbps (H.265) | 22-25 |
If the destination is HLS streaming on older clients, broadcast playout, IPTV, or a pipeline that explicitly expects MPEG-TS, TS is the right wrapper. If the destination is web playback, social media, or local viewing on a modern device, MP4 is the better target — MP4 is universally accepted and smaller in overhead. See Xvid to MP4 if MP4 is what you actually need.
Yes. The audio track inside the AVI (typically MP3, AC-3, or AAC) is re-multiplexed into the TS. If the source uses a codec that TS doesn't carry well, the audio is transcoded to AAC or AC-3, which are the broadcast-and-HLS-compatible defaults. Multi-language audio in the source is preserved as separate program elements where the source provides it.
For HLS, Apple's published guidance is a multi-bitrate ladder — typical rungs are 0.5, 1, 2.5, 5, and 8 Mbps for H.264 from 360p to 1080p. If you're outputting a single TS for one quality level, match the rung: 1080p HLS sits around 5-8 Mbps, 720p around 2.5-4 Mbps, 480p around 1-1.5 Mbps. CRF 20-23 with H.264 lands in those ranges automatically without manual bitrate math.
.ts larger than the original Xvid?If you kept MPEG-2 as the TS video codec (the legacy broadcast default), MPEG-2 is roughly 50-80% less efficient than MPEG-4 ASP — the file grows. Switch the output codec to H.264 to land below the original size at the same visual quality, or H.265 to land at roughly a third of MPEG-2 size. TS also adds packet overhead (188-byte framing, PSI/PMT tables, PCR) that slightly inflates output regardless of codec.
Yes. Under Trim, switch from Unchanged to Time Range and set start time and duration. The output is a single TS file covering exactly that span. For chunked HLS-style segmenting (e.g., 6-second segments + a manifest), you'll need a dedicated HLS packager downstream — this tool produces a single continuous .ts.
VLC, MPC-HC, mpv, ffmpeg, OBS, and standard non-linear editors (DaVinci Resolve, Premiere Pro, Final Cut) all accept MPEG-TS reliably. Some Windows native players and QuickTime do not — they expect MP4. If you need both, run the conversion twice, or convert TS to MP4 afterwards via TS to MP4.
For new encodes, no — H.264 and H.265 dominate, and Xvid's last stable release was December 2019. But existing Xvid AVI archives (early-2000s camcorder rips, ripped DVD libraries, fan-encoded TV episodes) are still everywhere. Converting them into TS with a modern codec (H.264 or H.265) is the practical migration path for content that needs to live on streaming or broadcast infrastructure.
M2TS is the Blu-ray / AVCHD variant of MPEG-TS — same 188-byte packet structure plus a 4-byte timecode prefix per packet. Most players that read .ts will also play .m2ts if you rename the extension, but proper Blu-ray authoring tools want true M2TS with the timecode header (this converter outputs standard .ts only). If you'd rather shrink the original Xvid file before any wrapper change, run it through Compress Xvid first.
Yes — drop in dozens of files. Each AVI processes independently and downloads as its own .ts, or as a single ZIP. Apply settings (codec, bitrate, resolution) once and they propagate across the batch, which is the typical pattern when migrating an archive.