Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
A .jfif file is an ordinary JPEG — the extension comes from ITU-T T.871, the 2011 recommendation that finally wrote down the JPEG File Interchange Format, and Windows Mail, Outlook and a few browsers have a habit of saving downloaded pictures with it. AVCHD is the camcorder format Panasonic and Sony licensed jointly in July 2006: H.264 video and Dolby Digital or Linear PCM audio carried in an MPEG-2 Transport Stream.
This page encodes your still picture as an H.264 transport stream so it can sit alongside camcorder footage on an editing timeline. Read the next section before you use it — what comes out is genuinely useful, but it is not a disc.
The converter encodes H.264 and forces an MPEG-2 Transport Stream muxer, then names the result .avchd. We compared that output against the same encode written as .mts and the two files were byte-identical — 8,836 bytes, 47 packets of 188 bytes each, sync byte 0x47 at offset 0. So:
.mts will handle them..mts is the fix, and it is a rename, not a conversion — no bytes change.BDMV/STREAM folder structure with index and clip-info files beside the video. Nothing here builds that..jfif on the page or click "+ Add Files". The picker also accepts .jpg and .jpeg, which is convenient because the three are the same format under different names..mts if your player refuses to open it. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.H.264 is a CRF codec, so the Quality Preset genuinely moves the encoder here rather than being decorative. Each preset maps to a fixed CRF value. We encoded the same 640 × 480 JPEG as a 5-second clip at each one:
| Quality Preset | H.264 CRF | Measured .avchd size (640 × 480, 5 s) |
|---|---|---|
| Highest | 17 | 9,024 bytes |
| Very High (preselected) | 18 | 8,836 bytes |
| High | 20 | 8,460 bytes |
| Medium | 23 | 7,896 bytes |
| Low | 26 | 7,332 bytes |
| Very Low | 28 | 6,956 bytes |
| Lowest | 32 | 6,580 bytes |
The spread is small because a still picture held for five seconds is almost entirely repeated frames — H.264 spends its bits on the first frame and then coasts. On a still, there is very little reason to drop below Very High.
| You might expect | What is actually there |
|---|---|
| A bitrate or target-file-size box | Hidden on image sources; Quality Preset, Constant Quality and Constraint Quality are the three modes offered |
| An audio codec selector | Hidden — a photograph has no soundtrack, so the clip is silent |
| A frame-rate control | The encode runs at a fixed 1 frame per second; Image Duration sets the length |
| Anything above 4096 pixels | Very large photos are normalised down to 4096 pixels on the long edge before encoding |
| A choice of codec | H.264 only, which is what the AVCHD specification calls for anyway |
Almost certainly not. The container is a standard 188-byte MPEG-2 transport stream — we verified the sync byte sits at offset 0 and the packet count divides exactly by 188 — but most players dispatch on the file extension and have no entry for .avchd. Rename the download to .mts and try again. That is a rename only; the bytes are unchanged, and we confirmed a .avchd and a .mts written from the same encode compare byte-for-byte equal.
Treat that as unlikely. AVCHD playback from a device expects the full folder layout that a camcorder writes — BDMV, STREAM, index and clip-info files — and this conversion produces one stream file with none of that scaffolding. The output is meant for an editing timeline or a media player, not for a camcorder deck.
A JPEG has no audio track, so there is nothing to carry across, and the audio controls are suppressed on image sources for that reason. To put sound under the picture you need a tool that muxes an audio file with a video file; this converter takes a single still and encodes it.
JPEG cannot store transparency, so it does nothing on a normal conversion. It becomes relevant the moment you pick a Fixed Resolution whose shape differs from the photo's — the picture is scaled to fit and the leftover bars are filled with this colour. It is preselected to white on image sources, so a 4:3 photo forced into a 16:9 frame gets white bars rather than black ones. Change it before converting if you want black.
Image Duration multiplied by the number of pictures, when Merge strategy is left on "Merge images". One photo at the preselected 5 seconds gives a 5-second clip; six photos give 30 seconds. Switching to "Video per image" gives you six separate 5-second files instead.
They are three names for closely related things, and on this site they differ in one measurable way. .avchd and .mts come out byte-identical — plain 188-byte transport-stream packets. .m2ts is framed for Blu-ray instead: each packet carries a four-byte arrival-timestamp prefix, which makes it 192 bytes and the file about 2% larger. Pick .m2ts only if a Blu-ray-oriented tool asked for it; otherwise .mts is the least surprising name.
Not in a single pass — Image Duration applies to every still in the batch. The workaround is to convert each photo separately with its own duration and join the clips afterwards in an editor.
No. Very large stills are normalised down to 4096 pixels on the long edge before they reach the encoder, so an 8000-pixel photo is halved on the way in. That is well above 4K delivery resolution, so it rarely matters in practice, but it does mean AVCHD is not a way to archive a high-megapixel original.
Then take the shortcut: JFIF to MP4 produces the same H.264 picture in a container that phones, browsers, Discord, Slack and every editor open without argument. Choose the transport-stream family only when something downstream specifically asked for it.