Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
A .jfif file is a plain JPEG — JFIF is the 1991 JPEG File Interchange Format, and Windows simply hands out that extension for some pasted and downloaded pictures. WMV is a Microsoft video format: Windows Media Video frames inside an ASF container. Turning one into the other is an encode, not a rename, so a handful of settings decide what you actually get.
This tutorial is for anyone feeding a still image into a Windows-native workflow — an old PowerPoint deck, a digital-signage player, a Windows Movie Maker or legacy NLE project, or a piece of kit that only ingests .wmv. It covers the four steps, then the one setting that behaves differently on WMV than on every other video target, then the failures people actually hit.
.jfif onto the page or click "+ Add Files" to browse. The uploader also accepts .jpg and .jpeg, and you can queue several images.The File Compression group shows three modes, and they do not all apply equally to WMV:
Sensible starting points for a static image, which is the easiest thing a codec ever has to compress:
| Property | Value |
|---|---|
| Container | ASF (Advanced Systems Format), Microsoft's Windows Media container |
| Video codec | WMV 2 = Windows Media Video 8 by default; WMV 1 = Windows Media Video 7 |
| Audio | None — image sources produce a silent clip and the audio controls are hidden |
| Frame rate | 1 frame per second; a static picture has no motion to sample |
| Clip length | Image Duration × number of images (5 seconds for one image by default) |
| Letterbox / pillarbox fill | The Background Color, white unless you change it |
| Resolution | Source size unless you set one; long edge capped at 4096 px |
| Rate control offered | Quality Preset, Constant Quality, Constraint Quality — bitrate and target-size modes do not apply here |
| WMV (Windows Media Video 8) | MP4 (H.264) | |
|---|---|---|
| Released | WMV 7 in 1999; WMV 8 followed it | H.264 standardised in 2003 |
| Standardisation | Proprietary Microsoft; only WMV 9 became SMPTE 421M (VC-1) in 2006 | ITU-T H.264 / ISO-IEC MPEG-4 AVC |
| Windows playback | Native | Native |
| macOS / iOS playback | Not native — needs VLC or similar | Native |
| Android playback | Not native | Native |
| Browser playback | No | Yes, everywhere |
| Compression efficiency on a photo | Dated; needs more bitrate for the same look | Substantially better |
| Choose it when | A Windows-only tool or device demands .wmv |
Anything else |
WMV is a legacy target, and it is worth being honest about when to walk away from it. If nothing in your chain specifically requires .wmv, this is the wrong conversion — MP4 plays on more devices, compresses a photo better, and is accepted by every editor that accepts WMV. If your goal is a web-embeddable loop rather than a file for a Windows application, JFIF to WebM is the open-format equivalent that plays in browsers, which WMV never will. And if you are producing a short looping animation for chat, a forum or an email signature, a video container is the wrong shape entirely — JFIF to GIF drops into places that reject video files outright. Reserve WMV for the case it was chosen for: a Windows-only tool, deck or player that will not take anything else.
They are two generations of Microsoft's codec: WMV 1 is Windows Media Video 7, introduced in 1999, and WMV 2 is Windows Media Video 8, its successor and the default on this page. WMV 2 compresses better, and anything that can decode WMV 1 can decode WMV 2 in practice, so there is rarely a reason to step back. Pick WMV 1 only when a specific old application or embedded player has told you it needs it. Neither is WMV 9 / VC-1, the later version that SMPTE standardised as 421M in 2006.
Because a JPEG holds pixels and nothing else — there is no audio to carry across, so the audio codec controls are hidden on this page rather than left visible to mislead you. Produce the silent clip here and lay a music or voice track over it in a video editor if you need one. This is not specific to WMV; every still-image-to-video conversion behaves the same way.
Not with a target-size field — those modes are not offered for image sources. You control size indirectly, and effectively, with two settings: Constraint Quality's Max bitrate, and the Video resolution. Size is roughly bitrate × duration, so halving the bitrate roughly halves the file, and shortening the Image Duration shortens it proportionally. For a still image, cutting the resolution to what the destination actually displays usually saves more than anything else you can do.
They are the same container with different extensions. A WMV file is Advanced Systems Format, Microsoft's container, carrying a Windows Media Video stream; .asf is the generic name for that container regardless of what is inside. The extension mostly tells Windows which application to launch. If a tool rejects .wmv but accepts .asf, renaming often works, though the reverse is not reliable because an .asf may hold codecs a WMV-expecting app does not anticipate.
Slightly, and unavoidably. Your .jfif is already lossy, and encoding it to WMV applies a second, different lossy compression on top — nothing here can restore what the original JPEG discarded. On a still image the loss is small if you give the encoder enough bitrate, which is why the walk-through above suggests being generous: a motionless frame at 2–4 Mbps at 1080p has far more data than it needs. If you want a genuinely pristine copy of the picture, keep it as an image: JFIF to PNG.
Yes. Upload them together and leave Merge strategy on "Merge images" for a single clip in which each photo is held for the Image Duration; switch to "Video per image" to get one WMV per file. Files are used in the order they are listed, so number your filenames before uploading. Images of differing shapes are placed on a common canvas, so mismatched aspect ratios will show the Background Color around the edges.
Because our pipeline encodes image-sourced video at one frame per second: every frame of a static photograph is identical, and writing thirty copies of it per second would only add bytes without changing what anyone sees. Players hold each frame for its full duration exactly as expected. The one consequence worth knowing is editing granularity — if you plan to cut the clip on sub-second boundaries in an NLE, re-time it to your project frame rate on import.
It is uploaded over an encrypted connection, encoded on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public. Source images larger than 4096 px on the long edge are scaled down before encoding, which is far above any resolution a WMV target realistically needs. The practical limit on your side is upload size and time rather than anything about the image.