AVCHD to MXF Converter

How to Convert AVCHD to MXF Online

1. Upload Your AVCHD File: Drag and drop or click "+ Add Files" to add your camcorder footage. AVCHD recordings typically arrive as .mts straight off the SD card or .m2ts after import — both work. Batch upload is supported, so you can queue an entire shoot.
2. Pick File Compression: Default is "Quality Preset" set to "Very High (Recommended)." Switch to "Constant Bitrate" and enter the rate your facility specifies (broadcast HD ingests typically run 25–185 Mbit/s depending on the codec wrapped). Choose "Variable Bitrate" for more efficient files, "Constant Quality" (CRF 18 is visually lossless for H.264) for archival, "Constraint Quality" (CRF + max bitrate) when you need a ceiling, "Specific file size" for hard delivery caps, or "Target file size (%)" to scale by percentage of source.
3. Set Resolution and Trim (Optional): Under "Video resolution," keep original, pick a Preset Resolution (2160p, 1440p, 1080p, 720p, 480p), use "Resolution Percentage" to scale by a multiplier, or enter exact "Width x Height." Under "Trim," switch from "Unchanged" to "Time Range" to extract a clip — useful for pulling a single take out of a long camcorder span.
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.

Why Convert AVCHD to MXF?

AVCHD is the consumer/prosumer camcorder format jointly developed by Sony and Panasonic in 2006, using H.264/AVC (Main or High Profile, Level 4.1 or 4.2) inside an MPEG-2 transport stream and capping at 24 Mbit/s for interlaced and 28 Mbit/s for progressive recording. MXF (Material eXchange Format), standardized as SMPTE 377M in September 2004, is the professional broadcast and post-production wrapper used by TV stations, film studios, archive facilities, and Media Asset Management systems. The two formats serve different ends of the same pipeline, so transcoding from one to the other is a routine step the moment camcorder footage enters a professional workflow.

• Avid Media Composer ingest — Media Composer's native essence is MXF (OP-Atom and OP-1A operational patterns). Although recent versions can edit AVCHD natively via AMA, transcoding to MXF up-front gives faster timeline performance, cleaner media management in the bin, and a single codec across the project.
• Broadcast delivery — TV stations, playout servers, and station automation systems (Imagine, Grass Valley, Harmonic) typically require MXF wrapping for delivery, often as OP-1A. AVCHD straight off a camcorder is rarely accepted.
• DaVinci Resolve color and finishing — Resolve supports AVCHD MTS and MXF OP-1A/OP-Atom for MPEG-2 and D-10 IMX, but real-world AVCHD imports often fail on audio or render slowly. A pre-transcode to MXF wrapping a mezzanine codec sidesteps the issue.
• Archive and Media Asset Management — MXF is the SMPTE-blessed container for long-term archive (PBCore, FIMS, IMF workflows). Storing camcorder footage as MXF preserves rich metadata — timecodes, descriptors, multi-track audio — that a transport stream can't carry as cleanly.
• DNxHD/DNxHR mezzanine workflows — Avid's DNxHD (SMPTE VC-3, ratified 2008) is typically stored in MXF and is the standard intermediate for cross-NLE collaboration when ProRes isn't an option (Windows, Linux, Avid).
• Delivering to facilities that won't take H.264 — Many post houses reject long-GOP H.264 source files. Re-wrapping or transcoding AVCHD into MXF with a broadcast-friendly codec is the path to acceptance.

AVCHD vs MXF — Format Comparison

Codec and Quality Settings Quick Guide

Frequently Asked Questions

What is MXF actually used for, and why do broadcasters insist on it?

MXF is the SMPTE 377M wrapper specifically designed in the early 2000s for professional video exchange between systems that need to agree on essence layout, timecode, and metadata. Avid Media Composer uses OP-Atom MXF as its native bin format. Broadcast playout servers from Imagine, Grass Valley, and Harmonic typically require OP-1A. Archive and MAM systems standardize on MXF because the wrapper carries the structural metadata (UMIDs, descriptors, KLV) that an MPEG-2 transport stream like AVCHD doesn't.

