DaVinci Resolve Club
Home   Troubleshooting   DaVinci Resolve Won't Import MP4? Fix Audio-Only Clips
Troubleshooting

DaVinci Resolve Won't Import MP4? Fix Audio-Only Clips

By Jason Miller Updated Aug 17, 2026 9 min read

Quick answer

An MP4 extension does not identify the video inside it. Use this symptom-first workflow to separate codec trouble, damaged media and a simple V1 source-patching mistake.

DaVinci Resolve MP4 import fix for an audio-only video file

An MP4 that imports as audio only is not one problem with one fix. The file may contain a video stream that your Resolve edition can't decode, the MP4 container may be damaged, or the video may already be available while the timeline's V1 source patch is turned off. Those cases look similar when you drag a clip, but converting every file will waste time and can reduce quality.

Start by checking where the picture disappears. If the clip is audio-only inside the Media Pool, inspect the file and codec. If video plays in the Source Viewer but only audio lands on the timeline, inspect source patching. Keep the original file untouched until you know which problem you have.

Match the symptom before changing anything

What you seeMost useful first checkLikely route
The MP4 is missing from the import browser or Resolve rejects itOpen it in another player, then inspect its streams in MediaInfoCodec, container, file access, or damaged media
The clip appears as audio-only in the Media PoolRead the video codec, profile, bit depth, and chroma samplingUnsupported video stream or incomplete file
The Source Viewer plays picture and sound, but dragging adds only audioLook at the V1 source patch and destination trackTimeline patching, not conversion
The clip imports but displays Media OfflineCheck the path, drive access, and decoder detailsUse the dedicated Media Offline diagnosis
Picture works but audio is silent or absentInspect the audio stream and Resolve's track and bus routingUse the no-audio troubleshooting path

This separation matters. A valid video stream doesn't need to be re-encoded because V1 was disabled. A genuinely unsupported stream won't be repaired by toggling a track control. If your symptom falls outside the table, start with the DaVinci Resolve troubleshooting map before changing the file.

MP4 is a container, not the video codec

The `.mp4` extension tells you how streams are packaged. It doesn't tell you whether the video is H.264, H.265, AV1, MPEG-4 Part 2, or something less common. It also doesn't reveal the profile, bit depth, chroma sampling, frame-rate mode, or whether the file was finalized correctly by the recorder.

That's why two files from the same folder can behave differently. A phone export, screen recording, camera original, and downloaded clip may all end in `.mp4` while carrying different video streams. Resolve can read the audio stream and reject the video stream, which produces the familiar audio-only result.

The current official codec matrix lists support by operating system, container, codec, and edition. Check the row for your operating system rather than relying on a general list copied from another tutorial. The matrix available while this guide was checked is labeled Resolve 20; Resolve 21 is current, so use the support center for any newer matrix Blackmagic releases.

Read the file with MediaInfo

Install MediaInfo from its official site, open the problem file, and switch to Text or Tree view. Don't stop at the line that says MPEG-4. Record the following fields:

MediaInfo Tree view for an MP4 H.264 file showing profile frame-rate mode chroma subsampling and bit depth
Read the Video section, not only General > MPEG-4. This real MediaInfo Tree view exposes AVC profile, constant or variable frame-rate mode, 4:2:0 chroma and 8-bit depth so you can compare the right Blackmagic matrix row.
  • Format and codec ID: identifies the actual video compression.
  • Format profile and level: narrows down which decoder capability the stream expects.
  • Bit depth and chroma subsampling: for example 8-bit 4:2:0 or 10-bit 4:2:2.
  • Frame-rate mode: constant or variable.
  • Audio format: the audio can be readable even when the video isn't.
  • Duration and stream count: spells out that the file actually contains a video stream.

Then note Resolve's exact version and build from DaVinci Resolve > About DaVinci Resolve, whether it's Free or Studio, your operating system, and your GPU. Those details aren't forum bureaucracy. They determine which row of the codec matrix applies.

Compare the stream with your OS and Resolve edition

H.264 and H.265 in MP4 are common, but their support isn't identical on every platform. The official matrix shows broad H.264/H.265 decoding on macOS and Windows, with additional profiles and GPU acceleration tied to Studio in some Windows cases. Linux is more restrictive and can require Studio and compatible Nvidia hardware for streams that work elsewhere.

