Initializing... drag & drop files here
Supports: WTV
.jfif baseline-JPEG file — no sign-up, no watermark, no DRM stripping (encrypted WTV recordings will refuse to decode; see the FAQ below).WTV (Windows Recorded TV Show) is Microsoft's DVR container, introduced with the Windows Media Center TV Pack 2008 for Vista and standard in Windows 7 Media Center. It wraps MPEG-2 (and sometimes MPEG-4) video with MPEG-1 Layer II or Dolby Digital AC-3 audio, plus broadcast metadata. Because Microsoft discontinued Windows Media Center starting with Windows 10 (May 2015 announcement), users with archived WTV recordings increasingly need a way to pull out individual frames for thumbnails, illustrations, or evidence — without installing legacy player software.
JFIF (JPEG File Interchange Format) is the baseline container for JPEG-compressed data — standardized as ITU-T T.871, ISO/IEC 10918-5, and ECMA TR-98. Files with a .jfif extension are byte-identical to .jpg in most pipelines, but Windows 10/11 sometimes saves images as .jfif by default after a 2018 Edge browser change, so receiving a .jfif directly avoids the rename step.
| Property | WTV (input) | JFIF (output) |
|---|---|---|
| Type | Video container | Still image |
| Compression | MPEG-2 / MPEG-4 video + MP2 or AC-3 audio | Baseline JPEG (lossy DCT) |
| Standard | Microsoft proprietary (closed) | ITU-T T.871 / ISO/IEC 10918-5 / ECMA TR-98 |
| Resolution | Broadcast: typically 1920x1080 (ATSC) or 720x480 (NTSC) | Inherits frame; any resize you choose |
| Audio | Yes — included in stream | No — image only |
| DRM | Yes — CGMS broadcast flag can lock files to the original Media Center PC | None |
| Default app | Windows Media Center (discontinued in Windows 10) | Any browser, Photos, Preview, IrfanView |
| Typical size | 4-8 GB / hour (HD) | 200 KB - 4 MB per frame at 1080p |
| Year introduced | 2008 (TV Pack for Vista), standard in Windows 7 | First published Sept 1992 (v1.02); standardized 2009-2013 |
| Setting | What it does | When to use |
|---|---|---|
| Specific Frame + Time (seconds) | Extracts one JFIF at the exact timestamp | Single thumbnail, evidence, cover art |
| Multiple Screenshots | Extracts frames at a fixed interval across the clip | Storyboards, OCR pipelines, scene index |
| Quality Preset: Highest / Very High | Lower JPEG compression (~92-95 quality) | Print, archival, upscaling |
| Quality Preset: High / Medium | Standard web JPEG (~75-85 quality) | Blog, Plex artwork, social |
| Quality Preset: Low / Lowest | Aggressive compression (~50-65) | Tiny indexes, OCR-only pipelines |
| Resolution Percentage | Scales relative to source | Keep aspect ratio while shrinking |
| Preset Resolutions | 2160p / 1440p / 1080p / 720p / 480p / 360p etc. | Match a target device or template |
| Specific file size | Hard cap in KB/MB; quality auto-adjusts | Email or upload limit (e.g., 1 MB max) |
WTV recordings made from cable or premium content often carry the CGMS-A broadcast flag, which Windows Media Center honored by tagging the file as DRM-protected and bound to the original recording PC. Free-to-air ATSC OTA broadcasts are usually unprotected and convert fine; CableCARD or premium subscription recordings will refuse to decode anywhere except the machine that made them. This isn't a converter limitation — it's enforced at the codec layer.
.jfif and .jpg?JFIF (JPEG File Interchange Format) is the wrapper that specifies how JPEG-compressed data is stored — color space (YCbCr), aspect ratio, density units, and thumbnail. Every "JPEG" you've ever seen is, technically, almost certainly a JFIF or Exif file. The bytes are interchangeable; only the extension differs. Windows 10/11 sometimes saves screenshots and browser downloads as .jfif due to a 2018 change in how Edge/Chrome registered the MIME type. If you need .jpg for a finicky tool, our JFIF to JPG page does the rename + re-encode.
PNG is lossless and far larger — a 1080p still at default settings is typically 1-3 MB as JFIF versus 4-10 MB as PNG. For broadcast video frames, which already lose detail to MPEG-2 motion compensation, the second lossy pass to JPEG is rarely visible, and you save 70-80% on storage. Pick PNG (/convert-wtv-to-png) only when you need a transparent background or pixel-perfect text capture, neither of which applies to over-the-air TV.
If you don't already know the second you want, the simplest workflow is to first convert the WTV to MP4 with WTV to MP4, scrub to find the moment in any video player, note the timecode, then come back to this page and enter it. The Time field accepts decimal seconds (e.g., 742.5), so half-second precision is supported.
Multiple Screenshots is built for fixed-interval sheets, not full-frame extraction. A typical 30-minute broadcast at 29.97 fps contains ~54,000 frames, which would be impractical to deliver as individual files in a browser session. For exhaustive frame extraction, transcode to MP4 first and run ffmpeg -i in.mp4 -qscale:v 2 frame_%06d.jpg locally — that's the right tool for that job.
Yes — the output is a still image. JFIF has no audio container. If you need to keep the audio alongside the still, run the conversion twice: once here for the frame, and once via WTV to MP4 for the playable clip. Or extract the audio separately with a WTV to MP3 / WAV path.
For HD WTV (1920x1080) recordings, leave Resolution Percentage at "Keep original" and pick the Highest Quality Preset. The result is typically 1.5-3 MB per frame and visually indistinguishable from the source MPEG-2 reference frame. For SD WTV (720x480, NTSC) or 720x576 (PAL), keep the source resolution — upscaling won't add detail, and any of the Preset Resolutions higher than the source just interpolates.
.jpg option here — only .jfif?The .jfif and .jpg files written here use the identical JFIF wrapper and baseline-JPEG payload; the only difference is the extension Windows and macOS register against. If your downstream tool insists on .jpg, either rename the file (no re-encode needed) or use our MP4 to JFIF and WTV to JPG variants — they share the encoder. There is no quality difference between the two extensions.
No. Broadcast metadata lives in the WTV container and the recording's .xml sidecar, not in the video stream itself. JFIF supports basic EXIF (capture date, color profile) but has no broadcast schema. If you need to retain the channel/title/air date, save the WTV's sidecar XML alongside the JFIF — or transcode to MP4 first, which can carry some of those tags in the metadata atoms.