Convert DVR to AIFF — Free Online Tool
Extract and convert audio from DVR recordings into AIFF, Apple's uncompressed lossless audio format. This tool decodes the AAC or MP3 audio stream embedded in your DVR file and re-encodes it as 16-bit big-endian PCM (pcm_s16be), producing a full-fidelity AIFF file ready for professional audio workflows on macOS.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your DVR 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
DVR files typically store video using H.264 (libx264) or MJPEG alongside compressed audio encoded in AAC or MP3 — both lossy formats designed to minimize file size for long-duration surveillance or broadcast recordings. During conversion, FFmpeg discards the video stream entirely and decodes the compressed audio track back to raw PCM samples. Those samples are then written into an AIFF container using the pcm_s16be codec — 16-bit signed integers in big-endian byte order, which is the native AIFF standard inherited from Apple's PowerPC architecture. Because the source audio is lossy (AAC or MP3), the output AIFF is losslessly preserving exactly what was in the DVR — no further audio generation is lost in this step, but any quality reduction from the original lossy encoding is already baked in.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program. In the browser-based version of this tool, FFmpeg runs via WebAssembly (FFmpeg.wasm) entirely within your browser — no file is sent to a server. The same command works identically on a local FFmpeg desktop installation for files over 1GB. |
-i input.dvr
|
Specifies the input DVR file. FFmpeg will probe this file to detect its container structure and identify the available streams — typically an H.264 or MJPEG video stream and an AAC or MP3 audio stream stored in the DVR's proprietary wrapper. |
-c:a pcm_s16be
|
Sets the audio output codec to pcm_s16be — 16-bit signed PCM in big-endian byte order, which is the standard uncompressed audio encoding used in AIFF files. This decodes the lossy AAC or MP3 audio from the DVR and writes it as raw, uncompressed samples in the format Apple's AIFF specification requires. |
output.aiff
|
Defines the output filename and tells FFmpeg to write an AIFF container. FFmpeg infers from the .aiff extension that the output must conform to the Audio Interchange File Format, which is an audio-only container — so the video stream from the DVR is automatically excluded without needing an explicit -vn flag. |
Common Use Cases
- Extracting a clean audio track from a surveillance DVR recording for use as evidence in a legal or insurance review, where an uncompressed format is required for chain-of-custody documentation
- Pulling the audio from a broadcast capture DVR file to import into Logic Pro or GarageBand on macOS, both of which handle AIFF natively and without additional codec installs
- Archiving the audio portion of long-form DVR recordings — such as council meetings or court proceedings recorded via broadcast capture — into a lossless format for long-term institutional storage
- Transcribing speech from a DVR recording by first extracting the audio to AIFF, then feeding the file into professional transcription software that requires uncompressed input
- Stripping audio from a CCTV DVR clip to analyze acoustic events (glass breaking, alarms, voices) in a waveform editor like Adobe Audition, which benefits from the full dynamic range of uncompressed PCM
Frequently Asked Questions
No — the AIFF output will be lossless, but it cannot recover quality that was already discarded when the DVR originally encoded the audio as AAC or MP3. Think of it like printing a JPEG at full resolution: the uncompressed container preserves every bit of what's there, but the lossy compression artifacts from the source are already permanent. What you gain is a format that won't degrade further through any subsequent editing or re-export steps in your audio software.
AIFF stores raw uncompressed PCM audio, so file size scales directly with duration and sample rate — a one-hour stereo recording at 44.1kHz and 16-bit depth takes roughly 600MB in AIFF. The DVR file was compact because its audio was stored as AAC or MP3, which achieve 5–10x compression ratios. The video stream from the DVR is also discarded entirely, so you're trading a compressed multi-stream container for a large but audio-only uncompressed file.
DVR-specific metadata like camera channel identifiers, recording timestamps, and motion-event markers are proprietary to the DVR system's format and are not mapped to standard FFmpeg metadata fields. The AIFF format supports only basic audio metadata (artist, title, etc.), and none of the surveillance-specific fields from the DVR will carry over. If timestamp documentation is important — for example, for evidentiary use — you should record that information separately before converting.
Yes — AIFF supports pcm_s24be (24-bit), pcm_s32be (32-bit), pcm_f32be (32-bit float), and pcm_f64be (64-bit float). To use 24-bit output, modify the command to: ffmpeg -i input.dvr -c:a pcm_s24be output.aiff. Keep in mind that since the DVR source audio is AAC or MP3 (typically 16-bit effective resolution), using a higher bit depth won't recover lost detail — it simply gives downstream processing tools more headroom. For most use cases, the default pcm_s16be is sufficient.
On macOS or Linux, you can loop over all DVR files in a folder with: for f in *.dvr; do ffmpeg -i "$f" -c:a pcm_s16be "${f%.dvr}.aiff"; done. On Windows Command Prompt, use: for %f in (*.dvr) do ffmpeg -i "%f" -c:a pcm_s16be "%~nf.aiff". This processes each file sequentially, producing a matching AIFF file for every DVR input. The browser-based tool on this page handles one file at a time, so the FFmpeg command is the recommended path for bulk conversions.
No — the video codec in the DVR file has no effect on this conversion because the FFmpeg command targets only the audio stream (-c:a pcm_s16be) and writes to AIFF, which is an audio-only container. FFmpeg will automatically ignore the video stream when muxing into AIFF. Whether the source video is MJPEG, H.264, or any other codec, the audio extraction process is identical.
Technical Notes
AIFF uses big-endian byte ordering (hence the 'be' suffix in pcm_s16be), a legacy of the Motorola 68000 and PowerPC processors in early Apple hardware. This distinguishes it from WAV, which uses little-endian PCM. Both are uncompressed, but software that reads raw audio data byte-by-byte — such as older broadcast tools or some embedded systems — must be byte-order aware. FFmpeg handles this transparently during the conversion. The DVR format itself is not a single standardized specification; it varies by manufacturer (Hikvision, Dahua, and others each have proprietary variants), but FFmpeg's demuxer handles the most common implementations. In rare cases where FFmpeg cannot identify the DVR container, you may need to probe the file with ffprobe first to confirm the detected format and audio stream codec before converting. Because DVR files do not support subtitle or chapter tracks, no ancillary data is lost in the audio extraction. The output AIFF will contain a single stereo (or mono, depending on the source) audio track with no embedded artwork, chapters, or subtitle cues.