Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
.jfif is just a JPEG. The extension is what Windows Mail, Outlook and a couple of browsers write when they save a downloaded picture, and it maps to ITU-T T.871 — the recommendation that standardised the JPEG File Interchange Format in 2011. .m2ts is the other end of the spectrum: the Blu-ray-flavoured MPEG-2 transport stream that camcorders and disc authoring tools expect.
People land here for one of two reasons. Either an authoring tool or an editor refuses everything except transport streams and a still has to be turned into one, or a title card, logo or photo needs to sit on a timeline beside AVCHD camcorder footage without a container mismatch. Both work. What follows is exactly what the conversion produces.
These three names get used interchangeably, and on most sites they are interchangeable. Here they are not, and the difference is visible in the first four bytes of the file.
| Output name | First bytes | Packet size | Framing |
|---|---|---|---|
.m2ts |
0e bf 46 22 47 40 11 10 … |
192 bytes | BDAV — a four-byte arrival timestamp precedes each transport packet |
.mts |
47 40 11 10 00 42 f0 25 … |
188 bytes | Plain MPEG-2 transport stream |
.avchd |
47 40 11 10 00 42 f0 25 … |
188 bytes | Plain MPEG-2 transport stream |
We wrote the same H.264 encode under all three names. The .mts and .avchd files came back byte-identical. The .m2ts file did not: it carries the extra four bytes on every packet, which is what Blu-ray's BDAV layer uses to record when each packet arrived.
That prefix is not free. On a full-size encode we measured 3,380,240 bytes as .avchd (17,980 packets × 188) against 3,452,928 bytes as .m2ts (17,984 packets × 192) — an overhead of 2.150%, which is exactly 192 ÷ 188. On a very short clip the figure looks much worse because muxer padding dominates; the 2% number is the one that holds at realistic lengths.
.jfif in or click "+ Add Files". The picker also takes .jpg and .jpeg — the same format under different names — and several photos can be queued together..m2ts for each. Image Duration is preselected at 5 seconds per still, adjustable from a single frame at 60 fps up to 10 seconds.| Codec | Encodes at 1 fps? | Use it when |
|---|---|---|
| H.264 (preselected) | Yes | Always, unless something downstream demands otherwise. Matches what AVCHD and Blu-ray expect |
| H.265 | Yes | A newer editor or player asked for HEVC; smaller files at the same quality |
| MPEG-2 | Yes | A DVD-era authoring tool needs MPEG-2 elementary video inside the stream |
| MPEG-4 / Xvid / DivX | Yes | Legacy hardware that predates H.264 |
| MPEG-1 | No | Do not pick it here. See below |
MPEG-1 is the one entry that will not work on this page. A still is encoded at one frame per second, and MPEG-1 only permits the eight frame rates written into its own specification — 1 fps is not among them, so the encoder refuses to open and no file is produced. MPEG-2 escapes the same limit because it can carry a non-standard rate in its sequence extension; we confirmed a 1 fps MPEG-2 stream reads back as r_frame_rate=1/1.
No. It is one correctly framed BDAV stream file, and disc structures are folder trees — BDMV, STREAM, playlist and clip-info files — that an authoring application builds around streams like this one. Think of this conversion as producing the ingredient, not the meal. Authoring software will happily import it; a Blu-ray player looking at a bare file on a USB stick generally will not.
Yes. A JPEG has no soundtrack, so there is nothing to carry over, and the audio controls are suppressed on image sources for that reason. Worth knowing if strict compliance matters: real AVCHD calls for AC-3 or Linear PCM audio, so a validator may object to a stream with no audio track at all.
Because it is no longer a photo. JPEG stores one picture once; video stores it repeatedly, five seconds' worth by default, plus transport-stream packet headers on every 188 bytes of payload and a four-byte BDAV prefix on top of that. If the result is bigger than you want, the levers are Image Duration (shorter clip), Quality Preset (fewer bits per frame) and Video resolution (fewer pixels per frame), in roughly that order of effectiveness.
Pick .m2ts only when a Blu-ray-oriented tool asked for it by name, because the BDAV timestamp prefix costs about 2% in file size for information most workflows never read. Otherwise JFIF to MTS gives you plain 188-byte packets that more players open on sight. Note that JFIF to AVCHD produces bytes identical to the MTS output — only the filename differs.
Try VLC first; it handles BDAV framing directly. If a player is extension-driven and does not know .m2ts, renaming will not help here — unlike the .avchd/.mts pair, the .m2ts bytes really are different, and a player that expects 188-byte packets will choke on 192-byte ones. Convert again choosing .mts, or use JFIF to MP4 if universal playback is what you actually need.
Only when you change the frame shape. JPEG cannot store transparency, so on a straight conversion the setting is inert. Choose a Fixed Resolution whose aspect ratio differs from the photo's and the picture is scaled to fit with the leftover bars filled in this colour — preselected to white on image sources, so a 4:3 photo forced into a 16:9 frame gets white bars unless you change it.
Not on this page. Stills are encoded at one frame per second and the clip's length comes from Image Duration instead. That is why a 5-second clip contains five frames rather than 125, and why the file is far smaller than a real 5-second recording.
Anything over 4096 pixels on the long edge is normalised down to 4096 before it reaches the encoder. A 6000-pixel camera JPEG therefore arrives at the encoder as a 4096-pixel image. That is still well above 4K delivery, so it rarely matters — but this is not a way to preserve a high-megapixel original.
On H.264 and H.265 the slider runs 16 to 51, where lower means better quality and a bigger file. For a still, anything in the high teens is already indistinguishable from the source. On the older codecs in the list — MPEG-2, MPEG-4, Xvid, DivX — the same control is a 1-to-31 quantiser scale instead, so a number that means "excellent" on one codec means something quite different on another. Quality Preset avoids that trap by mapping to the right scale for whichever codec is selected.