Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
This page turns a JPEG image — one saved with the .jfif extension Windows and older browsers sometimes produce — into an F4V video clip that holds that picture on screen. It is a narrow tool with a specific audience: people feeding a player, signage system or archive that reads Adobe's Flash-era container and will not accept a still. The walk-through below covers the one JFIF-specific quirk worth knowing about before you upload, the controls that actually change the output, and what an .f4v file really is in 2026.
.jfif, .jpg and .jpeg — they are the same JPEG bitstream under three names — and the Merge strategy control decides whether several uploads become one clip or one clip each..f4v. No sign-up, no watermark..jfif Extension Changes One Thing: Auto-RotationJFIF and JPG are not different formats. JFIF — JPEG File Interchange Format — is the header convention almost every JPEG already uses; the .jfif extension usually appears because a Windows application or an older browser save dialogue chose it, not because anything about the bytes is unusual. Rename a .jfif to .jpg and every program on earth still opens it.
There is, however, one real behavioural difference on this converter. The step that reads a photograph's EXIF orientation flag and physically rotates the pixels to match is keyed on the file's extension, and it matches names containing "jp" — which covers .jpg and .jpeg but not .jfif. A camera photo shot in portrait stores the pixels landscape with an orientation tag saying "rotate this"; upload it as .jpg and the converter honours that tag, upload the identical bytes as .jfif and it does not.
Uploaded as .jpg / .jpeg |
Uploaded as .jfif |
|
|---|---|---|
| Pixel data read | Identical | Identical |
| EXIF orientation flag applied | Yes | No |
| Portrait phone photo | Comes out upright | May come out on its side |
| Photo with no orientation tag (scans, screenshots, exports) | No difference | No difference |
| Everything else on this page | Identical | Identical |
The fix is a rename. If your JFIF came off a phone or camera and looks rotated in the output, rename it to .jpg and convert again — the page accepts that extension and the rotation is then applied. Files that never had an orientation tag in the first place, which is most JFIFs from web downloads and screenshots, are unaffected either way.
The output is H.264 video in an Adobe F4V wrapper, with no audio track — a still image has no soundtrack, which is why there are no audio controls on this page.
F4V itself is structurally an MP4. Adobe introduced it with Flash Player 9 Update 3 in 2007, built on the ISO base media file format, precisely so that Flash could carry H.264 instead of the older Sorenson and VP6 codecs the .flv container had been stuck with. We checked the first bytes of a converted file and the brand box reads ftyp followed by f4v — an ISO base media file that declares itself an F4V. That is why VLC, mpv and most desktop players open F4V files without complaint even though Adobe ended Flash Player support on 31 December 2020: they recognise the underlying structure and ignore the unfamiliar brand.
The clip is encoded at 1 frame per second, so a 5-second Image Duration writes exactly 5 frames. A 1000 × 750 photograph held for five seconds came out at about 6 KB in our testing — five nearly identical frames compress to almost nothing, which is why file size is rarely a concern on this conversion.
| Quality setting | Output size (1000 × 750 still, 5 s) |
|---|---|
| Constant Quality slider at 16 (best) | 7 901 bytes |
| Constant Quality slider at 23 (the opening value) | 5 998 bytes |
| Constant Quality slider at 30 | 5 623 bytes |
| Constant Quality slider at 40 | 3 520 bytes |
| Constant Quality slider at 51 (worst) | 2 619 bytes |
Because F4V exists to carry H.264. The whole reason Adobe added the container in 2007 was that the older FLV format could not hold H.264, and a player expecting an F4V is expecting exactly that. Offering VP9 or MPEG-4 inside an F4V would produce files that nothing which asked for F4V could actually decode, so the dropdown does not offer them. This also means the Quality Preset behaves normally here: H.264 is a CRF-based codec, so the preset maps to a real quality target rather than falling back on a bitrate calculation the way it must for older codecs.
Desktop media players do — VLC, mpv, IINA and anything built on ffmpeg read it fine, because the file is an ISO base media container underneath. What is gone is the browser path: Flash Player reached end of life on 31 December 2020 and browsers removed the plug-in entirely, so an F4V cannot be embedded in a web page any more. If you need this clip to play somewhere on the open web, JFIF to MP4 produces the same H.264 video in the container everything accepts.
Image Duration is the length control, and its maximum is 10 seconds per image. For anything longer, either upload the same file several times with Merge strategy set to Merge images — each copy is held for the duration you chose, and they are concatenated — or extend the clip in a video editor afterwards. Turning up the quality or the resolution does not affect length.
Because every frame of a still-image clip is identical, so writing 30 of them per second costs encoding time and file size for nothing visible. One frame per second holds the picture for exactly as long as you asked. If a downstream tool insists on a conventional rate, conform the clip on import — that is a metadata change and does not need the picture content re-encoded.
No. Video containers have no equivalent of EXIF, so camera model, exposure settings, GPS position, capture time and any embedded colour profile do not make it into the .f4v. Only the pixels do. If that metadata matters, keep the original JFIF alongside the video — and note that the orientation tag in particular is not just dropped but, as explained above, not even applied on a .jfif upload.
Because no video codec can store an alpha channel. Transparent regions are composited onto the Background Color before encoding, and that control defaults to White. This is rarely relevant with a genuine JFIF — JPEG has no transparency at all — but it applies if you rename a transparent PNG to .jfif in the hope of sneaking it through. Change Background Color in Advanced Options if you want a different fill.
Usually, yes. There is no reason to upscale a photograph into a video — the extra pixels are interpolated and cost size without adding detail — and Keep original preserves exactly what the image had, floored to even dimensions because video codecs need them. Do change it if the destination player expects a specific frame size: Fixed Resolutions gives you exact width-by-height pairs, while Preset Resolutions sets the height and lets the width follow the source aspect ratio, which is a distinction worth remembering.
Yes. Upload them together and leave Merge strategy on Merge images: they are concatenated into one clip in upload order, each held for the Image Duration. Switching to Video per image gives one file per photograph instead. Photos of different shapes are fitted inside the target frame with the Background Color filling the leftover space, so a mixture of portrait and landscape produces visible bars — crop to a common aspect ratio first if that bothers you.
It is uploaded over an encrypted connection, converted on our servers, and both the upload and the .f4v 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-to-video outputs are tiny — a few kilobytes for a five-second clip — so neither upload nor download time is usually a factor here.