Resolve has a "Bypass re-encode when possible" checkbox, but the manual attaches a condition to it: the direct copy happens "when the selected Format, Codec, and Type matches the source." Whether a MOV-to-MP4 job can meet that condition depends on two things Blackmagic documents precisely — which codec is inside the .mov, and whether you touched the clip in the timeline.
Most write-ups stop at "tick the box and your export gets faster." The reference manual goes much further than that: it lists, by name, every edit that forces a full re-encode anyway. That list is the useful part of this page.
Before you start
You need a timeline in the Deliver page and the render settings open. Two things worth knowing before you click anything:
- .mov is a container, not a codec. The manual describes the QuickTime format as "Apple's file-based media format, used when delivering Apple ProRes, DNxHD or DNxHR wrapped in QuickTime, GoPro Cineform RGB 16-bit and YUV 10-bit, Grass Valley HQ and HQX, Kakadu JPEG 2000, H.264, HEVC, H.265 (single or multi-pass), Photo JPEG, Kakadu JPEG 2000, Uncompressed 8- and 10-bit formats with ARGB/BGRA/RGB/YUV channel orders, and VP9 at 8-, 10-, and 12-bits." Two .mov files can therefore behave completely differently here.
- Bypass re-encode has a stated precondition. Verbatim from the manual: "Turning this checkbox on makes it possible to do a direct copy of the video essence of video items in the Timeline, directly from the source media to the file being output, when the selected Format, Codec, and Type matches the source. This also preserves Alpha channel data for compatible formats."
Read that condition literally. It is a match test against the source, not a general "go faster" switch — and it names three separate render settings. Format is its own dropdown, and QuickTime and MP4 are two different entries in it, so swapping the container changes exactly the thing the sentence asks you to keep matching.
Step 1: Find out what codec is inside the .mov
A ProRes .mov, a DNxHR .mov and an H.264 .mov are three different situations in the next step, even though all three end in the same extension. Blackmagic's documentation doesn't state a procedure for reading the codec out of a file; check the official documentation for your version.
Step 2: Turn on Bypass re-encode when possible
In the render settings, tick Bypass re-encode when possible. On its own this does not guarantee anything — the name says "when possible," and Steps 3 and 4 are what decide whether "possible" is true for your file.
Step 3: Check whether your codec is allowed to pass through at all
Blackmagic's Supported Formats and Codecs document (the one with "July 2025" on the cover) has a column literally headed "Codec Passthrough(1)". Its footnote reads: "Indicates if codec renders can be sped up by reusing the original source video essence if there are no effects or color changes to the clip. Relevant only for formats that can be read and rendered by DaVinci Resolve."
Here are the values as printed in that table:
| Codec | Codec Passthrough |
|---|---|
| H.264 (all platforms, all containers) | – |
| H.265 (all platforms, all containers) | – |
| MV-HEVC (mov, mp4) | – |
| AV1 | – |
| VP9 | – |
| Apple ProRes (mov, mkv) | mov |
| Apple ProRes (mxf Op1A / Op-Atom) | – |
| DNxHD | Yes |
| DNxHR | Yes |
| GoPro CineForm (avi / mov) | Yes |
| Grass Valley (avi / mov) | Yes |
| Uncompressed (avi / mov / mxf) | Yes |
| JPEG2000 video | for IMFs |
| Sony (mov / mxf) | for XAVC |
Those values are from the Codec Passthrough column only. The same codecs have separate Alpha Exports, Decode and Encode values that differ by platform and container — one column's value is not the other's.
Within this column, though, is the part nobody quotes, and it is the whole answer for most people: H.264, H.265, MV-HEVC, AV1 and VP9 have no Codec Passthrough value in that table. If your .mov is H.264 or HEVC off a camera or a phone, Resolve's own codec list does not offer passthrough for it in any container.
Note the ProRes row too: the value is mov, not "Yes," and the MXF-wrapped ProRes row on the same page is – — passthrough there is tied to the mov wrapper. Same pattern across the column: every codec carrying a passthrough value is listed under mov, mkv, mxf or avi, while the codecs that document puts in the mp4 row are the H.264/H.265/MV-HEVC/AV1/VP9 family, printed –.
Step 4: Leave the clip alone
Even with a passthrough-capable codec, the manual is blunt about what cancels it:
"Bypass re-encode eliminates the need to re-encode video media, preserves quality, and speeds up the output process dramatically, but it only works for clips in the Timeline to which no additional effects have been added. Doing any grading, adding a Resolve FX plugin, adding any overlapping effects or compositing to clips in the Timeline, resizing or stabilizing clips or altering the output sizing of the Timeline, and adding Fusion effects will all necessitate re-encoding the entire clip in order to process these effects. Transitions will require processing but only for the duration of each transition."
Broken out, the disqualifiers named by Blackmagic are:
- Any grading — the word is "any," not "heavy."
- Adding a Resolve FX plugin.
- Any overlapping effects or compositing on timeline clips.
- Resizing or stabilizing clips.
- Altering the output sizing of the Timeline.
- Adding Fusion effects.
Each of those "will all necessitate re-encoding the entire clip." Transitions are the one graded exception: they "will require processing but only for the duration of each transition."
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
If the actual goal is just an .mp4 you can hand to someone — no grade, no edit, no timeline — you do not need to open Resolve for it. The converter above runs inside your browser tab: the file is read from disk, processed locally and handed back, so nothing is uploaded to a server. The standalone MOV to MP4 page does the same job, and the rest of the set is at all Clapr tools.
When bypass actually pays off
The manual gives three worked scenarios, and they share a shape: the video essence already exists in its final form.
- Simple cuts-only edits assembled from previously rendered media and exported back to the exact same format.
- Small changes to an already-output program — re-import the rendered file, swap only the shots that changed, and Resolve re-encodes only the new clips "with whatever effects and grading they contain."
- A new audio mix over previously rendered video — the new Video+Audio file is written with the new audio, while "the video component of that file won't be re-encoded."
If your job does not look like one of those three, expect a normal encode.
Common mistakes
- Assuming the checkbox applies to H.264 source. It is the single most common case and the one the passthrough column marks
–. - Treating "a quick balance pass" as harmless. Official wording: "Doing any grading … will all necessitate re-encoding the entire clip."
- Changing the timeline's output size. "Altering the output sizing of the Timeline" is on the disqualifier list, verbatim.
- Expecting MXF-wrapped ProRes to pass through. That row's value is
–. - Panicking about a cross-dissolve. Transitions only cost their own duration, not the file.
FAQ
Can DaVinci Resolve convert MOV to MP4 without re-encoding?
The manual's condition is "when the selected Format, Codec, and Type matches the source," and QuickTime and MP4 are two different entries in the Format dropdown. On top of that, the codecs carrying a Codec Passthrough value are listed in mov, mkv, mxf and avi containers, while H.264, H.265, MV-HEVC, AV1 and VP9 are printed as –.
Where is the Bypass re-encode option? It is a checkbox in the render settings, documented in the reference manual as "Bypass re-encode when possible."
Does a small colour tweak really cancel it? Yes, per the manual's own wording: "Doing any grading … will all necessitate re-encoding the entire clip." There is no documented threshold below which grading is free.
Do transitions force a full re-encode? No. "Transitions will require processing but only for the duration of each transition."
Can I export H.265 in an MP4 container? The two official sources differ. The manual's format list says only "MP4: Dedicated MP4 encoding lets you export H.264-encoded movies," while the July 2025 codec list has encode values for H.265 in the mp4 row. Check the official documentation for your platform and version before planning around it.
Which codecs keep an alpha channel through bypass?
The manual says bypass "preserves Alpha channel data for compatible formats" without naming them. The codec list's separate "Alpha Exports" column is about exporting alpha, and it does not track Codec Passthrough: on macOS, H.265 is Alpha Exports Yes in mov and mkv, – in mp4, while its Codec Passthrough is – everywhere. Check the official documentation for your codec, container and platform.
Quotes from the DaVinci Resolve 21 Reference Manual and Blackmagic's Supported Formats and Codecs document (cover date July 2025), both linked from the DaVinci Resolve support page. Blackmagic notes that "Specifications format and codec support subject to change without notice." More walkthroughs like this one are in the how-to hub.