Convert AVI to TS (MPEG-TS) Online
Convert AVI files with DivX/Xvid codecs to MPEG Transport Stream for IPTV and broadcast, free, in your browser.
.avi · up to 100 MB
What it's for
AVI DivX/Xvid to TS: your legacy collection for IPTV and broadcast
DivX/Xvid to H.264 in TS
Re-encoding from MPEG-4 Part 2 to H.264 compatible with IPTV, DVB broadcast and modern players.
IPTV and TVHeadend
TS compatible with TVHeadend, Kodi IPTV Simple, VLC and DVB modulation hardware for home broadcast.
Legacy collection for streaming
Convert your 2000s DivX/Xvid archive to TS to retransmit it as an IPTV channel on your local network.
No servers, 100% private
Your AVI is processed locally with FFmpeg.wasm. No uploads, no registration, no limits.
How it works
Three steps, no hassle
Upload your AVI file
Drag or select the .avi from your DivX/Xvid collection or legacy archive. Up to 500 MB, no signup.
AVI to TS conversion in the browser
FFmpeg.wasm re-encodes DivX/Xvid video to H.264 and MP3/AC-3 audio to AAC, packaging everything into 188-byte MPEG-TS. No uploads.
Download the TS for IPTV or broadcast
Transport stream ready for TVHeadend ingest, IPTV players, Kodi, or DVB modulation hardware.
FAQ
Got questions?
The AVI (Audio Video Interleave) container was designed by Microsoft in 1992 for local playback on Windows. Its architecture based on data blocks and index tables at the end of the file makes it unsuitable for real-time streaming: an IPTV player cannot synchronise with an AVI stream mid-broadcast because it needs the index table for navigation. Additionally, DivX (MPEG-4 Part 2, ASP profile) and Xvid (open-source implementation of the same standard) are not natively supported in the standard MPEG-TS profile. The MPEG-TS standard, defined in ISO/IEC 13818-1, specifies H.264 (AVC) and H.265 (HEVC) as valid video codecs, not MPEG-4 Part 2. Therefore, AVI-to-TS conversion involves re-encoding DivX/Xvid video to H.264, the universal codec for current broadcast and IPTV.
DivX and Xvid are implementations of MPEG-4 Part 2 (published in 1999), a second-generation codec that was the standard for internet video distribution between 2001 and 2008 (the era of DVD movie rips on CDs). H.264 (published in 2003, widely adopted from 2005) is a third-generation codec with notably superior compression efficiency. Re-encoding DivX to H.264 at CRF 23 produces a TS with visually similar or better quality than the original AVI, generally with a 20–40% smaller file size. For archive video at standard resolution (typically 640×480 or 720×480 in DVD rips from the DivX era), the result is a TS perfectly reproducible on any modern platform.
Yes. DivX AVI files from the 2001–2008 era typically used MP3 (MPEG-1 Layer III) or AC-3 (Dolby Digital) audio. MPEG-TS natively supports AC-3 as the reference audio codec in European broadcast. MP3, while technically embeddable in TS, has limited support on IPTV hardware. Therefore, FFmpeg.wasm re-encodes MP3 audio to AAC-LC (192 kbps by default), the universal audio codec in modern streaming supported by all IPTV players, smart TVs, and broadcast hardware. If the AVI already has AC-3, stream copy is used without re-encoding.
The AVI container supports multiple audio tracks, but in a limited and non-standard way: many dual-language DivX AVIs use a technical hack of two interleaved audio streams, not formal multiple tracks. FFmpeg detects both tracks if they are correctly declared in the AVI and includes them in the TS as separate audio tracks. If the AVI uses the non-standard interleaving method, only the main track may be extracted. In that case, you can use the audio track selection field (when available) to choose which language to include in the TS.
Yes. AVI-to-TS conversion is especially useful for users with legacy collections of movies and series in DivX/Xvid who want to integrate them into a home IPTV infrastructure. Plex, Kodi, Emby, and Jellyfin can all play TS directly. To create a home IPTV channel with TVHeadend (the most popular IPTV server on Linux/Raspberry Pi), content must be in TS format: use Convertir.ai to convert AVIs individually and then add them as streams in TVHeadend. For large collections (hundreds of files), desktop FFmpeg with batch scripts is more efficient, but for individual or small batch conversions this tool eliminates the need to install additional software.
Subtitles in AVI files can exist in two forms: embedded as a text track (XSUB format or similar, uncommon in DivX) or as external SRT/SSA files separate from the AVI. Embedded AVI subtitles are discarded in the conversion to TS, as the MPEG-TS standard only supports DVB subtitles (bitmap) or Teletext, not time-based text formats like SRT. External SRT files remain unchanged and can be used independently in the target player if supported. If you need subtitles in the TS, the option is to burn subtitles into the video (hardcoded subtitles) before conversion using desktop FFmpeg.
Convert AVI to TS: DivX/Xvid collections for IPTV, DVB broadcast and modern streaming
The AVI (Audio Video Interleave) format with DivX and Xvid codecs represented the standard for internet video distribution between 2001 and 2008. Collections of movies and series in DivX accumulated during those years form a valuable digital archive that is, however, incompatible with modern streaming and broadcast infrastructure. Current IPTV servers such as TVHeadend, IPTV hardware players (MAG, Formuler, Zgemma), and DVB-T modulation systems require MPEG Transport Stream (.ts) as the transmission format. The AVI container, designed for local playback on Windows 95/98, lacks the real-time synchronisation features broadcast requires: it does not allow a receiver to synchronise mid-stream, does not include transport timing information (PCR, Program Clock Reference), and its MPEG-4 Part 2 codecs (DivX, Xvid) are not included in the standard MPEG-TS profiles defined by the DVB Project for European broadcast. This incompatibility is fundamental by design: AVI was conceived as an offline playback format, not a distribution protocol. MPEG-TS was built precisely for digital transmission — each 188-byte packet carries its own PCR timestamp, allowing any receiver to lock on to the stream at any point without needing the file header. The DVB-T, DVB-S, and DVB-C broadcast standards all mandate MPEG-TS as the transport layer, and every HLS streaming implementation segments content into TS chunks. AVI-to-TS conversion is therefore the essential modernisation step that rescues legacy archive collections and gives them a second life across all current IPTV, broadcast, and streaming distribution platforms. The DVB-T, DVB-S, and DVB-C broadcast standards all mandate MPEG-TS as the transport layer, as does Apple HLS — which segments content into TS chunks for adaptive bitrate delivery to every iOS device and Safari browser worldwide.
The technical process of AVI-to-MPEG-TS conversion involves two main operations: video re-encoding and audio remuxing. For video, DivX and Xvid are implementations of MPEG-4 Part 2 (ISO/IEC 14496-2), the standard video compression codec of the late 1990s and early 2000s, which emerged as a simplified MPEG-4 derivative designed for low-overhead internet distribution. FFmpeg.wasm re-encodes this video to H.264 (AVC, ISO/IEC 14496-10), the third-generation codec published in 2003 and universally adopted in broadcast, streaming, and storage from 2005. Re-encoding at CRF 23 (constant quality factor, the FFmpeg default for H.264) produces video of visually equivalent or superior quality to the original DivX/Xvid, typically 20–40% smaller thanks to H.264's superior compression efficiency over MPEG-4 Part 2. This efficiency gain comes from more sophisticated block headers, intra prediction with a greater number of directional modes, quarter-pixel motion compensation, and hierarchical B-frame structures that MPEG-4 Part 2 lacks. For audio, DivX AVIs used MP3 or AC-3: MP3 is re-encoded to AAC-LC 192 kbps for universal IPTV and broadcast compatibility; AC-3 is stream-copied without re-encoding as it is natively compatible with MPEG-TS in the European DVB standard profile, avoiding any generation loss. The output TS packet structure includes a valid PCR on the video PID, a correctly formed PAT identifying the programme, and a PMT listing all elementary streams with their codec type descriptors — the three mandatory components for any compliant IPTV or broadcast receiver to parse and play the stream without errors. The H.264 output uses High Profile Level 4.1, the widest-compatibility profile supported by all hardware decoders produced since 2009, including entry-level MAG IPTV boxes and basic DVB-T set-top boxes.
Convertir.ai executes AVI-to-MPEG-TS conversion entirely in the browser via FFmpeg.wasm, eliminating the need to install FFmpeg, HandBrake, or other desktop tools for individual or small-batch file conversion. The resulting TS uses the standard 188-byte-per-packet structure, includes correctly formed PAT and PMT tables with the mandatory programme and stream identifiers, and is compatible with TVHeadend for home IPTV (the most widely used IPTV server on Raspberry Pi and Linux), VLC for DLNA streaming on local networks, Kodi with the IPTV Simple plugin for TV playback, IPTV hardware players (MAG, Formuler, Enigma2/OpenATV), DVB-T laboratory modulators for RF broadcast, and professional broadcast encoders from Harmonic, Elemental, or Ateme as an ingest source. The conversion runs entirely client-side: no account creation is required, no usage limits apply, and the process works offline once the page has loaded. For collections of DVD rips in DivX or Xvid from the 2001–2008 era — a digital heritage many users accumulated over years and now want to make useful again in modern home theatre and IPTV setups — this tool enables complete migration to current IPTV infrastructure without significant perceptual quality loss, with total privacy as files are processed exclusively on the local device without sending any data to external servers. The tool requires no account creation, imposes no daily usage limits, and adds no watermarks to the output. It also works offline once the page has loaded, which makes it suitable for use in corporate environments with strict outbound network policies or air-gapped systems where cloud conversion services are not an option.