EnvironmentWhat to verifyDo not assume
macOSCodec, profile, OS-native decode support, and current Resolve buildEvery damaged or unusual MP4 will decode because ordinary H.264 does
WindowsCodec profile, bit depth, chroma sampling, Free/Studio differences, and GPU pathEvery 10-bit file fails in Free or every H.265 file requires Studio
LinuxThe Linux section of the matrix, Resolve edition, codec, and Nvidia requirementsA file that works in VLC or on Windows must work in Resolve for Linux

Don't buy Studio based on the MP4 extension. Identify the exact stream first. Studio can expand supported profiles and hardware decoding, but it doesn't repair a truncated recording, a bad container header, or a disabled V1 patch.

Fix V1 source patching when the Source Viewer has picture

If the clip plays normally in the Source Viewer, Resolve has decoded the video. On the far left of the Edit page timeline, Resolve 21 uses a two-column Source Track Selector: blue controls on the left represent source components, while red controls on the right represent timeline destinations. The two-column interface arrived in Resolve 20.2 and remains documented in Resolve 21.

  1. Load the clip into the Source Viewer and confirm that picture is visible.
  2. On the timeline, make sure an unlocked video destination track exists in the red right column.
  3. Enable the blue source V1 control and map it to the intended red video destination.
  4. Enable only the blue source audio components you want and map them to suitable red audio destinations.
  5. Perform a short overwrite or insert edit as a test.
DaVinci Resolve 20.2 Source Track Selector with blue source V1 and A1 beside red timeline destinations
The blue left column is the source clip; the red right column is the timeline. If the Source Viewer has picture but the edit inserts only audio, enable blue V1 and map it to an unlocked red video destination. Resolve 21 keeps this two-column model.

If blue source V1 is absent because the Source Viewer contains an audio-only item, return to codec diagnosis. If blue V1 is present but can't be selected, check that a compatible red video destination exists and is unlocked. Don't transcode until this branch is ruled out.

Use a safe repair ladder

Work from the least destructive test to the most expensive conversion. Save the original camera or downloaded file in a separate location first.

1. Test the file outside Resolve

Open the MP4 in a second player and scrub near the beginning and end. A player succeeding doesn't prove Resolve supports the stream, because players ship different decoders. A player failing, freezing, or reporting a much shorter duration is useful evidence that the file is incomplete or damaged.

2. Copy one clip to a simple local path

Copy a single source to a local folder with a short filename. This separates codec trouble from cloud placeholders, disconnected volumes, read permission problems, and unstable network storage. Import that copy into a new empty project. Don't move the whole production until the test proves location is the cause.

3. Compare it with a known-good file

Import a small MP4 that already works on the same machine. If every supported test file fails after an update, investigate Resolve, the GPU driver, or the operating system. If only files from one camera or recorder fail, compare their MediaInfo reports.

4. Remux only when the streams are already supported

A remux places the existing streams into a fresh container without re-encoding them. It's fast and avoids generation loss, but it can't turn an unsupported video codec or profile into a supported one. The current Shutter Encoder documentation calls this Rewrap and requires the chosen output container to support the source codec. Use it only when MediaInfo shows compatible streams and the evidence points to a malformed header or container.

Shutter Encoder Rewrap function with MP4 output selected for a container-only repair
Rewrap copies supported existing streams into a new container without a video re-encode. This older Shutter Encoder interface shows the real function; the current 2026 documentation keeps the same rule: the destination container must support the source codec.

After rewrapping, verify duration, picture, audio and sync. Keep the untouched source until the edit and final export are complete.

5. Transcode an unsupported or unreliable stream

Transcoding creates a new video stream. For editing, ProRes or DNxHR is usually a safer intermediate than repeatedly converting to another highly compressed delivery MP4. Choose a flavor appropriate to the source quality, preserve the source dimensions and intended cadence, and keep audio uncompressed when practical. Encode one short clip and test picture, audio, duration and sync before processing a batch.

