Quick answer: a file extension is not enough to tell whether DaVinci Resolve supports a clip. Check the container, video codec, audio codec, profile and bit depth, then match those streams to your operating system, Free or Studio edition, hardware, and the correct Decode or Encode column. An `.mp4` file can work, import as audio only, or fail completely because MP4 is the box, not the video inside it.
For a compatibility check, read the file with MediaInfo and compare the result with Blackmagic's official matrix. Do not rely on the extension, the camera brand, or a list that combines macOS, Windows and Linux into one yes/no answer.
One source limitation matters in 2026. The latest authentic desktop matrix I could verify on August 27 is Blackmagic's DaVinci Resolve 20 Supported Formats and Codecs, dated July 2025. Blackmagic has not exposed a separately titled Resolve 21 matrix in the observable source set. I use the real document as the baseline and name its version instead of silently relabeling it.
This page owns the cross-platform reference intent. If one MP4 already fails, use the MP4 import repair guide for the symptom-first workflow. The Resolve workflow hub connects this reference to ingest, proxy, playback and delivery tasks.
The six checks behind “supported”
| Check | Example | Why it changes the answer |
|---|---|---|
| Container | MP4, MOV, MKV, MXF | Defines the package, not every stream it may contain |
| Video codec | H.264, H.265/HEVC, AV1, ProRes, DNxHR | Resolve must be able to decode or encode that stream |
| Profile and bit depth | Main 10, 10-bit, 4:2:2 | Support can differ inside one codec family |
| Audio codec | AAC, PCM, MP3, FLAC | Video and audio support are independent |
| Platform and edition | Windows Free, macOS Studio, Rocky Linux | The official rows differ by OS and license |
| Hardware | Supported GPU decoder/encoder | GPU-accelerated rows still depend on the actual device and driver |
The official matrix adds two more distinctions: alpha export and codec passthrough. Those matter for transparency and finishing, but they are not substitutes for Decode and Encode. A codec can be readable without being available as a Deliver output.
Read the actual streams with MediaInfo
Open the source in MediaInfo and switch to Tree or Text view. Record these fields as separate claims:
- General Format: the container, such as MPEG-4.
- Video Format: the codec, such as AVC/H.264 or HEVC/H.265.
- Format profile and Bit depth: the profile that can cross a Free/Studio or hardware boundary.
- Chroma subsampling: commonly 4:2:0 or 4:2:2, another profile detail worth recording.
- Frame rate mode: Constant or Variable. Variable frame rate is a playback and sync risk even when the codec decodes.
- Audio Format: AAC, PCM, MP3, FLAC or another independent stream.
This example is not a claim that every HEVC Main 10 MP4 fails. It shows why two files ending in `.mp4` can behave differently. Renaming `clip.mkv` to `clip.mp4` changes the label, not the streams. Rewrapping moves compatible streams into another container; transcoding creates new encoded streams.
Common codec support by desktop platform
The compact table below summarizes the July 2025 official matrix. It is intentionally not a complete replacement for the PDF. Camera-specific RAW families, IMF/DCP, image sequences, alpha, passthrough and professional profile details still require the source table.
| Platform | H.264 / H.265 | AV1 | AAC audio |
|---|---|---|---|
| macOS | Decode and encode listed as GPU accelerated for MOV, MKV and MP4 | Decode Yes; Encode not listed | Decode and encode listed |
| Windows 10 | H.264: 8-bit OS-supported profiles. H.265: 8/10-bit OS-supported profiles. Studio adds more profiles and GPU acceleration | Decode and encode listed as GPU accelerated | Decode and encode listed |
| Rocky Linux 8.6 CUDA | Decode marked Studio Only with Nvidia acceleration; encode marked Studio and Nvidia graphics | Decode and encode require Nvidia GPU acceleration | Not listed for decode or encode |
“OS-supported profiles” is deliberate wording. On Windows, Resolve relies partly on codecs exposed by the operating system, while Studio adds profiles and acceleration. A blanket claim that all 10-bit H.265 is Studio-only on Windows contradicts the official row. The precise camera profile and installed hardware still decide the real result.
The Linux section is narrower than generic “Linux support.” Blackmagic names Rocky Linux 8.6 (CUDA) and Nvidia graphics in the H.264, H.265 and AV1 rows. Do not convert that into a promise for every distribution, package or GPU. The Resolve 21 system requirements guide owns installation and hardware compatibility.
Audio, alpha and passthrough need their own checks
A video container can be accepted while one stream inside it is not. The official macOS and Windows audio sections list constant-bit-rate MP3, AAC variants, FLAC, and OPUS decode, with Encode availability shown separately. The Rocky Linux section lists MP3 and FLAC but leaves AAC decode and encode blank. That is why a “supported MP4” table that ignores audio can still lead to silent exports or import failures.
When a destination requires a specific audio format, read the Audio row and the container note together. For example, embedded audio choices depend on what the selected video container permits. Do not assume that an audio codec available as a standalone file is available inside every MOV, MP4 or MXF output.
Alpha is another separate capability. The matrix has an Alpha Exports column because a codec that carries ordinary RGB/YUV video may not preserve transparency. Match the exact codec profile and container required by the receiving application. A file extension alone cannot prove that an export contains an alpha channel.
Codec Passthrough also has a narrow meaning. Blackmagic defines it as reusing original source video essence to speed a render when the format is readable and no effects or color changes prevent reuse. It is not a universal “export without recompression” switch, and a Yes in that column does not override Decode, Encode or delivery requirements.
ProRes, DNxHR, BRAW and editing intermediates
The matrix lists Apple ProRes and DNxHR decode and encode across macOS, Windows and Rocky Linux, with container and profile details that vary by row. Blackmagic RAW decode is also listed across the three desktop sections. That makes ProRes or DNxHR useful candidates for a short diagnostic transcode when a delivery codec is unsupported or unpleasant to edit.
Useful does not mean free of tradeoffs. Intermediate files are often much larger than H.264 or H.265. Choose a profile that preserves the source bit depth and intended quality, transcode a short representative section, and inspect it before committing an entire card. Keep the camera originals and treat the transcode as a working copy.
A supported codec can still be a poor editing codec on a particular machine. Long-GOP H.264/H.265 may decode correctly yet stutter under multicam, high resolution, high frame rate or effects. That is a performance problem, not proof that the format is unsupported. The slow-playback guide separates codec pressure from cache, GPU and timeline causes.
Decode and Encode are different promises
Decode answers whether Resolve can read the stream for import and playback. Encode answers whether Resolve can create that stream on the Deliver page. Check Decode when a source clip is invisible, audio-only or offline. Check Encode when a format or codec is missing from Deliver or a render reports that no appropriate codec is available.
The extension does not make both sides equivalent. You might import an AV1 file where AV1 encoding is unavailable, or decode a professional camera format that Resolve does not offer as the same Deliver output. Start the Resolve export workflow only after choosing a format and codec that match the destination rather than trying to mirror the source automatically.
Free versus Studio without the usual oversimplification
Blackmagic's Resolve Studio 21 page describes expanded professional format support, advanced H.264 camera profiles, 10-bit encoding, IMF and DCP capabilities. The detailed matrix remains the better source for an individual row because the Free/Studio answer changes with OS, codec, profile and hardware.
Examples show why a single rule fails:
- Windows Free has listed OS-supported H.264 and H.265 profiles; Studio adds more profiles and GPU acceleration.
- Rocky Linux H.264 and H.265 rows are explicitly Studio-only for decode and require Nvidia graphics for accelerated encode.
- macOS H.264 and H.265 rows are listed as GPU accelerated without the same Linux Studio-only label.
- The official notes say encoding video resolutions at or above 4K requires Studio in that matrix.
Check the exact row rather than importing a license rule from another OS. If the file's video profile is unclear, MediaInfo is part of the answer, not optional decoration.
The five-step codec diagnostic
- Read the streams. Record container, video codec, profile, bit depth, chroma, frame-rate mode and audio codec.
- Choose the correct OS section. Do not use a Windows row to diagnose Linux or macOS.
- Choose Decode or Encode. Import and export are separate tests.
- Apply edition and hardware conditions. Preserve every Studio, OS-supported profile, GPU and driver qualification.
- Test a short copy. If unsupported, transcode a representative sample to a listed intermediate. If supported, investigate the path, storage, cache, permissions or app build instead of repeatedly changing codecs.
If a previously linked clip turns red after moving a drive, start with the Media Offline relink workflow. Transcoding does not repair a missing path, and relinking does not add a missing decoder.
DaVinci Resolve supported codecs FAQ
Does DaVinci Resolve support MP4?
Resolve supports many streams inside MP4, but MP4 alone is not a compatibility answer. Check the video codec, audio codec, profile, bit depth, operating system, edition and Decode or Encode column.
Does DaVinci Resolve Free support H.264?
It depends on the platform and profile. The Windows matrix lists 8-bit OS-supported profiles in Free, macOS lists GPU-accelerated support, while Rocky Linux marks H.264 decode Studio-only with Nvidia acceleration.
Does DaVinci Resolve Free support 10-bit H.265?
The Windows matrix lists 8/10-bit OS-supported H.265 profiles and says Studio adds more profiles and GPU acceleration. Linux and macOS have different rows, so verify the exact platform and MediaInfo profile.
Why does an MP4 import as audio only?
The container and audio stream may be readable while the video codec or profile is not. Read the file in MediaInfo, then compare the video stream with the correct OS and edition Decode row.
Does DaVinci Resolve support AV1?
The July 2025 matrix lists AV1 decode on macOS without encode, GPU-accelerated decode and encode on Windows, and Nvidia-accelerated decode and encode on Rocky Linux 8.6 CUDA.
What codecs should I transcode to for editing?
DNxHR and ProRes are common intermediate candidates listed across the desktop platform sections. Match profile and bit depth to the source, test a short sample, and expect larger files than H.264 or H.265.
Why can Resolve import a codec but not export it?
Decode and Encode are separate capabilities. A codec can appear in the Decode column without an equivalent Encode option for that platform, edition or hardware.
