Convert MOD to AIFC — Free Online Tool
Convert MOD camcorder footage from JVC or Panasonic devices to AIFC audio, extracting the MPEG-2 audio track and re-encoding it as uncompressed 16-bit big-endian PCM — the native format for professional Apple audio workflows. Ideal for archiving interview audio, event recordings, or field audio captured on camcorder directly into a lossless-quality AIFC container.
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 store video and audio together in a modified MPEG-PS container, with the audio typically encoded as MPEG-1 Layer II or AC-3. During this conversion, FFmpeg demuxes the MOD container to extract the audio stream, then re-encodes it as PCM signed 16-bit big-endian audio (pcm_s16be) and wraps it in an AIFC container. The video stream is discarded entirely — this is a pure audio extraction. Because AIFC's pcm_s16be codec is uncompressed, the output represents the audio at full fidelity without further lossy degradation, though the source audio was already compressed inside the MOD file. No video re-encoding occurs, making the process fast and CPU-light.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the underlying engine that powers this browser-based tool via WebAssembly (FFmpeg.wasm). The same command runs identically in a local terminal installation of FFmpeg. |
-i input.mod
|
Specifies the input MOD file — a modified MPEG-PS container from a JVC or Panasonic camcorder. FFmpeg automatically detects the MPEG-2 video and compressed audio streams (typically MPEG-1 Layer II or AC-3) inside the container. |
-c:a pcm_s16be
|
Instructs FFmpeg to encode the output audio as signed 16-bit PCM in big-endian byte order, which is the native and most compatible PCM format for the AIFC container. This decodes whatever lossy audio codec was used in the MOD file and re-encodes it as uncompressed PCM, with no video stream written to the output. |
-b:a 128k
|
Specifies an audio bitrate target of 128 kbps. For uncompressed PCM codecs like pcm_s16be, this parameter has no effect — the actual bitrate is fixed by the source audio's sample rate, bit depth, and channel count — but it is included by the tool's default parameter set and does not harm 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 a valid AIFC file structure, producing a file natively readable by Logic Pro, GarageBand, Final Cut Pro, and other Apple audio tools. |
Common Use Cases
- Extracting interview or dialogue audio from JVC Everio or Panasonic SD camcorder footage to import into Logic Pro or Final Cut Pro for professional audio editing
- Archiving event recordings — weddings, concerts, speeches — captured on a camcorder as standalone AIFC audio files for long-term preservation in an Apple-native format
- Pulling field-recorded ambient audio from MOD camcorder footage to use as background sound design assets in a Pro Tools or GarageBand project
- Transcribing spoken content from old camcorder recordings by extracting the audio into AIFC for use with macOS speech recognition or third-party transcription tools
- Separating the audio track from MOD footage so a video editor and audio engineer can work on their respective streams independently without sharing large video files
- Converting a library of legacy MOD camcorder recordings to AIFC as part of a digital archiving workflow where Apple ecosystem compatibility is required
Frequently Asked Questions
No — the output quality is capped by the source. MOD files typically store audio as MPEG-1 Layer II or AC-3, both of which are lossy formats. Converting to pcm_s16be AIFC produces an uncompressed container, but the audio data itself was already lossy-compressed inside the MOD file. The AIFC output will faithfully preserve whatever fidelity existed in the original recording without introducing any additional compression artifacts, but it cannot recover detail that the camcorder's original encoding discarded.
AIFC with pcm_s16be stores audio as raw, uncompressed PCM samples — there is no compression applied to the audio data in the output file. A MOD file compresses its audio with a lossy codec like MPEG-1 Layer II, which is far more space-efficient. As a rule of thumb, uncompressed 16-bit stereo PCM at 48 kHz (common for camcorder audio) requires about 11 MB per minute, so a one-hour MOD recording could yield an AIFC file of roughly 650 MB for the audio alone.
Most JVC and Panasonic camcorders using the MOD format encode audio as MPEG-1 Layer II (MP2) at 256 kbps stereo, though some models use Dolby AC-3. FFmpeg automatically detects and decodes whichever codec is present during demuxing of the MPEG-PS container. Because the conversion decodes to raw PCM and re-encodes as pcm_s16be, the source codec does not affect the output format — but any artifacts from the original lossy encoding will carry through into the AIFC file.
Yes. Replace '-c:a pcm_s16be' with '-c:a pcm_s24be' to output 24-bit big-endian PCM, which is common in professional audio production and may be preferred when importing into Pro Tools or Logic Pro at high bit depths. AIFC supports pcm_s16be, pcm_s24be, pcm_s32be, pcm_f32be, and pcm_f64be — all big-endian formats. The full command would be: ffmpeg -i input.mod -c:a pcm_s24be output.aifc
On macOS or Linux, you can loop over all MOD files in a directory with: for f in *.mod; do ffmpeg -i "$f" -c:a pcm_s16be "${f%.mod}.aifc"; done — this processes each file sequentially and names the output after the original file. On Windows Command Prompt, use: for %f in (*.mod) do ffmpeg -i "%f" -c:a pcm_s16be "%~nf.aifc". The in-browser tool handles one file at a time, so the FFmpeg command is especially valuable when you have a large batch of camcorder footage to process.
MOD files may embed metadata such as recording timestamps in the MPEG-PS container, but AIFC has very limited metadata support compared to video containers. FFmpeg will attempt to copy any compatible metadata tags, but camcorder-specific fields like GPS coordinates or scene mode information will almost certainly be lost. If preserving this metadata matters, consider logging it separately before conversion or embedding it into the filename as part of your archiving workflow.
Technical Notes
AIFC (Audio Interchange File Format Compressed) is a big-endian format originally developed by Apple and commonly used in professional macOS and iOS audio toolchains. The pcm_s16be codec written by this conversion produces signed 16-bit samples in big-endian byte order — the native byte order for AIFC — which ensures full compatibility with Logic Pro, GarageBand, Final Cut Pro, and legacy QuickTime-based tools without any additional transcoding. The MOD container is a modified MPEG-PS (Program Stream) structure, and FFmpeg's demuxer handles both the standard JVC variant and Panasonic's slightly differing implementation reliably. One known limitation: MOD files sometimes contain multiple audio streams (e.g., a main mix plus a camera microphone channel), and by default FFmpeg will select only the first detected audio stream. To extract a secondary audio track, add '-map 0:a:1' before the output filename. The '-b:a 128k' flag in the command has no practical effect on uncompressed PCM codecs like pcm_s16be, since PCM bitrate is determined entirely by sample rate, bit depth, and channel count rather than a bitrate parameter — the actual bitrate will reflect the source audio's sample rate and stereo configuration.