A Video Editor's Guide to Ingest and Delivery Formats (MXF, M2TS, MP4)
A typical multi-camera shoot lands on your desk as a mess of formats. The A-cam shot in ProRes on CFast cards — you've got MXF files. The B-cam is a consumer Sony that recorded AVCHD — M2TS files in a nested folder structure. Someone's phone footage came as MP4. The drone shot 4K in H.265. And the audio recorder saved 24-bit WAV files at 48 kHz.
This is every freelance editor's Tuesday. Knowing which formats to transcode, which to edit natively, and which to convert on delivery saves you hours of troubleshooting.
Ingest formats: what cameras actually produce
MXF (Material Exchange Format) — the broadcast and cinema standard. Used by ARRI, RED (via REDCODE in R3D, though they also export to MXF), Sony XDCAM, Panasonic P2, Canon Cinema EOS (C300 Mark III, C70), and Blackmagic cameras. MXF is a container — it can hold almost any codec: ProRes, DNxHR, XDCAM HD, AVC-Intra, MPEG-2, even H.264. The format was designed for professional interchange, with rich metadata support (timecode, reel names, camera metadata).
M2TS / AVCHD — consumer and prosumer HD camcorders from roughly 2006-2015. Sony Handycam, Panasonic HC series, Canon VIXIA. H.264 video in an MPEG-2 Transport Stream container. Bitrates typically max at 28 Mbps (AVCHD 2.0). Still shows up regularly when clients hand over old event footage or corporate recordings.
MP4 — phones, GoPros, DJI drones, newer consumer camcorders (Sony XAVC S), and many mirrorless cameras. Contains H.264 or H.265 video. Bitrates range from 20 Mbps (phone footage) to 200+ Mbps (cinema cameras in H.264 All-I mode). The most universally readable format.
MOV — Apple cameras and many cinema cameras. Can contain ProRes (from iPhones in ProRes mode, from Atomos recorders, from ARRI cameras) or H.264/H.265 (from iPhones in normal mode, from DSLRs). Same underlying structure as MP4 with Apple-specific extensions.
Should you transcode before editing?
The answer depends on your hardware and your NLE (non-linear editor):
Premiere Pro — handles everything natively. H.264, H.265, MXF with most codecs, M2TS, MOV, ProRes. The only format that gives Premiere trouble is R3D (RED raw), which needs the RED codec plugin. For long-form projects (30+ minutes), generating proxies in Premiere saves a lot of timeline lag, especially with 4K H.265 and higher.
DaVinci Resolve — excellent native format support in the paid Studio version. The free version can't decode H.265 on some systems. Resolve's Optimized Media feature is its version of proxies — it transcodes to DNxHR or ProRes in the background while you keep working.
Final Cut Pro — transcodes everything to ProRes on import by default (you can turn this off). This means the source format barely matters in FCP — whether you feed it MXF, M2TS, or MP4, it's all ProRes on the timeline. The downside is that import takes time and the library gets very large.
Avid Media Composer — historically required transcoding to DNxHD/DNxHR before editing. Modern versions (2023+) support AMA (Avid Media Access) linking to native formats, but performance is still better with transcoded media. Most Avid shops still transcode on ingest.
Intermediate codecs: ProRes vs DNxHR
These are the two dominant editing codecs, and they serve the same purpose — fast, efficient decoding that doesn't tax your system during editing:
Apple ProRes — ProRes 422 Proxy (smallest), 422 LT, 422, 422 HQ, 4444, 4444 XQ (largest, highest quality). ProRes 422 is the standard for most editing. ProRes 4444 preserves alpha channels and higher color depth for VFX work. ProRes works natively on Mac in all NLEs. On Windows, Premiere Pro and Resolve can decode it, and Resolve Studio can encode it.
Avid DNxHR — LB (smallest), SQ, HQ, HQX, 444 (largest). Functionally equivalent to ProRes at each quality tier. Cross-platform without restrictions — encodes and decodes on Windows, Mac, and Linux. If you're on Windows, DNxHR avoids the ProRes encoding limitations.
For most editing work, ProRes 422 or DNxHR SQ are the go-to choices. They produce files about 8-10x larger than the H.264 source, which sounds wasteful but the editing performance gain is significant. A 1-hour 1080p project in ProRes 422 uses about 66 GB of storage — plan your drive space accordingly.
Delivery formats: what clients and platforms expect
Web / social media — H.264 in MP4, 1080p or 4K, 8-20 Mbps. Every platform re-encodes your upload, so give them the highest quality you can within their file size limits. YouTube recommends H.264 High Profile for best results after their re-encode.
Broadcast — varies by network and region. US broadcast often wants ProRes 422 HQ or DNxHR HQ in a MOV or MXF container. Some networks accept XDCAM HD (50 Mbps MPEG-2 in MXF). Always get the delivery spec sheet from the network — wrong format means rejection and re-delivery.
Streaming platforms (Netflix, Amazon, Disney+) — Netflix's spec requires ProRes 422 HQ or DNxHR 444 as the mezzanine delivery format. They handle their own encoding to H.264/H.265/AV1 for different device profiles. Amazon and Disney+ have similar requirements.
Client review / rough cuts — H.264 in MP4, 1080p, 5-8 Mbps. Small files that stream easily. Add a visible watermark and timecode overlay for review copies.
Dealing with mixed-format projects
When a project has footage from multiple sources in different formats, you have two workflows:
Native editing — import everything as-is, let the NLE handle the format differences. Works well for short projects (under 10 minutes) on modern hardware. Premiere Pro handles this best. The risk is timeline performance — scrubbing through a mix of 4K H.265 drone footage and 1080p AVCHD and iPhone MP4 can chug on a mid-range machine.
Transcode-first workflow — convert everything to one intermediate codec (ProRes 422 or DNxHR SQ) at one resolution and frame rate before importing to the timeline. Takes time upfront but editing is smooth and there are no surprises at export. This is the standard approach in broadcast and narrative work.
A hybrid approach works too: edit natively with proxy generation turned on. You work with lightweight proxy files on the timeline and the NLE swaps in the full-resolution originals at export time. Premiere Pro, Resolve, and FCP all support this.
For mixed frame rate projects (24fps cinema camera mixed with 30fps B-cam and 60fps drone), set your timeline to the primary camera's frame rate. Footage at other rates will be conformed — 60fps clips dropped to 30fps or 24fps lose the smooth motion but look fine, and 24fps clips on a 30fps timeline get pulldown added. Frame rate mismatches are cosmetic issues, not quality problems.
Quick reference: common format conversions
MXF to MP4 — for delivering broadcast footage to clients who just want a viewable file. See our MXF to MP4 guide.
M2TS to MP4 — for making old AVCHD camcorder footage usable. See the AVCHD to MP4 conversion guide.
MOV to MP4 — for sharing Apple-format files with Windows users. Often just a remux (container change) with zero quality loss. Use the MOV to MP4 converter.
MP4 to ProRes/DNxHR — transcoding for editing. Best done in your NLE's media management tools (Premiere's proxy workflow, Resolve's Optimized Media, FCP's transcode on import) rather than with a separate converter.
MP4 to MP3 — for extracting audio from video. Useful when you only need the soundtrack, interview audio, or lecture content. See our MP4 to MP3 guide.
MPG to MP4 — for modernizing old DVD rips and broadcast captures. See our MPG vs MP4 comparison.
FAQ
Does the container format affect video quality?
No. The container (MXF, MP4, MOV, M2TS) is just the wrapper. The codec inside (H.264, ProRes, MPEG-2) determines quality. The same H.264 stream looks identical whether it's in an MP4 or MOV container.
Why do broadcast cameras use MXF instead of MP4?
MXF supports richer metadata (timecode, camera ID, reel names), handles multi-channel audio better, and is designed for professional archive and interchange workflows. MP4 was designed for consumer playback.
Can I edit H.265 footage directly?
Yes, but it's CPU-intensive. H.265 decode requires roughly 2-3x more processing power than H.264. A modern desktop (M2 Pro Mac, recent Intel i7/i9 or AMD Ryzen 7/9) handles 4K H.265 fine. Older machines should use proxies.
What's the best export format for YouTube?
H.264 High Profile in MP4, at YouTube's recommended bitrates: 8 Mbps for 1080p30, 12 Mbps for 1080p60, 35-45 Mbps for 4K. Upload the highest quality — YouTube re-encodes to VP9 and AV1, and better source quality means better results after their re-encode.
Convert your footage
MXF, M2TS, MOV — convert any camera format to MP4 for delivery or playback.