Image to MXF Converter

Image to MXF: What This Tutorial Covers

This page is for editors, broadcast engineers and playout operators who need a still — a slate, a caption card, a graphic, a stills sequence — wrapped inside MXF, the SMPTE container that Avid, DaVinci Resolve, Premiere Pro and station automation ingest natively. By the end you will know which of the two available codecs to pick, what the Duration control actually does to a still, why the result is silent and larger than you expect, and which frame rates the MXF writer will and will not accept.

How to Convert an Image to MXF

1. Upload Your Image File: Drag and drop or click "+ Add Files" — one image for a slate, several for a sequence. 36 source types are accepted, including JPG, PNG, WebP, HEIC/HEIF, AVIF, TIFF, BMP, GIF, EPS, PSD and RAW from Canon, Nikon, Sony, Fujifilm, Olympus, Panasonic and Pentax.
2. Pick a Video Codec: Open Advanced Options. Video Codec offers exactly two essences for MXF — MPEG-2, which is preselected, and H.264. Nothing else is valid inside this container here, so H.265, ProRes and DNxHD are not on the menu.
3. Set Duration, Merge Strategy and Resolution: Duration defaults to "5 seconds per frame". Merge strategy defaults to "Merge images" (one combined clip) with "Video per image" as the alternative. Video resolution starts on "Keep original", with Fixed Resolutions, Preset Resolutions and Width/Height entry available, and Background Color — White by default — fills transparency and any letterbox area.
4. Convert and Download: Click Convert. The output is a silent MXF; a still image has no audio track to carry across.

Walk-through: Codec, Duration and Why the File Is So Big

The codec choice is a compatibility decision, not a quality one. MPEG-2 is preselected because it is what legacy XDCAM HD decks, older Avid systems and most station automation expect to find inside an MXF wrapper. H.264 inside MXF is accepted by modern NLEs and produces substantially smaller files, so pick it only when you know the destination will take it.

Duration behaves as clip length, not as timeline rate. A still-image source is encoded at one frame per second, and the Duration value becomes the length of the clip. With "Merge images", total length is simply the number of images multiplied by the per-image Duration — thirty stills at 6 seconds each is a 3-minute clip.

MXF output is deliberately all-intra, and that is why it is large. The MXF muxer places a hard constraint on the frame offsets it can index, so our pipeline pins the GOP length to 1 — every single frame is encoded as a complete I-frame with nothing predicted between frames. We verified this on our own encode: every frame in a 125-frame MPEG-2 MXF came back typed as an I-frame. That is exactly what an editorial container should do for scrubbing and frame-accurate conform, and it is also why a five-second still can run to several megabytes.

Common Errors and How to Fix Them

• "The conversion fails and no MXF comes back" — The MXF writer only accepts broadcast-standard frame rates. We tested the range directly: 23.976, 24, 25, 29.97, 30, 48, 50, 59.94, 60 and 120 fps are all written without complaint, while 1, 5, 10, 12 and 15 fps are refused outright. A still-image source is encoded at 1 frame per second, which is not on the accepted list, so the muxer rejects it when it writes the file header. If this is what you are hitting, produce the clip as Image to MP4 instead; MXF conversion is dependable from real footage that already carries a standard rate, via MP4 to MXF or MOV to MXF.
• "The clip is silent" — Expected and unavoidable. A still image carries no audio, so image-to-MXF always writes a video-only file. Lay the audio bed against it in your NLE after import.
• "It just shows one frozen frame" — Correct behaviour for a single image; the clip holds that frame for the Duration you chose. Upload multiple images, or a numbered sequence, if you want the picture to change.
• "My playout server rejected the codec" — Older automation and playout chains often accept only MPEG-2 inside MXF. Re-run with Video Codec left on the preselected MPEG-2 rather than switching to H.264.
• "Images of different sizes look padded" — Each frame is fitted to the chosen resolution with its aspect ratio preserved, and the leftover area is filled with the Background Color. That defaults to White; broadcast letterboxing is conventionally black, so change it if the clip is going to air.
• "I need something I can actually play or send someone" — MXF will not open in a browser, on a phone, or in most consumer players. Image to MP4 gives you H.264 that plays everywhere.

When This Doesn't Work

MXF is a workflow container, not a delivery format. If the destination is the web, social media or a colleague's laptop, wrapping a still in MXF is the wrong move regardless of how cleanly it encodes. It is also not a route to add music — image input is silent by definition, so bring the clip into Avid, Resolve or Premiere and lay audio against it there. And because only MPEG-2 and H.264 are offered here, an intermediate-codec conform that specifically requires ProRes, DNxHD or XAVC essence inside MXF is out of scope for this converter; those need a desktop transcoder. To go the other way and pull stills out of a finished MXF, use MXF to JPG.

Frequently Asked Questions

Why wrap a still image in MXF instead of MP4?

Because the consuming system demands it. Broadcast playout servers, Avid Interplay, station automation and many cinema DI suites ingest MXF and little else, so a slate or graphic delivered as MXF drops onto the timeline beside camera rushes without an extra transcode. If the destination is the web or a phone, MP4 is the right call every time.

What does MXF stand for, and is it a real standard?

Material Exchange Format, standardised by SMPTE as 377M and first published on 22 September 2004; the current revision is ST 377-1:2019. It is a vendor-neutral wrapper that carries video and audio essence together with timecode and descriptive metadata, and it underpins Sony XDCAM, Panasonic P2/DVCPRO, Avid and BBC infrastructure among others.

Which video codecs can go inside the MXF from this page?

Two: MPEG-2, which is preselected, and H.264. That is the entire list for this container here. If your facility spec calls for XDCAM HD422, IMX, DNxHD or ProRes essence specifically, this converter will not produce it — those are separate essence definitions, not just a codec dropdown entry.

Will the MXF have an audio track?

No. A still image contains only picture data, so image-to-MXF always writes a silent, video-only file. MXF itself supports multiple uncompressed audio channels; they just have to be added downstream in your NLE.

Can I match my edit timeline's frame rate?

Not from this page. There is no frame-rate control on an image source — stills are encoded at 1 frame per second and the Duration dropdown sets clip length rather than rate. On a 25p or 29.97 timeline your NLE will conform an image-derived clip on import anyway, since the picture is identical in every frame. If you need the file itself to carry a specific broadcast rate, start from footage that already has one.

Why is my MXF so much larger than an MP4 of the same still?

Two reasons compound. The GOP is pinned to 1, so nothing is predicted between frames and each one is stored complete; and MPEG-2, the preselected essence, is a 1990s codec that needs far more data than H.264 for the same picture. Switching Video Codec to H.264 shrinks the file considerably while keeping the MXF wrapper — as long as your destination accepts it.

Does the transparent background of my PNG survive?

No — no video format stores an alpha channel here. Transparent pixels are filled with the Background Color, which defaults to White for image sources, and the same colour fills any letterbox bars created by a resolution change. If you need a keyable graphic, deliver the PNG itself to your NLE and key it there.

How are my files handled?

Your image is uploaded over an encrypted connection, converted on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public. There is no limit on how many files you queue; the practical ceiling on a large batch is upload size and connection speed.