Convert HEVC to DVR — Free Online Tool
Convert HEVC/H.265 video files to DVR format using libx264 re-encoding, making high-efficiency compressed footage compatible with digital video recorder systems and surveillance playback software. This tool runs entirely in your browser — no uploads required — and displays the exact FFmpeg command for processing larger files locally.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your HEVC 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
HEVC (H.265) uses advanced compression that many DVR systems and proprietary playback platforms cannot decode natively. This conversion fully re-encodes the video stream from H.265 to H.264 using libx264 at CRF 23, which is a medium-quality lossy transcode — not a simple remux. The H.264 codec is far more broadly supported by DVR hardware and playback software. If your source HEVC file contains audio, it is simultaneously transcoded to AAC at 128k bitrate. Because both the video and audio are re-encoded, some generation loss occurs and processing is more CPU-intensive than a simple container swap. The output .dvr file uses a container structure expected by DVR platforms, wrapping H.264 video and AAC audio in a format compatible with digital recording and surveillance review systems.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg media processing engine. In this browser-based tool, FFmpeg runs locally via WebAssembly (FFmpeg.wasm) — your HEVC file never leaves your device. |
-i input.hevc
|
Specifies the input file — your source HEVC/H.265 video. FFmpeg reads and fully decodes the H.265 bitstream frame by frame before re-encoding begins. |
-c:v libx264
|
Sets the video encoder to libx264, the industry-standard open-source H.264 encoder. This is required because DVR systems expect H.264 video, and HEVC cannot be remuxed directly — a full re-encode from H.265 to H.264 is necessary. |
-c:a aac
|
Encodes the audio track as AAC (Advanced Audio Coding), the default and most widely supported audio codec for DVR containers. Any audio present in the HEVC source is transcoded to AAC regardless of its original format. |
-crf 23
|
Sets the Constant Rate Factor for the libx264 H.264 encode to 23, which is the libx264 default and produces a good balance of visual quality and file size. Lower values (e.g., 18) produce higher quality but larger DVR files; higher values (e.g., 28–36) reduce size at the cost of detail. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, which is sufficient for clear speech and general audio in DVR surveillance or broadcast capture recordings. Increase to 192k or 256k if the source contains music or high-fidelity audio that needs to be preserved. |
output.dvr
|
Defines the output filename with the .dvr extension, signaling FFmpeg to write the encoded H.264 video and AAC audio into a DVR-compatible container format suitable for playback on digital video recorder systems. |
Common Use Cases
- Importing drone or action camera footage encoded in H.265 into a legacy DVR system for security review or archival alongside surveillance recordings
- Converting broadcast captures or screen recordings saved in HEVC to a DVR-compatible format for playback on standalone DVR hardware units
- Preparing H.265 clips from modern smartphones or cameras for ingestion into surveillance management software that only accepts H.264-based DVR streams
- Downconverting high-efficiency HEVC recordings to H.264 DVR format to ensure compatibility with older video review workstations in law enforcement or facilities management
- Archiving HEVC-encoded video alongside existing H.264 DVR footage libraries to maintain a consistent codec baseline across a recording system
- Testing DVR system compatibility by converting a sample HEVC clip to .dvr format before committing to a full-scale recording pipeline migration
Frequently Asked Questions
Most DVR hardware and proprietary surveillance software were designed around H.264, which was the dominant codec when these systems were built. HEVC/H.265 requires significantly more complex decoding logic, and many embedded DVR processors lack the hardware acceleration needed to decode it in real time. Converting to H.264 in a .dvr container ensures the footage is immediately compatible without firmware upgrades or additional software licenses.
There will be some quality loss because this is a full re-encode from one lossy codec to another — a process sometimes called generational loss. However, at CRF 23 (the default used in this tool), libx264 produces high-quality H.264 output that is visually close to the source for most surveillance and review purposes. The loss is more significant if your source HEVC file was already heavily compressed at a high CRF value like 35 or above.
Almost always larger. HEVC is specifically designed to achieve the same visual quality as H.264 at roughly half the file size. Re-encoding to H.264 at a comparable quality setting (CRF 23) will typically produce a file that is 30–80% larger than the source HEVC file, depending on the content. If file size is critical, you can increase the CRF value in the FFmpeg command to trade quality for smaller output.
Adjust the -crf value in the command. For DVR/H.264, CRF ranges from 0 (lossless) to 51 (worst quality), with lower numbers meaning better quality and larger files. The default of 23 is a good all-purpose setting. For surveillance footage where fine detail matters (license plates, faces), try CRF 18. For rough previews where file size matters more, CRF 28–36 is acceptable. Replace '23' in the command with your chosen value: ffmpeg -i input.hevc -c:v libx264 -c:a aac -crf 18 -b:a 128k output.dvr
Yes, on a desktop you can use a shell loop to process multiple files. On Linux or macOS: for f in *.hevc; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.hevc}.dvr"; done. On Windows Command Prompt: for %f in (*.hevc) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.dvr". The browser-based tool processes one file at a time, so the FFmpeg command is especially useful for batch workflows.
Standard metadata such as creation timestamps may be carried over into the DVR container if FFmpeg can map them, but DVR is a proprietary format and many metadata fields are not standardized across manufacturers. GPS coordinates, camera model tags, and embedded chapter or subtitle data from the HEVC source are not preserved in the output. If metadata retention is critical, verify the output with a tool like MediaInfo or exiftool before using it in a production DVR workflow.
Technical Notes
The core technical challenge of this conversion is the codec mismatch between source and destination: HEVC (H.265) and H.264 are fundamentally different compression algorithms and cannot be remuxed — every frame must be fully decoded from H.265 and re-encoded to H.264, making this a computationally expensive operation compared to container-only conversions. The libx264 encoder used here is the gold-standard open-source H.264 implementation and produces output universally accepted by DVR platforms. CRF 23 represents the libx264 default and targets a visually acceptable quality level, but it is worth noting that because HEVC sources are already decoded to raw frames before re-encoding, any compression artifacts in the source become baked into the H.264 output alongside new quantization artifacts. The DVR format does not support subtitles, multiple audio tracks, or chapter markers, so any of these present in the source file will be silently dropped. HDR metadata (such as HDR10 or Dolby Vision tone mapping present in some HEVC files) is not preserved in this conversion — the output will be SDR H.264. For 4K or 8K HEVC source files, be aware that re-encoding at full resolution to H.264 is extremely CPU-intensive in a browser environment; for files over 1GB or high-resolution sources, using the displayed FFmpeg command on a desktop with hardware acceleration (e.g., -c:v h264_nvenc for NVIDIA GPUs) is strongly recommended.