Initializing... drag & drop files here
Supports: OGV
A .jfif is a JPEG. Not "like a JPEG" — the same encoded image data, in the same wrapper, under a different filename. JFIF is the interchange format that tells decoders how JPEG-compressed data is packaged, and .jpg, .jpeg, and .jfif are three extensions for it. This page decodes one frame out of your Ogg video and writes it as a JFIF still, which is useful when a specific application or workflow demands that extension by name. Everything below is reference material on the format, the controls, and what the extracted still can and cannot be.
| Property | Value |
|---|---|
| Full name | JPEG File Interchange Format |
| Origin | JFIF version 1.02, published 1992, adopted as a de facto standard |
| Formal standards | ITU-T Recommendation T.871 (May 2011) and ISO/IEC 10918-5:2013 |
| Underlying image standard | JPEG itself — ITU-T T.81 / ISO/IEC 10918-1 |
| What JFIF adds | The APP0 marker segment carrying version, pixel density and units, plus the colour and sampling conventions decoders rely on |
| Compression | Lossy, 8 bits per colour channel |
| Transparency | None — JPEG has no alpha channel |
| Animation | None — a single still image |
Relationship to .jpg |
Identical image data; only the filename differs |
| Encoder used here | libvips jpegsave |
.ogv onto the page or click "Add Files" to browse. Several clips can be queued and share the same settings.0. Type the moment you want, or switch to "Multiple Screenshots" to sample the whole clip at a Capture Rate..jfif. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours later — no sign-up, no watermark.Each preset maps to a specific JPEG quality number handed to the encoder. These are the actual values, not approximations:
| Quality Preset | JPEG quality value | What it is for |
|---|---|---|
| Highest | 100 | Maximum fidelity to the decoded frame; largest file, with diminishing returns above about 95 |
| Very High (Recommended) | 95 | The default; visually very close to the source frame at a sensible size |
| High | 90 | A good balance for web use |
| Medium | 80 | Noticeably smaller, with mild softening on fine detail |
| Low | 70 | Compression starts to show on edges and gradients |
| Very Low | 60 | Visible blocking in flat areas |
| Lowest | 50 | Thumbnails and placeholders only |
Because both Theora and JPEG are lossy, the still you get is a second lossy generation on top of footage that was already compressed. Nothing above "Very High" recovers detail the video never stored — it only spends more bytes reproducing the artefacts that are already in the frame. Keep the default unless you have a size constraint, in which case "Specific file size" with its Auto Scale toggle is a more direct lever than guessing at presets.
The Time (seconds) box starts at 0, and on real footage that is rarely the frame you want — recordings routinely open on black, on a fade, on a title card, or while the camera is still finding focus. Treat the zero as a placeholder.
12.5 is twelve and a half seconds in. The decoder seeks that point in the Theora timeline and saves the frame there..jfif, which is the practical way to find a usable moment when you cannot preview the video. On a long recording the default rate produces a lot of files, so start coarse and narrow down..ogv any more. VLC and mpv still play them; note the time there and type it in..jfif |
.jpg |
.jpeg |
|
|---|---|---|---|
| Image data | Identical | Identical | Identical |
| Origin of the name | The JFIF specification itself | The 8.3 filename era, where extensions were three characters | The unabbreviated form |
| Recognised by browsers | Yes | Yes | Yes |
| Recognised by every application | Not always — some older tools filter on .jpg |
Yes | Almost always |
| When to pick it | A workflow, importer, or archive that requires the .jfif extension |
The safe default for sharing and uploading | When a system spells it out |
If a program refuses your .jfif, renaming the file to .jpg is a complete fix — the bytes do not change. JFIF to JPG does the same thing without touching the filename manually, and OGV to JPG skips the round trip by writing .jpg from the video directly.
Yes. JFIF is the interchange format that defines how JPEG-compressed image data is stored — the APP0 marker segment, the pixel-density fields, and the colour conventions decoders expect. It began as JFIF version 1.02 in 1992 and was later formalised as ITU-T T.871 in 2011 and ISO/IEC 10918-5 in 2013. A .jfif and a .jpg written at the same quality are the same picture in the same wrapper; the only difference is the four characters after the dot.
Because the .jfif extension is a legitimate registered name for the format, and some combinations of Windows registry associations and browser save handlers pick it over .jpg when saving a JPEG. Nothing is wrong with those files — they open in every browser, in Photos, and in any image editor. The friction is purely that some older applications filter file pickers on .jpg alone and therefore refuse to show them. Rename the extension or run the file through JFIF to JPG.
Only if you ask it to. On the default "Specific Frame" setting it decodes exactly one moment and saves one still. Switching Frame Selection to "Multiple Screenshots" samples the clip repeatedly at the Capture Rate you pick and returns one .jfif per sampled frame, which on a long video at the default one-frame-per-second rate means a great many files. There is no mode that produces an animation — for a moving result use OGV to GIF.
By default, yes. Image resolution opens on "Keep original", so a 1280 x 720 video yields a 1280 x 720 still and a 1920 x 1080 video yields 1920 x 1080. Choose a Preset Resolution and the still is scaled to exactly that height with the width following the source aspect ratio — no rounding, unlike the video-to-video pages. Upscaling past the source is not useful: the frame carries only the detail Theora recorded, and enlarging it just interpolates.
No. JPEG has no alpha channel at all, and the source has nothing to contribute anyway — video frames are fully opaque, since Theora cannot store transparency either. If you need transparency you need a different target format: extract the frame with OGV to PNG, which supports an alpha channel, and cut out the background in an editor afterwards.
It is discarded. A JFIF is a single still photograph with nowhere to store sound, so the Vorbis audio in the .ogv is dropped during frame extraction. If you need the soundtrack, run the same file through OGV to MP3 separately.
Only up to a point. Raising the Quality Preset stops the JPEG encoder from adding new damage, but it cannot recover detail the Theora encoder already discarded, and an .ogv from a 2010-era web page was often encoded at a very low bitrate. Two things genuinely help: pick a moment that is not in fast motion, since heavily predicted frames in a lossy codec carry the most visible artefacts, and keep the preset at "Very High" or "Highest" so the second lossy generation adds as little as possible.
Because this page writes .jfif specifically — the File extension selector that appears on the JPEG converter does not render here. That is the whole point of a dedicated JFIF page: you land on it precisely when something in your workflow requires that extension. If you want the choice, use OGV to JPG instead, or convert afterwards with JFIF to JPG.
It is uploaded over an encrypted connection, decoded on our servers, and both the upload and the resulting image are deleted automatically a few hours after conversion. Files are never shared or made public, and there is no sign-up, no watermark, and no email required.