Privacy First
Uploaded files are automatically and permanently deleted within two hours.
Make professional MXF camera and broadcast files playable on phones, in browsers and in any editor by converting them to H.264 MP4
You can upload and convert 1 video at a time.
MXF (Material eXchange Format) is a wrapper used by broadcast cameras, newsroom systems and archives. It is excellent for production and terrible for playback on consumer devices. Our converter unwraps it, re-encodes the picture as H.264 and packages everything as a standard MP4.
Drag the file in or import it from Google Drive. Multi-gigabyte clips are supported; the upload bar shows progress.
The professional codec is decoded, the video is encoded to H.264 and all audio tracks become AAC at 192 kbps each.
The result plays in VLC, QuickTime, Windows Media Player, browsers and on phones, and imports into every NLE.
Works with OP1a and OP-Atom files from XDCAM, XAVC, Canon XF, P2 and Avid media, as long as the essence is a codec FFmpeg can decode.
Container metadata is copied where MP4 has a place for it. Timecode tracks are carried as MP4 timecode where possible.
Interlaced XDCAM and DVCPRO material is encoded as is; deinterlace in your editor if the destination is the web.
Long broadcast files are encoded on server-class hardware, so your workstation is free while the job runs.
Backed by 10+ years of engineering expertise in large-scale data and scientific computing, it’s built for real-world video workflows that require uncompromised output quality, dependable processing of large files, and reliable, high-level performance.
Uploaded files are automatically and permanently deleted within two hours.
Rated 5 stars on Trustpilot for speed, reliability, and ease of use.
Referenced in published research and used for interview transcription and qualitative data analysis.
MXF was standardised by SMPTE in 2004 as a vendor-neutral wrapper for professional video, with room for rich metadata, multiple audio channels, timecode and frame-accurate editing. Broadcasters and camera makers adopted it because it is reliable in automated workflows. The same strictness makes it awkward outside those workflows: a file from a Sony XDCAM deck and one from a Canon C300 are both .mxf but contain different codecs, different operational patterns and sometimes different file layouts.
All of these are decoded with FFmpeg on our servers. The output is always the same: H.264 video with AAC audio in an MP4 container that any device can open.
Video is encoded with x264 at CRF 23 using the high profile, or with NVIDIA NVENC at a matching constant quality level on our GPU nodes, which produce visually equivalent results several times faster. Audio tracks are encoded as AAC at 192 kbps each, which is transparent for speech and music. All streams are mapped, timecode and container metadata are preserved where MP4 has fields for them, and the pixel format is converted to 8-bit 4:2:0 so the file plays on every phone and browser. 10-bit 4:2:2 sources therefore lose chroma resolution; if that matters, keep the MXF for grading and use the MP4 as a proxy.
Sending rushes to a client or producer who has no NLE, uploading to YouTube or Vimeo, playing footage on a tablet on set, creating lightweight proxies for a laptop edit, and attaching clips to a shared drive where team members use different operating systems. In each case the MXF remains the master and the MP4 is the convenient copy.
MXF is only a container; playback depends on the codec inside and on the player having a decoder for it. Consumer players rarely ship XDCAM, AVC-Intra or DNxHD decoders, and some MXF variants split video and audio into separate files (OP-Atom), which players do not expect. Converting to MP4 with H.264 removes both problems.
The source codecs are usually intra-frame or high-bitrate formats, and H.264 at CRF 23 is a lower bitrate consumer format, so the MP4 is not a lossless copy. For review, delivery to clients, web upload and editing on a laptop the difference is not visible. For colour grading or archiving keep the original MXF.
All of them are kept as separate tracks in the MP4. Players will normally play the first one; in an editor you can route them as you like. If you need a single stereo mix, create it in the editor after conversion.
Upload the video MXF; it will be converted on its own. Because the audio lives in different files, the MP4 will be silent. For complete clips use the OP1a export of your camera or NLE, which stores everything in a single MXF.
The same as the source: 1920 by 1080 stays 1080p, UHD stays UHD, 25p stays 25p and 59.94i stays 59.94 fields per second. Nothing is scaled or retimed, which keeps the MP4 usable as an editing proxy.
Transfers are encrypted, the upload and the MP4 are deleted automatically within two hours and nobody looks at the content. For unreleased productions you can additionally convert a short excerpt first to check the result.