MXF to AVIF Converter

MXF to AVIF Converter

MXF is the professional broadcast and production wrapper defined by SMPTE ST 377-1 — the file that comes off Sony XDCAM decks, Panasonic P2 cards, Avid systems and broadcast archives, and one that no web browser will ever open. AVIF is the opposite end of the spectrum: an image format built on AV1 that browsers do open, at a fraction of the bytes a JPEG would need. This converter bridges them by pulling a single frame out of the moving picture and encoding it as an AVIF still. That is the whole job — the output is a photograph of one moment, not a clip, so the setting that matters most is which moment you get.

MXF at a Glance

AVIF at a Glance

How to Convert MXF to AVIF

1. Upload Your MXF File: Drag the .mxf onto the page or click "Add Files". Several files can be queued and all use the same settings.
2. Set the Frame Selection: Open Advanced Options. "Specific Frame" takes a Time in seconds and grabs the single frame at that point; "Multiple Screenshots" instead walks the clip at a Capture Rate you choose and hands you one AVIF per sampled frame.
3. Choose the Quality Preset and Image resolution: Quality Preset opens on "Very High"; "Specific file size" is the alternative if you have a byte budget to hit. Image resolution opens on "Keep original", with percentage, preset-height, Width, Height and Width x Height options if you want the still smaller than the master.
4. Convert and Download: Click Convert. 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.

Choosing Which Frame You Get

The Time field under "Specific Frame" starts at 0 seconds, and on a broadcast master the very first frame is frequently the least useful frame in the file. Tapes and card exports routinely begin with colour bars, a slate, a countdown, black, or a few frames of the camera settling — none of which is the picture you were after. Whenever the source came from a deck, a playout server or an archive rather than a phone, put a real timestamp in that field: something a few seconds past the head of the clip, or the exact point you already know you want.

If you are not sure where the good frame is, switch to "Multiple Screenshots" and sample the clip — one frame every second or two — then keep the still you want and discard the rest. The extraction happens before any image encoding: the frame is pulled out to a lossless PNG intermediate first and only then encoded to AVIF, so nothing is being compressed twice on the way to the frame you finally choose.

Frequently Asked Questions

Will the AVIF play the video or animate?

No. AVIF as a format can carry an image sequence, but this conversion is a frame grab: you get a single still image per output file. If you want something that moves, MXF to GIF produces an animation from the same source, and MXF to MP4 or MXF to WebM will give you real video that browsers play. Choosing "Multiple Screenshots" here still produces separate still images, one per sampled frame, rather than one animated file.

Why is my AVIF a black frame, colour bars or a slate?

Because the frame selector starts at time zero and that is genuinely what is at the head of your file. Broadcast and archive MXF regularly begins with bars and tone, a countdown, a production slate, or plain black before the picture starts. Nothing has gone wrong with the conversion — you asked for frame zero and got it. Type a timestamp a few seconds in and convert again.

How much difference is there between the "Highest" and "Very High" quality presets?

A lot more than the names suggest, and this is worth knowing before you pick. The presets map onto AVIF encoder quality values, with "Very High" landing at 95 and "Highest" at 100 — and on the AV1 encoder, 100 is where the encoder stops discarding almost anything. We measured a 1280×720 test frame at both settings: it came out around 151 KB at the "Very High" setting and around 406 KB at "Highest", roughly two and a half times larger for a difference most eyes will not find. "Very High" is the sensible default for anything going on a web page; save "Highest" for a frame you intend to inspect or print.

Should I grab the frame as AVIF, JPG or PNG?

AVIF if the still is going onto a web page and you want the smallest file that still looks right — it beats JPEG substantially at the same visual quality and is supported by roughly 95% of browsers in use. MXF to JPG if the destination is older software, a print workflow, or anything that has not caught up with AVIF, since essentially everything reads JPEG. MXF to PNG if you need the frame for compositing or graphics work and want a lossless intermediate rather than a delivery file.

Does the AVIF keep the timecode or the frame number from the master?

No. AVIF has nowhere to put the structural and timecode metadata an MXF carries — start timecode, reel and tape names, essence descriptors and the rest of the production layer all live in the wrapper you are leaving behind. Note down the timestamp you converted at if you need to find that frame in the master again, because the still itself will not tell you.

My master is 1440×1080 anamorphic — will the AVIF look stretched?

It can, if you resize. Broadcast MXF very often stores non-square pixels and relies on a widescreen flag to display correctly. Leaving Image resolution on "Keep original" carries the stored pixel dimensions straight through. Resizing normalises the output to square pixels, which throws that flag away and leaves 16:9 material looking narrow. If you need a smaller still from an anamorphic master, use the "Width x Height" option and type the display geometry you actually want, such as 1920×1080 or 1280×720, rather than picking a height preset.

Why does one MXF produce a frame while another fails outright?

Because .mxf describes a family of files rather than one format. The extension covers several operational patterns and many different video essences, and vendor implementations diverged early enough that Sony's and Panasonic's first camera files were mutually incompatible. Partial or still-growing captures pulled off a card mid-record, vendor-specific variants and unusual essence types are the usual failures. Re-exporting a flat OP-1a MXF from your editor and converting that clears it up almost every time.

Will an HDR or log-encoded master look right as an AVIF?

Not without help. There is no tone-mapping stage in this pipeline, so an S-Log, V-Log or HLG master gets a plain colour conversion and the still will look flat and washed out compared with what you see on a properly monitored timeline. AVIF the format is perfectly capable of holding wide-gamut, high-bit-depth images — the gap is the grade, not the container. Apply your Rec. 709 grade in the editor and export a graded MXF, then pull the frame from that.

What happens to my file after the conversion?

It is uploaded over an encrypted connection, processed on our servers, and both the upload and the resulting stills are deleted automatically after a few hours. There is no sign-up, no watermark, and nothing is shared or made public. MXF masters are large, so the upload is usually the slowest part of a frame grab — if you only need a still from one moment, trimming the clip first with Video Cutter makes the whole job much faster.