Add your VOB file
Drop one or more .vob 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 .vob video into .mxf 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 .vob video into .mxf audio keeps what you can hear and drops the picture entirely. A .vob file is a Video Object from a DVD's VIDEO_TS folder, holding the disc's actual movie data. Each .vob multiplexes MPEG-2 video, audio, subtitle subpictures, and navigation commands, split into pieces of about one gigabyte to satisfy the DVD specification.
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. For this route the practical draw is the interchange standard accepted by every professional broadcast system and carries frame-accurate timecode alongside rich descriptive metadata — balanced against two files with the same .mxf extension can be structured completely differently (OP1a versus OPAtom), confusing consumer tools, which is worth knowing before you commit a large batch.
The usual reason to take .mxf audio out of a .vob 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, files split at roughly 1 GB boundaries and must be rejoined for continuous playback; on the target side, the payoff is the interchange standard accepted by every professional broadcast system, which is exactly what you want for ingesting XDCAM and P2 camera cards into an edit.
| Aspect | DVD video object (.vob) | Material Exchange Format (.mxf) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | an MPEG-2 program stream variant extended with navigation packs (PCI/DSI) that DVD players use for menus and seeking | every element is encoded as KLV (key-length-value) triplets, making files self-describing to any compliant parser |
| Strongest at | backing up home-movie DVDs before the media degrades | ingesting XDCAM and P2 camera cards into an edit |
| Weak spot | files split at roughly 1 GB boundaries and must be rejoined for continuous playback | two files with the same .mxf extension can be structured completely differently (OP1a versus OPAtom), confusing consumer tools |
| Metadata | none inside the VOB itself; titles, chapters, and menu logic live in the accompanying IFO files on the disc | extensive by design: structural metadata, descriptive schemes such as DMS-1, embedded timecode, and UMID identifiers are core parts of the specification |
Drop one or more .vob 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 .mxf in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if MXF 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 MXF file. Outputs keep the original filename with the .mxf extension.
Since vob is container-oriented and mxf is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .mxf itself requires.
Yes — the .vob 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.
Professional editors, including Avid, Premiere Pro, Resolve, and Final Cut Pro, read .mxf directly, as do broadcast servers and ffmpeg. Consumer support is essentially nonexistent, so review copies are typically exported to MP4.
Much smaller — the video stream is usually 80–95% of a .vob 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, none inside the VOB itself; titles, chapters, and menu logic live in the accompanying IFO files on the disc; 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 .vob → .mxf → .vob is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.