Initializing... drag & drop files here
Supports: DV
A .dv file is a raw DV stream — the intra-frame format MiniDV, DVCAM and Digital8 camcorders wrote to tape, standardised in IEC 61834 and SMPTE 314M. Every frame is coded independently at a constant 25 Mbit/s, with uncompressed 48 kHz PCM audio alongside it, which is why an hour of tape is about 13 GB whatever was in shot. A .ts is an MPEG transport stream: the packetised container broadcast, IPTV and streaming systems use, built to survive dropped packets and to be cut and concatenated at any point.
This guide covers the settings that matter when moving between those two worlds, and the three things about DV that catch people out — pixel aspect ratio, interlacing, and the enormous size difference.
.dv onto the page or click "Add Files". Captured tapes are large, so the upload is usually the slowest part of the job; several files can be queued and they share one set of settings..ts. Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.DV comes in two shapes and knowing which one you have explains most of what happens next.
| Property | 625/50 (PAL) DV | 525/60 (NTSC) DV |
|---|---|---|
| Frame size | 720 x 576 | 720 x 480 |
| Frame rate | 25 fps | 29.97 fps |
| Chroma sampling | 4:2:0 | 4:1:1 |
| Stored pixel aspect | 16:15 (4:3 material) | 8:9 (4:3 material) |
| Video bitrate | 25 Mbit/s, constant, every frame a keyframe | 25 Mbit/s, constant, every frame a keyframe |
| Audio | Uncompressed PCM, commonly 48 kHz 16-bit stereo | Uncompressed PCM, commonly 48 kHz 16-bit stereo |
Two consequences follow immediately. First, DV's chroma is already thin — 4:1:1 in particular keeps only a quarter of the horizontal colour resolution — so heavily saturated edges and red titles will not sharpen up no matter what codec you encode them into. Second, the 25 Mbit/s figure is the whole budget regardless of content, which is why re-encoding to a modern codec shrinks the file so drastically. In one measured run, a six-second 720 x 576 PAL DV capture of 21,600,000 bytes came back as a 1,015,388-byte transport stream at the default CRF of 23 with AAC audio — about a twenty-first of the size.
On pixel aspect ratio. DV frames are not square-pixel. A 4:3 PAL tape stores 720 x 576 pixels that are meant to be displayed at 16:15, and a 4:3 NTSC tape stores 720 x 480 pixels displayed at 8:9. Nothing in this pipeline performs pixel-aspect correction, so if the display geometry matters, do not resize by percentage or by preset — set Width x Height to the shape you actually want the picture to be. For 4:3 PAL that is 768 x 576; for 4:3 NTSC, 640 x 480; for a 16:9 widescreen tape, 1024 x 576 and 854 x 480 respectively.
On interlacing. Camcorder DV is normally interlaced, storing two time-offset fields per frame. There is no de-interlacing step here, so the combing stays baked into the output and will be visible on progressive displays during motion. If your footage needs de-interlacing, do it in an editor before uploading.
.dv directly, before uploading a whole capture..ts and .m2ts Are Not the Same FramingBoth carry an MPEG transport stream, but the packet layout differs, and our output extension decides which one you get.
.ts (this page) |
.m2ts |
|
|---|---|---|
| Packet size | 188 bytes | 192 bytes |
| First byte of the file | Sync byte 0x47 at offset 0 |
Four-byte arrival timestamp, then 0x47 at offset 4 |
| Origin | Broadcast and IPTV (MPEG-2 Systems) | Blu-ray / AVCHD BDAV framing |
| Typical consumers | DVB tooling, HLS segmenters, capture cards, OBS | Blu-ray players, AVCHD camcorder folders |
If a Blu-ray-oriented tool insists on the timestamped variant, use DV to MP4 or convert into an .m2ts target instead — renaming a .ts will not add the extra four bytes per packet that the BDAV layout expects.
No. Every conversion here re-encodes: the DV frames are decoded and a new stream is encoded in the codec you selected. That is not entirely a loss — DV at 25 Mbit/s is a very inefficient way to store standard-definition footage, and H.264 at CRF 20–23 typically keeps everything visible while shrinking the file by an order of magnitude. But it does mean one generation of quality, so archive the original DV capture if it is your master.
H.264 for nearly everything — it is what modern TS-consuming devices and streaming tools expect, and it handles interlaced standard-definition material well. MPEG-2 if you are feeding an older broadcast chain or a DVB device that predates H.264. H.265 gives smaller files but is less universally supported inside a .ts, and the older options (MPEG-1, MPEG-4, DivX, Xvid) are only worth choosing when something specific asks for them.
The slider runs 16 to 51 and opens at 23, where lower is better quality and a bigger file. For standard-definition tape footage, 20 to 23 keeps the material looking as good as the source; going below 18 mostly spends bits preserving DV's own compression noise. If size is your constraint, 26 to 28 stays watchable for review copies.
Generally no. Upscaling invents no detail and makes the file much larger, and if a system needs a specific frame size it will normally scale on playback anyway. The exception is when you must hit a fixed delivery resolution — in which case set Width x Height explicitly so the anamorphic pixel aspect is handled at the same time.
AAC for anything general-purpose; it is efficient and widely supported. AC3 when the destination is an AV receiver or a set-top device that expects Dolby Digital, and MP2 when you are feeding a traditional DVB broadcast chain, which was built around it. DV audio arrives as uncompressed PCM, so whichever you pick is a first-generation encode of clean source audio.
No. DV carries timecode and recording date-and-time in its subcode area, and a transport stream has no equivalent place to keep them, so both are dropped. If your workflow depends on tape timecode, capture into an editing application that reads DV subcode and export from there instead of converting the raw stream.
.ts file useful at all compared with MP4?Because a transport stream is self-synchronising and stateless: it can be cut at almost any packet boundary, joined end to end, and played from the middle without an index, which is exactly what broadcast, IPTV and HLS segmenting need. MP4 stores its index in a header and is happier as a single complete file. For general viewing and sharing, MP4 is the more convenient container.
.dv is actually inside an AVI or a QuickTime file. Will it work here?This page accepts the .dv extension, so a DV stream wrapped in an AVI or MOV container needs to go through the page for that container instead. The video data inside is the same DV essence either way; only the wrapper differs. Renaming an .avi to .dv is not reliable, because the AVI headers are still in the file.
Yes. Set Trim to Time Range and enter a Start time and a Duration; both accept plain seconds or HH:MM:SS.sss. On a DV capture this is worth doing at the source instead — Video Cutter takes .dv directly, and cutting before uploading saves you pushing gigabytes over the connection for a clip you only need a minute of.
They are uploaded over an encrypted connection, converted on our servers and deleted automatically after a few hours, along with the output. There is no sign-up, no watermark and nothing is shared or made public. Because DV runs about 13 GB per hour, upload time on your connection is the realistic limit on how long a capture you can put through this page in one go.