MXF to WebP Converter

MXF Frame Grab as WebP — or PNG, or JPG?

You have an .mxf from a camera card, an Avid bin or a broadcaster's drive, and you want a still out of it for a web page, a CMS, a thumbnail or a press kit. This tool decodes the video essence and writes a single frame as a .webp image. The question worth answering first is whether WebP is the right still format for where the picture is going, because the three candidates behave very differently on a photographic video frame.

Short answer: WebP if the still is going on the web, because it is the smallest of the three at equivalent quality and every current browser reads it. PNG if the still is going into a design or print workflow where an editor will open, edit and re-save it. JPG if the recipient's software is old, unknown, or belongs to a press desk. One thing WebP will not do here: this page always writes a still, never an animation, no matter how long the clip is.

WebP vs PNG vs JPG for an MXF Frame

When to Export WebP

• The still is going straight onto a web page, into a CMS, or into an app bundle where page weight matters.
• You need the smallest file that still looks like the broadcast frame — WebP's lossy mode is the strongest of the three on photographic content.
• You want a lossless still that is still meaningfully smaller than the PNG equivalent: this is the one image target on the site with a real Lossless? toggle, and turning it on gives byte-exact pixels.
• You are producing many thumbnails from many clips and the total transfer size adds up.

When to Export PNG or JPG Instead

• Someone downstream will open the file in an older editor, a digital asset manager, a print RIP or a newsroom system — reach for MXF to PNG.
• The still is a working master that will be opened, edited and re-saved several times; a lossless PNG avoids generation loss and is more universally editable.
• The recipient is a press desk, a wire service or an unknown contact, where .jpg is still the safe assumption — use MXF to JPG.
• The frame is mostly graphics, titles or a chart with hard edges rather than photographic content; PNG's lossless encoding handles flat colour and sharp text better than any lossy setting.

How to Convert MXF to WebP

1. Upload Your MXF File: Drag the .mxf onto the page or click "+ Add Files". Several clips can be queued and they all run with the same settings. The file uploads over an encrypted connection and is decoded on our servers.
2. Set Frame Selection: Specific Frame is selected by default with Time (seconds) set to 0. Change that to a timestamp inside the actual programme — second zero on a broadcast master is very often bars, black or a slate. Or switch to Multiple Screenshots and set a Capture Rate to pull a series of stills across the clip.
3. Choose Lossless? and Quality Preset: Lossless? defaults to No (Recommended), which is the right choice for a photographic frame; set it to Yes for byte-exact pixels. Quality Preset (default "Very High (Recommended)") drives the lossy encode, and Specific file size with Auto Scale is there if you have a hard byte budget to hit.
4. Convert and Download: Set Image resolution if you want something other than the source frame size — Keep original is the default — then click Convert. No sign-up, no watermark; files are deleted automatically after a few hours.

Lossy vs Lossless WebP on a Video Frame

Frequently Asked Questions

Can I get an animated WebP out of my MXF?

No. This page is a frame exporter: it always writes a still image, however long the source clip is, and the WebP animation container is not produced here. That is a deliberate split rather than an oversight — animation from a video source is handled by the dedicated tools, so use MXF to GIF for something that plays in any context including email clients, or MXF to APNG for a moving image with a full 24-bit palette and proper alpha instead of GIF's 256 colours. If you specifically need an animated .webp, produce the motion as APNG or GIF here and convert that.

My still is colour bars or a black frame. What went wrong?

Frame Selection defaults to Specific Frame at Time = 0 seconds, and time zero on professional material is rarely picture. Broadcast delivery specs commonly require bars and tone, a countdown, a slate or a run of black before the programme starts, and camera-original MXF often begins with the operator settling the shot. Put an actual timestamp into the Time field. If you do not know where the good frame is, run it once with Multiple Screenshots at one frame every 5 seconds, look at what comes back, then re-run with a precise time.

Does the Lossless toggle actually do anything on this page?

Yes — WebP is the one image target here where Lossless? genuinely renders and takes effect, and it is worth knowing because that is not true across the site. Set to Yes you get byte-exact pixels and the quality controls stop mattering; left on No (Recommended) you get the lossy VP8-derived encode driven by the Quality Preset. For a photographic video frame, lossy is almost always the right answer — a 1080p frame with sensor noise or film grain in it will produce a very large lossless file, because grain is close to incompressible when you have to reproduce it exactly.

Will the WebP open in Photoshop, our DAM or our print system?

Possibly not, and this is the main reason to choose a different target. Browser support is settled — Chrome 32+, Edge 18+, Firefox 65+ and Safari 16+ all read WebP natively — but desktop and enterprise software lagged years behind. Older Photoshop builds need a plugin, plenty of digital asset managers still reject the MIME type, and print RIPs and newsroom systems are conservative by design. If the still is going anywhere other than a web page, MXF to PNG or MXF to JPG will save you an argument.

Is the frame deinterlaced or tone-mapped on the way out?

Neither, and both matter on broadcast sources. There is no deinterlacing in this pipeline, so a 1080i or SD interlaced master produces a still with combing baked in — horizontal comb teeth on anything that was moving. If the shot has motion in it and the master is interlaced, deinterlace in your NLE and export a progressive MXF first. There is also no HDR tone-mapping: an HLG or PQ graded master gets a plain colour conversion, which typically comes out flat and desaturated as a still. Grade to Rec. 709 upstream when the still needs to look like the programme.

Why is my frame stretched, and why are there black bars down the sides?

Two separate things. Stretching comes from non-square pixels — SD and anamorphic HD masters store a sample aspect ratio that a player applies at display time, and there is no pixel-aspect correction in this pipeline, so a 720×576 anamorphic frame is written as a literal 720×576 image. Set an explicit Width x Height under Image resolution to the display dimensions you actually want. Black bars, by contrast, are usually baked into the essence: a 4:3 programme delivered inside a 16:9 raster carries real black pixels, and there is no background-colour control on a video source — letterbox areas come out black because that is what is in the frame.

Can I hit an exact file size for a CMS upload limit?

Yes, that is what Specific file size with Auto Scale is for. Enter the byte budget your CMS enforces, and the encoder works toward it; with Auto Scale enabled it is allowed to reduce the pixel dimensions as well as the quality, which is what makes tight budgets achievable on a detailed frame. Bear in mind that a 4K broadcast frame squeezed into a very small budget will lose resolution rather than just fidelity. If the target is a thumbnail anyway, it is usually cleaner to set the dimensions you want under Image resolution — the height-based presets keep the source aspect — and let the Quality Preset handle the rest.

What are the practical limits and what happens to my file afterwards?

WebP maxes out at 16383 × 16383 pixels, which is comfortably above any broadcast raster including 8K, so the format is not your constraint. Upload is: the common broadcast MXF profiles are all-intra with a GOP of 1, meaning every frame is stored as a complete picture, which makes frame extraction very reliable and the source files very large — often several gigabytes for a few minutes. If you only need one still, trimming the clip in your editor before uploading saves more time than any setting here. Your file uploads over an encrypted connection, is decoded on our servers, and is deleted automatically after a few hours; there is no sign-up, no watermark, and files are never shared or made public.