WTV to BMP Converter

How to Convert WTV to BMP Online

1. Upload Your WTV File: Drag and drop or click "+ Add Files" to load a .wtv recording from Windows Media Center. Batch upload is supported, and files stay on your device — they are sent to a temporary processing session, not stored long-term.
2. Pick Frame Selection (Specific Frame or Multiple Screenshots): Choose "Specific Frame" and enter a timestamp under "Time (seconds)" to extract one still, or pick "Multiple Screenshots" to grab a sequence across the recording. WTV files are timecoded from 0, so set the offset relative to the start of the recording.
3. Set Image Resolution and Quality Preset (Optional): Keep the source resolution (typically 720x480, 720x576, or 1280x720 / 1920x1080 for HD broadcasts), pick a Preset Resolution, set a Resolution Percentage, or type custom Width and Height in pixels. Use the Quality preset dropdown ("High" is the default) if you want to bias toward smaller files; uncompressed 24-bit BMP output ignores most "quality" knobs and writes pixels verbatim.
4. Convert and Download: Click "Convert". Each captured frame becomes one .bmp file you can download individually or as a ZIP if you grabbed multiple screenshots.

Why Convert WTV to BMP?

WTV (Windows Recorded TV Show) is the proprietary container Microsoft introduced with the Vista Media Center TV Pack in 2008 and shipped in Windows 7 Media Center and the Windows 8 / 8.1 Media Center Pack. It typically wraps MPEG-2 video with MPEG-1 Layer II or Dolby Digital AC-3 audio, plus electronic program guide metadata and optional DRM flags. Microsoft discontinued Windows Media Center when Windows 10 launched in July 2015, and the upgrade installer removed it entirely — which is why most people only see .wtv files today on archived drives or external backups. BMP is Microsoft's native Device-Independent Bitmap format, in continuous use since the late-1980s Windows releases. Standard 24-bit BMPs store pixels uncompressed, so a single 1920x1080 still lands around 6.2 MB — large, but trivially decodable by anything that understands a BITMAPINFOHEADER, including 30-year-old applications, embedded toolchains, and scientific imaging pipelines that distrust DCT and entropy coding.

• Pull stills out of legacy DVR archives — Many households still have external drives full of .wtv recordings from a Windows 7 HTPC. Extracting a single frame as BMP is the simplest way to grab a usable thumbnail without re-encoding the whole broadcast.
• Frame-accurate evidence for forensic or compliance review — Uncompressed BMP preserves every original pixel of a decoded MPEG-2 frame with no second-stage JPEG quantization, which matters for FOIA-style media archives and broadcast monitoring.
• Feed legacy Windows software and embedded displays — Industrial HMIs, point-of-sale terminals, and CNC controllers built on Windows CE / Embedded often only accept BMP for splash screens and image assets. A still from a training recording in WTV converts cleanly into the format those panels expect.
• Scientific and machine-vision workflows — OpenCV's cv::imread and MATLAB's imread both treat 24-bit BMP as the canonical lossless RGB input. If you're frame-grabbing a recorded broadcast for image-analysis testing, BMP avoids any debate about JPEG artifacts confounding the experiment.
• Reverse-engineer or hand-edit broadcast graphics — On-screen channel bugs, scoreboards, and lower-thirds in MPEG-2 broadcasts often have crisp edges. A BMP frame extract keeps those edges pixel-exact for retouching in Photoshop or Paint.NET before re-export to PNG.

WTV vs BMP — Format Comparison

Frame Resolution Quick Guide

Tip: if you only need a preview thumbnail, set Resolution Percentage to 25-50% before extracting — a 480x270 BMP is around 390 KB and renders instantly in older viewers.

Frequently Asked Questions

Can the converter read DRM-protected WTV recordings?

No. Cable and satellite tuners that flagged content with the "Copy Once" or "Copy Never" Broadcast Flag wrote encrypted WTV files that only the originating Media Center install can decrypt. The converter handles plain (over-the-air ATSC/DVB) .wtv captures, which is what the vast majority of personal Media Center archives contain. If your .wtv is DRM-protected, no online tool — including ours — can extract its frames legally or technically.

Why is my output BMP so much larger than the WTV file?

Because BMP is essentially raw RGB. A one-hour HD WTV recording at 8 Mbps is around 3.6 GB, but a single 1920x1080 24-bit BMP frame is 6.2 MB on its own — and 30 fps of BMPs would be 186 MB per second. WTV is lossy MPEG-2; BMP is uncompressed. That trade-off is the whole reason to use BMP only for stills, not sequences. If you need a folder full of frames, consider PNG (WTV to PNG) instead — same lossless quality, roughly 30-60% the file size.

Should I pick BMP or JPEG/PNG for extracted frames?

Pick BMP only if a downstream tool requires it (legacy Windows software, embedded display firmware, certain OpenCV/MATLAB workflows) or if you want absolutely no DCT artifacts compounded on top of the MPEG-2 decoding artifacts. For sharing, archiving, or web use, PNG is lossless and much smaller, and JPEG is fine for casual previews. BMP is the right call when downstream tooling can't be changed.

What timestamp format does "Time (seconds)" expect?

Plain seconds from the start of the recording. Enter 15 to grab the frame at 15.0s, or 90.5 for one and a half minutes plus a half second. If your recording starts with a few seconds of black or a channel-change leader, you may need to add a small offset — Media Center sometimes pads the first one or two seconds of a .wtv file before the real broadcast begins.

What about the broadcast metadata, channel name, and program guide info?

That data lives in the WTV container's metadata streams, not in any image. When you extract a frame to BMP you get pixels only — no channel logo overlay (unless it was burned into the video), no EPG title, no recording timestamp. If you need that metadata, open the original WTV in MediaInfo before discarding it; the EPG fields are preserved in the container.

Will I get the full recording as BMPs, or just selected frames?

By default the tool extracts the specific frame(s) you ask for via "Specific Frame" or "Multiple Screenshots" — not every frame in the recording. Exporting every frame of a 30-minute HD show would mean ~54,000 BMPs totaling roughly 335 GB, which no browser session can handle. For a full-conversion workflow, convert to a video format first (WTV to MP4) and extract frames separately.

Does the BMP keep the broadcast's 4:3 or 16:9 aspect ratio?

The extractor decodes WTV's anamorphic SD frames into square-pixel BMPs by default, so 720x480 NTSC content with a 16:9 flag is rescaled to 854x480 (or whatever you set) so the BMP looks correct in modern viewers. If you need the raw 720x480 grid for archival reasons, set Width and Height explicitly to 720x480 and the tool will skip the anamorphic correction.

Can I use 1-bit, 8-bit (palettized), or 32-bit BMP output?

The default is 24-bit RGB BMP, which matches what nearly every modern tool expects. The interface exposes Image Bit Depth and Image Color Palette controls if you need 8-bit indexed (for very old Windows software or specific embedded targets) or 1-bit (black-and-white) output. 32-bit BMP with alpha is supported, but extracted video frames have no alpha channel, so the alpha byte will be set to 0xFF (fully opaque).

How big a WTV file can I upload?

Single HD broadcast recordings (typically 30-120 minutes, 3-15 GB) work fine through the browser. Multi-hour DVR archives at the upper end of typical capture sizes may hit browser memory limits before the upload completes — if you're trimming a long recording first, run Trim WTV on the source to grab just the segment you need, then extract frames from the trimmed file.