XCF to MXF

How to Convert XCF to MXF Online

1. Upload Your XCF Files: Drag and drop or click "+ Add Files" to select one or more GIMP project files. Batch upload is supported, so a full slate of slides or title cards can be queued in one pass.
2. Pick Merge Strategy and Duration: Under "Merge strategy" choose Merge images to render every XCF into a single timeline, or Video per image to emit one MXF per file. Set Duration (the dropdown defaults to "5 seconds per frame") to control how long each flattened still is held.
3. Tune Compression and Resolution (Optional): Under "File Compression" pick a Quality Preset (defaults to "Very High (Recommended)"), or switch to Constant Quality / Constraint Quality for tighter control. Under "Video Resolution" keep original, pick a Preset Resolution (1080p, 720p, 2160p), use a Fixed Resolution, or enter custom Width x Height. Set Background Color for any letterbox area not covered by the source pixels.
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. Download the resulting .mxf and ingest into Avid, Premiere Pro, or your broadcast playout system.

Why Convert XCF to MXF?

XCF is GIMP's native project format — first released in December 1997 — and stores layers, channels, paths, masks, guides, and selections that no broadcast NLE understands directly. MXF, ratified as SMPTE 377M in 2004, is the professional container the broadcast industry uses to move finished essence between cameras, edit bays, and playout servers. Going XCF → MXF means flattening a GIMP composition (lower thirds, title cards, station ID slates, season-launch promo frames) into a video file an ingest server will actually accept.

• TV station graphics packages — Lower thirds, sponsor bumpers, and "we'll be right back" cards built in GIMP need to land on a broadcast server as MXF, not PSD or XCF, before they hit air.
• Avid Media Composer ingest — Avid only natively understands OP-Atom and OP-1a MXF; importing a layered XCF directly is not supported, so a flattening render step is unavoidable.
• Slideshow rolls for newsrooms — Election results, sports tickers, weather grids drawn in GIMP can be rendered to a single MXF clip with controlled per-image duration.
• Promo / preview reels for ad agencies — When a deliverable spec calls for "MXF OP1a, broadcast safe," handing over an XCF is a non-starter; this conversion produces a deliverable a master control room can drop straight onto the timeline.
• Long-term tapeless archive — MXF was designed for tapeless broadcast archiving (a use case the Library of Congress sustainability assessment explicitly calls out), making it a more durable target than XCF for graphics destined for re-air years later.
• DaVinci Resolve and Premiere round-trips — Resolve and Premiere both accept MXF wrappers, so an XCF-derived MXF slots cleanly into a finishing timeline without a separate "render-to-video" step in After Effects.

XCF vs MXF — Format Comparison

MXF Operational Pattern Quick Guide

Quality Preset vs CRF — When to Use Which

Frequently Asked Questions

Will my GIMP layers be preserved in the MXF?

No — and this is unavoidable for any video wrapper. MXF carries flattened video essence, not layered raster data. Each XCF is rendered as a single composited frame (using the layer visibility and blend modes you saved with the file) before being placed in the timeline. If you need round-trip layer editing later, keep the original .xcf and re-render when changes are required.

Can Avid Media Composer ingest the MXF this tool produces?

Avid natively supports OP-Atom and OP-1a MXF wrappers. For the smoothest editing experience, Avid documentation recommends transcoding to DNxHD or DNxHR after ingest — that's standard practice for any third-party MXF, not specific to this converter. If your facility runs an AMA-link workflow, confirm the codec inside the wrapper meets your project's resolution and frame-rate spec before linking.

What resolution should I use for broadcast delivery?

Match the project. SD NTSC needs at least 720×486; HD broadcast typically targets 1920×1080; UHD playout uses 3840×2160 or 4096×2160 (DCI). For still-image source material, render at or above the project resolution — Avid's Pan & Zoom effect benefits from higher source resolution because it lets you push in without softening, but very large source images (above ~3K in either dimension) have historically caused issues with some Avid effects, so 1920×1080 is a safe ceiling for slide content.

How long should each slide stay on screen?

Broadcast graphics slates typically hold 3–10 seconds depending on use: a sponsor bumper might be 5 seconds, a "stay tuned" card 3 seconds, an editorial/legal slate 10+ seconds. The default of 5 seconds per frame is a sensible neutral starting point. Different durations per slide aren't supported in batch — for that, render each XCF individually with "Video per image" and assemble the timeline in your NLE.

Why does the output have black bars around my image?

The Background Color fills any portion of the output frame your XCF doesn't cover. If your source is, say, a 1280×720 PNG-style XCF and you're rendering 1920×1080, the converter pillar/letterboxes the difference. Either render at a resolution that matches your XCF aspect ratio, or change the Background Color (default Black) to match your station's safe color.

What's the difference between OP-1a and OP-Atom MXF, and which do I need?

OP-1a wraps a single playable program — interleaved video + audio + data — into one self-contained file. OP-Atom requires that each file contain exactly one essence track (video alone, audio alone). Broadcasters usually want OP-1a for ad spot delivery and standalone clips; Avid uses OP-Atom internally for its media files. If a deliverable spec doesn't say, OP-1a is the safer default for finished slate content.

Can I batch convert multiple XCF files at once?

Yes. Add several files at once and choose Merge images to combine them into a single MXF timeline (each held for the duration you set), or Video per image to emit one MXF per XCF. For dozens of files where each needs different settings, render in groups rather than one massive batch.

My XCF uses indexed color or a single layer — will it still convert?

Yes. The renderer flattens the XCF using the data the file actually contains. Indexed-color XCFs are converted to RGB before encoding (broadcast video essence is RGB or YUV, not paletted). If your XCF is older (pre-GIMP 2.10) and uses RLE compression rather than zlib, that's fine too — both compression schemes are read transparently.

Should I convert XCF to a still image first, then to video?

You can — exporting XCF to PNG or TIFF in GIMP and then running PNG to MXF or TIFF to MXF gives you the same end product. Going directly to MXF is simply one fewer step and avoids a manual flatten in GIMP. If you also need a flat raster for thumbnails or print, XCF to PNG or XCF to TIFF covers that path. After converting, MXF compression can shrink the file further if your delivery cap is tight.