Add your MXF file
Drop one or more .mxf files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Pulling the soundtrack out of a .mxf video into .ts audio keeps what you can hear and drops the picture entirely. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Pulling the soundtrack out of a .mxf video into .ts audio keeps what you can hear and drops the picture entirely. An .mxf file is a Material Exchange Format container, the professional broadcast industry's standard wrapper for camera masters and finished programs. Newsrooms, playout servers, and cameras like Sony XDCAM and Panasonic P2 all exchange .mxf because it binds video, audio, and detailed production metadata into one interoperable file.
A .ts file is an MPEG transport stream, the packetized format built to carry television through unreliable channels like antennas, satellites, and cable. DVR recordings, IPTV captures, and HLS streaming segments all use .ts, making it one of the most common raw broadcast formats people encounter. For this route the practical draw is corruption costs a fraction of a second, not the whole file and trivially concatenable without remuxing — balanced against packet overhead runs several percent above an equivalent MP4, which is worth knowing before you commit a large batch.
The usual reason to take .ts audio out of a .mxf file is that only the sound matters — a talk, interview, song, or podcast segment. Keeping the video stream would waste storage, and a dedicated audio file is easier to trim, tag, and play. On the source side, two files with the same .mxf extension can be structured completely differently (OP1a versus OPAtom), confusing consumer tools; on the target side, the payoff is corruption costs a fraction of a second, not the whole file, which is exactly what you want for saving recordings from DVRs and set-top boxes.
| Aspect | Material Exchange Format (.mxf) | MPEG transport stream (.ts) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | every element is encoded as KLV (key-length-value) triplets, making files self-describing to any compliant parser | fixed 188-byte packets with sync bytes and continuity counters allow receivers to detect and skip corrupted data |
| Strongest at | ingesting XDCAM and P2 camera cards into an edit | saving recordings from DVRs and set-top boxes |
| Weak spot | two files with the same .mxf extension can be structured completely differently (OP1a versus OPAtom), confusing consumer tools | packet overhead runs several percent above an equivalent MP4 |
| Metadata | extensive by design: structural metadata, descriptive schemes such as DMS-1, embedded timecode, and UMID identifiers are core parts of the specification | broadcast service tables (SDT/EIT) can carry channel names and program-guide data, but there is no field for user tagging |
Drop one or more .mxf files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .ts in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if TS is selectable, the route is real and validated.
Press Convert. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid TS file. Outputs keep the original filename with the .ts extension.
Since mxf is container-oriented and ts is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .ts itself requires.
Yes — the .mxf file is processed inside your browser tab and never uploaded. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded. Close the tab and the file is gone from memory.
VLC, ffmpeg, and every broadcast tool read .ts natively, and smart TVs often play recordings made by their own tuners. Browsers only consume transport streams indirectly through JavaScript HLS players, so standalone .ts files need conversion for the web.
Much smaller — the video stream is usually 80–95% of a .mxf file's weight, and it is discarded entirely. The remaining audio is re-encoded at the bitrate implied by your quality setting.
This converter strips container metadata deliberately (the FFmpeg command runs with metadata mapping disabled) so exported files do not leak recording details. In the source, extensive by design: structural metadata, descriptive schemes such as DMS-1, embedded timecode, and UMID identifiers are core parts of the specification; none of it is transmitted anywhere because the file never leaves your browser.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .mxf → .ts → .mxf is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.