Will Avid Media Composer accept the MXF this tool produces?

Avid Media Composer specifically requires OP-Atom or OP-1A operational patterns. The MXF this tool produces is OP-1A wrapped, which Media Composer ingests directly. If your facility specifically requires OP-Atom (rare, but some legacy Avid environments enforce it), you may need to re-wrap with Avid's own tools or use Media Composer's "Consolidate/Transcode" once imported.

Should I transcode AVCHD to MXF, or just edit the.mts files natively in my NLE?

It depends on the editor and your performance bar. Premiere Pro CS5+ ingests AVCHD.mts directly, but renders and timeline scrubbing on long-GOP H.264 are noticeably slower than on a mezzanine codec like DNxHD or ProRes wrapped in MXF. DaVinci Resolve technically supports AVCHD but has well-documented issues with audio tracks dropping or imports failing on certain camcorder variants. For anything beyond a quick rough-cut, transcoding to MXF up-front is the standard professional workflow.

What codec gets wrapped inside the MXF — DNxHD, MPEG-2, AVC-Intra?

This converter wraps H.264/AVC inside the MXF container by default, which preserves quality near the AVCHD source while gaining MXF's metadata and operational-pattern benefits. For Avid-only workflows that demand DNxHD specifically, you'd typically use Avid's own Media Composer transcode or a dedicated tool like Avid Media Access. The MXF produced here is broadly compatible with Resolve, Premiere Pro, and broadcast playout systems but is not a 1:1 substitute for Avid-native DNxHD MXF.

Will my original AVCHD timecodes and 5.1 audio survive the conversion?

Audio: stereo and most multichannel layouts pass through. AC-3 5.1 from consumer camcorders typically downmixes to stereo unless you re-wrap losslessly — verify in your NLE before locking the deliverable. Timecode: AVCHD timecode metadata doesn't always map cleanly into MXF's timecode track during a re-encode. If timecode preservation is critical (e.g., conforming a multicam shoot back to source), test one clip end-to-end through your edit system before processing the full shoot.

How big will the MXF file be compared to the source AVCHD?

It depends entirely on the compression setting. At "Quality Preset: Very High" with no resolution change, expect MXF roughly the same size as source (within ±20%) — MXF wrapping adds slight overhead but the H.264 essence is similarly efficient. Switching to a broadcast CBR setting at 50 Mbit/s on 1080p source will roughly double the file size. Constant Quality (CRF 18) typically produces files 30–60% smaller than equivalent CBR for similar perceptual quality.

Can I trim, scale, or change frame size during the conversion?

Yes. The "Trim" control accepts a start time and duration to pull a sub-clip — useful for grabbing a single take out of a long camcorder span before ingest. "Video resolution" lets you keep the original, drop to a preset (1080p, 720p, etc.), scale by percentage, or set a custom Width x Height. Aspect ratio is locked when you change only width or only height; use "Width x Height" if you specifically want to change framing.

What's the difference between this and converting to MP4 or MOV?

MP4 and MOV are general-purpose containers tuned for distribution, web playback, and cross-platform compatibility. MXF is tuned for production exchange — it carries metadata, operational patterns, and multi-track audio that distribution containers don't expose cleanly. For broadcast delivery, Avid ingest, or archive, MXF is the right answer. For editing in FCP X, sharing, or web upload, AVCHD to MOV or AVCHD to MP4 is the more practical choice. If you're starting from camera SD card files specifically, MTS to MXF handles the same conversion under the camcorder-side filename.

What if I just need a smaller MXF, not a format change from AVCHD?

If you already have MXF and need to reduce size for delivery or storage, use Compress MXF instead — it keeps the wrapper intact and re-encodes only the essence. To shrink AVCHD before transcoding, Compress AVCHD reduces the.mts source first.