DNxHD

DNxHD is Avid's intra-frame HD video codec, wrapped in MXF or MOV, built to give offline-friendly file sizes with online-editing image quality inside Avid and third-party NLEs.

Extension

.mxf

Full name

Avid DNxHD

Introduced

2004; standardized by SMPTE as VC-3 in February 2008

Vendor

Avid Technology

What is inside the container

DNxHD is a codec, most commonly wrapped in MXF (OP-Atom, Avid's native pattern) or MOV, and defined for fixed HD resolutions (720p/1080i/1080p) at selectable bitrates and bit depths (8-bit or 10-bit). Like ProRes, it uses intra-frame compression so every frame is independently editable, and it was the first codec accepted as compliant with the SMPTE VC-3 standard, giving it a formally documented, vendor-independent specification alongside its Avid implementation.

How to open it

Windows/Mac Avid Media Composer natively encodes and decodes DNxHD

Cross-platform editing Adobe Premiere Pro and DaVinci Resolve decode and encode DNxHD via the free Avid DNxHD/DNxHR codec pack

Playback VLC and FFmpeg-based players decode DNxHD without requiring Avid software

Transcoding Avid Media Encoder or FFmpeg batch-convert DNxHD to/from other mezzanine or delivery codecs

For archives

DNxHD (particularly DNxHD 175/220 10-bit) is a solid archival mezzanine codec for Avid-centric production pipelines, valued for its documented SMPTE VC-3 specification and intra-frame editability; since Avid superseded it with the resolution-independent DNxHR for anything above 1080p, keep DNxHD reserved for genuinely HD-resolution assets rather than upscaling into it. As with any MXF-wrapped codec, record the operational pattern (commonly OP-Atom for Avid media) alongside the codec profile in metadata.

Avid introduced DNxHD in 2004 as its answer to the same problem Apple’s ProRes would address a few years later: HD source footage was too heavy to edit comfortably in real time on the hardware of the mid-2000s, so Avid designed an intra-frame codec that preserved near-source quality at a fraction of uncompressed file sizes. Avid then submitted the codec to SMPTE for standardization, and in February 2008 DNxHD became the first codec formally compliant with the resulting SMPTE VC-3 standard — giving it a documented, vendor-independent specification beyond Avid’s own implementation.

Because Avid built its entire Media Composer ecosystem around DNxHD, and because Avid released the codec pack freely for other NLEs to decode and encode, DNxHD became the standard mezzanine codec for broadcast and episodic television post-production, particularly in workflows that move footage between multiple editorial and finishing tools. Its MXF OP-Atom wrapping — separate essence files for video and each audio channel — reflects Avid’s own media management model, distinct from ProRes’s typical single-file MOV wrapping.

In a DAM supporting broadcast or episodic post-production, DNxHD assets usually represent editorial or delivery masters from an Avid pipeline, and they carry real archival value precisely because of the VC-3 standardization — future decoders have a public specification to work from, not just a proprietary Avid implementation. Since Avid has since introduced the resolution-independent DNxHR for 2K/4K/UHD work, a DAM should treat DNxHD specifically as the HD-resolution predecessor and avoid conflating the two when validating or transcoding assets.

Frequently asked

Is DNxHD typically found in MXF or MOV wrappers in a DAM's library?

Most commonly MXF, specifically the OP-Atom operational pattern that is Avid's native wrapping pattern, though it can also appear in MOV — a DAM should record which wrapper a given DNxHD asset uses since that affects tooling compatibility.

Why does DNxHD's SMPTE standardization matter for long-term archival trust?

DNxHD was the first codec accepted as compliant with the SMPTE VC-3 standard in February 2008 after a two-year validation process, giving it a formally documented, vendor-independent specification beyond Avid's own implementation.

Should a DAM use DNxHD for 4K or UHD assets?

No — DNxHD is defined only for fixed HD resolutions (720p/1080i/1080p); Avid superseded it with the resolution-independent DNxHR for anything above 1080p, so a DAM should reserve DNxHD for genuinely HD-resolution assets rather than upscaling into it.

What metadata should accompany a DNxHD asset in a DAM?

In addition to codec profile and bit depth, a DAM record should capture frame rate, resolution (720p, 1080i, or 1080p, since DNxHD is HD-only), the specific bitrate/quality tier (e.g., DNxHD 36 through 220x), color space (YCbCr 4:2:2), and the timecode start. Timecode start matters most: it lets editors relink the archived master back to the original Avid bin frame-for-frame during a later conform, without drift.

What editing tools can work with DNxHD without owning Avid Media Composer?

Adobe Premiere Pro and DaVinci Resolve decode and encode DNxHD via the free Avid DNxHD/DNxHR codec pack, and VLC or FFmpeg-based players decode it without requiring Avid software at all.

Why does DNxHD use intra-frame compression, and what does that mean for editing workflows?

DNxHD compresses every frame independently with DCT-based intra-frame compression, much like a sequence of JPEG stills, rather than referencing neighboring frames the way inter-frame/long-GOP codecs such as H.264 do. Because no frame depends on decoding others around it, the NLE only has to unpack the single frame being displayed. That makes scrubbing and frame-accurate trimming fast and responsive, which is exactly what demanding online and offline editing workflows need.

What archival quality tier of DNxHD is recommended?

DNxHD 220 — and its 10-bit sibling DNxHD 220x — sits at the top of Avid's mastering-codec range, which also includes 145, 175, 185/185x, and the still-higher 440/440x. It's the tier most often recommended for an archival master: at roughly 220 Mb/s the high bitrate keeps DCT quantization loss minimal, and 220x's 10-bit depth preserves finer color and gradient detail than 8-bit offline tiers like DNxHD 36, making it the safer long-term mezzanine choice.

What production context most commonly delivers DNxHD assets to a DAM?

DNxHD assets most commonly arrive in a DAM from post-production studios and editorial houses running Avid Media Composer as their primary NLE. Avid built DNxHD specifically for tight, native integration with Media Composer, so files typically show up wrapped as MXF OP-Atom straight from an editing timeline. Broadcast, film, and episodic-TV finishing facilities are the typical source, delivering mezzanine or archival masters generated during offline/online conform rather than raw camera acquisition.

Sources

On February 13, 2008, Avid announced that DNxHD was the first codec approved as compliant with the SMPTE VC-3 standard, after a two-year testing and validation process. checked 2026-08-07 — Avid Technology press release via Sports Video Group
Avid DNxHD is Avid's intra-frame HD codec, later complemented by the resolution-independent DNxHR for 2K, UHD, and 4K workflows. checked 2026-08-07 — Wikipedia: DNxHR codec