Before importing camera footage into DaVinci Resolve on a Mac, identify its video and audio codecs, match them to the macOS decode table, and test one representative clip. This tells you whether to edit the originals, create proxies, or convert a copy first.

This workflow is for a Mac editor preparing camera recordings for a new project. It uses Blackmagic Design’s September 2026 DaVinci Resolve 21.1 documentation and Apple’s QuickTime Player instructions. If you use an older Resolve release, check its matching documentation before assuming that a newly listed format will work.

What information determines whether a clip will import?

A filename extension is only the starting point. The container, such as MOV or MP4, holds the video and audio streams. The codec describes how a stream is encoded. Apple’s export documentation illustrates the distinction: QuickTime Player can produce a MOV file containing either H.264 or HEVC video. Changing a filename extension does not perform that conversion. Apple’s QuickTime export guide

Build a short record for each recording mode you used. Two clips from the same camera may need separate checks if their recording settings differ. Capture the container, video codec, resolution, frame rate, bit depth when available, and audio format. Also record your Resolve version, whether it is the free or Studio edition, your macOS version, and your Mac model.

Keep three questions separate: can Resolve decode the clip, can your Mac play it smoothly enough to edit, and can you export the required result? A successful import answers only the first. Treat a compatibility listing as a reason to test the footage, rather than a promise about your complete timeline.

Identify the actual recording on your Mac

Open a representative file in QuickTime Player, then choose Window > Show Movie Inspector or press Command-I. Apple documents that the inspector can display video compression format, dimensions, frame rate, bit depth, aspect ratio and HDR format, plus audio information. Record what appears; leave unavailable details marked as unknown. View information about a media file in QuickTime Player

Inspect the file you intend to edit. For example, a transferred phone recording may differ from the camera original: Apple documents that some sharing and import methods can convert HEVC to H.264. The camera’s selected recording mode therefore does not necessarily describe the copy on your Mac. Using HEIF or HEVC media on Apple devices

If QuickTime cannot open the recording, continue with the camera’s recording-mode information and Resolve’s format table. QuickTime playback is a useful inspection route, but it is a separate application test. Do not conclude that a camera format is unsupported in Resolve solely because QuickTime cannot inspect it.

Read the macOS decode table correctly

Open Blackmagic’s supported-codec document and use the macOS section. Match the format and file extension, then read the Decode column for import support. Encode concerns output. For example, the September 2026 table lists ProRes RAW in MOV as decodable on macOS, with no corresponding encode support. DaVinci Resolve 21.1 Supported Formats and Codecs

The same table lists H.264 and H.265 decoding in MOV and MP4 as GPU accelerated, without a Studio-only label on those macOS entries. Its footnotes make acceleration conditional on hardware support. Avoid applying another platform’s restrictions to your Mac, or interpreting a broad entry as a detailed guarantee for every recording profile. Blackmagic’s macOS codec entries and footnotes

Read conditions in the column where they appear. A Studio restriction beside encoding does not automatically restrict decoding. Check audio independently, too: Blackmagic lists supported embedded audio subject to valid header metadata. Picture support alone does not establish that every audio stream will decode. Blackmagic’s codec and audio tables

For HEVC, retain the resolution and frame-rate details in your notes. Apple says these affect compatibility on some older devices. That supports a practical rule: test the actual high-resolution or high-frame-rate recording you plan to edit, even if a smaller HEVC file already plays successfully. Apple’s HEVC compatibility guidance

Run a small import test before committing the whole shoot

Copy the footage to the location you intend to edit from before importing. Resolve’s manual explains that adding clips to the Media Pool links to existing files; it does not move, copy or transcode them. Preserving the camera folders also gives you a consistent starting point for troubleshooting. DaVinci Resolve 21.1 Reference Manual, Chapter 17

Use a temporary project for the first test. In the Media page, locate a representative recording in Media Storage and drag it into the Media Pool. Blackmagic also documents selecting files and using Add into Media Pool. If Resolve offers to change the project frame rate, choose deliberately according to the intended edit. Resolve’s documented media-import procedure

For this diagnostic, test one clip from every distinct recording mode before importing everything. Play the beginning, a middle section and the end; listen to the expected audio; and check duration and motion. Then place a clip on a simple timeline without effects. This recommended sequence helps isolate source playback from the additional work of a finished edit.

Test result What it establishes Next action
Picture and audio play correctly This sample works in your installation Import more clips from that recording mode
Correct playback, but frequent stuttering Decoding works; performance needs investigation Try a proxy for comparison
Picture plays, but expected audio is absent Video and audio need separate diagnosis Check the audio format and channel interpretation
Clip is rejected or picture is unavailable Compatibility remains unresolved Recheck the exact format, version and source copy

Treat these as diagnostic branches, not automatic diagnoses. One working clip does not validate every file, and one failing clip does not prove that the entire codec family is unsupported. Keep the failing sample and your recorded settings together so that each further test answers a specific question.

Choose originals, proxies or a converted copy

Use originals when the test meets your editing needs

If representative clips play correctly and the simple timeline responds well, proceed with the originals. Keep the source files in the location you tested. There is little value in converting an entire shoot before establishing that conversion solves a problem you actually have.

Create proxies when footage decodes but editing is slow

Resolve’s proxy workflow creates alternate media linked to the sources. In Project Settings > Master Settings, find Optimized Media and Render Cache and set Proxy Media Resolution and Proxy Media Format. For a first comparison, try a reduced resolution and an available ProRes proxy option. Check the destination under Working Folders, then select the test clip in the Media Pool, right-click and choose Generate Proxy Media. Resolve 21.1 Reference Manual, Chapter 8

Choose Playback > Proxy Handling > Prefer Proxies to compare editing response. To verify the originals specifically, use Disable All Proxies: the manual says this forces original-media playback. Prefer Camera Originals can fall back to proxies when originals are unavailable, so it is less decisive for that check. Resolve’s proxy-handling controls

Proxy generation requires the source to be decoded. It cannot make an unreadable original decodable merely by selecting a different proxy format. Also plan the final output: Resolve normally uses original media for delivery, while Use proxy media in the delivery settings overrides that behavior. Recheck original playback before finishing. Resolve’s proxy generation and delivery documentation

Convert a copy when a documented alternative fits the job

If an HEVC recording opens in QuickTime but your Resolve test fails, Apple documents a straightforward conversion path. Open the original, choose File > Export As, and select an appropriate resolution. For 4K or 1080p export, choose Greater Compatibility to create H.264. Save under a distinct name, inspect the result, and repeat the Resolve test. The output is MOV, not MP4. QuickTime Player export instructions

Use that route only when its output fits the edit. Apple lists the 4K option as up to 3840 × 2160, so it is not a preservation path for every camera resolution. Keep the original and compare the converted copy’s dimensions, motion, color appearance and audio before batch conversion. If QuickTime cannot decode the source, this route is unavailable. QuickTime export resolutions and formats

For an illustrative decision, suppose a 3840 × 2160 HEVC camera clip imports with correct picture and sound but stutters on a simple timeline. Start with a proxy comparison. If it instead fails to decode in Resolve but opens in QuickTime, test one H.264 export. These are different remedies because they address different observed failures; neither result should be assumed before testing.

Your pre-import check is complete when you can identify the recording, locate its documented decode support and demonstrate a workable editing path with a representative sample. Keep that short record beside the footage, then apply the tested approach to the remaining clips while retaining the originals.

Sources