Top Post Ad

How to Sync Audio and Video in DaVinci Resolve: A Practical Guide

On this page

    Professional DaVinci Resolve editing suite with audio waveforms

    How to Sync Audio and Video in DaVinci Resolve: A Practical Guide

    A version-aware DaVinci Resolve guide to manual clap and waveform sync, Auto Sync Audio, drift diagnosis, VFR cautions, Fairlight cleanup, and QC.
     

    How to Sync Audio and Video in DaVinci Resolve: A Practical Guide

    A macro shot of a digital audio waveform on a professional editing monitor, high contrast, vibrant blue and green colors, shallow depth of field, minimalist tech aesthetic.

    Good audio-video sync is not a matter of finding one magic shortcut. It is a process of matching the right picture and sound, choosing an appropriate sync method, checking the result, and keeping a reversible project history. DaVinci Resolve can synchronize separate recordings by timecode or waveform, and it also supports careful manual alignment. The correct choice depends on what was recorded, how reliably it was recorded, and which Resolve version and edition you have installed.

    This guide replaces shortcuts, sub-frame, Elastic Wave, and reliability claims that cannot be made universally. It does not promise that every waveform match will succeed, that every control will appear in every build, or that a sync created at the beginning of a long take will remain correct at the end. Menu names and shortcuts may vary by Resolve version, operating system, keyboard layout, page, edition, and custom keymap. Check Help > Reference Manual and the current Blackmagic Design support documentation for your installed build.

    Disclosure: The steps below are based on the supplied research records and are intended as a version-aware workflow. Options may vary by DaVinci Resolve edition and version. The official Blackmagic documentation for the installed build is authoritative.

    What audio-sync problems look like

    Sync problems are easier to diagnose when you describe the behavior rather than immediately moving a clip. Common patterns include:

    What you noticeWhat it may indicateFirst check
    The entire take is early or late by roughly the same amount.A fixed offset, an incorrect manual alignment, or a wrong source pair.Compare a clear clap, consonant, hand movement, or other event in both picture and sound.
    Sync starts well but becomes increasingly wrong.Drift caused by unequal device timing, clock behavior, time-base differences, or a source problem.Check a point near the beginning and another near the end of the long take.
    The waveform match fails or selects an implausible result.Missing or poor scratch audio, silence, heavy reverberation, clipping, mostly ambience, an unsuitable channel, or unrelated recordings.Listen to both files and select a channel with comparable, intelligible overlapping content; otherwise align manually.
    Only some clips in a batch synchronize.Different recording conditions, missing metadata, different takes, or clips that do not contain a usable common event.Read Resolve's warning about unsuccessful clips and investigate those pairs individually.
    Dialogue appears correct in one place but not elsewhere.A local mismatch, a bad pairing, or drift rather than a single constant offset.Check visible mouth movement, consonant attacks, room tone, and more than one point in the scene.

    Before you start: a sync checklist

    1. Protect the originals. Keep camera cards/files, production WAVs, and the only project copy untouched. Blackmagic recommends verified clone or checksum backups before cards are erased or reused.
    2. Make a reversible working version. Duplicate the project, timeline, or relevant bins before testing a batch sync, retime, bounce, or other major change. Use clearly named versions such as Project_sync-test_v01.
    3. Identify the intended pair. Use scene, take, slate, recorder, camera, filename, and timecode information. Do not let a similar filename or a waveform coincidence replace editorial judgment.
    4. Inspect the source audio. Confirm that the camera clip has usable scratch/reference audio if you intend to use waveform matching. Determine which external recording and channel contain the corresponding event.
    5. Check timecode honestly. Choose timecode only when the audio and video carry matching, usable timecode. Separate device clocks can diverge during a long recording unless they remain locked to a common source.
    6. Check frame-rate conditions. If the footage may be variable frame rate (VFR), diagnose it before committing to a long edit. A separate constant-frame-rate (CFR) derivative may be safer for a test.
    7. Decide what must remain available. Retaining the embedded camera audio can make comparison easier. Resolve's Resolve 20 guide states that omitting the Retain embedded audio option does not delete the original embedded audio; it remains accessible through Clip Attributes. Still verify your channel configuration before editing or delivering.

    Manual sync with a clap or slate

    A clap is a useful sync aid because it creates two related observations: a visible event in the picture and a sharp audible transient in the sound. It is not an automatic guarantee, and the same clap does not prove that a long take will remain aligned if the devices drift.

    1. Use slate information and the production notes to identify the correct camera clip and external audio file.
    2. In the picture, find the frame in which the clapper closes or the hands meet. Do not rely only on the frame before or after the contact.
    3. In the external recording, find the transient made by that same event. Zoom into the waveform if necessary, but use the audible event and not waveform shape alone.
    4. Align the corresponding picture and audio event using the manual sync workflow available in your Resolve build. Blackmagic's product documentation describes selecting the audio and video, choosing a frame in the picture viewer, choosing the corresponding frame in the audio viewer, and using the page's link control.
    5. Play through the event while watching the mouth, hands, or slate and listening to the attack. Then check another clear event later in a long take.

    There is no universal sync shortcut asserted here. The current Blackmagic product page documents the manual viewer-to-viewer method without publishing a universal keyboard shortcut. If a tutorial gives a shortcut that is absent from your build, use the visible command or the version-matched manual rather than guessing.

    Manual sync without a clap

    Many recordings have no slate. You can still align them, but the evidence is weaker and the verification burden is higher.

    Use comparable waveforms

    1. Open the camera/reference audio and the external recording so you can inspect their waveforms.
    2. Find a distinctive shared event: a spoken consonant, door close, hand movement with sound, footstep, or another transient present in both recordings.
    3. Compare surrounding material, not just one spike. Similar-looking peaks can come from unrelated noise, and a waveform match requires sufficiently similar recorded content in both files.
    4. Align the event, play it with the picture, and check more than one point. If the recordings have different microphones or room sound, dialogue timing and visible mouth movement may be more useful than the overall waveform.

    Waveform matching may fail or choose the wrong location when camera scratch audio is missing, clipped, heavily reverberant, mostly ambience, too quiet, or otherwise unlike the external recording. Silence, noisy channels, unrelated takes, and different microphone feeds are also warning signs. When the comparison is unreliable, fall back to a clear manual point or properly shared timecode.

    Use visual cues and dialogue

    When there is little common audio, use a visible mouth movement, a hand gesture with a sound, an object being struck, or another event that can be located in both recordings. Stack the material on neighboring timeline tracks if useful, zoom in, and compare the event in playback. A waveform can support the decision, but it cannot substitute for seeing and hearing the same event.

    In Fairlight, the official Resolve 20 guide demonstrates stacking takes, zooming the waveform, temporarily overlaying one clip to compare waveforms, and moving the clip into alignment. Command-B on macOS or Ctrl-B on Windows is documented for splitting at the playhead in that guide, and the period key is demonstrated for a one-frame right nudge under the default layout. These are version- and keymap-dependent examples, not universal sync commands.


    Resolve automatic sync options

    Resolve has two different ideas that are easy to confuse: automatic synchronization of separate media in the Media Pool, and alignment of clips already placed in a timeline. The workflow below describes Media Pool Auto Sync Audio. Timeline Clip > Auto Align Clips is a separate operation for applicable timeline material.

    Media Pool Auto Sync Audio

    1. Import and organize the camera/video clips and separately recorded audio in the Media page/Media Pool. Clear bins such as CAMERA, RECORDER, and SYNC_TEST make review easier.
    2. Select the relevant clips or bins. In the Resolve 20 Editor's Guide example, right-click the selection and choose Auto Sync Audio.
    3. In the Automatically Sync Audio window, use the Synchronize using control. Choose Timecode only for genuinely matching, usable timecode. Choose Waveform when the camera clip contains overlapping scratch/reference audio.
    4. For waveform analysis, use the documented Use channel number option when a particular channel is a better match. Resolve 19 documentation also describes channel choices such as Auto, Mix, or an individual channel; the exact choices depend on the release.
    5. Consider Retain embedded audio when you want the original camera reference available for checking. Retain video metadata keeps the video clip's metadata from being overridden by the audio file's metadata.
    6. Click Sync, then review any warning. The Resolve 20 guide says an unsuccessful operation produces a warning identifying clips that could not be synchronized.
    7. In Media Pool List View, use the Synced Audio column where available. Select and play several successful and unsuccessful-looking clips before relying on the batch.

    Resolve 20.1 documentation adds In point, Out point, and Marker to the Media Pool AutoSync Audio dialog's Synchronize Using choices. Treat these as version-specific additions. Older tutorials may use wording such as “Based on Waveform,” “Based on Timecode,” or “Append Tracks”; do not assume those labels exist in a newer build.

    Resolve's product information describes synced media as being managed without rendering new media. That does not make the source files disposable: preserve the originals, keep the project backup, and verify channel configuration. The Retain embedded audio choice changes what is active in the synced result; it is not a destructive replacement of the original file.

    Timecode versus waveform

    MethodUse it whenLimitations
    TimecodeThe recordings have matching, usable timecode from a compatible timing source.Independent clocks can drift. An LTC signal recorded as audio is not automatically metadata, and a starting reference does not prove long-take stability.
    WaveformThe camera file has overlapping scratch/reference audio that resembles the external recording.It can fail or produce a wrong match with silence, noise, clipping, heavy reverb, unrelated takes, missing scratch audio, or a poor channel.
    In point, Out point, or MarkerThe installed version documents these Media Pool methods and you have a trustworthy common reference.They are version-specific options and still require manual verification.

    Diagnosing sync drift

    First separate a constant offset from a growing offset. If the whole clip is early or late by the same amount, manual alignment may be enough. If the beginning is close but the end is increasingly wrong, moving the clip once will not solve the underlying timing disagreement.

    1. Mark or remember a clear sync point near the start.
    2. Check a similar point near the end, and check the middle of a long recording when practical.
    3. Describe the direction: is the sound leading the picture, or lagging it? Record the observed amount and location.
    4. Check device clocking, timecode continuity, frame-rate interpretation, timestamps, and sample-rate metadata. Resolve's video-production example uses 48 kHz, meaning 48,000 samples per second, but that convention does not prove every source was recorded at 48 kHz.
    5. Test any correction on a duplicate timeline and a short export. Do not overwrite the source recording or the only project copy.

    Auto Sync Audio aligns clips; it is not documented as a clock-drift correction or a guarantee for arbitrarily long takes. A measured retime or replacement may be appropriate in some cases, but it should be based on evidence and verified at the beginning, middle, end, and after export. Sample-rate mismatch and clock drift are related but not identical diagnoses, so do not relabel a file or stretch it without understanding the actual source metadata and timing.

    Variable-frame-rate cautions

    Variable frame rate (VFR) video changes frame timing over time, while constant frame rate (CFR) video uses one cadence. Phone and screen recordings are common sources of VFR, but the file's nominal frame-rate number alone is not proof. Diagnose frame-rate mode and, when troubleshooting, inspect timestamps or decoded frames with an appropriate tool.

    1. Preserve the original file and create a new output folder with new filenames.
    2. Use a diagnostic such as MediaInfo's Frame Rate Mode field. It can identify Variable and expose minimum and maximum rates; treat it as a diagnostic, not as a Resolve setting.
    3. If a CFR derivative is appropriate, use a documented external workflow such as HandBrake's Constant Frame Rate option. “Same as Source + CFR” detects the source rate and makes variable portions constant; selecting a particular rate conforms the entire video to that new rate.
    4. Alternatively, an FFmpeg output-rate conversion such as the following creates a new re-encoded file, where frames may be duplicated or dropped to reach the chosen constant rate:
    ffmpeg -i input.mp4 -r 30 output-cfr.mp4

    Do not use stream copy for this purpose, and do not copy an input-side -r command without understanding its different timestamp semantics. A CFR transcode can change motion cadence, so review duration, motion, and audio sync rather than assuming it repairs every unusual recording.

    In Resolve, set the intended project/timeline rate before creating a timeline. The Resolve 20 guide documents Timeline Resolution, Timeline Frame Rate, and a Don’t Change choice when an imported clip has a different rate. It also says that after a timeline is created, the Timeline Frame Rate in Project Settings cannot be changed, although later timelines can have their own settings. These details are version-specific; check the manual for your build.

    Organizing linked and compound clips without destructive baking

    Link Clips and Linked Selection are different

    Clip > Link Clips creates a relationship between already-aligned timeline clips. In the Resolve 20 Editors Guide, linked clips show a chain icon, and moving one without the other can produce a red out-of-sync indicator. The guide documents Option-Command-L on macOS and Alt-Ctrl-L on Windows for this command under the default DaVinci Resolve preset. Confirm the command in your active keymap before publication or production use.

    Linked Selection is a separate toolbar mode. It controls whether linked audio and video parts are selected together; it does not create the link. The Resolve 20 guide documents Shift-Command-L on macOS and Shift-Ctrl-L on Windows under the default preset. A user can have linked clips while Linked Selection is off, or have Linked Selection on without having just created a link.

    Use compound clips as organization, not as a backup

    To make a compound clip, select the intended timeline material, choose the destination bin in the Media Pool, choose Clip > New Compound Clip, name it, and click Create. To inspect or change its contents, select it and choose Clip > Open in Timeline, or use the equivalent context-menu command available in your build.

    A compound clip is a nested project/timeline object. Changes made inside its nested timeline are seen on the parent timeline. It is not an archival copy of the original media and should not be used as a reason to overwrite camera or recorder files. Save a project version and preserve the original bins before experimenting.

    Keep channel and track decisions reversible

    Audio Configuration choices affect which channels are active or edited into a timeline. Disabling a track hides it from timeline editing, while muting leaves it edited in but automatically disabled. Do not delete channels before verifying the synced result. The Resolve 20 guide also documents Timeline > Audio > Detach Synced Audio from Video as a Resolve 20.2 version-specific operation; treat it as a timeline change, not as a replacement of source media.

    For layered timeline edits, select the complete intended range. Selecting only a visible top-layer clip can leave other clips behind and create gaps or unintended overlaps. Sync Lock and ripple behavior can also vary by track state and version, so inspect the track controls before making a major ripple edit.

    Fairlight cleanup after sync

    Sync first, then clean up while preserving an untreated reference. Duplicate the dialogue track before processor-heavy experiments or cache/bounce operations. A clip effect affects a selected clip; a Track FX affects the complete track, so confirm the scope before enabling anything on a track with unrelated clips or speakers.

    1. Audition before processing. Solo the relevant track, use looped playback, watch the viewer and meters, and establish what the untreated material sounds and looks like.
    2. Remove problems conservatively. The Fairlight guide demonstrates De-Hummer before Noise Reduction for material containing hum and broadband noise. Treat this as an example sequence, not a guarantee. Use Noise Reduction's Noise Only/Listen to Noise Only mode to check that recognizable dialogue is not being removed.
    3. Use modest EQ changes. Fairlight provides six-band parametric EQ. Listen while rolling off unnecessary low end, checking muddiness or boxiness, and making a restrained presence adjustment. Example frequency ranges are not universal presets.
    4. Control level in context. Normalize Audio Levels changes clip peak gain, not perceived loudness or scene balance. Dialogue Leveler can reduce loud dialogue, lift soft dialogue, and reduce background noise. Audition the bypass state and follow the actual delivery specification.
    5. Duck music or effects when appropriate. Fairlight's Ducker Track FX can lower a target music/effects track based on one or more dialogue source tracks. Adjust Duck Level, Lookahead, Rise Time, Hold, and Recovery Time while listening; it is not a substitute for a final mix review.
    6. Treat Studio-only tools accurately. The cited Fairlight guide identifies Voice Isolation and Dialogue Separator as DaVinci Resolve Studio features. Voice Isolation can remove natural ambience, and Dialogue Separator has separate Voice, Background, and Ambience controls. Reduce or bypass these tools when the scene becomes unnatural.

    When a measured retime is necessary

    Fairlight's Trim > Slip Audio is different from moving a clip on the timeline: it changes the audio heard inside the clip. The Resolve 20 Fairlight guide demonstrates selecting a clip with the Arrow tool, using Trim > Slip Audio to inspect the installed shortcuts, and holding Option on Mac or Alt on Windows while pressing comma to slip the audio earlier. Do not describe this as a universal increment or as a clip-edge move; inspect the menu in your build.

    For frame-based timeline nudging in the documented Fairlight exercise, the Range tool selects the intended clips, comma nudges left by one frame, and period nudges right by one frame. With layered clips, select across the stack rather than only the visible top clip. Listen before and after every change.

    Resolve 21's cited New Features Guide documents Edit-page audio keyframes with subframe/audio-sample accuracy, between-frame markers, subframe scrubbing with audio feedback when highly zoomed in, and Frames/Subframes/Audio Sample timecode display. These are version-specific Edit-page features, not proof of a universal sub-frame clip-nudge shortcut. A subframe is not automatically a fixed number of audio samples; timing depends on the relevant frame duration, sample rate, media time base, and project settings.

    The same caution applies to Elastic Wave. The Fairlight guide describes it as a way to retime a whole clip or use time keyframes for a local stretch or condense after comparing picture and sound. It is not a promise of perfect correction, and it should never replace a beginning/middle/end check and an export review.

    Verification and QC checklist

    Waveform coincidence is evidence, not proof. Use both visual and auditory checks.

    • Confirm that each synced audio file belongs to the intended camera clip and take.
    • Play a slate/clap or another unmistakable event while watching the visible contact and listening to the transient.
    • Check several phrases, especially consonant attacks and visible mouth movements.
    • For a long take, check near the beginning, middle, and end. Record whether any error is fixed or growing.
    • Listen for room tone and ambience continuity; a wrong take can appear close at one loud event.
    • Check channel count, active/disabled tracks, embedded camera reference audio, and metadata.
    • Review Resolve's failed-clip warning and the Media Pool Synced Audio column where available.
    • Review linked and unlinked states separately. Check the chain icon, Linked Selection state, and any red out-of-sync indicator.
    • Watch meters and the viewer during looped playback. Use JKL auditioning if it is available in your version and keymap.
    • Export a short review file. Check sync at the beginning and end of the exported file, not only inside the timeline.
    • Document any measured offset, its direction, the source files, the Resolve version/edition, and the correction applied.

    For formal delivery, follow the commissioning or platform specification. EBU QC 0098B describes a human-only lip-sync review and shows a configurable example of a 100 ms threshold over a minimum five-second segment; that is an example QC configuration, not a universal web, cinema, or streaming pass/fail rule. ITU-R BT.1359 reports historical broadcast reference values and recommended broadcast-path limits, not a universal Resolve tolerance.

    Common mistakes to avoid

    • Relying on a shortcut from an old tutorial. Shortcuts and menu labels vary. The supplied records verify Shift-S for audio scrubbing, along with several version-specific Fairlight exercises, but they do not verify a universal Auto Sync Audio shortcut.
    • Calling a clap a guarantee. A clap establishes a useful event; it does not prove long-take stability.
    • Assuming waveform matching is frame-perfect for every source. It depends on comparable overlapping audio and can fail or select the wrong location.
    • Using timecode without checking the clocks. Matching labels are useful only when the timecode is actually compatible and the devices have not diverged in a way that matters.
    • Moving a clip when the problem is drift. A single offset adjustment cannot correct an error that grows over time.
    • Confusing Slip Audio with timeline movement. Slip Audio changes the audio content heard inside a clip; it does not mean the clip's timeline position has moved.
    • Treating a compound clip as a backup. It is a nested object whose contents remain editable and can change on the parent timeline.
    • Deleting embedded channels too early. Disable or mute deliberately, retain a reference, and confirm the synced result before removing anything from the edit.
    • Applying track processing to unrelated material. Track FX affect the whole track. Confirm whether you are working at clip or track scope.
    • Assuming normalization fixes dialogue balance. Peak normalization does not account for scene context, perceived loudness, or performance.
    • Calling a CFR transcode a guaranteed VFR repair. It may duplicate or drop frames and can change motion cadence. Test the exact files and review the result.
    • Overwriting originals or the only project version. Keep untouched media and use versioned projects, duplicate timelines, and new output files.

    A compact, reversible workflow

    1. Back up source media and duplicate the project.
    2. Identify the correct camera/audio pair.
    3. Check timecode, scratch audio, channels, and frame-rate mode.
    4. Use Timecode when matching timecode is real; otherwise test Waveform.
    5. If automatic sync fails, align a clear clap or visual/audio event manually.
    6. Verify at multiple points, especially on long takes.
    7. Organize with links or compounds only after alignment is confirmed.
    8. Clean dialogue on a duplicate/reference track.
    9. Export a short QC file and recheck sync.
    10. Keep the original media and document the final correction.

    Conclusion

    The most dependable Resolve sync workflow is evidence-based: protect the source, identify the intended pair, use matching timecode when it is genuinely available, use waveform analysis only when the recordings contain comparable material, and manually align a visible and audible event when automation is uncertain. Then verify the result at more than one point, diagnose drift separately from a fixed offset, and keep the project reversible.

    Resolve's controls evolve. A command documented in Resolve 20, 20.1, 20.2, or 21 may be labeled differently or unavailable in another build, and a shortcut may change with the operating system or keyboard preset. Use the installed version's current Blackmagic manual as the final authority.

    FAQ

    Is there a universal keyboard shortcut for syncing audio and video in Resolve?

    No universal shortcut is established by the supplied records. The documented Media Pool workflow uses the context menu's Auto Sync Audio command and its dialog. Menu names and shortcuts vary by version, OS, page, and keymap, so check the installed manual.

    Should I use timecode or waveform matching?

    Use matching timecode when it is genuinely present, compatible, and aligned. Otherwise use waveform matching when the camera clip has overlapping scratch/reference audio comparable to the external recording. Verify either result manually.

    Why did waveform sync fail?

    The files may not contain enough comparable content. Missing or clipped scratch audio, silence, heavy reverberation, mostly ambience, noisy or unsuitable channels, different microphone feeds, and unrelated takes can all prevent a match or lead to a wrong one. Try a suitable channel or manual alignment.

    Does Auto Sync Audio fix drift?

    It aligns clips; it is not documented as a clock-drift correction. Compare a sync point near the start with one near the end of a long take. If the error grows, investigate device clocks, timecode continuity, frame-rate interpretation, timestamps, and sample-rate metadata before applying a measured correction.

    Does Retain embedded audio delete the camera audio when I turn it off?

    The Resolve 20 Beginner's Guide says that omitting Retain embedded audio does not delete the original embedded audio; it remains accessible through Clip Attributes. Nevertheless, keep source media backed up and verify which channels are active or edited into the timeline.

    Should I make a compound clip after syncing?

    Only if nesting helps organize the edit. A compound clip is an editable nested timeline object, not an archival copy and not a substitute for a project backup. Preserve original bins/media and make a clearly named project or timeline version before experimenting.

    Can I use Slip Audio or Elastic Wave for sub-frame correction?

    Use them only when the installed version documents the relevant operation and after you have measured the problem. Slip Audio changes audio content inside a clip; it is not the same as moving the clip. Elastic Wave can retime a clip or a local section, but neither is a universal guarantee. Resolve 21's documented subframe/audio-sample Edit-page features are version-specific and should not be generalized to every page or release.

    Should I convert VFR footage to CFR?

    If the footage is VFR and the test shows timing or editing problems, a separate CFR derivative can be a conservative workflow. Keep the original, use a new output path, and test duration, motion, and sync at several points. A CFR conversion can duplicate or drop frames and is not guaranteed to repair every source.

    What is the best way to check a final sync?

    Watch and listen together. Check a clap or clear event, several dialogue phrases, the beginning/middle/end of a long take, channel assignments, and a short exported file. Follow the actual delivery specification rather than treating a historical broadcast threshold as a universal rule.

    Sources

    The workflow above was written only from the supplied research records. The primary references are:

    Information checked against the linked official sources in September 2026; DaVinci Resolve features and documentation may change.

    A close-up shot of an editor's hands on a backlit mechanical keyboard and a professional editing console, intense focus, dramatic chiaroscuro lighting, cinematic atmosphere.

    Read more information: The 2026 Design Arsenal: 15 AI Chrome Extensions for Elite Workflows


    Post a Comment

    0 Comments
    * Please Don't Spam Here. All the Comments are Reviewed by Admin.

    In-Article Ad (Long Posts Only)

    Below Post Ad