Initializing... drag & drop files here
Supports: AVCHD
This page pulls one frame out of an AVCHD camcorder clip and saves it as a .jfif. AVCHD is the high-definition format Sony and Panasonic introduced in 2006: H.264 video multiplexed into an MPEG-2 transport stream and written to the card as .MTS clips. JFIF is the other end of the scale — a still-image convention old enough that most people meet it by accident, usually because a browser or an email client saved a picture with that extension instead of .jpg. The conversion itself is a frame grab, and the interesting question is what a .jfif file actually is.
JFIF stands for JPEG File Interchange Format. JPEG itself only standardised how pixels are compressed; it said nothing about how to write the result into a file, which colour space to assume, or how to record the aspect ratio. JFIF filled that gap with a small APP0 marker segment placed right after the start-of-image marker, and it became the de facto way every JPEG on the internet is written. So a .jfif file is a JPEG. It carries the same image/jpeg MIME type, opens in the same viewers, and can be renamed to .jpg with no change to a single byte.
One detail is worth stating precisely, because it occasionally matters to ingest systems that check file structure. In our testing the file this converter writes is a baseline JPEG that begins with an Exif APP1 block rather than the classic APP0 JFIF segment — the encoder records orientation and resolution as Exif instead. Every JPEG decoder reads it identically. If a receiving system genuinely insists on seeing the literal JFIF identifier at the head of the file, re-save it through a tool that writes one.
0, which grabs the opening frame. Type a timestamp to move — the field accepts decimals, so 83.5 is one minute twenty-three and a half seconds in. "Multiple Screenshots" instead samples a run of frames at a chosen rate.Measured on the same 1920 × 1080 frame:
| Quality Preset | JPEG quality | File size |
|---|---|---|
| Highest | 100 | 395,352 bytes |
| Very High (the default) | 95 | 232,979 bytes |
| High | 90 | 183,303 bytes |
| Medium | 80 | 88,917 bytes |
| Low | 70 | 75,502 bytes |
| Very Low | 60 | 66,804 bytes |
| Lowest | 50 | 61,463 bytes |
The shape of that curve is the useful part. Going from Very High to Highest nearly doubles the file for a difference almost nobody can see on a video frame — quality 100 mostly stops discarding coefficients that were never there, because the source has already been through H.264 compression. Going from Very High down to Medium cuts the file to a third and is where most of the practical saving lives. Below Medium the curve flattens out and you are just adding artefacts on top of the camera's own.
| Property | .jfif |
.jpg |
|---|---|---|
| Compressed data | Identical baseline JPEG | Identical baseline JPEG |
| MIME type | image/jpeg |
image/jpeg |
| Renaming between them | Safe, byte-for-byte | Safe, byte-for-byte |
| Recognised by Windows Explorer | Yes, though the thumbnail handler is less consistent | Yes |
| Accepted by web upload forms | Sometimes rejected by extension-based filters | Almost always accepted |
| Where it comes from | Browsers and mail clients saving a JPEG under the format's formal name | Everything else |
No. Both hold baseline JPEG data and both are served as image/jpeg. JFIF is the name of the file-format convention that JPEG itself never specified, and .jpg is simply the extension that won. Renaming a .jfif to .jpg changes nothing inside the file.
Usually because something downstream asked for it by name — a document-management system, a legacy imaging pipeline, or a workflow that was set up around files a browser saved. If nothing has asked, take AVCHD to JPG instead; the picture is the same and the extension causes fewer arguments with upload forms.
Whatever the clip's frame size is, since Image resolution starts on "Keep original". AVCHD's high-definition modes top out at 1920 × 1080, roughly 2.1 megapixels, and 1280 × 720 modes yield a 720-line still. You can scale down with the presets or a percentage, but nothing adds detail the camcorder never recorded.
Because the clip was shot in one of AVCHD's interlaced modes, 1080/60i or 1080/50i. Each stored frame is woven from two fields captured a fraction of a second apart, and no deinterlacing is applied when the frame is grabbed, so anything that moved between the fields freezes as stripes. Pick a lower-motion moment, or use footage from one of the progressive modes.
Some AVCHD modes record 1440 × 1080 with non-square pixels and rely on the player to stretch them to a 16:9 shape on playback. A still taken from one of those clips arrives at its stored 1440 × 1080 size and therefore looks narrow. Resizing to 1920 × 1080 in any editor restores the intended proportions; no detail is lost in doing so.
Yes. Switch Frame Selection to "Multiple Screenshots" and choose a capture rate — from ten frames a second down to one every ten seconds. Each captured frame becomes its own JFIF at the quality and resolution you set, which is a quick way to find the sharpest moment in a pan or a burst of action.
It flips the relationship around: instead of naming a quality and accepting whatever size results, you name a size in bytes, kilobytes or megabytes and the encoder works out the quality that fits. That is the mode to use when an upload form imposes a hard cap. The Auto Scale option beside it allows the pixel dimensions to be reduced as well if quality alone cannot reach the target.
Not reliably. The frame is decoded from the video stream and re-encoded as a fresh image, so recording metadata held in the AVCHD stream or its sidecar files does not travel with it. What the output does carry is basic Exif written by the encoder — orientation and resolution — rather than anything about the original shoot.