Extract Audio from DVR to M4A — Free Online Tool
Extract the AAC audio track from DVR recordings and save it as an M4A file — a clean, iTunes-compatible audio container without any re-encoding quality loss. Since DVR files already store audio as AAC and M4A is a native AAC container, this conversion is a lossless stream extraction.
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 store audio as AAC (Advanced Audio Coding) alongside their video stream, which is typically encoded with H.264 (libx264) or MJPEG. This tool strips the video stream entirely and extracts the raw AAC audio data, placing it directly into an M4A container — an MPEG-4 audio-only wrapper popularized by Apple iTunes. Because both the source and destination use AAC as the audio codec, no audio re-encoding occurs by default; the AAC bitstream is copied as-is into the new container. The result is an audio file that is bit-for-bit identical in quality to the audio in the original DVR recording, just without the video overhead.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program — the open-source multimedia processing engine running here as FFmpeg.wasm inside your browser via WebAssembly, with no server upload required. |
-i input.dvr
|
Specifies the input file in DVR format — a proprietary container used by digital video recorders for surveillance and broadcast capture, which FFmpeg will demux to access its internal audio and video streams. |
-vn
|
Disables video output entirely, ensuring that only the audio track from the DVR recording is passed through — the video stream (typically H.264 or MJPEG in DVR files) is discarded and does not appear in the M4A output. |
-c:a aac
|
Sets the audio codec to AAC (Advanced Audio Coding). Since the DVR source already contains AAC audio and M4A is natively an AAC container, this maintains codec consistency and allows direct stream handling without transcoding quality loss. |
-b:a 128k
|
Specifies a target audio bitrate of 128 kilobits per second — matching the typical default audio bitrate in DVR recordings and providing a standard quality level for AAC that is well-suited for voice, broadcast dialogue, and general audio content. |
-vn
|
A second instance of the video-disable flag, which reinforces that no video stream should be written to the M4A output. This is redundant but harmless — M4A is inherently an audio-only container and would reject a video stream regardless. |
output.m4a
|
Defines the output file as an M4A — an MPEG-4 audio container with the .m4a extension that signals to players like iTunes and Apple Music that this is an audio-only file, ensuring correct handling and metadata support across the Apple ecosystem. |
Common Use Cases
- Extract the audio from a DVR-captured security camera feed to archive or review spoken events — such as doorbell conversations or intercom exchanges — without needing a video player.
- Pull the audio from a DVR broadcast recording (e.g., a recorded TV program or sports event) to create a standalone audio file for playback in iTunes, Apple Music, or any AAC-compatible player.
- Convert DVR surveillance footage audio into M4A files for use as evidence transcripts or for sharing with transcription services that accept standard audio formats.
- Extract commentary or dialogue from a DVR-recorded lecture, seminar, or broadcast interview to repurpose as a podcast episode or audio-only archive.
- Reduce file size dramatically by discarding the video stream from large DVR recordings when only the audio content is needed for review or storage.
- Prepare DVR audio for import into iOS or macOS workflows, where M4A with AAC is the native format for GarageBand, Logic Pro, and the Apple ecosystem.
Frequently Asked Questions
No — because DVR files store audio as AAC and M4A is simply an MPEG-4 container designed to hold AAC streams, the audio data is extracted and placed into the new container without re-encoding. This is sometimes called a 'remux' or 'stream copy.' The audio quality in your M4A file will be bit-for-bit identical to what was in the original DVR recording. Quality loss would only occur if you explicitly forced transcoding to a different codec or bitrate.
DVR files contain both a video stream and an audio stream. Video data — especially from H.264-encoded surveillance or broadcast recordings — makes up the vast majority of the file size. By extracting only the audio track, you discard all video data, which typically results in the M4A file being 95–99% smaller than the source DVR file. The M4A will only contain the audio, so its size reflects the audio bitrate multiplied by the duration.
Yes — M4A with AAC encoding is Apple's native audio format and is fully supported by iTunes, Apple Music, iPhone, iPad, iPod, and macOS QuickTime Player. The M4A container also supports iTunes metadata tags (artist, title, album art), so you can tag the extracted audio after conversion. It is one of the most compatible audio formats across the entire Apple ecosystem.
DVR formats are proprietary and typically embed recording metadata (timestamps, channel names, device IDs) in format-specific ways that are not standardized. FFmpeg will attempt to copy any metadata it can parse into the M4A container's standard tags, but proprietary DVR metadata fields are often lost or unreadable. The M4A container supports standard iTunes-style tags like title, artist, and date, but you may need to manually add meaningful metadata after conversion.
The command uses '-b:a 128k' to set the audio bitrate to 128 kbps. However, since this conversion performs a stream copy of the existing AAC data rather than re-encoding, the '-b:a' flag does not actually alter the audio in this specific command — it would only take effect if you added '-c:a aac' to force re-encoding. If you want to re-encode at a different quality (e.g., 192k), use: ffmpeg -i input.dvr -vn -c:a aac -b:a 192k output.m4a. Valid bitrate options include 64k, 96k, 128k, 192k, 256k, and 320k.
Yes — on Linux or macOS, you can loop over DVR files in a shell script: for f in *.dvr; do ffmpeg -i "$f" -vn -c:a aac -b:a 128k -vn "${f%.dvr}.m4a"; done. On Windows Command Prompt, use: for %f in (*.dvr) do ffmpeg -i "%f" -vn -c:a aac -b:a 128k -vn "%~nf.m4a". This is particularly useful for processing large batches of surveillance recordings or broadcast archives offline.
Technical Notes
DVR is a proprietary container format with no single standardized specification — different manufacturers (Hikvision, Dahua, standalone PVR devices) implement it differently. FFmpeg has general support for DVR demuxing but may occasionally fail to parse certain vendor-specific DVR variants; if the command errors, try probing the file first with 'ffmpeg -i input.dvr' to verify the detected audio stream. The default audio codec in DVR recordings is AAC at 128k, making the M4A container a natural fit since M4A is itself an MPEG-4 Part 14 container optimized for AAC streams. The '-vn' flag appears twice in the resolved command (once before the codec flags and once at the end), which is harmless — both instances instruct FFmpeg to exclude any video stream from the output. M4A supports chapter markers (unlike many audio formats), which could be useful if you segment long DVR recordings, though chapter data would need to be added manually post-conversion. One known limitation is that multi-channel audio beyond stereo (e.g., 5.1 surround from broadcast DVR recordings) is preserved in M4A/AAC without downmixing, so channel layout from the source is respected.