Quick answer: DaVinci Resolve supports many common codecs, but a file extension is not enough to check a clip. Identify its container, video and audio codecs, profile and bit depth. Then check the row for your operating system, Free or Studio edition and hardware. Use Decode for import and Encode for export. MP4 is the container, not the video inside it.
For a compatibility check, read the file with MediaInfo and compare the result with the official matrix. Don't rely on the extension, the camera brand, or a list that combines macOS, Windows and Linux into one yes/no answer.
Checked September 5, 2026: the latest codec matrix found in Blackmagic's support listing is DaVinci Resolve 20 Supported Formats and Codecs, dated July 2025. The platform table below summarizes that document; it is not a newly issued Resolve 21 matrix. Check your installed build and a representative file before relying on an older row for a new camera profile or GPU.
If a particular MP4 already fails, the MP4 import repair guide walks through that problem. For the steps around importing and editing, the Resolve workflow hub brings together media, proxy and playback guides.
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 aren't 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 file in MediaInfo and choose Tree or Text view. Note these fields before changing anything in Resolve:
- 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: record both; support can differ within one codec family.
- Chroma subsampling: commonly 4:2:0 or 4:2:2, another profile detail worth recording.
- Frame rate mode: Constant or Variable. If a readable phone or screen recording drifts out of sync, variable frame rate is worth checking; it does not automatically make the codec unsupported.
- Audio Format: AAC, PCM, MP3, FLAC or another independent stream.
The example above has 8-bit, 4:2:0 video at a constant frame rate. Your file may have different values even when its extension is the same. Renaming clip.mkv to clip.mp4 does not change those streams. Remuxing moves compatible streams into a different container without re-encoding them; transcoding creates new encoded streams.
For an OBS recording, a remux can help when the container is the obstacle and its streams are already compatible. It cannot turn an unsupported AV1, HEVC or audio stream into a supported one. The OBS formats guide explains the distinction; check video and audio after remuxing instead of assuming a new extension fixes both.
Common codec support by desktop platform
This is a quick reference to the July 2025 Resolve 20 matrix, using its exact platform headings. It is not a complete format list or a guarantee for every current computer. Camera RAW variants, image sequences, IMF/DCP, alpha and professional profiles still need their individual rows.
| 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: Studio-only; Nvidia GPU acceleration is noted separately. Encode: Studio and Nvidia graphics | Decode and encode listed with Nvidia GPU acceleration | Not listed for decode or encode |
On Windows, the matrix lists 8-bit OS-supported H.264 profiles and 8/10-bit OS-supported H.265 profiles, with additional profiles and GPU acceleration in Studio. That is not the same as saying every 10-bit HEVC file needs Studio. Check its exact profile and chroma subsampling: two 10-bit camera files need not use the same decoding path.
For Linux, keep two conditions separate: H.264/H.265 decode is marked Studio-only, with Nvidia acceleration noted in parentheses; encode explicitly calls for Studio and Nvidia graphics. The decode note does not establish that all software decoding needs Nvidia. These are Rocky Linux 8.6 CUDA rows, not a promise for every distribution or GPU. Check the Resolve 21 system requirements separately when choosing a supported installation.
Audio, alpha and passthrough need their own checks
Audio needs its own row. The macOS and Windows sections list AAC, constant-bit-rate MP3, FLAC and OPUS decode, with encoding availability shown separately. The Linux section lists MP3 and FLAC but leaves built-in AAC decode and encode blank. A container can therefore contain usable video and unusable audio. Do not assume that buying Studio alone fixes Linux AAC.
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. Don't 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 can't prove that an export contains an alpha channel.
Codec Passthrough means Resolve may reuse source video instead of encoding it again. The Resolve 21 Deliver documentation also requires matching Format, Codec and Type for its source-reuse option; grades, effects, resizing and other changes can prevent reuse. It is not a universal lossless-export switch. A Yes in the passthrough column does not override the required output format or its limitations.
ProRes, DNxHR, BRAW and editing intermediates
The matrix lists Apple ProRes 422/4444-family and DNxHR decode and encode across macOS, Windows and Rocky Linux, subject to the container and profile rows. Advice that Resolve cannot export ProRes on Windows is outdated: Blackmagic added Windows and Linux ProRes encoding in Resolve 19.1.4. ProRes 422/4444 support is not evidence of ProRes RAW support. Blackmagic RAW is a separate codec family, listed for decode across the three desktop sections.
ProRes or DNxHR can be useful working formats, but the profile matters. Choose one that preserves the source bit depth and intended quality, convert a short representative section, and inspect it before processing an entire card. Intermediate files are often much larger than H.264 or H.265. Keep the camera originals and treat the transcode as a working copy.
A supported codec can still be difficult to edit smoothly. Long-GOP H.264/H.265 may play correctly on its own yet stutter in multicam, high-frame-rate or effects-heavy timelines. That is not proof of an unsupported format. The slow-playback guide helps separate decoding pressure from cache, GPU and timeline problems.
Hardware acceleration is a separate check from whether a codec is readable. In Preferences > System > Decode Options, inspect the available H.264/HEVC hardware-decoding controls. The devices shown depend on the installation. Puget's profile-by-profile testing also separates bit depth and chroma subsampling; the name H.265 alone does not tell you which GPU can accelerate a clip.
Decode and Encode are different promises
Decode means reading a source stream for import and playback. Encode means creating an output stream. If video imports as audio only, inspect the video Decode row. If a codec is missing from Deliver, inspect Encode instead. The list of possible outputs is not a list of every format Resolve can read.
The extension doesn't 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/H.265 decode is marked Studio-only; its encode rows explicitly require Studio and Nvidia graphics.
- macOS H.264 and H.265 rows are listed as GPU accelerated without the same Linux Studio-only label.
- Free can finish up to 60 fps at UHD 3840×2160. That includes the resolution commonly called 4K for YouTube. Do not confuse it with a wider DCI 4K frame such as 4096×2160, which exceeds the Free UHD limit.
Match the codec row to your platform before deciding whether an upgrade solves the problem. A license upgrade does not add a missing hardware decoder to a GPU or make every recording profile equivalent.
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. Don't 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 the stream is unsupported, convert a representative sample to a listed intermediate and inspect it. If the source should be supported, check the file path and integrity, storage access and app build. For stuttering rather than a failed import, investigate decoding load and cache separately.
If a previously linked clip turns red after moving a drive, start with the Media Offline relink workflow. Transcoding doesn't 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 isn't 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 July 2025 matrix lists 8-bit OS-supported H.264 profiles on Windows and GPU-accelerated support on macOS. The Rocky Linux row marks decode Studio-only, with Nvidia acceleration noted separately.
Does DaVinci Resolve Free support 10-bit H.265?
The July 2025 Windows matrix lists 8/10-bit OS-supported H.265 profiles and says Studio adds more profiles and GPU acceleration. That does not guarantee every 10-bit or 4:2:2 file works. Check the exact MediaInfo profile and the separate row for your platform.
Why does an MP4 import as audio only?
The container and audio stream may be readable while the video codec or profile isn't. 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 but no encode entry. Windows lists GPU-accelerated decode and encode; Rocky Linux 8.6 CUDA lists Nvidia-accelerated decode and encode. This is a Resolve 20 reference, so confirm the options on your installed build and GPU.
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.
