NEF to MXF Converter

NEF to MXF: the Honest State of This Conversion

MXF is the wrapper broadcast, playout and archive systems ingest, and a Nikon NEF raw photo is a single still. Putting one inside the other sounds like it should be trivial. It is not, and this page is going to tell you why up front rather than after a failed job: an MXF built from a still image does not currently complete here. The reason is a frame-rate rule baked into the MXF wrapper itself, explained below, and there is no setting on this page that works around it. What does work is a two-step route through a container that accepts a one-frame-per-second still, then a wrap to MXF in the tool that owns your delivery spec. That route is the how-to further down.

Why a Still-Image MXF Does Not Complete

MXF does not simply hold video the way MP4 or MOV do. It ties essence to a content package rate — the wrapper records what editing rate the material runs at, because downstream systems need to line frames up against timecode. That rate has to come from a fixed broadcast set. An image-to-video conversion, by contrast, encodes a still at one frame per second: there is no motion to sample, so one coded picture per second of hold is all that is needed, and nothing on this page exposes a frame-rate control to change it.

One frame per second is not in the set the wrapper will accept. In our testing, MXF writes at 1, 2, 5, 10, 12 and 15 frames per second were all refused, while every rate in the broadcast set wrote cleanly:

This is a wrapper-level rule, not a codec one, so switching Video Codec between MPEG-2 (the default here) and H.264 makes no difference — both are rejected at the same point. It is also why an MXF made from an actual video file works fine: a camera clip already carries a broadcast frame rate.

How to Get a Nikon Still Into an MXF Workflow

1. Upload Your NEF File: Start on a converter whose container accepts a one-frame-per-second still. NEF to MOV is the closest match for a post-production chain; NEF to MP4 is the better pick if the file also has to be viewed or emailed on the way.
2. Set a Broadcast Frame Size: Under Video resolution, set an explicit raster rather than leaving "Keep original" — 1920 x 1080 and 1280 x 720 are both in the Fixed Resolutions list, and "Width x Height" lets you type any standard-definition raster your spec calls for. A Nikon frame is thousands of pixels on the long edge and no ingest system wants that.
3. Set the Hold Duration: Image Duration opens on 5 seconds per frame. For a slate, a test card or a holding image, 3 to 10 seconds is normally plenty — every extra second is another coded picture of the same photograph.
4. Wrap to MXF in Your Editor or Transcoder: Import the resulting clip into the NLE, transcoder or MAM that owns your delivery specification and export MXF from there. That step is also where the facility profile gets applied — operational pattern, essence codec, timecode start, audio layout — which a general-purpose converter cannot pick for you. Files uploaded here go over an encrypted connection, are processed on our servers and are deleted automatically after a few hours. No sign-up, no watermark.

Doing the wrap in your own tool is not a workaround so much as the correct order of operations. Broadcast MXF delivery is rarely "any MXF will do" — it is a named profile with a named essence, and the system that will ingest the file is the one that knows which.

MXF at a Glance

Frequently Asked Questions

Can I get an MXF out of a photograph at all?

Yes, but not in one step from here. Convert the NEF to a clip whose container accepts the still-image frame rate — NEF to MOV or NEF to MP4 — and then wrap or transcode that clip to MXF in the tool that owns your delivery spec. That is also the only way to hit a specific facility profile, since operational pattern, essence codec and timecode rules vary from one ingest system to the next.

Why does converting a video file to MXF work when a photo does not?

Because a video file already carries a broadcast frame rate. A clip shot at 25 or 29.97 frames per second hands the wrapper a rate it recognises, so the write proceeds normally. A photograph has no rate at all, and the image-to-video path supplies one frame per second, which the wrapper refuses. Our MP4 to MXF and MOV to MXF pages take that video path.

Would changing the codec from MPEG-2 to H.264 help?

No. The Video Codec control on this page offers MPEG-2 (the default) and H.264, but the rejection happens in the wrapper before either encoder's output is written, so both behave the same way. The frame rate is the deciding factor, and this page exposes no frame-rate control to change it.

What is MXF actually for?

Moving finished material between professional systems. Material Exchange Format is defined by SMPTE ST 377-1 as a container that carries picture and sound essence together with structured metadata, so a newsroom system, a playout server, a camera and an archive can all hand the same file to each other without renegotiating what is inside it. Consumer software has no reason to support it, which is why nothing on a phone or in a browser opens one.

Does MXF store the picture, or does it just wrap it?

It wraps it. MXF is a container: the picture inside might be MPEG-2, AVC-Intra, DNxHD, XDCAM or something else entirely, and the audio alongside it is commonly uncompressed PCM. This is why "we need an MXF" is never a complete specification on its own — the operational pattern and the essence codec matter just as much, and a facility that accepts one MXF profile may reject another.

Is a still-image MXF even the right deliverable?

Often it is not. Slates, test cards and holding images do get delivered as MXF in tapeless chains, but many systems would rather take the still as a graphic and generate the clip themselves at the project's frame rate — which sidesteps the whole problem and guarantees the result matches the timeline. Ask the ingest side whether they want a picture file or a clip before you build anything; if it is a picture they want, NEF to PNG gives them a clean full-resolution frame.

Will the still keep its full Nikon resolution?

You would not want it to. Recent Nikon bodies record roughly 20 to 45 megapixels, and broadcast rasters top out far below that. Whichever route you take, set an explicit frame size that matches the delivery spec — 1920 x 1080 for HD is the usual answer — so the downscale happens once, predictably, rather than being applied unpredictably by whatever ingests the file.

How are my uploaded files handled?

Any file you upload goes over an encrypted connection, is processed on our servers and is deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. Nikon raw files are large, so the upload is normally the slowest part of a job. The full list of targets available from a NEF source is on the NEF converter page.