Shutter Encoder DNxHR HQ editing-codec conversion with source scale and frame-rate controls
DNxHR is a transcode, not a rewrap: it creates a new edit-friendly video stream. This real v16.6 screen uses an older layout, but DNxHR remains a current Shutter Encoder 20.2 editing-codec function. Do not copy the shown 30 fps blindly; preserve cadence unless a deliberate CFR conversion is required.

An intermediate will be larger than the camera MP4. That's expected. It trades storage for easier decoding and more predictable seeking. If storage or playback is the real constraint, the proxy workflow explains how to create lighter working media without replacing your masters.

Treat variable frame rate as a separate risk

Phones, screen recorders, meeting apps, and browser capture tools often produce variable-frame-rate media. VFR can cause drifting sync, uneven playback, or frame-accurate editing problems. It does not automatically explain why Resolve sees no video stream at all.

If MediaInfo reports variable frame rate and the clip imports but behaves unpredictably, encode a test copy to an intended constant frame rate and inspect it from start to finish. Shutter Encoder's Conform control changes frame-rate metadata and its documentation explicitly says it doesn't solve VFR. Don't type a frame-rate number into a converter without confirming the source cadence and timeline target.

Update Resolve only when the evidence supports it

A newer Resolve build can include decoder fixes, but updating is not the first move for one unusual file. Compare the release notes, back up the project library, export a project archive for important work, and confirm system compatibility. Follow the safe Resolve update checklist instead of changing the application in the middle of diagnosis.

If the whole application is unstable or decoding fails across many known-good files, confirm that the machine meets the current Resolve system requirements. One unsupported MP4 and a general GPU or driver failure require different repairs.

Avoid the fixes that create new problems

  • Don't rename `.mov`, `.mkv`, or another extension to `.mp4`. A new filename doesn't change the container or codec.
  • Do not transcode before reading MediaInfo. You may hide a V1 patching error or convert hundreds of clips unnecessarily.
  • Don't assume HandBrake is a remux tool. Its normal video workflow re-encodes, so choose settings deliberately and inspect the result.
  • Don't delete the only source after one successful import. Verify the full clip, sync, metadata, and final render first.
  • Don't clear every cache folder for an import rejection. Cache is relevant to generated working media, not to making an unsupported source stream decodable.

Prevent the next MP4 import failure

  1. Record a short test in the exact camera or capture settings planned for the job.
  2. Import it into the same Resolve edition and operating system used for the edit.
  3. Check the first and last minute for picture, audio, sync, and seeking.
  4. Save a MediaInfo report with the camera preset notes.
  5. If the source is VFR or difficult to decode, plan intermediates or proxies before the deadline.
  6. Keep camera originals read-only and separate from generated media.

Frequently Asked Questions

Why does DaVinci Resolve import my MP4 as audio only?

Resolve may be able to decode the MP4's audio stream but not its video stream. Check the actual video codec, profile, bit depth, chroma sampling, operating system, and Free or Studio edition in MediaInfo and Blackmagic's codec matrix. If picture plays in the Source Viewer, check V1 source patching instead.

Does DaVinci Resolve support MP4 files?

Resolve supports many streams stored in MP4 containers, including common H.264, H.265, and AV1 cases, but support varies by operating system, codec profile, hardware, and edition. The `.mp4` extension alone can't prove compatibility.

Can I fix the file by changing its extension?

No. Renaming an extension doesn't change the container, video codec, or file structure. Remux the streams into a fresh container when they're supported, or transcode to a supported edit codec when the video stream itself is the problem.

Should I convert the MP4 to H.264?

Not automatically. H.264 still has profiles, bit depths, and platform-specific decoding limits, and another delivery codec may remain difficult to edit. For an unsupported source, ProRes or DNxHR is usually a more predictable intermediate. Test one clip before processing a batch.

Why can I see video in the Source Viewer but only audio reaches the timeline?

That symptom usually points to source patching rather than codec support. Enable the blue source V1 control, map it to an unlocked red video destination track, and repeat a short insert or overwrite edit.

Use the DaVinci Resolve troubleshooting map for the wider diagnostic path. If a file imports but turns red, continue with Media Offline diagnosis; if picture works and sound doesn't, use the no-audio workflow.

Updated August 17, 2026 Checked against DaVinci Resolve 21 documentation and edition notes
Jason Miller
Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.
Explore the troubleshooting hub: match the symptom, then test the smallest fix