Initializing... drag & drop files here
Supports: WTV
\Users\Public\Recorded TV\ folder (or wherever Media Center saved it). Batch upload of multiple recordings is supported.WTV is Microsoft's container for Windows Media Center TV recordings, introduced in 2008 alongside Windows 7 (it replaced the older DVR-MS format). Inside, the file is MPEG-2 video with MPEG-1 Layer II or Dolby Digital AC-3 audio, captured at up to 30 Mbps per Microsoft's SDK docs. Windows Media Center was discontinued in Windows 10 (2015), so unless you keep an old Windows 7 or 8.1 box running, those .wtv recordings sitting on a network drive are increasingly hard to play. WebM, designed by Google in 2010 with VP8/VP9 (and now AV1) video plus Vorbis or Opus audio, is the modern open-web answer.
<video> tag plays WebM natively, no Flash, no JW Player licence, no proprietary codec fee..wtv.A note on copy protection: per Microsoft's SDK, WTV files flagged with CGMS-A "broadcast" copy-protection from the station are encrypted to the recording PC and cannot be transcoded off that machine. Recordings of clear OTA broadcasts (most public TV, network primetime, sports) are unencrypted and convert fine.
| Property | WTV | WebM |
|---|---|---|
| Introduced | 2008 (Windows 7 / Media Center TV Pack) | 2010 (Google) |
| Container | Microsoft proprietary (SBE) | Matroska-derived, open spec |
| Typical video codec | MPEG-2 (also MPEG-4 / H.264 in some recordings) | VP8, VP9, AV1 |
| Typical audio codec | MPEG-1 Layer II or Dolby Digital AC-3 | Vorbis or Opus |
| Royalty-free | No (MPEG-2 + AC-3 patent pools) | Yes |
| Native browser playback | None | Chrome 25+, Firefox 28+, Edge 79+, Safari 16+ desktop / iOS 17.4+ |
| Subtitles / captions | Embedded EIA-608/708 if broadcast | WebVTT (external) |
| EPG metadata (show title, episode, channel) | Yes, baked in | No (lost on conversion) |
| Typical 1 hr HD size | 3-6 GB | 400 MB - 1.2 GB at "High" |
| Copy protection (CGMS-A) | Honoured / enforced | None |
The metadata loss matters for archivists: if you want to keep show titles and episode info, export them with a tool like MCEBuddy or VideoReDo first, then convert the stripped MPEG-2 here.
| Codec / preset | Encode speed | Size vs source | Best for |
|---|---|---|---|
| VP8 + Vorbis, "High" | Fast | ~25-35% of WTV | Maximum browser compatibility (anything from 2014 onward) |
| VP9 + Opus, "Very High" (default) | Medium | ~15-25% | The right choice for almost everyone — modern browsers, great quality/size |
| VP9 + Opus, "High" | Medium | ~10-18% | Embedding on websites where bandwidth matters |
| AV1 + Opus, "Very High" | Slow | ~10-15% | Long-term archival, future-proofing, or hosting at scale |
| VP9 with Specific File Size (e.g., 500 MB) | Medium | Hits your target | Discord (10 MB free / 50 MB Nitro), email caps, USB stick fits |
VP9 hits the sweet spot in 2026. AV1 gives another ~30% reduction at the cost of significantly slower encoding — worth it for an archive you'll keep for a decade, overkill for a one-off clip.
Windows Media Center was removed from Windows 10 in 2015 and never came back. The .wtv container relies on Media Center's Stream Buffer Engine (SBE) and the Windows Media Format runtime. Without Media Center, Windows can't decode the proprietary header even though the underlying MPEG-2 video is a well-known codec. Converting to WebM (or MP4 / MKV) re-muxes the video into an open container that plays natively in browsers and modern players like VLC and mpv.
Per Microsoft's Windows Media Center SDK, WTV recordings carry the broadcaster's CGMS-A copy-protection flag. If a station sets it to "Copy Never" or "Copy Once" (common for premium cable, occasional for OTA), the audio and video streams are encrypted to the original recording PC's hardware key. There's no legitimate way to decrypt that off the source machine. If the recording was made from clear OTA (most network, public, and local broadcast), it'll be unencrypted and convert fine.
WTV often contains a primary stereo AC-3 track plus a secondary audio program (SAP) and EIA-608/708 closed captions embedded in the MPEG-2 video. The conversion preserves the primary audio track as Opus or Vorbis. SAP tracks and embedded captions are usually dropped — WebM expects captions as external WebVTT files. If captions matter, run the WTV through a tool that exports them to .srt first.
For 95% of uses, VP9 (the default). VP8 only matters if you need to play on devices from 2012-2014 that never updated their browser — increasingly rare. AV1 produces files about 30% smaller than VP9 at the same quality but encoding takes roughly 3-5× longer. Pick AV1 only if you're archiving and don't mind the wait, or if you're hosting video at scale where bandwidth savings compound.
A 60-minute HD WTV at "Very High" / VP9 typically takes 8-20 minutes depending on server load. AV1 at the same settings runs 30-60 minutes. VP8 is the fastest at 5-12 minutes. Browser-based encoding scales with CPU; larger files benefit from leaving the tab open with the page focused.
Yes — use the Trim Time Range control. Set the start time after the opening bumper and the end time before the closing credits. For multiple commercial breaks in the middle, the cleanest workflow is to convert the full WTV once to MP4, then chop it with a frame-accurate editor like LosslessCut. Mid-roll splits require re-encoding around the cuts in any case.
Those live in WTV's proprietary metadata section, which doesn't have an equivalent in WebM. The conversion preserves the video and audio but drops the EPG (Electronic Program Guide) metadata. Filename is the only place that survives — name your output something like Nova-S52E04-PBS-2026-03-12.webm before downloading.
Set the Specific File Size to your target (e.g., 100 MB) — the encoder picks a bitrate that hits it. For a 60-minute show at 100 MB you'll need to drop to 480p or 360p; for a 10-minute clip 720p stays watchable. If you need to compress further after the fact, the dedicated WebM compressor gives you finer control over the bitrate ladder.
WebM is the better answer if your goal is web embedding, royalty-free distribution, or staying on the open-codec stack. MP4 (H.264 / H.265) is the better answer if you need playback on Apple TV, older smart TVs, hardware media players, or you'll edit the file in Final Cut / Premiere. For pure browser playback in 2026 the two are tied; for desktop / mobile app compatibility, MP4 still wins.