MyMediaTools

Convert DVR to M2TS — Free Online Tool

Convert DVR recordings — proprietary digital video recorder files used for captured TV and surveillance footage — into M2TS, the Blu-ray BDAV MPEG-2 Transport Stream format. The video is re-encoded using H.264 (libx264) and audio is transcoded to AAC, producing a broadcast-grade M2TS file compatible with Blu-ray authoring tools, AVCHD workflows, and HD media players.

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 use a proprietary container storing H.264 or MJPEG video alongside AAC or MP3 audio, captured directly from television tuners or surveillance systems. Because DVR is not a standardized container, FFmpeg demuxes the raw streams and fully re-encodes both video and audio into the M2TS (BDAV MPEG-2 Transport Stream) format. The video is encoded using libx264 with a CRF of 23, which balances visual quality and file size. The audio is transcoded to AAC at 128k bitrate, as M2TS requires standardized codec streams for compatibility with Blu-ray players and AVCHD-aware software. The result is a structured, standards-compliant transport stream that carries timing and sync metadata suitable for professional broadcast and disc authoring pipelines.

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 its video and audio streams, re-encoding them, and muxing the output into a standards-compliant M2TS transport stream.
-i input.dvr Specifies the input DVR file. FFmpeg will probe the file to detect its internal codec structure — typically H.264 or MJPEG video with AAC or MP3 audio — before beginning the conversion pipeline.
-c:v libx264 Sets the video encoder to libx264, the industry-standard H.264 encoder. Since DVR containers often have non-standard stream packaging, this ensures the video is fully re-encoded into a clean, transport-stream-compatible H.264 bitstream suitable for M2TS.
-c:a aac Transcodes the audio to AAC using FFmpeg's native AAC encoder. AAC is the default and most compatible audio codec for M2TS files, ensuring playback on Blu-ray players, AVCHD-compatible software, and broadcast systems regardless of what audio codec the source DVR file used.
-crf 23 Sets the Constant Rate Factor for the libx264 encoder to 23, which is the default and represents a balanced trade-off between visual quality and file size. For DVR footage — whether TV recordings or surveillance clips — this setting produces visually acceptable quality without unnecessarily large output files.
-b:a 128k Sets the AAC audio bitrate to 128 kilobits per second. This is appropriate for the typically mono or simple stereo audio found in DVR recordings from television tuners and security cameras, where voice intelligibility and ambient audio are the primary content.
output.m2ts Defines the output filename with the .m2ts extension, which signals to FFmpeg to mux the encoded streams into the BDAV MPEG-2 Transport Stream format — the standard container used for Blu-ray disc video, AVCHD camcorders, and HD broadcast workflows.

Common Use Cases

  • Archive recorded television broadcasts from a DVR box into M2TS format for long-term storage and playback on Blu-ray-compatible media players
  • Convert surveillance or security camera DVR footage into M2TS for ingestion into professional video editing software that uses AVCHD or Blu-ray transport stream workflows
  • Prepare DVR-captured content for Blu-ray disc authoring by converting it to the native M2TS container used by Blu-ray Video (BDAV) structures
  • Transcode proprietary DVR recordings to M2TS so they can be played back on smart TVs, AV receivers, or NAS-connected players that support AVCHD but not DVR containers
  • Convert DVR footage to M2TS to take advantage of M2TS subtitle track support when adding burned-in or embedded captions for broadcast compliance
  • Re-encode low-quality MJPEG-based DVR surveillance clips into H.264-encoded M2TS files to significantly reduce file size while maintaining acceptable HD quality

Frequently Asked Questions

Yes, some quality loss is inevitable because the video is fully re-encoded from the DVR source into H.264 using a CRF of 23. If the original DVR file used MJPEG, the quality difference may be noticeable, as MJPEG stores each frame independently whereas H.264 uses inter-frame compression. If the source was already H.264, re-encoding introduces an additional generation of lossy compression. To minimize quality loss, you can lower the CRF value (e.g., to 18) in the FFmpeg command, which trades a larger file size for better fidelity.
DVR is a proprietary container format with non-standard stream packaging and timing metadata. Even when the underlying video codec (e.g., H.264) is technically compatible with M2TS, the stream headers, PTS/DTS timestamps, and container-level signaling from a DVR file are often malformed or incompatible with the strict BDAV transport stream specification. Re-encoding ensures the output is a properly structured MPEG-2 Transport Stream that M2TS-compliant players and authoring tools can reliably parse.
M2TS natively supports multiple audio tracks and subtitle streams, but DVR files typically do not. The DVR format is generally limited to a single audio track and has no subtitle or chapter support. As a result, this conversion will produce an M2TS file with one video and one audio stream. If your DVR source somehow contains additional audio data, FFmpeg would need explicit stream mapping flags to include them — the default command maps only the primary streams.
The CRF (Constant Rate Factor) value in the command controls video quality and file size. Lower CRF values produce higher quality and larger files, while higher values produce smaller files with more compression. For archiving TV recordings where quality matters, try '-crf 18'. For surveillance footage where storage is a priority and fine detail is less critical, '-crf 28' or '-crf 36' can significantly reduce file size. The valid range for libx264 is 0 (lossless) to 51 (worst quality).
Yes. On Linux or macOS, you can use a shell loop: 'for f in *.dvr; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.dvr}.m2ts"; done'. On Windows Command Prompt, use: 'for %f in (*.dvr) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.m2ts"'. This is especially useful for processing large batches of surveillance recordings or archived TV captures that exceed the browser tool's 1GB per-file limit.
DVR containers often embed proprietary metadata — such as recording date, channel name, or device identifier — that FFmpeg cannot interpret or carry forward into a standardized M2TS container. Standard M2TS metadata fields (such as title or creation time) may be written if FFmpeg can extract equivalent values from the source, but proprietary DVR metadata will be lost. If preserving recording timestamps is important, note them manually before conversion or use FFmpeg's '-metadata' flag to write them explicitly into the M2TS output.

Technical Notes

DVR is not a single unified format — it is a catch-all extension used by many different DVR manufacturers, each implementing their own container structure around common codecs like H.264 or MJPEG for video and AAC or MP3 for audio. This proprietary variation means stream copy is rarely viable, and full re-encoding is the safest path to a standards-compliant output. M2TS (BDAV MPEG-2 Transport Stream) is a well-specified format originally designed for Blu-ray Disc and AVCHD, and it expects clean, properly timestamped transport streams. The libx264 encoder at CRF 23 is appropriate for the broadcast-quality expectations of M2TS, but users working with high-motion surveillance footage or interlaced TV captures should consider adding '-vf yadif' to the command to deinterlace before encoding, as interlaced content from DVR tuners can cause artifacts when compressed with progressive H.264. The AAC audio at 128k is sufficient for mono or stereo speech-heavy DVR content, though stereo music or broadcast audio may benefit from 192k. M2TS supports FLAC and Opus audio natively, so power users can substitute '-c:a flac' for lossless audio archiving if storage is not a constraint. File sizes will vary significantly depending on DVR source quality, with MJPEG-originating files typically shrinking considerably due to H.264's superior compression efficiency.

Related Tools

Convert DVR to RM Convert DVR to VOC Convert DVR to SWF Convert MPG to M2TS Convert RMVB to M2TS Convert HEVC to M2TS Compress DVR Extract Audio DVR to MP3