Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
This turns a .jfif photo — which is an ordinary JPEG that Windows saved under an unfamiliar extension — into a short MPEG-2 video clip that displays that single picture for a number of seconds you choose. MPEG-2 is the video codec behind DVD-Video, SVCD, and a great deal of digital broadcast, so this is the conversion to reach for when a disc-authoring package, an older set-top box, or an ingest system will take video but refuses a loose image. The result is silent: a photograph has no audio to encode. Files are uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours — no sign-up, no watermark.
Worth knowing before you download it: mpeg2 is a codec name, not a container name, and there is no such thing as an "MPEG-2 container format". The file you get is named .mpeg2 because that is the extension this page promises, but the bytes inside are an MPEG program stream — byte for byte the same kind of file a .mpg or .mpeg download would give you.
That matters in practice. Players, DVD-authoring tools, and media servers frequently decide whether to even probe a file based on its extension, and .mpeg2 is not on most of their lists. If something refuses to open the download, rename it to .mpg or .mpeg. Nothing is re-encoded and no data changes — you are only giving the file a name the software recognises. If you would rather skip that step, JFIF to MPG and JFIF to MPEG write the identical stream under a conventional filename.
Because this target names a specific codec, MPEG-2 is the only codec available here. The sibling .mpeg page additionally offers MPEG-1, which is the older Video CD codec.
| Property | Value |
|---|---|
| Full name | Generic coding of moving pictures and associated audio information: Video |
| Standard | ITU-T H.262 / ISO/IEC 13818-2, first version approved July 1995 |
| Part of | The MPEG-2 suite: 13818-1 Systems, 13818-2 Video, 13818-3 Audio |
| Container written here | MPEG program stream, the payload of a .mpg / .mpeg file |
| Coding | Lossy, block-based DCT with I, P and B frames; a direct descendant of MPEG-1 |
| Rate control | Bitrate-driven; there is no CRF-style constant-quality mode |
| Common tier | Main Profile at Main Level — the standard-definition tier DVD-Video and SVCD use |
| Interlacing | Supported natively, which is why broadcast adopted it |
| Licensing | The MPEG-2 patent pool has expired, so decoders now ship freely |
| Still in use for | DVD-Video and SVCD authoring, legacy set-top boxes, some broadcast and archive workflows |
| Not usable for | Web pages and phones — it is not an HTML5 <video> codec and iOS has no native support |
| Property | Value |
|---|---|
| Full name | JPEG File Interchange Format |
| Standard | ITU-T Recommendation T.871, approved May 2011 |
| Original specification | JFIF 1.02, September 1992, by Eric Hamilton at C-Cube Microsystems |
| Image data | Ordinary JPEG (ITU-T T.81 / ISO/IEC 10918-1), lossy and block-based |
| MIME type | image/jpeg — identical to a .jpg |
| What JFIF adds | An APP0 marker segment carrying version, pixel density, density units, and an optional thumbnail |
| Frames | Exactly one; no animation, no audio, no alpha channel |
| Why you have one | Windows maps the image/jpeg content type to .jfif in its MIME registry on some machines |
.jfif onto the page or use the upload button to browse; .jpg and .jpeg are the same format and are accepted too. With several images, "Merge strategy" chooses between "Merge images" for one chained clip and "Video per image" for a separate file each..mpg if your player or authoring tool ignores the .mpeg2 extension. No sign-up, no watermark.Rename it to .mpg or .mpeg if anything refuses to open it. The download is an MPEG program stream regardless of what it is called, so the rename is purely cosmetic — no re-encoding, no quality change, no risk. Do it before handing the file to DVD-authoring software in particular, since those tools tend to filter their file browsers by extension and will not show a .mpeg2 at all.
No. A JFIF is a single still image with no audio stream, so there is nothing to encode and no audio controls appear on this page. The output is video-only by design. Disc-authoring packages normally add the soundtrack during the build, or you can attach one afterwards in a video editor.
Because MPEG-2 has no constant-quality mode. Its rate control needs a real bitrate and it fails outright if that bitrate is too low for the frame size, so our encoder derives a safe minimum from the output dimensions — never below about 2 Mbps, and around 7.5 Mbps for a 1920×1080 frame. Multiply that by the duration and you have the file size. The effective lever is "Video resolution": halving the width and height cuts the minimum bitrate sharply. Shortening the "Duration" is the other one.
Not as-is. DVD-Video permits only a short list of frame sizes — 720×480 for NTSC and 720×576 for PAL, plus a few reduced variants — along with fixed frame rates and an audio track, and a 1 fps silent still-image clip meets none of those. Authoring software conforms the file during the build, re-encoding as needed. Treat this output as source material for that process rather than as a finished disc asset, and let the authoring tool handle the spec compliance.
Yes. JFIF is the JPEG File Interchange Format, standardised as ITU-T T.871 in 2011 and built on a 1992 specification from C-Cube Microsystems. It defines a small APP0 marker segment — version, pixel density, an optional thumbnail — sitting in front of ordinary JPEG image data, and it reports the same image/jpeg MIME type a .jpg does. Renaming one to the other changes no pixels, which is the clearest proof the two are one format under two names.
One frame per second, with B-frames disabled. Both choices follow from the source: every frame of a still-image clip is identical, so there is nothing for motion prediction or bidirectional frames to do, and a higher frame rate would only add duplicate data. The duration you set is honoured exactly — a five-second clip is five seconds long regardless of the frame rate underneath.
Yes. Every uploaded image is re-rendered as a clean PNG capped at 4096 pixels on the long edge before it reaches the encoder, so a very large scan or camera file is scaled down whether or not you touch the resolution controls. That cap exists because the still-image input path becomes unreliable above it. Below 4096 pixels, "Keep original" writes the clip at the photo's exact dimensions.
Only for compatibility with disc and broadcast hardware. MPEG-2 is what DVD-Video and SVCD mandate and what a lot of set-top and ingest equipment decodes natively, so if that is your destination it is the correct choice. For anything modern, H.264 in an MP4 is dramatically smaller for the same picture and plays essentially everywhere — JFIF to MP4 is the right target for phones, browsers, and social platforms.
Then skip the video path entirely. A .jfif is already a JPEG, so JFIF to JPG hands you the same picture under an extension every viewer, editor and upload form accepts. Use JFIF to PNG if you need a lossless copy for further editing. Convert to MPEG-2 only when the destination has specifically asked for MPEG video.
It is uploaded over an encrypted connection, rendered and encoded on our servers, and deleted automatically after a few hours. Nothing is shared, published, or indexed, and no account is needed. The real constraint on a large photo is upload size and transfer time rather than anything about the image itself.