TIFF to MXF Converter

How to Convert TIFF to MXF Online

1. Upload Your TIFF Files: Drag-and-drop a single TIFF or a numbered image sequence (frame_0001.tif, frame_0002.tif, ...) into the uploader, or click "+ Add Files". Both .tif and .tiff are accepted, including 8-bit and 16-bit RGB or grayscale variants.
2. Pick Merge Strategy and Image Duration: Choose Merge images to wrap the sequence into one MXF file, or Video per image to wrap each TIFF individually. Set Image Duration to a per-frame interval — pick 1/24s for cinema, 1/30s for NTSC broadcast, 1/25s for PAL/EBU, or longer holds (1–10 seconds) for stills-on-screen slideshows.
3. Set Background Color, Quality and Resolution (Optional): Pick a Background Color (default Black) to fill letterbox/pillar areas when TIFF aspect differs from the target frame. Choose a Quality Preset (Very High is the default), set a Video resolution preset (768p, 1080p, etc.), and use File Compression to target a bitrate, exact size, or quality level.
4. Convert and Download: Click "Convert". MXF files are wrapped as SMPTE 377-1 Operational Pattern 1a (OP1a) with MPEG-2 video and PCM 16-bit little-endian audio by default — the layout most broadcasters and NLEs expect.

Why Convert TIFF to MXF?

TIFF (Tagged Image File Format) was published by Aldus in 1986 and is now maintained by Adobe; it stores lossless 8-/16-/32-bit raster images and is the workhorse format for VFX renders, scanned film frames, and DI (digital intermediate) plates. MXF (Material Exchange Format) is the SMPTE ST 377-1 wrapper that broadcasters, archives, and digital cinema use to package video, audio, and metadata into a single, frame-accurate, repairable file. Converting a TIFF image sequence to MXF turns still renders into a broadcast-deliverable clip.

• Broadcast deliverables to SMPTE specs — Networks and stations frequently require MXF OP1a per SMPTE ST 378-2004 for ingest. Wrapping a TIFF graphics build (lower-thirds, bumpers, station IDs) as MXF makes it ready for playout servers like Grass Valley K2, Imagine Nexio, or Harmonic Spectrum.
• VFX and DI renders into edit — 3D and compositing apps (Nuke, Fusion, After Effects, Houdini) export numbered 16-bit TIFF sequences. Wrapping the sequence in MXF (typically with DNxHD or MPEG-2) lets Avid Media Composer ingest it as a single clip, with timecode, instead of an image-sequence stream.
• Stills-as-video for archive — National archives and libraries (the Library of Congress lists OP1a as a sustainable format) prefer MXF for long-term storage. A scanned photo or document archive (one TIFF per page, often 600 dpi) can be wrapped as a single MXF reel for preservation alongside born-digital video.
• Digital signage and playout loops — Set Image Duration to 5–10 seconds and Merge images to render a slideshow MXF for broadcast-grade playout systems that don't accept loose image files.
• News and sports graphics — Score bugs, weather maps, and lower-thirds rendered as TIFF frames need to land on the playout server as MXF clips with embedded timecode and channel-mapped audio (the default PCM 16-bit S16LE audio track is silent but channel-correct).
• Camera-rig matching — Sony XDCAM, Panasonic P2, and Canon XF cameras all record native MXF. Wrapping graphics or VFX renders as MXF means everything in the bin is the same wrapper — no transcodes inside Media Composer.

TIFF vs MXF — Format Comparison

MXF Operational Patterns and Codecs Quick Guide

Frequently Asked Questions

What MXF operational pattern does xconvert produce?

OP1a — a single, self-contained MXF file with interleaved video and audio essence, as specified in SMPTE ST 378-2004. This is the pattern broadcasters, the Library of Congress's preservation guidelines, and most playout servers expect. If your NLE is Avid Media Composer and you need OP-Atom (separate video/audio files), import the OP1a output into Media Composer and let it transcode on ingest, or use MXF to MOV and re-wrap in your facility's preferred tool.

Why is my MXF file so much larger than the source TIFFs?

Because MXF wraps a video essence, not still images. A 5-second MPEG-2 4:2:2 clip at 50 Mbps is about 31 MB regardless of whether the source was one TIFF or 120 TIFFs. The wrapper also embeds KLV (Key-Length-Value) metadata, timecode, and a silent PCM audio track. To shrink the output, lower the Quality Preset, use File Compression to target a specific bitrate or file size, or drop the Video resolution to 720p/768p.

How many TIFFs do I need for a usable MXF clip?

For a slideshow, one TIFF with an Image Duration of 5–10 seconds is fine. For broadcast or VFX, you want a numbered sequence: at 24 fps a 10-second shot needs 240 TIFFs (shot_0001.tif…shot_0240.tif), at 25 fps it's 250 frames, at 29.97 fps roughly 300. Set Image Duration to 1/24s, 1/25s, or 1/30s to match.

Should I pick 1/24s, 1/25s, or 1/30s frame interval?

Match your delivery spec. 1/24s (24 fps) is cinema and most streaming masters; 1/25s (25 fps) is PAL territories and EBU broadcasts (UK, most of Europe, Australia, much of Asia); 1/30s is approximately NTSC broadcast (true NTSC is 29.97 fps — round-tripping through MXF at 30 fps is fine for ingest but a strict broadcast deliverable may need 29.97 drop-frame, which most playout servers will conform on ingest).

What's the difference between MXF and MOV for broadcast?

Both are wrappers. MXF was designed by SMPTE specifically for broadcast and archive — it carries KLV metadata in every frame, supports robust partial-file repair, and is the deliverable spec for most networks, the EBU, and the FCC's emergency broadcast workflows. MOV (Apple QuickTime) is more common in post-production round-trips with Final Cut Pro and DaVinci Resolve. If you don't have a hard MXF spec, TIFF to MOV or TIFF to MP4 is simpler.

Will my 16-bit TIFFs keep their precision in the MXF?

Only partially. MPEG-2 4:2:2 (the default video codec on this page) is 8-bit; 16-bit TIFF detail is quantized down. If you need 10-bit or higher precision through the wrapper, you'd want an MXF wrapping DNxHR HQX, AVC-Intra 100, or JPEG 2000 — those codecs preserve 10/12-bit luma. For a fully lossless intermediate from TIFFs, an EXR-based pipeline is more common in VFX; MXF is best when you specifically need a broadcast wrapper.

Can I add an audio track to the MXF?

Not on this page — TIFF inputs have no audio, so the default PCM 16-bit S16LE track is silent but channel-correct (so playout servers don't reject the file for missing audio essence). If you need to marry the slideshow to a music bed, render the MXF, then mux it with a WAV in a tool like FFmpeg, or run the source images through JPG to MXF / PNG to MXF workflows that share the same wrapper logic.

Does this work for animated/multipage TIFF?

Yes — multipage TIFFs are unpacked and each page is treated as one frame in the output sequence, using the Image Duration you set. If your TIFF has 200 pages and you pick 1/24s, you get an 8.33-second clip at 24 fps.