VOB to MXF Converter

How to Convert VOB to MXF Online

1. Upload Your VOB File: Drag and drop or click "+ Add Files" to select VOB segments from a VIDEO_TS folder. Add multiple .vob parts (e.g. VTS_01_1.VOB, VTS_01_2.VOB) and they will be processed in batch.
2. Pick a Quality Preset: Default is "Very High (Recommended)". Choose Highest for archival masters where every macroblock matters, or step down to High/Medium when you only need a screening copy. For tighter control, switch from Quality Preset to Constant Bitrate, Variable Bitrate, Constant Quality, or Constraint Quality and dial in a target.
3. Set Resolution and Trim (Optional): Under Video Resolution, keep the DVD's native 720x480 (NTSC) or 720x576 (PAL), scale by Resolution Percentage, pick from Preset Resolutions, or enter custom Width x Height with aspect-ratio lock. Use Trim → Time Range to drop the FBI warning, menus, or unused chapters before wrapping.
4. Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared. Each VOB segment becomes a standalone MXF you can drop straight into Avid, Premiere, or DaVinci Resolve.

Why Convert VOB to MXF?

VOB (Video Object) is the DVD-Video container introduced with the DVD-Video 1.0 specification finalized in September 1996. It strictly follows the MPEG-2 Program Stream defined in ISO/IEC 13818-1 and is split into 1 GiB segments for legacy filesystem compatibility. MXF (Material Exchange Format) is the broadcast-grade container standardized as SMPTE ST 377-1 — initially published in 2004 and most recently revised in 2019 (ST 377-1:2019) — designed by SMPTE specifically for tapeless workflows, professional metadata, and timecode preservation.

Converting VOB to MXF moves DVD content out of a consumer playback container and into a wrapper professional NLEs treat as a first-class citizen. Common reasons:

• Avid Media Composer ingest — Media Composer stores all imported and transcoded media as MXF (OP-Atom by default), so converting VOB up front avoids the AMA-plugin guessing game that breaks if the DVD encoder used non-standard MPEG-2 GOP structures.
• Broadcast delivery specs — Most station and network delivery specs (for example, the DPP/AMWA AS-11 UK delivery profile) require an MXF wrapper with embedded timecode and as-broadcast metadata, which a raw VOB cannot carry.
• Archival of old DVD masters — Libraries and broadcast archives standardize on MXF for long-term preservation because the wrapper survives codec migrations and stores rich descriptive metadata alongside the essence.
• Cross-NLE handoff — Premiere Pro reads MXF in DV, DVCPRO, DVCPRO HD, AVC-Intra, XDCAM HD, and Canon XF flavors natively; DaVinci Resolve treats MXF similarly. Sending an MXF instead of a raw VOB removes the "what codec is inside" guesswork.
• DVD restoration projects — When upscaling or color-grading DVD footage, working from a re-wrapped MXF (rather than the original .vob) lets you carry timecode forward and keep clean reel names per chapter.
• Joining the 1 GiB segments — VOB's per-file 1 GiB split mid-program (e.g., VTS_01_1.VOB → VTS_01_2.VOB) is awkward to edit around. Converting through MXF lets you wrap each segment cleanly or output one continuous file per title.

For the reverse direction — wrapping an MXF back into a DVD-compliant program stream — see MXF to VOB. To send DVD content somewhere consumer-facing instead, VOB to MP4 is usually the better target.

VOB vs MXF — Format Comparison

Quality and Codec Quick Guide

Quality presets below are the xconvert presets; the codec column is what's typically wrapped inside an MXF for the listed use case. The Pick column maps to the controls in step 2 (Quality Preset, Constant Bitrate, Variable Bitrate, Constant Quality, Constraint Quality).

Frequently Asked Questions

Why bother converting VOB to MXF when both can carry MPEG-2?

The wrapper matters as much as the codec. VOB is a DVD-Video Program Stream optimized for set-top playback, with navigation packets, mandatory 1 GiB segmentation, and minimal descriptive metadata (most of which lives in a sibling .ifo). MXF is a self-describing professional container with embedded timecode, reel name, and structural metadata. Even if you keep the underlying MPEG-2 essence, MXF is what every broadcast delivery spec, MAM system, and pro NLE expects.

Will Avid Media Composer open the MXF directly?

Avid only natively supports OP-Atom and OP-1A MXF flavors, and inside the wrapper it cares which codec is present. If you target a codec Media Composer ingests natively (DNxHD, DNxHR, DV, DVCPRO HD, XDCAM HD, AVC-Intra), the file imports cleanly. If you wrap something exotic, Media Composer may ask you to transcode through AMA on import — which defeats much of the point of converting up front. Aim for a DNx codec for the smoothest Avid path.

What about the .ifo and .bup files next to the VOBs?

You can ignore them for the conversion. .ifo (information) and .bup (backup of the .ifo) carry DVD navigation — chapter offsets, menu structure, language tables — which is irrelevant once you're moving to a professional edit container. Just upload the .vob segments. If you need to preserve chapter boundaries, use Trim → Time Range in step 3 to cut individual MXF outputs per chapter.

My DVD's title is split across VTS_01_1.VOB, VTS_01_2.VOB, and so on. Will I lose the join?

The 1 GiB split is a filesystem artifact, not a content boundary — DVD players stitch the segments transparently. The converter processes each uploaded VOB independently, so you'll get one MXF per segment with a clean cut at the segment boundary (usually mid-GOP). If you need one continuous MXF, concatenate the source VOBs first (most DVD-ripping tools have a "join" option), then upload the joined file.

Should I pick OP1a or OP-Atom?

xconvert's MXF output is OP1a-style — a single interleaved file containing video and audio — which is the right pick for delivery, archive, and most non-Avid workflows. OP-Atom is Avid's per-track convention (one file for video, one per audio channel) and is generally created by Avid itself on import, so you don't need to pre-produce it. If your Avid project absolutely requires OP-Atom, import the OP1a MXF and let Media Composer transcode to OP-Atom on ingest.

Why does my MXF look softer than the original DVD playback?

DVD players upscale and apply post-processing (deinterlacing, noise reduction, edge enhancement) during playback that the file itself does not contain. The MXF you get back is the raw essence — typically interlaced 720x480 NTSC or 720x576 PAL. If softness is a problem, deinterlace and upscale in your NLE after wrapping. Don't compare DVD-on-a-TV playback to the file straight off disk; you're seeing the player's processing, not the source.

Can I convert copy-protected DVDs this way?

No. CSS-encrypted commercial DVDs need to be decrypted before ripping VOBs to a hard drive, and that step happens before files reach xconvert. Convert VOBs that you have already ripped from your own source material (home recordings, unencrypted screeners, archive masters), where you own or have licensed the rights.

Is there a max file size?

xconvert applies anonymous-tier upload limits per file — check the upload area for the current cap on your tier. Because a single VOB segment is capped at 1 GiB by the DVD-Video spec itself, individual segments typically fit comfortably. If you joined segments into one large file before upload and exceed the cap, either split back to the original VOBs or sign in for a higher limit.