Extract Audio from M4V to AIFC — Free Online Tool
Extract audio from M4V video files and save it as AIFC, converting the AAC-encoded audio track to uncompressed PCM (pcm_s16be) in Apple's extended AIFF container. Ideal for professional audio workflows that require lossless-quality output from iTunes video content.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M4V file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
M4V files typically contain AAC-encoded audio alongside an H.264 or H.265 video stream. This tool strips the video entirely and decodes the compressed AAC audio, then re-encodes it into AIFC using 16-bit big-endian PCM (pcm_s16be) — the AIFC default codec. Unlike a simple remux, this process fully decodes the AAC stream and writes uncompressed PCM samples into the AIFC container, meaning the output is no longer lossy-compressed. While the original AAC compression introduced some quality reduction, the AIFC output preserves all remaining audio fidelity without any further degradation, and the big-endian byte ordering matches the AIFC/AIFF specification used historically in professional Apple and broadcast environments.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg toolchain. In the browser-based version of this tool, this runs via FFmpeg.wasm (WebAssembly), executing the same command logic locally in your browser without sending your M4V file to any server. |
-i input.m4v
|
Specifies the input M4V file. FFmpeg reads the container and identifies all streams, including the H.264 or H.265 video stream and the AAC audio stream typical of M4V files from Apple ecosystems. |
-vn
|
Disables video output entirely, discarding the H.264 or H.265 video stream from the M4V. Since the target format is AIFC — a pure audio container — no video data is written to the output file. |
-c:a pcm_s16be
|
Decodes the AAC audio from the M4V and re-encodes it as 16-bit signed big-endian PCM, the standard and default codec for AIFC files. This is the format expected by professional Apple and broadcast audio tools that read AIFC. |
-b:a 128k
|
Sets a target audio bitrate of 128 kbps, though this parameter has no practical effect on pcm_s16be since PCM bitrate is determined entirely by sample rate and bit depth rather than a compression target. It is included for consistency but can be omitted without changing the output. |
output.aifc
|
Defines the output filename and triggers FFmpeg to use the AIFC container format based on the .aifc file extension. FFmpeg wraps the pcm_s16be audio stream in the AIFC container structure, producing a file compatible with Logic Pro, Pro Tools, and other professional audio applications. |
Common Use Cases
- Extracting dialogue or music from an iTunes-purchased M4V movie or TV episode for use in a professional audio editing session in Logic Pro or Pro Tools, which natively support AIFC
- Archiving the audio track of an M4V home video in an uncompressed AIFC format for long-term storage without further lossy compression cycles
- Pulling a music performance recorded in M4V format into an AIFC file for import into a Digital Audio Workstation that requires PCM-based input
- Converting M4V lecture or educational video audio into AIFC for transcription workflows where uncompressed audio yields better speech recognition accuracy
- Delivering extracted audio from an M4V source to a broadcast or post-production house that requires AIFC files with big-endian PCM as part of their ingest specification
- Stripping the audio from an iOS screen recording saved as M4V to produce an AIFC file for further audio processing and noise reduction
Frequently Asked Questions
Not in the strictest sense. The AAC codec inside the M4V is lossy, so some audio information was discarded when the M4V was originally created. However, once the AAC is decoded and written as uncompressed PCM in AIFC, no additional quality loss occurs. The AIFC file preserves every bit of the decoded audio faithfully — it simply cannot recover what AAC already discarded. Think of it as lossless from this point forward.
AIFC is designed around PCM audio, and its default and most compatible codec is pcm_s16be — 16-bit signed PCM in big-endian byte order. Unlike MP4 or MKV containers, AIFC does not natively support AAC or MP3 streams in a way that is broadly compatible across professional tools. Using pcm_s16be ensures the file opens correctly in Logic Pro, Pro Tools, Final Cut Pro, and other professional applications that expect standard AIFC content.
The AIFC audio file will typically be significantly larger than the audio portion of the M4V, because AAC at 128k is highly compressed whereas 16-bit PCM at CD quality (44.1 kHz stereo) runs approximately 10 MB per minute. Since the video stream is discarded entirely, the AIFC will be much smaller than the full M4V, but the audio itself expands substantially when decompressed from AAC to PCM. A 30-minute M4V episode's audio track might produce an AIFC file of 300–500 MB depending on sample rate.
No. AIFC does not support chapters or multiple audio tracks — the format is a single-stream audio container. Only the first (or default) audio track from the M4V will be extracted. If your M4V contains multiple language tracks, you would need to modify the FFmpeg command to specify a particular audio stream using the -map flag, for example '-map 0:a:1' to select the second audio track.
Replace 'pcm_s16be' with another supported AIFC codec to change the bit depth or encoding. For example, use 'pcm_s24be' for 24-bit PCM (preferred in professional audio production), 'pcm_s32be' for 32-bit integer PCM, or 'pcm_f32be' for 32-bit floating-point. The '-b:a 128k' flag has no meaningful effect on PCM codecs since PCM bitrate is determined by sample rate and bit depth, not a target bitrate — you can safely omit it for PCM output. A 24-bit example: ffmpeg -i input.m4v -vn -c:a pcm_s24be output.aifc
Yes. On Linux or macOS, you can use a shell loop: 'for f in *.m4v; do ffmpeg -i "$f" -vn -c:a pcm_s16be "${f%.m4v}.aifc"; done'. On Windows Command Prompt, use: 'for %f in (*.m4v) do ffmpeg -i "%f" -vn -c:a pcm_s16be "%~nf.aifc"'. This will process each M4V in the current directory and produce a matching AIFC file, which is useful when extracting audio from a collection of iTunes video downloads.
Technical Notes
M4V uses the same underlying container structure as MP4, with AAC as the dominant audio codec and H.264 as the default video codec. When extracting audio to AIFC, FFmpeg must fully decode the AAC bitstream before encoding to PCM, as there is no direct remux path between these formats. The resulting pcm_s16be stream uses big-endian 16-bit samples, consistent with the AIFC/AIFF specification that originated on Motorola 68k and PowerPC Macs. Modern Apple Silicon Macs are natively little-endian but read AIFC correctly regardless. The '-b:a 128k' parameter in the command is technically a no-op for PCM codecs since PCM bitrate is mathematically fixed by sample rate and bit depth (e.g., 44100 Hz × 16 bits × 2 channels = 1,411.2 kbps), but FFmpeg accepts it without error. Metadata such as title and artist tags embedded in the M4V's iTunes metadata atoms will generally not transfer to the AIFC output, as AIFC has limited metadata support compared to MP4. DRM-protected M4V files purchased from iTunes cannot be converted by any tool, including this one, as the FairPlay DRM prevents decryption of the audio stream.