Convert M2TS to AVI Online Free

Why an M2TS programme cannot simply be renamed AVI

M2TS is the Blu-ray BDAV form of MPEG-2 Transport Stream. It is a multiplex designed to deliver several synchronized streams—commonly video, several languages of audio, subtitles and programme information—in short packets. An ordinary transport packet is 188 bytes long; M2TS adds a four-byte BDAV header before every packet, yielding 192-byte source packets. The transport sync value 0x47 appears after that prefix, so packet alignment must be established before any video or audio can be identified.

Convert M2TS to AVI when an older editor, playback device or ingest workflow specifically needs AVI. The operation must select a programme, demultiplex its video and desired audio, decode or transcode streams as needed, and mux a new RIFF AVI file with AVI-compatible codec settings. A change of extension cannot do that work. It leaves the M2TS packet layer, PIDs and clock information in place and creates a file most AVI readers will reject.

PAT and PMT determine what an AVI conversion receives

Programme selection in a transport stream begins with the Program Association Table. The PAT maps a programme number to the packet identifier, or PID, carrying that programme's Program Map Table. The PMT lists the elementary stream PIDs in that programme, including video, audio and the PID used for the programme clock reference. A demuxer follows those tables instead of assuming that the first payload PID is the desired picture or sound.

This matters when a Blu-ray title has a main mix, an alternate-language dub, audio description and commentary. Choose a particular audio PID before making AVI, and choose the intended video stream if the source has more than one. AVI contains streams in its own numbered order, not original TS PIDs; source PID 0x1011 does not survive as an AVI identity. Keep the M2TS if you need all tracks or original disc semantics after delivery.

PCR provides a programme timing reference and PTS says when decoded access units should be presented. Damaged captures, playlist joins and splices may produce discontinuities. The conversion must build a sensible AVI stream timeline from valid decoded data rather than turn a reset into a multi-hour gap. Conversely, it should not conceal missing media by inventing frames. Verify a complete source title where duration or sync looks implausible.

AVI RIFF anatomy: headers, movi data and indexes

An AVI file is a RIFF file whose form type is AVI . Its required LIST 'hdrl' defines stream formats and its required LIST 'movi' holds actual frame and audio chunks. The main AVI header, avih, carries global sequence information such as stream count and frame dimensions. Each stream gets its own LIST 'strl', including a strh stream header and strf stream-format chunk. For video, that format commonly uses a bitmap-information structure; for audio it uses a WAVEFORMATEX-style description.

Inside movi, a chunk identifier starts with a two-digit stream number and ends with a two-character type. 00wb identifies audio data for stream zero, while 01db and 01dc can identify uncompressed and compressed video for stream one. The mapping follows the order of the strl lists, not an MPEG PID. An optional AVI 1.0 idx1 after movi points to data chunks; OpenDML extensions add an indx index approach and can organize extended AVI structures for large files.

Indexes are not cosmetic. A file may contain decodable frames yet seek poorly or appear truncated if its index is absent, inaccurate or unsupported by a destination application. For long outputs, confirm the receiving software supports the particular AVI/OpenDML form and codec combination your workflow produces rather than judging compatibility by the .avi extension alone.

RIFF uses chunk identifiers and chunk lengths, with alignment considerations for the stored chunks. That is a very different navigation model from scanning fixed-size transport packets and following a PID. AVI readers rely on the declared stream format to hand bytes to an appropriate decoder. A valid strf description for one codec does not authorize another codec's payload: copying arbitrary M2TS video bytes into a movi chunk without a compatible stream description is not an AVI conversion. Remuxing is only plausible after confirming both payload and destination decoder compatibility.

M2TS transport design versus AVI file organization

Codec planning before creating an AVI delivery file

AVI is a container, so it does not by itself solve codec compatibility. M2TS sources may use H.264/AVC, MPEG-2 video or other video codecs alongside LPCM, Dolby or DTS-family audio. An older AVI workflow can require a video codec it recognizes and audio in a supported WAVEFORMATEX arrangement. If a direct rewrap is not accepted, transcoding is a compatibility decision with quality and time costs; it is not evidence that the original source was broken.

Match frame rate, dimensions, aspect ratio, sample rate and channel configuration to the destination's documented needs. Altering frame rate changes motion cadence; scaling changes pixels; downmixing changes the audio relationship; recompressing a lossy source adds generation loss. Use those changes intentionally. If your need is only modern playback, a newer container may be a better fit; AVI is appropriate when a real downstream requirement calls for it.

For long files, leave room for indexing and test a short representative export first. Some applications understand only older index behavior or specific four-character codec identifiers. A file that plays in one tool but fails in the actual production system has not met the conversion goal.

AVI stream interleaving also affects practical playback on constrained or old software. Video and audio data may be grouped in rec lists for read-together behavior, and the spacing of stream chunks can influence how much buffering a simple reader needs. This should be managed by the muxer rather than hand-edited after export. If playback works initially but audio drifts or stutters under the actual delivery conditions, inspect the stream's codec timing and AVI interleave/index support rather than blaming the source extension.

Reviewing AVI playback, sync and seek behavior

Test the first minute, a late scene, a fast seek and the final minute. Confirm that the selected language and video stream are correct, dialogue remains synchronized, and duration is credible. Fast seeking that lands on wrong positions can indicate an index or decoder-support issue even when linear playback works. Silence, a wrong language or missing picture often points back to PMT selection rather than RIFF chunk syntax.

Artifacts after conversion require a source-versus-target diagnosis. A corruption at the same point in both M2TS playback and AVI is likely source damage. New blockiness, ringing or dropped audio after AVI conversion suggests codec settings or incompatible transcoding. A huge time jump suggests transport PTS/PCR discontinuity or incorrect timeline construction. Preserve the source and log conversion settings so the output can be recreated accurately.

M2TS to AVI questions for legacy workflows

Can I rename M2TS to AVI?
No. M2TS is packetized MPEG transport data; AVI is a RIFF structure with headers, movi chunks and optional indexes. The streams must be demuxed and a new AVI muxed.

What is the difference between idx1 and indx?
idx1 is the AVI 1.0 index normally written after movi. OpenDML uses indx-based indexing approaches that are relevant to larger or extended AVI files.

Will AVI retain all Blu-ray subtitles and languages?
Not as a full Blu-ray programme. This conversion targets selected streams; convert needed audio tracks separately and preserve M2TS for original disc content.

Why does AVI open but not seek correctly?
The data chunks may be readable while the relevant index is missing, incorrect or unsupported. Check the resulting AVI form against the destination application's capabilities.

Does AVI conversion improve video quality?
No. Rewrapping preserves compatible streams; transcoding is often required for compatibility and can only retain or reduce source quality, never recreate detail.

Why does the AVI have a different stream number from the M2TS PID?
AVI assigns streams by the order of its strl lists and labels data chunks with two-digit stream numbers. M2TS PID values belong only to the source transport multiplex.