Initializing... drag & drop files here
Supports: DVR
A .dvr file is a recording from a digital video recorder — most often a .dvr-ms file created by Windows Media Center (MPEG-2 video with MP2 or Dolby Digital AC-3 audio), though the same extension is also used by some set-top boxes and surveillance / CCTV systems. MTS is the camcorder-side extension of AVCHD, the HD recording format Sony and Panasonic introduced in 2006: H.264 video and AC-3 audio multiplexed into an MPEG transport stream. This guide covers when converting to MTS actually makes sense (it is a narrow case), how to set the codec and resolution, and what to do when a DVR file refuses to convert. Before you start, the honest steer: most people who land here want a normally playable video, and for that DVR to MP4 is the better target — MTS is worth choosing only for a specific AVCHD editing workflow described below.
.dvr (or .dvr-ms) recording onto the page or click "+ Add Files". You can queue several recordings and they convert with the same settings. Only files a normal media player can open are reliably decodable — copy-protected DVR-MS recordings and proprietary CCTV dumps may not be (see "Common Errors")..mts file individually or as a ZIP. No sign-up, no watermark.MTS is a niche conversion target. The mainstream reason to produce one is an AVCHD editing workflow: some non-linear editors (and a few older camcorder-companion tools) ingest AVCHD-style .mts files cleanly, so wrapping a recording as MTS can slot it into that pipeline. If you do not have that specific need, a .mts file is simply a less compatible container than MP4 holding the same H.264 video — .mp4 plays in browsers, on phones, and in nearly every editor, while .mts does not.
If MTS is genuinely what you need, match the settings to AVCHD's expectations:
A note on quality you cannot get back: a DVR-MS recording carries MPEG-2 video, and converting it to H.264 is a lossy-to-lossy transcode. The new file is re-encoded from already-compressed video, so it cannot recover detail the MPEG-2 encoder discarded — at best it matches the source; pushing the bitrate far above what the original held only grows the file.
The MTS container on this page is an MPEG transport stream, and the Advanced Options only offer codecs that stream can legally carry. Here is what you can actually pick and what each choice means:
| Control | Default here | Other choices offered | What to know |
|---|---|---|---|
| Video Codec | H.264 | DivX, H.265, MPEG-1, MPEG-2, MPEG-4, Xvid | AVCHD is defined around H.264 — anything else produces a transport stream that is technically valid but not AVCHD, and editors expecting .mts may reject it |
| Audio Codec | AAC | AC3, DTS (DCA), EAC3, MP2, MP3 | Real AVCHD uses Dolby Digital (AC-3); AAC rides fine in a transport stream and is the shipped default, so switch to AC3 only if a downstream tool insists |
| Container | MPEG transport stream | (fixed) | .mts is the transport stream — there is no alternate wrapper to choose |
| Rate control | Quality Preset (Very High) | Constant Bitrate, Variable Bitrate, Specific file size | For a container change, an explicit bitrate or target size is more predictable than a percentage |
| Resolution | Keep original | Preset Resolutions (height-only), Width × Height, Resolution Percentage | Standard-definition DVR footage gains nothing from a 1080p setting |
| Property | MTS (AVCHD) | MP4 | MKV |
|---|---|---|---|
| Container base | MPEG-2 transport stream | ISO base media format | Matroska |
| Usual video codec | H.264 | H.264 | H.264 (any codec allowed) |
| Usual audio codec | AC-3 (AAC here) | AAC | AAC, AC-3, FLAC, Opus |
| Plays in a browser | No | Yes | No |
| Plays on phones | Rarely | Yes | Rarely without an app |
| Editor / NLE ingest | Good, in AVCHD-aware tools | Universal | Good in desktop editors |
| Subtitles and chapters | Not typical | Limited | Soft subtitles, chapters, attachments |
| Streams while incomplete | Yes — transport streams are designed for it | No | No |
| Best for | Feeding an AVCHD workflow | Playing and sharing anywhere | Archiving to a media server |
If your .dvr came from a security camera or surveillance DVR, two cautions apply. First, many of these systems write a proprietary, sometimes encrypted container that only the manufacturer's own player or export tool can read — a general-purpose converter cannot open it directly. If the file will not load here, export a standard file from the device's own software first, then convert that. Second, treat any converted .mts as a working copy, not a legal record. A general-purpose converter produces a playable video; it does not establish chain of custody. For evidence use, export the original recording through the DVR vendor's own software, preserve that original untouched, and document how any working copy was produced.
.dvr extension is shared by unrelated systems. A Windows Media Center .dvr-ms recording is the well-supported case; a proprietary file from a CCTV or satellite DVR may use a vendor-specific, sometimes headerless container that standard tools can't read. Export a standard file from the device's own software first..dvr-ms files are encrypted and play back only on the PC that recorded them, so they can't be converted elsewhere. Export an unprotected copy from the source PC..mts is a camcorder/editing container with thin consumer-device support. Convert to DVR to MP4 instead for a file that plays nearly everywhere.The honest limit is the source file, not the converter. A simple rule decides it: if a normal media player such as VLC can open the recording, it can be transcoded here; if VLC can't open it, neither can this tool. The two cases that genuinely fail are broadcaster-flagged copy-protected DVR-MS recordings (encrypted by design) and encrypted or headerless surveillance / satellite dumps that only the manufacturer's player reads — in both cases, export to a standard file from the device's own software first. And if you only want the soundtrack rather than the video, use DVR to MP3 instead.
For most people, MP4. MTS (AVCHD) is a camcorder and editing container with limited consumer-device playback, while MP4 holds the same H.264 video and plays in browsers, on phones, and in nearly every editor. Choose MTS only when a specific AVCHD editing workflow expects .mts input; otherwise DVR to MP4 is the more compatible result.
No — and that is a fact of the formats, not a tool limitation. A DVR-MS recording carries MPEG-2 video, and converting to the H.264 video MTS uses is a lossy-to-lossy transcode: the output is re-encoded from already-compressed video and cannot regain detail the original codec discarded. Standard-definition TV recordings also stay standard-definition; forcing a 1080p resolution stretches the frame without adding real detail.
Keep the Video Codec on H.264, which is the codec AVCHD is built around and the one editors expect. For audio, real AVCHD uses Dolby Digital, so switch the Audio Codec to AC3 if a downstream tool requires classic AVCHD audio; the AAC default also works inside the transport stream. AVCHD's container is an MPEG transport stream, which is exactly what an .mts file is.
Many security DVRs save a proprietary, sometimes encrypted container that only the manufacturer's own player or export utility can read, so a general-purpose converter can't open it directly. The fix is to export a standard file (often MP4 or AVI) from the camera system's own software first, then convert that file here. As a quick test, try opening the original in VLC — if VLC can't play it, this tool can't either.
Treat it as a working copy, not a legal record. A general-purpose converter produces a playable video; it does not establish chain of custody. For evidence work, export the original recording through the DVR vendor's own software, preserve that original untouched, and document how any working copy was made — then a converted clip is something you produced from a preserved source rather than the record itself.
No — this conversion always re-encodes, and on this pairing it has to. A Windows Media Center .dvr-ms is an ASF-derived container holding MPEG-2 video, while .mts is an MPEG transport stream expecting H.264, so both the wrapper and the video codec change. There is no stream-copy path on this page in any case: every conversion decodes the source and encodes fresh output. Keeping the Quality Preset at Very High is what keeps that single generation of loss hard to see.
Very little at the format level — both are MPEG-2 transport streams carrying H.264. The split is a naming convention: AVCHD camcorders write .mts files into the AVCHD/BDMV/STREAM folder on the memory card, while .m2ts is the extension used on Blu-ray discs and by a lot of import software when those clips are copied onto a computer. If a tool wants one and you have the other, the underlying stream is usually identical.
Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion finishes. There is no sign-up, no watermark, and your files are never shared or made public. On a large recording, the practical limit is upload time, not a per-file size cap.