Convert M2TS to AIFF Online Free

M2TS packet anatomy before AIFF extraction

An M2TS file is not an audio file with a different extension. It is the Blu-ray Disc Audio-Video transport-stream form of MPEG-2 Transport Stream, designed to carry several time-related elementary streams at once: usually picture, one or more sound tracks, subtitles and programme information. Ordinary transport packets are 188 bytes long. In the BDAV form used by M2TS, each transport packet is preceded by a four-byte arrival-time header, so the repeating on-disk unit is 192 bytes. Treating that extra four-byte prefix as media data shifts the 0x47 transport-stream sync byte and prevents reliable demuxing.

Convert M2TS to AIFF when the useful result is a broadly editable, uncompressed audio track rather than the video programme. The converter must first identify the programme, then the selected audio PID inside it, decode that stream, and write sample data to a new AIFF container. It does not turn the video bytes into sound, and it cannot restore channels or samples excluded from the source track.

Following PAT and PMT to the intended soundtrack

The Program Association Table (PAT) is the directory at the start of this decision. It maps a programme number to the packet identifier, or PID, carrying that programme's Program Map Table (PMT). The PMT then lists the elementary streams for that programme and their PIDs. A disc title can consequently contain a main-language track, an alternate dub, descriptive audio, commentary and a high-resolution track without any of them being “the M2TS audio” by default.

Audio extraction should choose an actual PMT stream entry, not guess from file order. Its descriptors and stream type help distinguish LPCM, AC-3, DTS, TrueHD or other Blu-ray audio, while language information can help make a human choice. If a player exposes several tracks but an output sounds like commentary, the wrong PID was selected; reconvert from the intended programme and track. Subtitles and video PIDs are deliberately not copied to AIFF.

Program clock references (PCR) synchronize a programme's timeline. Presentation timestamps (PTS) label when decoded audio should be presented. Splices, damaged captures, playlist joins and broadcast-derived material can introduce discontinuities. A careful extractor follows timestamps, handles a new timestamp epoch rather than silently inserting a huge gap, and reports failure rather than fabricating continuous samples. AIFF stores sample frames, not transport-stream PID or timing tables, so programme-level timing context is intentionally left behind.

What an AIFF file records after decoding

Classic AIFF is an Interchange File Format family file beginning with a FORM identifier. Its form type is AIFF; the essential COMM chunk identifies channel count, number of sample frames, sample size and the 80-bit extended floating-point sample rate. The SSND chunk carries the sound data, with an offset and block-size field before the samples. The normal AIFF convention is big-endian PCM, so the conversion writes byte order expected by traditional AIFF readers rather than merely relabelling a little-endian WAV file.

AIFC is the related compressed-AIFF variant. It can name a compression type in its common chunk; that makes it a distinct compatibility question from ordinary uncompressed AIFF. This converter's AIFF target is best understood as decoded PCM: practical for waveform editors, archival handoff and applications that expect sample-accurate uncompressed input. It is normally much larger than a losslessly compressed alternative because every decoded sample is stored directly.

The numerical fields are useful when investigating a compatibility issue. The sample-frame count is a count of simultaneous channel samples, not a count of individual values: one stereo frame contains a left and a right sample. The sample rate uses an 80-bit IEEE extended representation in the AIFF common chunk, an older convention that differs from the integer rate fields used by several modern containers. Sample data follows the SSND offset and block-size values. An editor that expects big-endian signed PCM should therefore receive real byte-swapped PCM where required; changing a filename from .wav to .aiff does not make its internal byte order or chunk layout valid.

The source codec controls the decode stage. Blu-ray titles may carry LPCM, Dolby-family bitstreams, DTS-family bitstreams or other formats, and each must be decoded before ordinary AIFF PCM can be written. A source that is already LPCM still needs correct PID selection, PES reassembly and timestamp handling. The fact that it contains uncompressed samples does not make an M2TS packet sequence an AIFF file.

M2TS and AIFF conversion trade-offs at a glance

Preparing a Blu-ray stream for reliable audio conversion

Start with a complete file rather than a partial copy from the middle of a title. A transport stream needs recurring programme information and enough packets for a demuxer to establish the track layout. Keep the original M2TS if you might need another language, the video, subtitles or different output settings later; an AIFF output cannot be remuxed back into the original title with all of those elements restored.

Check the displayed duration and selected track before conversion. If the file is a playlist segment, the audible programme may not start at zero or may contain an intentional chapter boundary. If the output begins late, ends early or jumps, inspect the source with a media analyser and try a complete title or playlist. A timestamp discontinuity is a source characteristic to resolve, not a reason to compensate by duplicating silence.

Choose AIFF when the next application specifically supports it or when uncompressed PCM makes your workflow simpler. For a 48 kHz, 24-bit, six-channel source, the approximate uncompressed payload is 48,000 × 24/8 × 6 = 864,000 bytes each second before container overhead. That size is expected. It is not evidence that the conversion duplicated audio.

Do not decide output quality from the extension alone. Preserve the decoded track's sample rate and channel arrangement unless the receiving application has a documented requirement for conversion. Resampling changes every sample position; downmixing changes the relationship between channels; lowering bit depth needs a considered quantization policy. Those may be useful delivery choices, but they are separate operations from extracting an M2TS audio PID to an AIFF container. Where an editor offers a target bit-depth choice, select a setting it can read and document the choice in the project rather than silently relying on its default.

Quality checks that expose wrong-track or timing errors

Listen at the beginning, an interior chapter transition and the end. Confirm the spoken language or mix matches the intended PMT entry. Compare duration with the programme's known runtime, allowing only for material deliberately excluded by the selected playlist. Verify channel count and sample rate in the receiving editor; an unexpected stereo result from a multichannel track often means the output policy downmixed it, rather than an AIFF limitation.

Clicks near a join, a long silence or an abrupt time jump point to packet loss or timestamp handling, not a “bad AIFF extension.” AIFF's COMM and SSND structure cannot encode a repair history for a broken transport capture. Retain the source and rerun from an intact copy where possible. If a target editor rejects the output, check whether it requires classic AIFF PCM rather than an AIFC compressed variant, and whether its supported bit depths match the exported PCM.

M2TS to AIFF questions with practical answers

Does converting M2TS to AIFF extract every audio language?
No. An AIFF file represents one output stream. Select and convert each desired PID separately; the M2TS remains the source that holds the multiple programme components.

Why is the AIFF much larger than the M2TS?
M2TS can package compressed video and compressed audio, whereas a normal AIFF stores decoded PCM samples directly. A larger file is a normal consequence of uncompressed storage, especially with multichannel or high-bit-depth audio.

Will AIFF preserve Blu-ray chapter markers and subtitles?
No. Those belong to the disc or transport-stream/playlist context. This operation extracts sound; it is not a Blu-ray authoring conversion.

Can a 192-byte M2TS be read as a normal 188-byte TS?
Not without accounting for the four leading BDAV bytes in every packet. Correct packet alignment is necessary before PAT, PMT and PID parsing can work.

Is AIFF lossless?
Its PCM storage is uncompressed, so a correctly decoded source is not recompressed by the AIFF container. That does not undo lossy compression already present in an AC-3 or other lossy source track.

Can I change the sample rate during conversion?
You can choose a workflow that resamples, but that is not required merely to make AIFF. Keeping the decoded rate avoids an additional signal-processing step; change it only for a known destination requirement.