Initializing... drag & drop files here
Supports: AVI
This grabs one still frame — or a series of separate stills — out of an AVI video and saves each one as a JFIF image. It does not convert the clip. JFIF is the original 1992 name for what everybody now calls a JPEG, so the file you get back is an ordinary JPEG in every way that matters; only the extension differs. Below: how to land on the exact frame you want, when to use a timestamp versus a screenshot sequence, and what to do when an app refuses a .jfif file.
2.1 for 2.1 seconds in — to capture exactly one still, or switch to Multiple Screenshots to pull a sequence at a fixed Capture Rate.Picking the wrong mode is the most common reason people redo an extraction, and the two solve genuinely different problems.
| Specific Frame | Multiple Screenshots | |
|---|---|---|
| What you set | Time (seconds), with decimals for sub-second precision | Capture Rate, from one frame every 0.1 s to one every 10 s |
| What starts selected | Yes — with the time at 0, meaning the first frame | No |
| What you get back | Exactly one image | One image per sampled moment, downloadable as a set |
| Right for | A thumbnail, a poster frame, the one instant something happens on a dashcam or CCTV clip | A contact sheet, a storyboard, a frame-by-frame reference set |
| Common mistake | Leaving the time at 0 and getting a black opening frame | Setting a dense rate on a long clip and generating hundreds of files |
Two things to watch whichever mode you pick. The output matches the AVI's real pixel dimensions, not the size of the window you watched it in — a "720p" file from the DivX era is often actually 720x404 or an upscaled 640x360, so the still can look smaller than you expected. And quality is bounded by the source: AVI frames are usually already lossy, and JFIF adds a second JPEG compression pass on top, which a high Quality Preset keeps close to invisible.
For the image data, yes. JPEG File Interchange Format was published in September 1992 by Eric Hamilton at C-Cube Microsystems to standardise how JPEG-compressed bytes are actually laid out in a file, and it was later folded into the formal standards as ITU-T T.871 and ISO/IEC 10918-5. A .jfif file holds an ordinary JPEG stream: same DCT-based compression, same quality, same pixels as a .jpg. The friction is never the bytes — it is the extension.
| JFIF (.jfif) | JPG (.jpg) | PNG (.png) | |
|---|---|---|---|
| Image data | JPEG stream | The same JPEG stream | Deflate, lossless |
| Compression | Lossy | Lossy | Lossless |
| Accepted by upload forms | Often rejected by extension filters | Almost always accepted | Almost always accepted |
| File size for one frame | Small | Identical to JFIF | Several times larger |
| Rename to the other freely | Yes, no quality change | Yes | No — different format |
| Right when | Something specifically asked for .jfif |
The still has to work everywhere | You need a pixel-exact frame to edit |
If the extension is causing trouble you can rename .jfif to .jpg with no quality loss at all, or extract with the friendlier extension directly using AVI to JPG.
.jpg, or use AVI to JPG from the start.A few AVIs resist frame extraction outright: files using an exotic or proprietary codec the decoder does not recognise, partially downloaded or truncated recordings, and the rare copy-protected container. If a clip refuses to extract, re-save or remux it in a desktop tool such as VLC or HandBrake and upload the clean copy. And if what you actually wanted was motion rather than a frozen frame, AVI to GIF keeps the animation instead of pulling a single still.
Stay in Specific Frame mode and type the moment into Time (seconds), using a decimal for precision — 2.1 is 2.1 seconds in, 12.45 is 12.45 seconds in. That returns a single JFIF image at that point, which is what you want for a thumbnail, a poster frame, or the exact instant something happens on a dashcam or security recording. The field starts at 0, so an untouched run gives you the opening frame.
No — they are the same format. JPEG File Interchange Format is the original specification for how a JPEG is written to a file, and .jpg files follow it too. The compression, the quality, and the pixel data are identical, and renaming .jfif to .jpg changes nothing but the name. Any quality difference you see between two files comes from the encoder settings used, not from the extension.
Because a lot of upload forms and a few older Windows applications filter strictly on the extension string and whitelist only .jpg and .jpeg. A perfectly valid JFIF gets refused before anything looks inside it. Rename the file, or extract with AVI to JPG to get the .jpg extension directly. This same quirk is why Windows and Chrome sometimes save a downloaded JPEG as .jfif — a file-association oddity, not a different image.
There is only one lossy step. The frame is first decoded out of the video and written as a lossless PNG, so nothing is discarded at capture time; that PNG is then encoded to JFIF at the quality you chose, which is where JPEG compression is applied. So the total damage is one JPEG pass on top of whatever compression the AVI already carried. At the default "Very High (Recommended)" preset that second pass is difficult to see at normal viewing size.
No. A JFIF is a still image with no audio track, so any sound in the AVI is simply not part of the output. That is a property of the format, not a setting. If you need the soundtrack, extract it separately with AVI to MP3, or pull the audio and the frames in two passes if you need both.
Yes. Queue multiple .avi files before converting and they are processed with the same Frame Selection, quality, and resolution settings. That works well for a folder of clips where you want the same timestamp from each — for example a poster frame five seconds in from every recording. Note that combining a batch of clips with a dense Capture Rate in Multiple Screenshots mode can produce a very large number of images, so start with a coarse rate.
Essentially none worth relying on. The frame is decoded to raw pixels and re-encoded as a new image, so there is no camera EXIF block to inherit — an AVI does not carry per-frame photographic metadata the way a camera JPEG does. If you need provenance recorded, keep the source filename and timestamp alongside the extracted stills rather than expecting the image to carry it.
It is uploaded over an encrypted connection, read on our servers to produce the frames, and then both the upload and the output images are deleted automatically a few hours later. No watermarks, no sign-up, and files are never shared or made public. The only practical limit on a very large AVI is upload size and time over your own connection.