Extract Audio from MOD to AIF — Free Online Tool
Extract audio from MOD camcorder footage into AIF, a lossless uncompressed PCM format ideal for archiving or professional audio workflows on Mac. The conversion decodes the AAC or MPEG audio track embedded in the MPEG-PS container and writes it as 16-bit big-endian PCM — no compression, no quality loss beyond what the original camcorder recording introduced.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MOD 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
MOD files from JVC and Panasonic camcorders store audio as a compressed stream (typically AAC or Dolby AC-3) inside a modified MPEG-PS container alongside MPEG-2 video. This tool discards the video stream entirely and decodes the compressed audio, then re-encodes it as 16-bit big-endian PCM (pcm_s16be) wrapped in Apple's AIF container. Because AIF is uncompressed, the output file will be significantly larger than the original audio track — but every sample decoded from the source is preserved exactly as-is. Any quality ceiling comes from the original lossy camcorder audio, not from this conversion step.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that handles demuxing the MPEG-PS container, decoding the camcorder's compressed audio stream, and writing the uncompressed AIF output. |
-i input.mod
|
Specifies the input MOD file from your JVC or Panasonic camcorder. FFmpeg's MPEG-PS demuxer reads the file despite the non-standard .mod extension, correctly identifying the MPEG-2 video and compressed audio streams inside. |
-vn
|
Disables video output entirely, discarding the MPEG-2 video stream from the MOD file. This flag is required because AIF is a pure audio container and cannot hold a video stream — omitting it would cause FFmpeg to error. |
-c:a pcm_s16be
|
Decodes the MOD file's compressed audio (AAC or AC-3) and re-encodes it as signed 16-bit big-endian PCM — the native uncompressed audio format inside an AIF file. This produces a lossless representation of whatever the camcorder originally recorded. |
output.aif
|
Sets the output filename and triggers FFmpeg to wrap the PCM audio in Apple's Audio Interchange File Format container. The .aif extension is recognized natively by macOS and by professional audio applications like Logic Pro and GarageBand without any additional configuration. |
Common Use Cases
- Extracting spoken word recordings from JVC or Panasonic camcorder footage to import into Logic Pro or GarageBand, which natively favor AIF over compressed formats
- Archiving the audio track of family or event MOD recordings in a lossless, uncompressed format that remains readable without proprietary codecs decades from now
- Pulling location audio recorded on a camcorder to sync with separately recorded video in a professional post-production timeline that requires uncompressed PCM
- Preparing camcorder interview audio for transcription or podcast editing, where a lossless AIF source prevents generational quality loss across multiple edits and exports
- Converting MOD audio to AIF for analysis in audio research or forensic workflows where uncompressed waveforms are required and compressed artifacts must be avoided
- Stripping the audio from a MOD file to deliver a clean AIF stem to a musician or sound designer who needs to score or sweeten the original camcorder audio
Frequently Asked Questions
No — and it's important to understand why. The audio inside a MOD file was captured by the camcorder using a lossy codec (typically AAC or AC-3), so some compression artifacts were introduced at the moment of recording. Converting to AIF decodes that compressed audio and stores the result as uncompressed PCM, preserving every sample faithfully, but it cannot recover information the lossy codec discarded. Think of AIF here as a lossless container for a lossy source — you get a perfect copy of what the camcorder actually captured, with no further degradation.
The MOD file stores audio in a compressed format like AAC, which achieves high compression ratios. AIF with pcm_s16be stores every audio sample as a raw 16-bit integer — no compression whatsoever. A typical stereo audio track at 48 kHz in 16-bit PCM consumes roughly 5.6 MB per minute, compared to under 1 MB per minute for a 128 kbps AAC stream. If your MOD footage is long, expect AIF files that are 5–10 times larger than the original audio track alone.
MOD files carry limited metadata in their MPEG-PS container headers, and AIF's metadata support is minimal — it uses a basic ANNO chunk that most tools ignore. FFmpeg does not map MPEG-PS metadata fields into AIF chunks during this conversion, so recording date, GPS coordinates, or device information embedded in the MOD file will not carry over. If preserving that metadata matters, note it separately before converting.
Yes — by modifying the FFmpeg command, you can select pcm_s24be (24-bit) or pcm_s32be (32-bit) instead of the default pcm_s16be. Change '-c:a pcm_s16be' to '-c:a pcm_s24be' for 24-bit output. However, since the camcorder's original audio was captured and compressed at a fixed quality ceiling, increasing the bit depth in the output will not reveal additional dynamic range — it simply stores the decoded samples in a wider container. For most camcorder recordings, 16-bit is entirely sufficient.
On macOS or Linux, you can loop over all MOD files in a directory with a shell one-liner: 'for f in *.mod; do ffmpeg -i "$f" -vn -c:a pcm_s16be "${f%.mod}.aif"; done'. On Windows Command Prompt, use 'for %f in (*.mod) do ffmpeg -i "%f" -vn -c:a pcm_s16be "%~nf.aif"'. Each file is processed sequentially. This is especially useful for digitizing a collection of camcorder tapes that were split into multiple MOD files by the device.
Yes. FFmpeg detects the audio codec inside the MOD container automatically and decodes it regardless of whether it is AAC, AC-3, or another supported format. The '-c:a pcm_s16be' flag instructs FFmpeg to decode whatever audio it finds and re-encode the result as 16-bit PCM for AIF — you do not need to specify the input audio codec. JVC and Panasonic camcorders vary in their audio encoding choices depending on the model and recording mode, so this flexibility matters in practice.
Technical Notes
MOD is a file extension used by specific JVC (Everio series) and Panasonic camcorders to store MPEG-2 video in a modified MPEG Program Stream container — essentially a renamed .mpg with a non-standard file extension that can confuse some media players. The audio track is typically AAC stereo at 48 kHz or Dolby AC-3, depending on the camcorder model and firmware version. FFmpeg handles MOD natively through its MPEG-PS demuxer, so no special input flags are required. The output codec pcm_s16be (signed 16-bit big-endian PCM) matches Apple's historical preference in the AIF format and is universally compatible with Mac audio tools including Logic Pro, GarageBand, Final Cut Pro, and Audacity. The '-vn' flag is essential here because AIF is an audio-only container — without it, FFmpeg would attempt to encode a video stream into a format that cannot hold one and return an error. File sizes for AIF are predictable: stereo 16-bit 48 kHz audio produces approximately 11.5 MB per minute. There is no chapter, subtitle, or secondary audio track support in either format, so multi-track MOD recordings (rare but possible on some professional Panasonic models) will only yield the first detected audio stream.