Convert DVR to AIFC — Free Online Tool

Convert DVR surveillance or broadcast recordings to AIFC audio, extracting the AAC or MP3 audio track and re-encoding it as uncompressed PCM (pcm_s16be) in Apple's compressed AIFF container. Ideal for archiving or professionally processing audio captured from DVR footage in a lossless-quality, big-endian format compatible with pro audio tools.

FFmpeg Command

Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg

Free — no uploads, no signups. Your files never leave your browser.

Estimated output:

Conversion Complete!

Download

How It Works

DVR files typically store video encoded with H.264 (libx264) or MJPEG alongside AAC or MP3 audio in a proprietary container. During this conversion, FFmpeg discards the video stream entirely and decodes the compressed audio (AAC or MP3) from the DVR file, then re-encodes it as 16-bit big-endian PCM (pcm_s16be) wrapped in an AIFC container. AIFC is an extension of Apple's AIFF format that supports both uncompressed and compressed audio — in this case the output is uncompressed PCM, which is lossless at the PCM stage, though any quality lost during the original lossy DVR audio encoding cannot be recovered. The result is a professional-grade audio file with no further lossy compression applied.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg binary, the open-source multimedia processing engine that handles demuxing the proprietary DVR container, decoding the compressed audio stream, and encoding the output AIFC file entirely within your browser via WebAssembly.
-i input.dvr Specifies the input DVR file. FFmpeg will probe the file to detect the proprietary DVR container structure and identify the available audio stream (typically AAC or MP3) and video stream (typically H.264 or MJPEG) inside it.
-c:a pcm_s16be Sets the output audio codec to 16-bit signed big-endian PCM, which is the standard uncompressed audio encoding for AIFC files. This decodes the lossy DVR audio (AAC or MP3) and re-encodes it as uncompressed PCM, applying no further lossy compression in the output.
-b:a 128k Specifies a 128 kbps audio bitrate target. For uncompressed PCM codecs like pcm_s16be, this flag has minimal functional effect since PCM bitrate is determined by sample rate and bit depth rather than a compression target, but it is included for compatibility with the tool's quality parameter system.
output.aifc Defines the output filename with the .aifc extension, which tells FFmpeg to mux the PCM audio into an AIFC container — Apple's big-endian IFF-based audio format that supports both compressed and uncompressed audio data, compatible with macOS and professional audio applications.

Common Use Cases

  • Extract and archive the audio from DVR surveillance footage for use as evidence or documentation, in a format that professional audio editors and legal tools can reliably open.
  • Pull broadcast-captured audio from a DVR recording into a DAW like Logic Pro or Pro Tools, which natively handle AIFC/AIFF files for editing or transcription.
  • Convert DVR interview or conference recordings to AIFC so the audio track can be processed with high-fidelity audio analysis tools that require uncompressed PCM input.
  • Strip audio from DVR CCTV recordings to create a clean audio-only archive file that is smaller than the original video but retains maximum audio fidelity in a standardized format.
  • Prepare DVR-captured television audio for further processing in macOS-based audio workflows, where AIFC is a first-class format supported by Core Audio and related APIs.
  • Convert DVR audio to big-endian PCM AIFC as an intermediate step before further codec processing, avoiding the cumulative quality loss of repeated lossy re-encoding.

Frequently Asked Questions

No — the conversion will not recover quality lost during the original DVR recording. DVR files use lossy codecs like AAC or MP3 for audio, and any compression artifacts from that stage are baked into the audio data. What this conversion does is decode the lossy audio and re-encode it as uncompressed PCM (pcm_s16be), which means no additional quality is lost in the output AIFC file. Think of it as 'freezing' the audio at its current quality in a lossless container.
AIFC's native and most compatible audio codec is big-endian PCM, and pcm_s16be (16-bit signed big-endian PCM) is the default because it matches the original AIFF/AIFC specification and is universally supported by pro audio applications on macOS and other platforms. AIFC does technically support compressed codecs like pcm_alaw or pcm_mulaw, but for archival and professional use, uncompressed PCM is preferred. The 'big-endian' byte order is a defining characteristic of the AIFC format, distinguishing it from WAV which uses little-endian PCM.
The video stream is dropped entirely. Since AIFC is a pure audio container with no support for video, FFmpeg automatically excludes the H.264 or MJPEG video track from the DVR file and only processes the audio. You will be left with an audio-only AIFC file. If you need to keep the video, you would need to convert to a different output format that supports video.
To change the PCM bit depth, replace pcm_s16be with another supported codec such as pcm_s24be for 24-bit audio or pcm_s32be for 32-bit integer audio — for example: ffmpeg -i input.dvr -c:a pcm_s24be output.aifc. The -b:a flag has limited effect on uncompressed PCM codecs since their bitrate is determined by sample rate and bit depth, but you can control the sample rate by adding -ar 48000 (for 48 kHz) to the command. Higher bit depths like 24-bit are useful if you plan to do further processing in a DAW.
Yes — on the command line you can use a shell loop to process multiple files. On Linux or macOS, run: for f in *.dvr; do ffmpeg -i "$f" -c:a pcm_s16be -b:a 128k "${f%.dvr}.aifc"; done. On Windows Command Prompt, use: for %f in (*.dvr) do ffmpeg -i "%f" -c:a pcm_s16be -b:a 128k "%~nf.aifc". This is especially useful for batch-archiving large libraries of DVR surveillance footage as audio. The in-browser tool processes one file at a time, so the FFmpeg command is the recommended approach for bulk jobs.
Metadata preservation is limited in this conversion. DVR files use proprietary container formats that may embed recorder-specific metadata (timestamps, camera IDs, channel info) that FFmpeg cannot reliably parse or map to AIFC metadata fields. Standard tags like title or date may be carried over if FFmpeg can read them, but specialized DVR metadata will likely be lost. AIFC itself has limited metadata support compared to containers like MP4 or MKV, so if metadata retention is critical, you should document it separately before conversion.

Technical Notes

DVR is a proprietary container format with no universal specification, meaning FFmpeg's ability to demux it depends on the specific DVR system that created the file — some DVR recordings are internally structured as AVI or MPEG-PS variants, while others use entirely vendor-specific layouts. The audio codec inside a DVR file is most commonly AAC at 128k or MP3, both of which FFmpeg can decode reliably when the container is recognized. The output AIFC container uses big-endian byte ordering as defined by Apple's original AIFF/AIFC specification (IFF-based), which makes it natively compatible with macOS Core Audio, Logic Pro, Pro Tools, and other professional audio environments. The pcm_s16be codec produces CD-quality 16-bit stereo audio, which is appropriate for most DVR audio content that was originally recorded at similar or lower quality. One known limitation is that AIFC does not support multiple audio tracks, chapters, or subtitles, so only the first (or primary) audio stream from the DVR file will be included in the output. Files converted to pcm_s16be AIFC will be significantly larger than the original lossy DVR audio — a 10-minute stereo AAC stream at 128k (~9.6 MB) will expand to approximately 100 MB as 16-bit PCM at 44.1 kHz — so plan storage accordingly for long DVR recordings.

Related Tools