Initializing... drag & drop files here
Supports: MXF
MXF is the Material Exchange Format — SMPTE's professional interchange container (specification ST 377-1, first published 22 September 2004), the wrapper broadcasters, camera manufacturers and archives use for masters and deliverables. JFIF is the JPEG File Interchange Format: the specification that actually describes the files everybody calls JPEGs. So this page decodes one frame out of a professional master and writes it as a JPEG-compressed still carrying the .jfif extension.
Two things distinguish it from the JPG version of the same job. There is no file-extension chooser here — the JPG page lets you pick between .jpg and .jpeg, whereas this page writes .jfif and nothing else. And because MXF is a professional container rather than a consumer one, whether you get a frame at all depends on what kind of MXF you have, which is where most of the trouble on this page comes from.
.mxf onto the page or click "Add Files". Broadcast masters run to many gigabytes, so upload time dominates the job; several files can be queued and they share the same frame and quality settings.0. On a professional master that is very often bars, black, a countdown or a slate rather than programme content, so type a timestamp from inside the programme — decimals such as 65.5 are accepted. "Multiple Screenshots" with a Capture Rate is the alternative for sampling a whole clip..jfif. Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.MXF is a wrapper, not a codec, and the professional world puts a lot of very different things inside it. What matters for a frame grab is whether the file you upload contains picture at all, and whether the essence is something a decoder can read.
| MXF flavour | What it is | Frame grab outlook |
|---|---|---|
| OP1a, self-contained | Picture, sound and metadata in one file — the usual delivery shape | Straightforward; this is what the page expects |
| Avid OP-Atom | Each essence track written to its own file inside an Avid MediaFiles tree |
Only the picture file yields a frame; the audio companions contain no video |
| XDCAM (MPEG-2 422P@HL, or IMX/D10) | Sony's broadcast essence, long-GOP or intra depending on flavour | Decodes normally |
| AVC-Intra | Panasonic's all-intra H.264 variant, 50 or 100 Mbit/s class | Decodes normally |
| DNxHD / DNxHR | Avid's mastering codecs, frequently seen in OP1a exports too | Decodes normally |
| DV / DVCPRO in MXF | Standard-definition tape essence rewrapped | Decodes normally, but expect non-square pixels |
| Growing or partial file | An interrupted card offload or an in-progress record | Often needs repair before any frame can be read |
If your file will not open in a desktop player but converts here, that is expected rather than surprising: consumer players usually lack both the MXF demuxer and the professional essence decoders, while the decode on this page runs on our servers with a build that carries them.
The frame is decoded and handed to the JPEG encoder losslessly, so the Quality Preset is the only new compression in the chain. What is less obvious is that it also decides chroma subsampling: our encoder leaves subsampling on its automatic setting, and in that mode it is switched off for quality 90 and above and switched on below. Putting one detailed 1920 x 1080 test frame through the same encoder at each rung gives the sizes below — real footage varies with content, but the shape of the curve does not.
| Quality Preset | Encoder quality | Chroma sampling | Test-frame size |
|---|---|---|---|
| Highest | 100 | 4:4:4, full colour resolution | 392,198 bytes |
| Very High (Recommended) | 95 | 4:4:4, full colour resolution | 233,124 bytes |
| High | 90 | 4:4:4, full colour resolution | 184,839 bytes |
| Medium | 80 | 4:2:0, colour halved in both directions | 89,907 bytes |
| Low | 70 | 4:2:0 | smaller again |
| Very Low / Lowest | 60 / 50 | 4:2:0 | smallest, visibly blocky |
The step from High to Medium is therefore not one rung of quantisation — it is where the colour planes lose half their resolution in each direction, and it roughly halves the file. On broadcast frames that carry a station logo, a lower third, or coloured captions, that is exactly the step where those elements start to smear. Stay at High or above whenever text or graphics are in shot.
.jfif file different from a .jpg file?Not in its contents. JFIF is the interchange specification that describes what a JPEG file looks like on disk, and .jfif, .jpg, .jpeg, .jpe and .jif are all names for the same encoded data. You can rename the download to .jpg and every viewer, editor and upload form will treat it identically — worth doing, since a few older content systems and ingest tools filter on the extension string and do not recognise .jfif.
.jfif and .jpg?Because the extension chooser exists only on the pages that own both spellings in one control. This page writes .jfif exclusively. If you would rather have the more widely recognised name from the start, run the same file through MXF to JPG, which performs an identical decode and encode and hands you a .jpg.
Because Time (seconds) starts at 0, and the head of a professional master is very rarely programme content. Bars and tone, a countdown clock, a slate and a few seconds of black are all standard delivery conventions. Enter a timestamp from inside the programme — the field takes plain seconds with an optional decimal.
The source frame's pixel dimensions, because Image resolution opens on Keep original — a 1080p master gives 1920 x 1080 and a UHD master gives 3840 x 2160. Note that anamorphic essence keeps its stored dimensions rather than being stretched to its display shape, so a 1440 x 1080 HDCAM-style frame arrives 1440 x 1080 rather than 16:9. Use Width x Height to set the display geometry you want. The Preset Resolutions list sets height only, with width following the source aspect.
No. Interlaced essence stores two time-offset fields per frame, and there is no de-interlacing step in this pipeline, so both fields land in the still and read as combing on anything in motion. Choose a frame from a static shot, or de-interlace in your editing system and export a progressive file before grabbing from it.
That is usually an HDR master — HLG or PQ — receiving a plain colour conversion. There is no tone-mapping stage here, so highlight roll-off and the wide gamut are not mapped into the still's SDR range. Grab the frame from a Rec. 709 export instead if colour fidelity matters.
They are discarded; a JFIF is one still picture and has no audio capability. Professional MXF files often carry several discrete PCM tracks rather than one stereo mix, and there is no track picker on the audio pages either — automatic stream selection takes the audio stream with the most channels, breaking ties by lowest index. If you need the sound, run the file through MXF to WAV separately.
Yes — set Frame Selection to "Multiple Screenshots" and choose a Capture Rate. The entries are intervals, not frame rates, so "1 second per frame" on a forty-minute rush is 2,400 images. Pick a slow rate such as five or ten seconds per frame for scouting, find the moment you want, then re-run with "Specific Frame" and an exact timestamp.
There is no file-count limit, and the practical constraint is upload time on your connection rather than anything on our side — broadcast masters routinely run to tens of gigabytes. If you only need one frame, trimming the clip first with Trim MXF is dramatically faster than pushing the whole master up for a single still.
JFIF when the still is going into a document, an email, a rundown or a web page, because JPEG compression makes it small and every system opens it. MXF to PNG when the frame will be cropped, annotated or re-exported repeatedly, since PNG avoids stacking a new generation of JPEG artefacts on each save, and when the frame is dominated by flat colour, graphics or text rather than photographic detail.