Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
WTV is Microsoft's Windows Recorded TV Show container — the file a Windows Media Center PC wrote when it recorded from a TV tuner. It replaced the earlier DVR-MS format used by Windows XP Media Center Edition, arrived with the Windows Media Center TV Pack 2008 on Vista, and shipped in every Media Center edition of Windows 7. Microsoft then dropped Media Center from Windows 10 entirely, which is why almost nobody produces new WTV files today.
That makes this a deliberately narrow conversion: it exists for people who need a still image to appear inside a Media Center-era library, a home-theatre PC playlist, or an archive of recordings that is indexed by container type. If you just want a video of a photograph, almost any other target is a better fit — and the reason why is measurable.
| Property | Value |
|---|---|
| Full name | Windows Recorded TV Show |
| Vendor | Microsoft — proprietary, no published open specification |
| Predecessor | DVR-MS, used by Windows XP Media Center Edition |
| Introduced | Windows Media Center TV Pack 2008 (Vista); standard in Windows 7 Media Center |
| Discontinued with | Windows Media Center, dropped from Windows 10 |
| File structure | Sector-based structured storage keyed by GUIDs, not a simple stream |
| Video codec written here | H.264 |
| Audio | None on this page — a still image has no soundtrack |
| Reads in | VLC, mpv, ffmpeg-based tools, Windows 7 Media Center |
| Does not read in | Browsers, phones, smart TVs, most editing software |
WTV is not a lightweight wrapper. Its structured-storage layout allocates space in 4096-byte sectors and writes a substantial fixed set of tables and GUID-keyed records whether the recording is two hours or two frames long. We measured this directly by encoding the same 1000 × 750 photograph three times, changing only the length, and writing each one as both WTV and F4V from an identical H.264 encode.
| Clip length | WTV output | Same encode as F4V |
|---|---|---|
| 1 second | 36 864 bytes | 4 742 bytes |
| 5 seconds | 36 864 bytes | 5 998 bytes |
| 10 seconds | 36 864 bytes | 6 755 bytes |
The WTV number does not move at all — 36 864 bytes is exactly nine 4096-byte sectors, and the picture data disappears inside that allocation. For a two-hour TV recording, which is what the format was designed for, this overhead is irrelevant. For a five-second still it is roughly six times the size of the video it contains. That is not a defect, just a mismatch between what the format was built for and what you are asking it to do.
.jpg and .jpeg — the same JPEG bitstream under different names — and Merge strategy decides whether several uploads become one clip or one clip each..wtv. No sign-up, no watermark.Because there is nothing meaningful to choose between. Every codec entry is suppressed for this target and the converter writes H.264, which is what a Media Center-era WTV consumer expects and what the container's writer handles reliably. On targets like MOV or MKV, where the container genuinely is codec-agnostic, the dropdown offers you a real decision; here it would only offer combinations that nothing asking for a WTV could play.
Not by double-clicking. Media Center was removed from Windows 10, and the Movies & TV and Media Player apps that replaced it do not register .wtv. Windows 10 did retain some underlying compatibility for existing WTV files, but in practice the reliable way to play one on a modern Windows machine is VLC or mpv, both of which read the container without any extra components. If the file needs to open on an arbitrary Windows PC, this is the wrong format.
No, and there are no audio controls on this page for that reason. A JFIF is a photograph — it carries no soundtrack — so the output is a video-only WTV. If you need audio, build the clip in a video editor, or produce the silent file here and add a track afterwards.
.jfif extension change anything about the conversion?One thing. JFIF is simply the standard JPEG header convention under a different extension, so the pixels are identical to a .jpg file — but the step that reads a photograph's EXIF orientation flag and rotates the pixels accordingly is keyed on extensions containing "jp", which .jfif does not match. A portrait phone photo saved as .jfif may therefore come out on its side, where the identical bytes named .jpg would come out upright. Since this page accepts .jpg as well, renaming before upload is the whole fix. Images without an orientation tag — screenshots, web downloads, scans — behave identically either way.
Because Image Duration defaults to 5 seconds. That dropdown is the length control and it caps at 10 seconds per image; quality and resolution settings have no bearing on duration. For a longer clip, upload the same file several times with Merge strategy set to Merge images — each copy is held for the chosen duration and they are concatenated — or extend it in an editor afterwards.
One frame per second. Every frame of a still-image clip is identical, so writing 25 or 30 of them a second costs encoding time and file size with nothing visible to show for it. A 5-second Image Duration therefore writes exactly 5 frames, which we confirmed by counting them in a converted file. Note that WTV's timestamp handling is coarse enough that a player may report the duration as a second longer than you asked for; the frame count is exact even when the reported duration rounds.
Because no video codec can store an alpha channel. Any transparent region is composited onto the Background Color before encoding, and that control defaults to White. A genuine JPEG has no transparency at all, so this only arises if you have renamed a PNG or WebP to .jfif. Change Background Color in Advanced Options if you want a different fill.
No. WTV's metadata model is built around broadcast information — channel, programme title, recording time, guide data — and has no place for camera EXIF. Model, exposure, GPS coordinates, capture date and any embedded colour profile are all dropped; only pixels reach the video. Keep the original JFIF if that information matters.
Almost certainly. JFIF to MP4 gives you the same H.264 picture in the container that plays on phones, browsers, TVs and editing software alike, with a fraction of the container overhead — our 5-second test was about 6 KB as an ISO-based file against 36 KB as WTV. Choose WTV only when something specifically requires it. If you need Windows-native rather than universal, the WMV family is a closer fit than WTV for anything that is not a TV recording.
It is uploaded over an encrypted connection, converted on our servers, and both the upload and the .wtv output are deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. The photograph on your own device is untouched. Still-image WTV files are small in absolute terms — well under a megabyte — so neither upload nor download time is a practical constraint.