Convert M2TS to DVR — Free Online Tool

Convert M2TS Blu-ray and AVCHD footage to DVR format using H.264 video and AAC audio, making high-definition disc recordings compatible with digital video recorder systems. This tool re-encodes the M2TS transport stream — which may contain multiple audio tracks and subtitles — into a streamlined DVR container optimized for playback and archival on recording hardware.

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

M2TS files use the BDAV MPEG-2 Transport Stream container, which wraps video (typically H.264 or MPEG-2), multiple audio tracks, and subtitle streams into a structure designed for Blu-ray and AVCHD playback. DVR format, by contrast, is a lean proprietary container designed for captured television and surveillance footage — it supports only a single audio track, no subtitles, and no chapter markers. During this conversion, FFmpeg re-encodes the video stream using libx264 (H.264) at CRF 23, which is a perceptually transparent quality level for most content. The audio is transcoded to AAC at 128k bitrate. If your M2TS source contains multiple audio tracks or subtitle streams, only the default (first) audio track is carried over and all subtitle data is dropped, as DVR does not support these features.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg binary, which is running entirely inside your browser via WebAssembly (FFmpeg.wasm) — no file data leaves your device during this conversion.
-i input.m2ts Specifies the input M2TS file — a BDAV MPEG-2 Transport Stream that may contain Blu-ray or AVCHD video, multiple audio tracks, and subtitle streams. FFmpeg reads and demuxes the transport stream container before processing.
-c:v libx264 Re-encodes the video stream using the libx264 H.264 encoder. Since DVR requires its own container structure, the M2TS video cannot be stream-copied and must be re-encoded; H.264 is the primary video codec supported by the DVR format.
-c:a aac Transcodes the audio to AAC, which is the default and most compatible audio codec for DVR output. Any lossless or high-bitrate audio from the M2TS source (such as DTS-HD or TrueHD) is decoded and re-encoded to a single AAC stream, as DVR supports only one audio track.
-crf 23 Sets the Constant Rate Factor for libx264 to 23, the default quality level that balances file size and perceptual quality for most HD content. Lower values (e.g., 18) produce higher-quality larger DVR files; higher values (e.g., 28–36) reduce file size at the cost of visible compression artifacts.
-b:a 128k Targets an AAC audio bitrate of 128 kilobits per second in the DVR output. This is a reasonable quality level for speech and general television audio, though users converting high-fidelity Blu-ray audio may prefer to raise this to 256k or 320k.
output.dvr Defines the output filename and instructs FFmpeg to write the result in DVR container format. Subtitle streams and secondary audio tracks from the M2TS source are automatically dropped here because the DVR format does not support them.

Common Use Cases

  • Archiving Blu-ray rips or AVCHD camcorder recordings onto a DVR system for playback through a set-top box or home recording appliance
  • Transferring high-definition home video captured with an AVCHD camcorder into a surveillance or security DVR system for long-term storage
  • Converting broadcast-captured M2TS recordings from a TV tuner into a DVR-compatible format for playback on older or proprietary recording hardware
  • Reducing Blu-ray M2TS file complexity — stripping multiple audio tracks and subtitle streams — for ingestion into DVR workflows that cannot parse transport stream metadata
  • Preparing M2TS footage from a professional AVCHD field recorder for archive on a DVR-based media server used in broadcast capture environments
  • Batch-converting a library of M2TS recordings from a Blu-ray disc ripper into DVR files for cataloguing on a standalone digital video recorder

Frequently Asked Questions

Yes. The DVR format does not support subtitles or multiple audio tracks, so FFmpeg will automatically discard all subtitle streams and retain only the first (default) audio track from the M2TS file. If your M2TS contains a DTS-HD or Dolby TrueHD audio track, that will also be transcoded down to a single AAC stereo stream at 128k. You should select the correct default audio language in your M2TS source before converting if language matters.
If your M2TS source is already encoded in H.264 (which is common for AVCHD recordings), the re-encode to libx264 at CRF 23 introduces a generation loss since the video must be decoded and re-encoded rather than copied. CRF 23 is generally considered visually transparent for standard-motion content, but for high-motion Blu-ray footage or fine-grained film grain, you may want to lower the CRF value to 18 to preserve more detail. The audio transcoding from lossless or high-bitrate formats to AAC 128k is also lossy, though it is acceptable for most playback scenarios.
Stream copying (using -c:v copy) would preserve the original video quality with no generation loss, but it only works reliably when both containers support the same codec and the container framing is compatible. DVR is a proprietary format with specific structural requirements, and the MPEG-2 Transport Stream packetization used in M2TS must be unwrapped and repackaged. In practice, re-encoding with libx264 at a high-quality CRF setting is the safer and more compatible approach when targeting DVR output.
The CRF value controls video quality — lower numbers mean higher quality and larger file sizes. You can replace -crf 23 in the command with values between 0 (lossless) and 51 (lowest quality). For high-definition M2TS Blu-ray content where you want to preserve detail, try -crf 18. For smaller DVR archive files where storage is limited, -crf 28 or -crf 36 are reasonable tradeoffs. The DVR format only supports lossy encoding, so CRF 0 will still produce a large H.264 file rather than truly lossless output.
Yes. On Linux or macOS, you can wrap the command in a shell loop: for f in *.m2ts; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.m2ts}.dvr"; done. On Windows Command Prompt, use: for %f in (*.m2ts) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.dvr". This is especially useful for processing files over 1GB, which exceeds the browser tool's capacity.
Chapter markers and Blu-ray-specific metadata (such as disc index information, CLPI clip info, and navigation data) are not carried over to DVR output. The DVR format does not support chapters, and FFmpeg does not attempt to map transport stream navigation metadata into proprietary DVR container fields. If preserving chapter structure is important, consider an intermediate format like MKV, which supports chapters, before any DVR-specific workflow.

Technical Notes

M2TS files originating from Blu-ray discs frequently carry MPEG-2 or AVC (H.264) video alongside lossless or high-bitrate audio formats such as DTS-HD Master Audio, Dolby TrueHD, or LPCM — none of which are supported by the DVR container. The conversion to AAC at 128k represents a significant downgrade from these lossless sources, so users archiving high-fidelity audio should consider increasing the -b:a value to 256k or 320k. The libx264 encoder at CRF 23 produces variable bitrate output, meaning short high-definition clips will result in relatively smaller DVR files while complex Blu-ray feature films can still produce large outputs. The DVR format's single-audio-track limitation means multi-language Blu-ray titles will lose all secondary language tracks silently during conversion — FFmpeg selects the first detected audio stream by default. Additionally, AVCHD-sourced M2TS files from consumer camcorders often contain interlaced video; FFmpeg does not automatically deinterlace, so you may wish to add -vf yadif to the command for cleaner progressive output on DVR playback devices that do not handle interlaced content well.

Related Tools