What Is DNxHD? Avid's DNxHD and DNxHR Codecs Explained
What Is DNxHD? The Short Answer
DNxHD is Avid's professional editing codec. It compresses each video frame independently at a high, fixed data rate, so footage plays back and scrubs smoothly in an editor and keeps its quality through repeated renders. SMPTE standardized it as VC-3 (ST 2019-1) in 2008, and it's the Avid-world counterpart to Apple's ProRes.
DNxHD only works at HD sizes (1920x1080 and 1280x720) and specific frame rates. For anything bigger, Avid added DNxHR in 2014, which works at any resolution. Recent Avid documentation groups both under a single name, Avid DNx.
Three things to know up front:
- It's an intermediate codec, not a delivery codec. DNxHD files are 10 to 20 times larger than an H.264 export of the same video. You edit in it, then export something smaller.
- It's visually lossless, not lossless. The higher profiles look identical to the source, but the data isn't bit-for-bit the same.
- The container matters. DNxHD lives in MXF (Avid's native wrapper) or MOV. It can't go in an MP4.
If codecs in general are new to you, start with what a codec is in video.
DNxHD vs DNxHR: Same Codec, Different Rules
Avid introduced DNxHD in 2004 with its DS Nitris and Media Composer Adrenaline systems. SMPTE approved it as VC-3 in 2008, and that standard covers the bitstream format (ST 2019-1) and how it maps into MXF (ST 2019-4).
DNxHD was built for HD broadcast, so every profile is tied to a fixed frame size, frame rate and bitrate. When 2K and 4K cameras arrived, Avid announced DNxHR ("HR" for high resolution) in September 2014. SMPTE added it to the VC-3 standard in its 2016 revision as a resolution-independent profile.
| DNxHD | DNxHR | |
|---|---|---|
| Resolutions | 1920x1080, 1280x720 (plus 1440x1080 and 960x720 thin-raster variants) | Any, including 2K, UHD, 4K DCI and above |
| Frame rates | Fixed list per profile | Any |
| Profile names | Bitrate-based: DNxHD 36, 115, 175, 220x... | Quality levels: LB, SQ, HQ, HQX, 444 |
| Bit depth | 8-bit, or 10-bit for "x" profiles | 8-bit (LB, SQ, HQ), 10/12-bit (HQX, 444) |
| Chroma | 4:2:2 (plus a 4:4:4 option) | 4:2:2, or 4:4:4 for the 444 level |
At 1080p the two produce the same data rates. In FFmpeg, DNxHR HQ at 1080p 23.976 encoded at exactly the same 176 Mbps as DNxHD 175. The difference is that DNxHR doesn't care what resolution or frame rate you give it.
DNxHD Profiles: What the Numbers Mean
DNxHD profile names are the approximate bitrate in megabits per second at a given frame rate. An "x" suffix means 10-bit; no suffix means 8-bit.
The confusing part is that the same compression setting has different names at different frame rates. Each profile stores a fixed number of bytes per frame, so more frames per second means a higher bitrate and a different name. DNxHD 175, 185 and 220 are the same quality setting at 23.976, 25 and 29.97 fps.
Here are the 1920x1080 progressive profiles, from Avid's published resolution list:
| Quality family | 23.976 / 24p | 25p | 29.97p | 50p | 59.94p | Bit depth |
|---|---|---|---|---|---|---|
| Offline | DNxHD 36 | DNxHD 36 | DNxHD 45 | DNxHD 75 | DNxHD 90 | 8-bit |
| Standard | DNxHD 115 | DNxHD 120 | DNxHD 145 | DNxHD 240 | DNxHD 290 | 8-bit |
| High | DNxHD 175 | DNxHD 185 | DNxHD 220 | DNxHD 365 | DNxHD 440 | 8-bit |
| High, 10-bit | DNxHD 175x | DNxHD 185x | DNxHD 220x | DNxHD 365x | DNxHD 440x | 10-bit |
| Highest, 10-bit | DNxHD 350x | DNxHD 365x | DNxHD 440x | — | — | 10-bit |
A few notes:
- DNxHD 36 was designed for offline editing: cutting with small files, then relinking to full-quality media for the finish. It's the ancestor of today's proxy workflows.
- DNxHD 80, 85 and 100 are "thin raster" profiles that store 1440x1080 and stretch it on playback. Avoid them unless a spec asks for them.
- 720p and interlaced 1080i formats have their own profile lists (DNxHD 60, 90x, 110x and so on).
DNxHR Profiles: LB, SQ, HQ, HQX and 444
DNxHR replaces the bitrate names with five quality levels. Each level keeps a fixed amount of data per pixel, so the bitrate scales with resolution and frame rate. We measured these rates by encoding with FFmpeg 9's DNxHR encoder, which follows the VC-3 frame sizes, and they match Avid's published figures:
| Level | Chroma and bit depth | 1080p 29.97 | UHD 23.976 | UHD 29.97 | Typical use |
|---|---|---|---|---|---|
| DNxHR LB (Low Bandwidth) | 4:2:2, 8-bit | 45 Mbps | 144 Mbps | 180 Mbps | Proxies and offline editing |
| DNxHR SQ (Standard Quality) | 4:2:2, 8-bit | 145 Mbps | 462 Mbps | 577 Mbps | Everyday editing, camera-native acquisition |
| DNxHR HQ (High Quality) | 4:2:2, 8-bit | 220 Mbps | 698 Mbps | 873 Mbps | Mastering 8-bit sources |
| DNxHR HQX (High Quality 10/12-bit) | 4:2:2, 10 or 12-bit | 220 Mbps | 698 Mbps | 873 Mbps | HDR, log footage, color grading |
| DNxHR 444 | 4:4:4, 10 or 12-bit, RGB | 440 Mbps | 1,398 Mbps | 1,747 Mbps | VFX, graphics, finishing masters |
HQ and HQX have the same bitrate. Avid's own notes say HQX uses gentler quantization tuned for more than 8 bits, so it's the one to pick for 10-bit log or HDR footage. For 8-bit sources, HQ is fine.
Two caveats if you encode with FFmpeg:
- FFmpeg's encoder writes LB, SQ and HQ as 8-bit (
yuv422p) and HQX and 444 as 10-bit (yuv422p10le,yuv444p10le). Avid's own encoder can produce 12-bit HQX and 444. - FFmpeg's encoder has no alpha channel output. If you need transparency for graphics, use ProRes 4444 instead.
Is DNxHD Lossless?
No. DNxHD and DNxHR are lossy, DCT-based codecs, much like a high-quality Motion JPEG. At SQ and above they are designed to be visually lossless: you won't see compression artifacts in normal viewing, and footage holds up through several render generations.
But the decoded frames aren't identical to the source. When we compared DNxHR LB, SQ and HQ encodes back to the original with FFmpeg's PSNR filter, none came back as identical, and HQ scored higher than LB, as expected. LB in particular is meant for proxies, not masters.
If you need real lossless video for archiving, our guide to lossless video compression covers FFV1 and other options.
DNxHD File Size per Minute
Because DNxHD and DNxHR run at a constant bitrate, file size is easy to predict: megabits per second x 60 / 8 = megabytes per minute. These figures use the bitrates we measured, for video only:
| Level | 1080p 23.976 | 1080p 29.97 | UHD 23.976 | UHD 29.97 |
|---|---|---|---|---|
| LB | 271 MB/min | 339 MB/min | 1.08 GB/min | 1.35 GB/min |
| SQ | 872 MB/min | 1.09 GB/min | 3.46 GB/min | 4.33 GB/min |
| HQ / HQX | 1.32 GB/min | 1.65 GB/min | 5.24 GB/min | 6.55 GB/min |
| 444 | 2.64 GB/min | 3.30 GB/min | 10.48 GB/min | 13.10 GB/min |
Stereo 24-bit, 48 kHz PCM audio adds about 17 MB per minute. Our test files matched these numbers closely: a 4-second DNxHR HQ clip at 1080p 30 fps with stereo audio came out at 110.8 MB.
An hour of UHD 29.97 DNxHR HQ is about 393 GB, which is why proxies exist. For other codecs and bitrates, use our video file size calculator, and see what video bitrate means for the background.
DNxHD vs ProRes
DNxHD and ProRes do the same job, and Avid and Apple sized their tiers almost identically. At 1080p 29.97 the match is close to exact:
| Tier | Avid DNx | 1080p 29.97 | UHD 23.976 | Apple ProRes | 1080p 29.97 | UHD 23.976 |
|---|---|---|---|---|---|---|
| Proxy | DNxHR LB / DNxHD 45 | 45 Mbps | 144 Mbps | ProRes 422 Proxy | 45 Mbps | 145 Mbps |
| Standard | DNxHR SQ / DNxHD 145 | 145 Mbps | 462 Mbps | ProRes 422 | 147 Mbps | 471 Mbps |
| High | DNxHR HQ, HQX / DNxHD 220(x) | 220 Mbps | 698 Mbps | ProRes 422 HQ | 220 Mbps | 707 Mbps |
| 4:4:4 | DNxHR 444 | 440 Mbps | 1,398 Mbps | ProRes 4444 / 4444 XQ | 330 / 495 Mbps | 1,061 / 1,591 Mbps |
ProRes figures are Apple's target rates from its ProRes white paper. DNx has no direct equivalent to ProRes 422 LT (102 Mbps at 1080p 29.97). ProRes also varies its bitrate with image complexity, while DNx stays constant.
The real differences are in support:
| You work in... | Pick | Why |
|---|---|---|
| Final Cut Pro, or Mac-only workflows | ProRes | macOS decodes ProRes natively; DNx needs extra software (see below) |
| Avid Media Composer | DNxHR / DNxHD in MXF | It's Avid's native media; no transcoding or linking needed |
| Premiere Pro | Either | Premiere reads and exports both on Mac and Windows |
| DaVinci Resolve | Either | Resolve reads both; DNxHR is the usual pick on Windows and Linux |
| Mixed Windows and Mac teams | DNxHR | Encoding is well supported on every OS, while ProRes encoding outside Apple's tools varies by app |
| Broadcast delivery | Whatever the spec says | Broadcasters often specify a DNxHD profile in MXF OP1a or ProRes 422 HQ in MOV |
One Mac-specific point we tested: on macOS 27, Apple's AVFoundation framework, which QuickTime Player and Quick Look use, opened our DNxHD and DNxHR MOV files but reported the video as "Cannot Decode". If a colleague sends you DNx files and you work on a Mac, plan to open them in Premiere, Resolve or VLC, or transcode them. Our ProRes guide covers the Apple side of this comparison in more depth.
DNxHD MOV vs MXF: Which Wrapper?
DNxHD is the codec; MOV and MXF are the containers that hold it.
| Wrapper | Layout | Best for |
|---|---|---|
| MXF OP-Atom | One file per track: a video MXF plus one mono MXF per audio channel | Avid Media Composer's native media (Avid MediaFiles/MXF/) |
| MXF OP1a | Video and all audio in one file | Broadcast delivery, Premiere and Resolve exchange |
| QuickTime MOV | Video and audio in one file | Premiere, Resolve, general exchange between apps |
| MP4 | Not supported | FFmpeg refuses it (see below) |
We tried writing DNxHR to MP4 and FFmpeg stopped with Could not find tag for codec dnxhd in stream #0, codec not currently supported in container. Use .mov instead.
Our MXF file guide explains OP-Atom and OP1a in more detail, including how to open and convert camera MXF files.
How to Encode DNxHD and DNxHR with FFmpeg
FFmpeg has a built-in dnxhd encoder that writes both DNxHD and DNxHR. Every command below was run with FFmpeg 9.0 on a Mac. Start by checking what your source is:
ffprobe -v error -select_streams v:0 \
-show_entries stream=codec_name,profile,width,height,pix_fmt,r_frame_rate \
-of default=nw=1 input.mov
DNxHR HQ to MOV (any resolution, the safe default)
ffmpeg -i input.mp4 -c:v dnxhd -profile:v dnxhr_hq -pix_fmt yuv422p \
-c:a pcm_s16le output.mov
This works at 1080p, 1440p, UHD, 4K DCI, and non-standard sizes such as a 1920x800 crop. Swap dnxhr_hq for dnxhr_sq or dnxhr_lb to trade quality for size.
DNxHR HQX and 444 for 10-bit footage
# 10-bit 4:2:2 for log, HDR or iPhone/ProRes sources
ffmpeg -i input.mov -c:v dnxhd -profile:v dnxhr_hqx -pix_fmt yuv422p10le \
-c:a pcm_s24le output_hqx.mov
# 10-bit 4:4:4 for graphics and VFX
ffmpeg -i input.mov -c:v dnxhd -profile:v dnxhr_444 -pix_fmt yuv444p10le \
-c:a pcm_s24le output_444.mov
Classic DNxHD at 1080p
DNxHD has no profile names in FFmpeg. You pick it with a bitrate that matches the table above for your frame rate:
# 1080p 23.976: DNxHD 115 (8-bit)
ffmpeg -i input.mov -c:v dnxhd -b:v 115M -pix_fmt yuv422p -c:a pcm_s16le output.mov
# 1080p 23.976: DNxHD 175x (10-bit)
ffmpeg -i input.mov -c:v dnxhd -b:v 175M -pix_fmt yuv422p10le -c:a pcm_s24le output.mov
# 1080p 29.97: DNxHD 145
ffmpeg -i input.mov -c:v dnxhd -b:v 145M -pix_fmt yuv422p -c:a pcm_s16le output.mov
FFmpeg picks the quality family from the bitrate and then encodes at that family's real rate for your frame rate. In our tests, asking for -b:v 220M on a 23.976 fps clip produced DNxHD 175 at 176 Mbps, and -b:v 36M on a 59.94 fps clip produced DNxHD 90. It's still clearer to pass the name that matches your frame rate.
Fixing "video parameters incompatible with DNxHD"
This is the most common DNxHD FFmpeg error. Running the DNxHD encoder without a bitrate, on a 2560x1440 screen recording, on a 4K clip, or with a bitrate that doesn't exist at that size (like -b:v 100M at 1920x1080) prints:
[dnxhd @ 0x...] video parameters incompatible with DNxHD. Valid DNxHD profiles:
[dnxhd @ 0x...] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10
[dnxhd @ 0x...] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10
...
Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.
It also appears when you request an 8-bit-only bitrate such as -b:v 36M with -pix_fmt yuv422p10le. There are two fixes:
- Use DNxHR instead. Add
-profile:v dnxhr_hq -pix_fmt yuv422p. DNxHR has no size or frame rate restrictions. - Conform the video to a DNxHD format if a spec requires DNxHD:
ffmpeg -i screen.mp4 -vf "scale=1920:1080,fps=30000/1001" \
-c:v dnxhd -b:v 145M -pix_fmt yuv422p output.mov
Fixing "pixel format is incompatible with DNxHR LB/SQ/HQ profile"
If your source is 10-bit (ProRes, HEVC from an iPhone, most log footage) and you leave out -pix_fmt, FFmpeg keeps it 10-bit and DNxHR HQ refuses it. Either add -pix_fmt yuv422p to convert to 8-bit, or switch to -profile:v dnxhr_hqx -pix_fmt yuv422p10le to keep the 10 bits. HQX has the reverse rule: it rejects yuv422p with "pixel format is incompatible with DNxHR HQX profile".
Writing MXF OP1a
ffmpeg -i input.mp4 -c:v dnxhd -profile:v dnxhr_hq -pix_fmt yuv422p \
-c:a pcm_s24le -ar 48000 output.mxf
Keep -ar 48000. FFmpeg's MXF muxer only accepts 48 kHz audio. Our 44.1 kHz test file failed with "only 48khz is implemented" until we added it.
Writing MXF OP-Atom (one file per track)
OP-Atom takes exactly one stream per file, and audio must be mono. Write the video and each audio channel separately:
ffmpeg -i input.mp4 -map 0:v -c:v dnxhd -profile:v dnxhr_hq -pix_fmt yuv422p \
-f mxf_opatom clip_v1.mxf
ffmpeg -i input.mp4 -map 0:a -af "pan=mono|c0=c0" -c:a pcm_s24le -ar 48000 \
-f mxf_opatom clip_a1.mxf
ffmpeg -i input.mp4 -map 0:a -af "pan=mono|c0=c1" -c:a pcm_s24le -ar 48000 \
-f mxf_opatom clip_a2.mxf
Sending stereo audio straight in fails with "MXF OPAtom only supports single channel audio". Media Composer usually expects its own media database and metadata, so for real Avid projects, bringing files in through Media Composer's own import or linking is more reliable than dropping FFmpeg OP-Atom files into the MediaFiles folder. Check this on your version.
To go the other way and turn an MXF back into a MOV without re-encoding, ffmpeg -i clip.mxf -c copy clip.mov worked on our OP1a test file.
DNxHR LB proxies
ffmpeg -i input_4k.mov -vf scale=-2:1080 -c:v dnxhd -profile:v dnxhr_lb \
-pix_fmt yuv422p proxy.mov
Our guide to creating proxy files covers how to attach proxies in Premiere, Resolve and Final Cut.
Which DNxHD Codec Should You Use?
- Proxies or offline edit: DNxHR LB (or DNxHD 36/45 for HD-only Avid projects).
- Everyday editing of 8-bit camera or phone footage: DNxHR SQ.
- Masters from 8-bit sources: DNxHR HQ, or DNxHD 175/185/220 at 1080p.
- 10-bit log, HDR, or anything you'll grade hard: DNxHR HQX, or DNxHD 175x/185x/220x at 1080p.
- Graphics, VFX plates, RGB or 4:4:4 masters: DNxHR 444.
- A delivery spec names a profile: match it exactly, including the wrapper (MXF OP1a vs MOV).
In the apps, the settings are in these places:
- Premiere Pro: Export, then Format DNxHR/DNxHD MXF OP1a or QuickTime with the DNxHR/DNxHD codec. See our Premiere Pro export settings guide.
- DaVinci Resolve: Deliver page, Format QuickTime or MXF OP1A, Codec DNxHR (or DNxHD), then choose the level. Our DaVinci Resolve export settings guide explains the rest of the Deliver page.
- Final Cut Pro: It doesn't export DNx and needs third-party support to read it. Use ProRes instead; see exporting from Final Cut Pro.
Making Delivery Copies From DNxHD
Nobody watches DNxHD. Once the edit is done, you need a delivery file: H.264 or HEVC in an MP4 or MOV. Our HEVC vs H.264 comparison helps you choose. With FFmpeg:
# H.264 MP4, plays everywhere
ffmpeg -i master_dnxhr.mov -c:v libx264 -crf 18 -preset slow -pix_fmt yuv420p \
-c:a aac -b:a 192k -movflags +faststart delivery.mp4
# HEVC MP4 using the Mac's hardware encoder
ffmpeg -i master_dnxhr.mov -c:v hevc_videotoolbox -q:v 65 -tag:v hvc1 \
-c:a aac -b:a 192k delivery_hevc.mp4
On our test clip, a 110.8 MB DNxHR HQ file became a 4.5 MB H.264 MP4 and a 4.2 MB HEVC MP4. Test patterns compress unusually well, so expect less dramatic numbers on real footage, but a 10x or bigger reduction from an intermediate codec is normal.
Where Compresto Fits
Compresto is not a DNxHD encoder. It doesn't output DNxHD, DNxHR or ProRes, and it doesn't open .mxf files, so for creating DNx media or handling Avid MXF, use FFmpeg, Resolve, Premiere or Media Composer as shown above.
Where it helps is the step after. A DNxHD or DNxHR file in a .mov wrapper is a QuickTime movie (we confirmed macOS identifies our FFmpeg-encoded DNxHR test file as com.apple.quicktime-movie), which is a video input Compresto accepts. macOS's own frameworks can't decode DNx, so the in-app preview may stay blank; Compresto encodes through FFmpeg, but run one short clip through first before you queue a whole project. It can re-encode those masters to H.264 or HEVC in MP4 or MOV with hardware acceleration, downscale them, trim them, and target a specific file size for a client portal or upload form. It processes whole folders in a batch, and everything stays on your Mac. If your DNx media is in MXF, rewrap it to MOV first with ffmpeg -i clip.mxf -c copy clip.mov.
Frequently Asked Questions
What is DNxHD?
Avid's intra-frame editing codec, standardized by SMPTE as VC-3 (ST 2019-1). It compresses each frame independently at a high, fixed bitrate so footage edits smoothly and holds quality through re-renders. It covers 1920x1080 and 1280x720 only; DNxHR covers every other resolution.
What is the difference between DNxHD and DNxHR?
DNxHD is tied to fixed HD sizes and frame rates, with profiles named after their bitrate (36, 115, 175, 220x). DNxHR, introduced in 2014, works at any resolution and uses five quality levels: LB, SQ, HQ, HQX and 444. At 1080p the bitrates match.
Is DNxHD lossless?
No. It's lossy but visually lossless at SQ and above. Decoded frames differ slightly from the source. For true lossless video, use FFV1 or uncompressed.
DNxHD vs ProRes: which should I use?
Their data rates are nearly identical tier for tier. Use ProRes on a Mac and in Final Cut Pro, where it's natively supported. Use DNxHR for Avid Media Composer and mixed Windows/Mac teams. Premiere Pro and DaVinci Resolve handle both.
Should I wrap DNxHD in MOV or MXF?
MXF for Avid (OP-Atom) and broadcast delivery (OP1a); MOV for Premiere, Resolve and general exchange. MP4 doesn't support DNxHD at all.
Why does FFmpeg say "video parameters incompatible with DNxHD"?
Classic DNxHD only accepts specific sizes, frame rates, bitrates and pixel formats. Switch to DNxHR with -profile:v dnxhr_hq -pix_fmt yuv422p, or scale to 1920x1080 at a supported frame rate and pass a matching -b:v such as 115M or 145M.
The Short Version
DNxHD is Avid's VC-3 editing codec for HD, and DNxHR is its resolution-independent successor with five levels: LB, SQ, HQ, HQX and 444. Both are intra-frame, visually lossless and large: about 1.65 GB per minute for HQ at 1080p 29.97, almost exactly matching ProRes 422 HQ. Use MXF for Avid and broadcast, MOV for everything else, and never MP4. In FFmpeg, -profile:v dnxhr_hq -pix_fmt yuv422p avoids nearly every DNxHD error. When the edit is done, export an H.264 or HEVC copy for sharing.