Free online MXF to TS converter

What the MXF format is

MXF, or Material Exchange Format, is a professional video container designed to carry video, audio, timecode, captions, and production metadata. It is commonly created by Sony XDCAM, Panasonic P2, and other broadcast cameras, as well as Avid Media Composer, Adobe Premiere Pro, and DaVinci Resolve.

MXF files can use different operational patterns, including OP1a and OP-Atom, and may contain MPEG-2, AVC-Intra, DNxHD, DNxHR, JPEG 2000, or other codecs. The .mxf extension therefore does not identify one fixed video encoding or bitrate. MXF is usually encountered in professional camera cards, broadcast deliveries, editing projects, and archived masters.

What the TS format is

TS, also called MPEG transport stream or MPEG-TS, is a packetized container designed for continuous delivery of audio and video over broadcast, multicast, and streaming systems. It is used for digital television, IPTV, Blu-ray-related workflows, network transmission, and some hardware players.

TS can recover playback after transmission errors because it divides media into fixed-size packets and carries synchronization information within the stream. It is generally more suitable than MXF for broadcast transport or simple network delivery, but it does not preserve every type of MXF production metadata.

How to actually convert MXF to TS

Using the built-in online converter

You can convert the file for free on the 101convert.com website without installing software. Upload the MXF file, choose TS as the output format, start the conversion, and download the resulting transport stream when processing finishes. This method is practical for ordinary files, but upload only footage permitted by your organization and avoid confidential productions.

Using FFmpeg for local conversion

FFmpeg is the most controllable desktop method. It can either repackage compatible streams without changing their encoded quality or decode and encode them into codecs more widely accepted by TS players.

To attempt a lossless stream copy, open a terminal in the folder containing input.mxf and run:

ffmpeg -i input.mxf -map 0 -c copy -f mpegts output.ts

-map 0 includes all input streams, while -c copy avoids re-encoding. If the MXF contains a codec or stream type that the MPEG-TS muxer or destination device cannot carry, FFmpeg will report an error or the resulting file may not play correctly.

For broad compatibility, encode the video as H.264 and the audio as AAC:

ffmpeg -i input.mxf -map 0:v:0 -map 0:a? -c:v libx264 -preset medium -crf 18 -pix_fmt yuv420p -c:a aac -b:a 192k -ar 48000 -f mpegts output.ts

The -crf 18 setting provides high-quality H.264 output; higher CRF values create smaller files with more compression. Remove -ar 48000 only when the target system accepts the source audio sample rate. To reduce the file size further, use a higher CRF such as 22 or 24.

For a constant delivery bitrate required by some broadcast equipment, add video and audio bitrate limits, for example -b:v 8M -maxrate 8M -bufsize 2M. Use the exact bitrate, frame rate, resolution, audio codec, and service parameters specified by the receiving system.

Quality, compatibility, and limitations

A stream-copy conversion does not reduce image quality, but it also does not make an unsupported codec compatible. Transcoding to H.264/AAC improves consumer-player compatibility and reduces size, but it introduces generation loss and can change interlacing, timecode behavior, captions, or camera metadata.

MXF files may contain multiple audio tracks, proxy video, timecode, ancillary data, or subtitles. The first FFmpeg command attempts to retain them; the compatibility command selects the first video stream and available audio streams but may omit data and subtitle tracks. Inspect the source with ffprobe input.mxf before converting when track preservation matters.

Check the result with ffprobe output.ts or test it on the intended decoder. Some devices require MPEG-2 video rather than H.264, AC-3 or MP2 rather than AAC, a specific 188-byte packet structure, or a defined program/service configuration; those requirements must be supplied explicitly instead of assumed from the .ts extension.