Initializing... drag & drop files here
Supports: MKV
This pulls one frame — or a series of separate frames — out of a Matroska (.mkv) video and saves it as a JFIF image. It does not convert the clip; it freezes a moment from it. JFIF is the 1992 interchange convention that wraps JPEG-coded image data, so what you get back is an ordinary JPEG under a different extension. This tutorial covers choosing the exact frame, what the quality and resolution controls actually do to a video still, why the default settings can hand you a black image, and what to do when an app refuses the .jfif name.
.mkv onto the page or click "+ Add Files" to browse. Matroska files carrying H.264, HEVC, VP9 or AV1 video all decode here, and you can queue several recordings for batch extraction.0 — literally the opening frame, which on most videos is black. Enter the real moment you want, decimals included (12.45 is 12.45 seconds in). Switch to "Multiple Screenshots" and set a "Capture Rate" to sample the whole clip instead..jfif file — no sign-up, no watermark.Almost every redo of this conversion comes from one of three things — the wrong timestamp, the wrong mode, or an expectation the source can't meet.
0, leaving it alone gives you the first frame of the file, which is a fade-in or a black leader on a huge share of real videos. Note the moment in your own player first, then type it in. Decimals work, so you can land on a specific instant rather than a rough second.For the pixels, yes. JFIF — JPEG File Interchange Format — is the wrapper convention Eric Hamilton and C-Cube Microsystems published as version 1.02 on 1 September 1992 to pin down how JPEG-coded bytes should be packaged so different programs could exchange them. The base JPEG standard left several of those details open, and JFIF filled them in with a mandatory APP0 marker segment recording the JFIF version, the pixel-density units and values, and optionally a small uncompressed thumbnail. Decades later the same convention was formalised twice: as ITU-T Recommendation T.871 in May 2011 and as ISO/IEC 10918-5 in 2013, both editorial rather than technical rewrites. A .jfif file therefore holds exactly the kind of JPEG data a .jpg holds. The friction is never the bytes — it is the four-letter extension, which some Windows applications and upload forms simply don't have on their allow-list. If that bites, rename the file, or produce the friendlier extension directly with MKV to JPG.
| Property | Value |
|---|---|
| Full name | JPEG File Interchange Format |
| First published | Version 1.02, 1 September 1992 (Eric Hamilton, C-Cube Microsystems) |
| Formal standards | ITU-T T.871 (May 2011); ISO/IEC 10918-5 (2013) |
| Image data | JPEG-coded, lossy DCT compression |
| What JFIF itself adds | APP0 segment — JFIF version, pixel density units, optional thumbnail |
| Transparency | None |
| Frames per file | One |
Relationship to .jpg |
Same coded image data; the extension is the practical difference |
JFIF (.jfif) |
JPG (.jpg) |
PNG (.png) |
|
|---|---|---|---|
| Compression | Lossy JPEG | Lossy JPEG | Lossless format — but our default preset quantizes the palette; pick "Highest" for true colour |
| File size for a photo-like frame | Small | Small | Several times larger |
| Text, UI and hard edges | Softens them | Softens them | Stays crisp |
| Accepted by upload forms | Sometimes refused by extension | Accepted almost everywhere | Accepted almost everywhere |
| Transparency | No | No | Yes |
| Best use for a video still | When something specifically wants .jfif |
General-purpose stills, thumbnails | Screen recordings, text, graphics |
| Get it here | This page | MKV to JPG | MKV to PNG |
0, and most videos open on black. Enter a later timestamp, or use "Multiple Screenshots" to sample the clip..jpg, or use MKV to JPG from the start.Some MKVs resist frame extraction: files using an exotic codec our decoder doesn't recognise, partially downloaded or truncated Matroska containers, and DRM-wrapped video. If a clip refuses to decode, re-save or remux it in a desktop tool such as VLC or HandBrake and upload the clean copy. If your MKV is very long, trimming it first with the video cutter makes the upload far quicker, since only the segment holding your frame needs to travel. And if you actually want motion rather than a frozen instant, MKV to GIF keeps the animation.
No. They carry the same JPEG-coded image data; JFIF is simply the interchange convention that standardised how those bytes are wrapped, published in 1992 and later formalised as ITU-T T.871 and ISO/IEC 10918-5. Same compression, same pixels, different four letters after the dot. Renaming .jfif to .jpg changes nothing about the image.
Because the "Time (seconds)" field starts at 0 and takes the very first frame of the file. Videos frequently open on black, a fade-in, or a blank slate before the content starts. Type the timestamp you actually want, or switch Frame Selection to "Multiple Screenshots" so the clip is sampled at an interval and you can pick from the results.
Only if they were burned into the picture. Matroska normally carries subtitles as separate soft tracks that a player draws on top at playback time — those tracks are not part of the video frame, so the decoded still comes back with clean pixels underneath. Hardcoded subtitles, by contrast, are pixels like any others and will be in the image. The same applies to every other Matroska extra: additional audio tracks, chapters and metadata have nowhere to go in a still image.
Because the frame goes through a plain colour conversion rather than a tone-mapping pass. HDR footage stores highlight and colour information in a range a standard JPEG still cannot represent, and without tone mapping the result reads flat or desaturated compared with what your player shows. If your source exists in an SDR version, pull the frame from that instead.
Yes — switch Frame Selection to "Multiple Screenshots" and choose a "Capture Rate", from a frame every tenth of a second up to one every ten seconds. Each sampled frame is encoded as its own JFIF. This is also the fastest way to hunt for a good thumbnail, since you get a spread of moments in a single run rather than converting repeatedly with different timestamps.
By default it matches the MKV's real stored frame size, because "Image resolution" starts on "Keep original". You can override that with "Resolution Percentage", a "Preset" height with the width following your frame's aspect ratio, or an explicit "Width x Height". Bear in mind that a video's stored resolution is often lower than the window it plays in, so a still that looks small is usually reporting the truth about the source.
Essentially none. EXIF fields such as camera model, lens, exposure and GPS live in photo files; a video frame decoded out of a Matroska container has no such record attached to it, so there is nothing to copy into the JFIF. What you get is the picture data plus the JFIF APP0 segment, which just records the JFIF version and pixel-density values.
Use .jpg unless something specifically demands .jfif. The image is identical either way, but .jpg sails through upload forms, CMS media libraries and older Windows applications that filter strictly by extension — which is precisely the friction that sends most people looking for a .jfif converter in the first place. MKV to JPG produces the same still under the friendlier name.
Files are uploaded over an encrypted connection, decoded and encoded on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public. Extracting a frame is a light operation, so the practical limit is upload size and time rather than the conversion; trimming a very long recording first makes the whole thing noticeably quicker.