Initializing... drag & drop files here
Supports: WTV
.wtv recordings from your PC — typically found under \Users\Public\Recorded TV\. Batch upload is supported, so you can grab thumbnails from a whole season of recordings in one pass. Files process in your browser session — nothing is stored on a server.WTV (Windows Recorded TV Show) is the proprietary container Windows Media Center wrote when it recorded broadcast TV — MPEG-2 video with MPEG-1 Layer II or Dolby Digital AC-3 audio, often DRM-tagged. Windows Media Center shipped on Vista (with TV Pack 2008) and Windows 7, and Microsoft removed it from Windows 10 at launch on July 29, 2015. That leaves a lot of old .wtv archives that can't play on a modern PC out of the box, and the easiest way to surface a memorable moment from one is to pull a frame as a still. AVIF — the AV1 Image File Format, standardised by AOMedia in 2019 — is the right target: roughly 50% smaller than JPEG at matched quality, with 10/12-bit HDR support and 94%+ global browser coverage (Chrome 85+, Firefox 93+, Edge 121+, Safari 16.4+).
.wtv so you can browse a Plex/Jellyfin library visually without re-encoding multi-gigabyte MPEG-2 streams.Need the full video instead of a still? Use WTV to MP4. Prefer a universal still format? Try WTV to JPG. Already have AVIFs you want shrunk further? See Compress AVIF.
| Property | WTV (source) | AVIF (target) |
|---|---|---|
| Media type | Video container (MPEG-2 + MPEG-1 Layer II / AC-3) | Still image (AV1 keyframe in HEIF container) |
| Released | Vista TV Pack 2008 (2008) | AOMedia AV1 spec 2018; AVIF spec Feb 2019 |
| Royalty status | Proprietary Microsoft format; may carry DRM | Royalty-free under AOMedia patent policy |
| Compression vs source | Lossy MPEG-2 (broadcast bitrate, ~5-15 Mbps) | Lossy or lossless AV1 still; ~50% smaller than JPEG at matched quality |
| Color depth | 8-bit 4:2:0 (broadcast standard) | Up to 12-bit, supports HDR10 / PQ / HLG |
| Transparency | Not applicable (video) | Yes (alpha channel) |
| Native playback | Windows Media Center only (discontinued 2015) | Chrome 85+, Firefox 93+, Edge 121+, Safari 16.4+, iOS 16.4+ |
| Typical size | 3-8 GB per hour at SDTV bitrate | 30-150 KB per 1080p still |
| Best for | DVR archives, original broadcast playback | Web thumbnails, modern image archives, HDR stills |
Quality presets map to AV1 quantizer levels. Lower quantizer = bigger file, higher fidelity. Numbers below are typical for a 1280x720 still pulled from a 720p WTV.
| Preset | Approx. file size | Visible quality | When to choose |
|---|---|---|---|
| Highest (Lossless) | 400-900 KB | Pixel-identical to decoded frame | Archival masters, before further processing |
| Very High (Recommended) | 80-150 KB | Visually indistinguishable from source | Default — best size/quality balance for web and storage |
| High | 50-90 KB | Tiny artefacts in flat colour areas, no perceptible loss on detail | Image galleries, blog headers |
| Medium | 30-60 KB | Mild blocking visible on close inspection | Thumbnail strips, contact sheets |
| Low / Lowest | 10-30 KB | Visible artefacts; use only when size is critical | Email previews, low-bandwidth mobile lists |
No. WTV files recorded from CableCARD or other copy-protected sources carry DRM that locks playback to the original PC. We can decode the unencrypted MPEG-2 stream and pull frames, but DRM-tagged files will fail at upload — that protection is enforced at the file level, not by the player. Recordings from free over-the-air ATSC tuners are almost always unencrypted and convert without issue.
Three reasons. (1) Size — AVIF is roughly 50% smaller at visually matched quality, which matters when you're extracting thousands of thumbnails from a Recorded TV archive. (2) Colour depth — AVIF supports 10- and 12-bit, so HDR broadcasts preserve highlights that JPEG (8-bit) clips. (3) Browser-native — every major modern browser decodes AVIF directly, no JavaScript polyfill needed. The trade-off is encode time: AVIF encodes 5-10x slower than JPEG, but that's a one-time cost.
Use Keep original. SDTV WTVs from ATSC or analog cable are typically 720x480 (NTSC) or 720x576 (PAL). Upscaling to 1080p won't add detail — it just wastes bytes and can amplify MPEG-2 macroblocking. If you specifically need a higher pixel count for layout reasons, scale in a dedicated image editor where you can apply a sharpening pass, not at the conversion step.
Yes. Pick Specific Frame, then enter your timestamp in Time (seconds) — 90 for 1:30, 300 for 5:00, 3725 for 1:02:05. The converter seeks to the nearest keyframe and decodes forward to that exact frame. MPEG-2 GOP size on WTV is typically 12-15 frames, so seek accuracy is within ±0.5 s for older recordings and effectively frame-exact for newer modern-Recorded TV streams.
The control accepts a fixed interval (e.g., every 5 seconds, every 1 second) or a fixed frame count (e.g., 10 frames evenly spaced across the clip). For a 30-minute episode at 1-second intervals you'll get 1,800 AVIFs at ~80 KB each — about 140 MB total — which is easily handled in the browser without server upload. For longer recordings, raise the interval to keep memory pressure reasonable.
iOS Safari supports AVIF from version 16.4 (released March 2023) — partial support on 16.0-16.3, full from 16.4 onward. Chrome on Android has supported AVIF since Chrome 85 (August 2020). For phones running iOS 15 or older, or Android with WebView <85, fall back to WTV to JPG for guaranteed compatibility. AVIF coverage as of 2026 sits above 94% globally per caniuse.com.
No — AVIF is a still-image format, not a video container, so audio is dropped by definition. If you want to keep the audio track, convert the whole recording to MP4 instead via WTV to MP4, or pull the audio separately as MP3 or WAV using a video-to-audio tool.
That's almost certainly DRM. Microsoft's wtvconvert.exe (still shipping in system32 on Windows 7) could strip DRM on locally-recorded ATSC content by re-wrapping the file as DVR-MS, and that re-wrapped file would then upload cleanly here. CableCARD-protected recordings cannot be stripped — that's a hardware-level restriction.
A few possibilities. (1) You picked Highest (Lossless) instead of Very High — lossless AVIF is genuinely lossless and can run 5-10x larger than a perceptually-equivalent lossy AVIF. (2) The source frame has heavy MPEG-2 noise (broadcast or analog capture), which AV1 has to faithfully encode, inflating the file. Try the Medium preset to let AV1 smooth that noise out. (3) You're at 4K — extracting a 3840x2160 still will always be 4x bigger than 1080p, regardless of codec.
Files process in your browser session and are deleted when your session ends. No account is required, no email gating, no watermark, and no hidden Pro tier.