Convert MOV to DVR — Free Online Tool
Convert MOV files from Apple's QuickTime container into DVR format for compatibility with digital video recorders and surveillance systems. This tool re-encodes your MOV footage using H.264 video and AAC audio — the codecs most widely supported by DVR hardware — directly in your browser using FFmpeg.wasm.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MOV 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
MOV is Apple's professional container format that can carry a wide range of codecs including H.265, VP9, ProRes, and lossless audio. DVR format, used by digital video recorders and surveillance systems, is a much more constrained proprietary container that typically expects H.264 video and AAC or MP3 audio. During this conversion, if your MOV file already uses H.264 video, the stream is still explicitly encoded to ensure DVR-compatible settings and bitrate characteristics. Audio is encoded to AAC at 128k. Critically, MOV features that DVR does not support — including transparency channels (alpha), subtitle tracks, chapter markers, and multiple audio tracks — are dropped during conversion. Only the primary video and audio streams are preserved in the output.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary. In this browser-based tool, FFmpeg runs locally via WebAssembly (FFmpeg.wasm) — no data leaves your machine. When running the command on your desktop for files over 1GB, this calls your locally installed FFmpeg installation. |
-i input.mov
|
Specifies the input file as a MOV (QuickTime) container. FFmpeg reads and demuxes the MOV file, separating the video, audio, and any other streams (subtitles, chapters, alpha) for processing. Only the primary video and audio streams are passed to the output. |
-c:v libx264
|
Instructs FFmpeg to encode the video stream using the H.264 codec (libx264). DVR format requires either H.264 or MJPEG, and H.264 is the default because it delivers far better compression efficiency and is universally supported by DVR playback hardware. This re-encoding step is mandatory regardless of what video codec the source MOV contained. |
-c:a aac
|
Encodes the audio stream to AAC, which is the default and most broadly compatible audio codec for DVR format. If the source MOV contained lossless audio (FLAC), multi-channel Opus, or Vorbis, those tracks are all transcoded down to stereo AAC at the specified bitrate. |
-crf 23
|
Sets the Constant Rate Factor for H.264 video quality. A value of 23 is the libx264 default and produces a good balance between visual quality and file size appropriate for DVR recording use cases. Lower values (e.g., 18) produce sharper output with larger files; higher values (e.g., 28–36) reduce file size with increasing visible compression. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second. For voice-over, broadcast capture, and surveillance audio — the primary use cases for DVR — 128k AAC provides transparent or near-transparent quality. If your source MOV contains high-fidelity music or professional audio, you may want to increase this to 192k or 256k. |
output.dvr
|
Specifies the output filename with the .dvr extension, signaling FFmpeg to write the encoded video and audio into a DVR-format container. The .dvr extension is what DVR hardware and management software use to identify and play back recordings. |
Common Use Cases
- Importing iPhone or Mac screen recordings saved as MOV files into a standalone DVR or network video recorder (NVR) for archival alongside surveillance footage
- Preparing edited QuickTime footage from Final Cut Pro or DaVinci Resolve for playback on a DVR-based media appliance that only accepts DVR-format video
- Converting MOV clips captured by professional cameras (such as Canon or Sony mirrorless cameras) into DVR format for ingestion into a closed-circuit TV management system
- Re-packaging MOV security camera exports — which macOS tools often default to saving as MOV — into the native DVR format expected by the original recorder's playback software
- Downgrading a MOV file that uses H.265 or VP9 video to a DVR-compatible H.264 stream, since many DVR systems lack the hardware decoding capability for modern codecs
Frequently Asked Questions
Yes, some quality loss is unavoidable because DVR is a lossy-only format. The conversion re-encodes the video using H.264 at CRF 23, which is a good general-purpose quality setting but introduces compression artifacts compared to lossless or high-bitrate MOV sources. If your original MOV used a high-quality codec like Apple ProRes or lossless FLAC audio, both the video and audio will be transcoded down to H.264 and AAC respectively, which represent a meaningful quality reduction. For surveillance and DVR playback purposes, CRF 23 is typically more than adequate.
DVR format does not support transparency (alpha channels), subtitle tracks, chapter markers, or multiple audio tracks. If your MOV file contains any of these — for example, a Final Cut Pro export with embedded chapter markers or a multi-language audio track — those elements will be silently dropped during conversion. Only the primary video stream and the first audio track are carried over. There is no way to preserve these features within a DVR container.
No — DVR format only supports H.264 (libx264) and MJPEG for video. If your MOV source uses H.265, this conversion will automatically transcode it to H.264 using the CRF 23 quality setting. This makes the file compatible with DVR hardware but also increases encoding time and introduces a quality trade-off, since H.265 is generally more efficient than H.264 at equivalent visual quality.
The video quality is controlled by the -crf flag. The default is 23, where lower values produce higher quality and larger files, and higher values produce smaller files with more compression. For DVR output, valid CRF values are 0, 10, 18, 23, 28, 36, and 51. For example, to get higher quality output, change the command to use -crf 18: ffmpeg -i input.mov -c:v libx264 -c:a aac -crf 18 -b:a 128k output.dvr. For surveillance or archival use where storage is a concern, -crf 28 offers a reasonable size reduction with acceptable quality.
The single-file command displayed on this page can be adapted for batch processing on your desktop using a shell loop. On Linux or macOS, you can run: for f in *.mov; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.mov}.dvr"; done. On Windows PowerShell, use: Get-ChildItem *.mov | ForEach-Object { ffmpeg -i $_.Name -c:v libx264 -c:a aac -crf 23 -b:a 128k ($_.BaseName + '.dvr') }. The browser-based tool on this page processes one file at a time and supports files up to 1GB.
This can happen if your source MOV file used a highly efficient codec like H.265, or if it was heavily compressed to begin with. When FFmpeg re-encodes to H.264 at CRF 23, the output bitrate is determined by the complexity of the video content, not the size of the input. Short, high-motion clips from H.265 MOV sources are especially likely to produce larger H.264 DVR outputs because H.264 requires more data to represent the same visual information. You can increase the CRF value (e.g., -crf 28 or -crf 36) to reduce file size at the cost of some quality.
Technical Notes
DVR is a proprietary, recorder-vendor-specific container format with significantly fewer capabilities than Apple's MOV container. The codec surface area of DVR is limited to H.264 or MJPEG for video and AAC or MP3 for audio, making it unsuitable for modern high-efficiency codecs. This conversion uses libx264 with CRF 23 as the default, which balances file size and quality well for the surveillance and broadcast-capture use cases DVR was designed for. Unlike MOV-to-MP4 conversions, there is no stream copy (remux) shortcut available here: the output must be fully re-encoded to conform to DVR's codec and container constraints even if the source MOV already uses H.264. Metadata including QuickTime chapter atoms, Apple-specific timecode tracks, GPS metadata (common in iPhone MOV files), and multi-channel audio configurations are all discarded. The MOV container's -movflags +faststart optimization for web streaming also has no equivalent in DVR. If you need to retain rich metadata or lossless quality, DVR is not an appropriate target format — consider MP4 or MKV instead.