Convert MKV to AIFF Online for Free
Extract a chosen MKV soundtrack as uncompressed AIFF while checking Matroska timing, source quality, channels, sample frames, and file size.
- Add a file Choose or drop it here
- Pick the format Change it whenever needed
- Download the result After conversion completes
An AIFF File Starts With One Deliberately Chosen MKV Audio Track
MKV is Matroska, an EBML-based audiovisual container. It can hold video plus many audio, subtitle, chapter, attachment, and metadata tracks. An AIFF file is audio-only, so MKV to AIFF begins with track selection rather than with a general video conversion. List the MKV audio TrackEntries and note language, name, codec, sample rate, channel count, duration, and default status. The first track is not automatically the main program: it can be a commentary, descriptive track, dub, or alternate mix.
Matroska describes its tracks with fields including CodecID and, for some codecs, CodecPrivate initialization data. Clusters contain timed Blocks. A player may show video yet lack a decoder for one source soundtrack, so do not mistake visible picture for successful audio access. Listen to the intended stream at the beginning and a later point before extracting. The wrong language encoded perfectly into AIFF is still a failed delivery.
Keep the MKV after conversion. It retains the video, subtitles, alternate tracks, chapter navigation, and original coded audio. AIFF is a separate audio handoff, not a replacement for a multi-track movie. If a source is encrypted, unreadable, or missing a decodable audio stream, changing the target to AIFF does not create recoverable sound.
AIFF Stores Sample Frames in FORM, COMM, and SSND Chunks
AIFF is an audio container built from chunks. A standard AIFF begins with a FORM container whose type is AIFF. The Common chunk, COMM, describes the number of channels, number of sample frames, sample size in bits, and sample rate. The Sound Data chunk, SSND, carries the sample-frame data and includes offset and block-size fields before the audio bytes. These chunks describe decoded audio samples, not video packets or Matroska blocks.
A sample frame is one sample for every channel at one instant. For stereo, each frame contains a left and right sample; a file with 48,000 frames per second has a 48 kHz sample rate. Standard AIFF stores uncompressed signed sample data, commonly big-endian. AIFF-C is a related variant that can declare compression, but ordinary AIFF extraction should not quietly claim losslessness if a compressed AIFF-C option was selected. Inspect the form type and audio properties in the output.
This target can be useful where uncompressed PCM-like audio is required, but it is not automatically small. At 44.1 kHz, 16-bit stereo, one minute of uncompressed audio is about 10 MB before metadata and container overhead. Calculate storage from channels, sample rate, bits per sample, and duration instead of expecting the source MKV’s compressed audio size to predict the AIFF size.
Uncompressed Output Cannot Restore What the MKV Codec Removed
AIFF can store decoded samples without a new lossy compression stage. That is useful when the source track is PCM or lossless and the destination needs uncompressed samples. But “uncompressed output†does not mean the source was high resolution. If the MKV audio is AAC, MP3, Opus, AC-3, Vorbis, or another lossy codec, its missing detail was discarded before AIFF receives decoded samples. The AIFF preserves the decoder’s result; it cannot recover original information by using more bytes.
Do not inflate technical numbers without a reason. Raising 22.05 kHz to 48 kHz adds interpolated samples, not captured high frequencies. Padding a decoded 16-bit signal to a larger word size does not regain dynamic detail. A sample-rate conversion, dither, normalization, or downmix is a real processing choice that should be recorded. Preserve decoded rate, channels, and sensible bit depth when the intended AIFF receiver accepts them.
- No extra lossy encode is required: decoded samples can be written directly as uncompressed AIFF.
- Existing losses remain: lossy MKV audio does not become original quality after AIFF extraction.
- Video and subtitles are omitted: AIFF contains sound sample frames only.
- File size rises predictably: uncompressed storage follows duration, rate, channels, and sample size.
- Channel policy matters: a stereo or surround conversion must keep/mix channels intentionally.
Matroska Timing Must Be Decoded Before AIFF Frames Are Written
MKV timing is stored through Cluster timestamps and Block offsets. RFC 9559 also defines TrackTimestampScale and CodecDelay. When CodecDelay exists, its value is subtracted from a track’s Block timestamps for presentation. Those details matter to a sound extraction because the first encoded packet does not always mean the first audible sample. Source audio codecs can also have priming/delay and final padding behavior.
Decode the selected source track in presentation order, then compare the opening audible event, a clear mid-program event, and the final tail with the source. A waveform alone cannot prove that the selected language or cut is right; listen as well. Do not remove samples only because player duration displays differ by a fraction of a second. Rounded displays are not a sample-level timing test.
A fixed start offset and growing drift are distinct clues. A fixed offset can reflect track delay, priming, or a trim policy; growing drift points more toward rate or timestamp interpretation. If the AIFF needs to line up with an external video, document the source track and timing decisions. AIFF carries audio samples, not the MKV’s video timeline or subtitle timing.
Channels, metadata, and software support need verification.
Before writing AIFF, determine whether the MKV source is mono, stereo, or multichannel and whether each channel has a defined purpose. Two mono tracks may be independent recordings rather than a stereo pair. A surround track cannot be casually folded to stereo without changing balance and routing. Preserve the decoded layout where practical, or use a documented downmix and listen for missing dialogue, overly loud effects, and phase problems.
AIFF metadata is a different environment from Matroska Tags and Attachments. Transfer only verified audio information that belongs with an audio file. Video dimensions, chapter lists, subtitle languages, artwork that does not represent the selected soundtrack, and unknown container fields should not be presented as AIFF song metadata. Retain the source or a conversion note for information the new format cannot express safely.
Name the actual receiving program. Some tools treat AIFF as a normal uncompressed interchange format, while other devices favor WAV or another audio form. A file can be technically valid yet rejected because the target expects stereo, a specific sample rate, or a different endianness/container family. Inspect the finished FORM/COMM/SSND structure and test the destination rather than relying on one desktop player.
Troubleshooting a Sound-Only Export From MKV
Wrong language, commentary, or audio description means the wrong Matroska track was selected. Compare the output’s content against the source inventory, not merely its duration. No sound can mean a missing decoder, an unavailable track, or a source access problem. A valid-looking AIFF header does not prove meaningful samples were decoded; check sample-frame count and listen to the opening and later content.
An AIFF that begins with a click, misses the first word, or stops early needs a timing check. Review source CodecDelay/padding behavior and the extraction’s first/last decoded samples. Do not add silence just to make a duration number match. Conversely, a file that seems huge is expected when decoded audio is stored without compression. Compare its size with the rate × channels × bytes-per-sample × duration calculation before treating size as an error.
If the receiver plays an incorrect channel balance, inspect channel mapping before changing sample rate or bit depth. Preserve the MKV until all required content, timing, channel behavior, and target playback have passed. AIFF is a good sample-based handoff only when those practical conditions are met.
MKV Audio Track Details Compared With AIFF Sample Details
| Check | MKV source | AIFF output |
|---|---|---|
| Organization | EBML Tracks and timed Blocks in Clusters. | FORM container with COMM and SSND chunks. |
| Track choice | Can include languages, commentary, and several mixes. | One selected decoded audio program. |
| Codec context | CodecID plus possible CodecPrivate identify decoder needs. | COMM records channels, sample frames, bit size, and sample rate. |
| Timing | Cluster/Block timing plus possible CodecDelay. | Continuous audio sample frames; no video timeline. |
| Compression | Audio may be lossy, lossless, or PCM. | Standard AIFF stores uncompressed sample data. |
| Size | Compressed audio can be relatively compact. | Rate, channels, depth, and duration directly drive storage. |
Questions Before Saving MKV Audio as AIFF
Can AIFF keep the MKV video?
No. AIFF holds audio sample frames, not a movie video or subtitle track.
Will AIFF make AAC audio lossless again?
No. It writes the decoded AAC result uncompressed but cannot restore information AAC discarded.
Why is the AIFF much larger?
AIFF commonly stores uncompressed samples. Its size rises with duration, sample rate, channels, and bits per sample.
Why is the wrong audio track extracted?
Choose the intended Matroska TrackEntry explicitly and audition it before writing the AIFF.
Why is the start or end different?
Check Matroska timing, CodecDelay, source decoder delay, and first/last audible samples.