Podcast audio goes out of sync with video for three main reasons: the files started at different times, the audio and video gradually ran at different speeds, or frames and audio samples were dropped during recording.

The correct fix depends on which problem you have.

A fixed offset means the audio is early or late by the same amount throughout the episode.
Progressive drift means the episode begins in sync but moves farther out of sync over time.
A sudden sync jump means the timing changes abruptly at one or more points.

Moving an audio track left or right can fix a constant offset. It cannot fix progressive drift. Similarly, automatic waveform synchronization can align the beginning of two files without correcting timing differences that accumulate during a long recording.

This guide will help you identify the type of synchronization problem, understand its cause, repair the episode, and prevent audio drift during future recordings.

Audio offset vs. audio drift

Audio offset and audio drift are related, but they are not the same problem.

What is a fixed audio offset?

A fixed offset occurs when the audio and video have the same duration but start at different times.

For example, the guest’s voice might be half a second ahead of their lips at the beginning, middle, and end of the episode.

Common causes include:

Starting the camera and audio recorder at different times
Bluetooth monitoring latency
Incorrect synchronization during editing
Moving a track accidentally
Export or playback delay
Missing or inaccurate timecode

A fixed offset is usually straightforward to repair. Move the audio until a clear sound matches the corresponding video frame.

What is progressive audio drift?

Audio drift occurs when two recordings run at slightly different effective speeds.

The episode may begin perfectly synchronized. Twenty minutes later, the guest’s voice is visibly ahead of their lips. After an hour, the difference may be several frames—or even several seconds.

Moving the entire audio track will not solve this. Aligning the end will cause the beginning to fall out of sync.

Progressive drift usually requires a small duration or speed adjustment.

What is a sudden sync jump?

A sudden jump occurs when audio or video disappears, repeats, freezes, or changes timing at one particular point.

The recording might remain synchronized for 25 minutes, suddenly jump out by half a second, and then maintain that new offset for the rest of the episode.

Possible causes include:

Dropped video frames
Missing audio samples
A recording pause
A browser, camera, or encoder interruption
A participant leaving and rejoining
A damaged file segment
Cloud recording affected by connection loss

Sudden jumps must normally be repaired at the point where the discontinuity occurs.

How to identify your sync problem

Before changing frame rates or stretching audio, diagnose the pattern.

Step 1: Find a clear synchronization point near the beginning

Look for a moment that produces a visible action and a sharp sound:

A hand clap
A finger snap
A hard consonant
A laugh
An object touching the desk

Zoom into the timeline and align the sound’s waveform peak with the corresponding video frame.

Step 2: Check the middle of the episode

Move to a section approximately halfway through the recording and observe the guest’s lips.

If the middle remains synchronized, continue to the end.

If the audio is already drifting, note whether it is ahead of or behind the video.

Step 3: Check the end

Find another clear word, clap, or visible sound near the end.

Then classify the problem:

Beginning, middle, and end are off by the same amount: fixed offset.
Beginning is correct but the error grows steadily: progressive drift.
The sync changes abruptly at a particular point: dropped or duplicated media.
Only the editor preview is wrong, but the exported file is correct: playback or system-performance problem.
The editor is correct, but the export is wrong: timeline, frame-rate, codec, or export-setting problem.

Step 4: Compare every available track

Do not assume the external audio file is wrong.

Compare:

The camera’s scratch audio
The external microphone recording
Each participant’s isolated track
The mixed recording
A cloud or streaming backup
Screen recordings
Any locally recovered files

The camera’s lower-quality scratch track is particularly useful as a timing reference, even when it will not appear in the finished episode.

This is one reason professional editors prefer isolated tracks instead of a single mixed recording. Separate files make it easier to identify which participant or device introduced the problem.

Why podcast audio and video go out of sync

Several issues can produce similar-looking symptoms. Understanding the cause helps you choose the least destructive repair.

1. The files started at different times

When audio and video are recorded on separate devices, the recordings rarely begin on the same frame.

This is normal. Editors typically synchronize files using:

Timecode
Matching audio waveforms
A slate or hand clap
File creation timestamps
Manual markers

Adobe Premiere can merge audio and video using synchronization points, while Final Cut Pro can analyze timecode, markers, creation dates, and audio waveforms. These automatic tools are useful for establishing initial synchronization, but they cannot always repair drift that develops later.

See Adobe’s audio and video synchronization guide or Apple’s Final Cut Pro synchronization instructions.

2. Separate devices have separate internal clocks

Two recording devices do not measure time with perfect agreement.

A camera, audio interface, phone, and computer each use an internal clock. One device may record a tiny fraction faster than another. The difference is almost invisible during a short clip but can become noticeable during a one- or two-hour podcast.

Imagine that an audio recorder captures what it considers exactly one hour while the camera’s internal clock measures the same period as one hour and three seconds. The files begin together but do not have the same final duration.

This clock difference is one of the most common causes of gradual drift in recordings captured on independent devices.

Professional studio systems may use shared timecode, word clock, or synchronized hardware. Remote podcasts normally depend on software to align and manage independently recorded tracks.

3. Sample rates were interpreted incorrectly

Sample rate describes how many audio samples are captured each second. Common rates include:

44.1 kHz
48 kHz
96 kHz

Video production commonly uses 48 kHz audio.

Modern editing software can usually resample 44.1 kHz audio into a 48 kHz timeline without creating drift. Problems can occur when a file’s sample rate is interpreted incorrectly, its metadata is damaged, or it is converted improperly.

For example, audio captured at one rate but treated as though it were recorded at another will play at the wrong speed and duration.

Simply seeing 44.1 kHz and 48 kHz files in the same project does not prove that sample rate caused the drift. Check how the editing application interpreted and converted the files before changing them.

For more on podcast audio formats, see What Is Lossless Audio? And Other Bitrate Questions for Podcasters.

4. The video uses a variable frame rate

Constant-frame-rate video maintains a consistent number of frames per second. Variable-frame-rate video changes the frame rate according to motion, lighting, device performance, or available resources.

Phones, webcams, meeting applications, and screen-recording tools may create variable-frame-rate footage.

Many modern editors support these files, but variable frame rates can still create synchronization or playback problems in certain workflows—particularly after transcoding, proxy generation, multicamera editing, or interchange between applications.

If a phone or screen recording drifts while other files remain synchronized, inspect whether the problem file uses a variable frame rate.

Transcoding it to a constant-frame-rate editing format before cutting may solve the issue.

5. Frames or audio samples were dropped

An overloaded computer may fail to record every expected video frame or audio sample.

Possible causes include:

Insufficient processing power
Inadequate device storage
An overheating computer or phone
Competing applications
A slow external drive
Browser instability
Camera capture problems
An interrupted cloud recording

When media is dropped, the resulting problem may appear as a sudden jump rather than smooth progressive drift.

A cloud-only recording is particularly exposed to connection problems because the recorded media must travel across the network in real time. Local recording captures media at each participant’s device before uploading it.

Learn more about the distinction in Local vs. Cloud Recording: Why the Internet Shouldn’t Control Your Podcast.

6. A participant disconnected or changed devices

When a remote guest leaves and rejoins, the platform may create a new file segment.

Those segments can have:

A different starting point
A gap between files
Overlapping media
A different microphone
A different camera
New timing metadata

The editor may need to align each segment independently.

A recording platform with progressive uploads and recovery tools can reduce the chance that a brief disconnection becomes a lost or unusable episode. See What Happens When a Guest Disconnects Mid-Recording? for a detailed explanation.

7. Bluetooth introduced a constant delay

Bluetooth devices buffer audio before playing or recording it. This delay normally creates a fixed offset rather than progressive drift.

If the audio remains late by the same amount for the entire recording, Bluetooth or monitoring latency may be responsible.

Whenever practical, record with a wired microphone and wired headphones. If Bluetooth must be used, confirm that the intended microphone is selected and make a test recording before the interview.

8. The editing timeline or export settings are wrong

Sometimes the source files are synchronized, but the editing project is not.

Check:

Timeline frame rate
Audio sample rate
Proxy settings
Interpreted footage settings
Nested or compound clips
Speed changes
Multicamera synchronization
Export frame rate
Export codec
Audio processing plug-ins

Create a short test export around an obvious sync point. If the timeline preview and export behave differently, the issue is probably in the editing or export pipeline rather than the original recording.

Is audio drift the same as podcast latency?

No.

Latency is the live delay between one person speaking and another person hearing them. It can cause awkward pauses, interruptions, and people talking over one another.

Audio drift is a recorded timing difference that increases over time.

A weak internet connection can create latency during the conversation. It may also cause missing or interrupted media in a cloud recording. However, latency does not automatically mean properly captured local files will drift.

Local recording protects the quality of the final tracks, but it cannot eliminate the real-time communication delay between people in different locations.

Our guide to reducing latency during remote podcast recording covers the live-conversation side of the problem.

How to fix podcast audio that is out of sync

Always duplicate the project or sequence before making timing changes. Preserve the original files.

Fix 1: Move a track to correct a fixed offset

Use this method when the sync error remains constant.

Find a sharp waveform peak near the beginning.
Locate the matching action in the video.
Move the audio track until the two events align.
Check several points throughout the episode.
Lock or group the synchronized tracks.

Use subframe audio adjustments when the editor supports them. Moving audio only in whole video frames may not provide sufficient precision.

If the track remains synchronized throughout the episode, no speed correction is necessary.

Fix 2: Use automatic waveform synchronization

When the camera recorded scratch audio, editing software can compare that waveform with the higher-quality external recording.

Premiere, Final Cut Pro, and DaVinci Resolve all provide waveform-based synchronization options.

Automatic synchronization works best when:

Both files contain the same continuous sound
Scratch audio is clear enough to analyze
Neither file has long silent sections
The recordings have not already been heavily edited
The files have similar start and end points

After automatic synchronization, check the end of the episode. A successful starting alignment does not guarantee that the recordings will remain synchronized.

Fix 3: Time-stretch a track that drifts gradually

If the beginning is synchronized but the end is not, adjust the duration of the drifting track.

A practical workflow is:

Align the beginning.
Find a clear synchronization point near the end.
Measure the duration of the reference track.
Measure the corresponding duration of the drifting track.
Stretch or compress the drifting track until both end points align.
Enable pitch preservation when adjusting audio.
Check synchronization at several points between the beginning and end.

For a precise speed adjustment:

New speed percentage = drifting duration ÷ reference duration × 100

If the drifting audio lasts 3,603 seconds while the correct video segment lasts 3,600 seconds:

3,603 ÷ 3,600 × 100 = 100.0833%

The audio would need to play approximately 0.0833% faster to match the video duration.

Editing applications express time correction differently. Some request a speed percentage; others allow you to enter the desired duration or drag the end of a clip while using a stretch tool.

Use the smallest correction necessary. Large speed changes may indicate dropped media or incorrect file interpretation rather than ordinary clock drift.

Fix 4: Repair a sudden jump

If synchronization changes abruptly, locate the exact frame where the jump begins.

Look and listen for:

A frozen frame
Repeated audio
Missing words
A visible cut
Silence
A participant reconnecting
A change in microphone or camera quality

Split the affected track at that point. Then move the material after the split until it is synchronized again.

Depending on what is missing, you may need to:

Remove duplicated frames
Insert a short video hold
Add room tone
Cover the repair with another camera angle
Use B-roll or a branded layout
Create a crossfade
Cut an incomplete phrase
Replace the section with a backup recording

Do not stretch the entire episode to repair one isolated jump.

Fix 5: Transcode variable-frame-rate video

If a phone, webcam, or screen recording repeatedly loses sync inside the editor, create a constant-frame-rate copy.

Choose a frame rate matching the intended editing timeline, such as:

24 fps
25 fps
29.97 fps
30 fps

Keep the original media. Transcode from the source file rather than repeatedly converting an already compressed export.

After transcoding, import the new file and synchronize it with the original audio.

Fix 6: Rebuild the edit from isolated tracks

When a mixed recording contains irreparable timing errors, return to the original participant tracks.

Isolated tracks let you repair one speaker without affecting the others. They also make it possible to replace damaged video with another layout while retaining clean audio.

This is often faster than trying to repair a flattened final file.

For additional workflow guidance, see The Professional Podcast Workflow: Record, Clip, Publish.

How to prevent podcast audio drift

Prevention begins before recording.

Use a local recording platform

Choose a platform that records each participant on their own device and synchronizes the files after capture.

Boomcaster records individual audio and video tracks locally, uploads them progressively, and provides automatic synchronization and recovery tools. This prevents the final quality from depending entirely on the live internet connection.

Record isolated tracks

Capture separate audio and video for every participant.

Individual tracks make synchronization problems easier to diagnose and repair. They also give editors control over volume, noise, framing, color, and timing.

Use consistent production settings

Where possible:

Record audio at 48 kHz for video production.
Choose a consistent video frame rate.
Use constant-frame-rate cameras or recording formats.
Avoid unnecessary format conversions.
Confirm that the editing timeline matches the intended delivery format.
Keep source files in their original form.

Record a synchronization clap

At the beginning of the session, ask everyone to clap once where their camera can see it.

For long or high-value recordings, consider another clap at the end. Two reference points make progressive drift easier to measure.

Remote participants will not clap at precisely the same instant because of network latency. Each visible clap should be matched with the corresponding sound on that participant’s local track.

Avoid switching equipment during the session

Changing a microphone, camera, browser, or device can create a new recording segment or timing reference.

If a change is necessary:

Pause the conversation.
Mark the time.
Confirm the new device.
Make another synchronization clap.
Resume with a complete sentence.

Run a preflight check

Before recording:

Restart devices when appropriate.
Close unnecessary applications.
Confirm available storage.
Connect computers to power.
Select the correct microphone and camera.
Verify audio sample rates.
Check camera frame rates.
Record and review a short test.
Confirm that every participant is being captured.

A repeatable setup is one of the most effective ways to prevent the hidden technical problems that cause podcast episodes to fail. See Why Podcasts Fail: The Hidden Technical Reasons Episodes Get Lost.

Confirm every upload before leaving

Do not let participants close their browser or recording application until all local files have finished uploading.

The host or producer should confirm:

Every expected participant track exists.
The files have the expected duration.
Reconnected participants have no missing segments.
Audio and video can be previewed.
The platform reports that processing or upload is complete.

Frequently asked questions

Why does my podcast begin in sync and end out of sync?

The audio and video were probably recorded at slightly different effective speeds. Separate device clocks, incorrectly interpreted sample rates, variable-frame-rate video, or dropped media can cause this progressive drift.

Can I fix audio drift by moving the audio track?

Moving the track fixes a constant offset. It does not fix progressive drift. When the error grows over time, the drifting file’s duration or speed must usually be adjusted.

Can different sample rates cause audio drift?

They can when a file is interpreted or converted incorrectly. Modern editing software normally resamples common rates correctly, so the presence of both 44.1 kHz and 48 kHz files does not automatically prove that sample rate caused the problem.

What sample rate should I use for a video podcast?

48 kHz is the standard choice for audio used with video. Use consistent settings throughout recording, editing, and export whenever possible.

Does a clap prevent audio drift?

A clap does not prevent drift. It creates a clear synchronization point. A clap at both the beginning and end can help an editor measure whether two recordings changed duration relative to each other.

Why does my phone video go out of sync?

Phones may record using variable frame rates, especially under difficult lighting or device load. Transcoding the footage to a constant frame rate can improve compatibility with an editing timeline.

Will local recording prevent audio drift?

A well-designed local recording platform can synchronize participant files and protect them from network-related dropouts. Independently operated cameras and external audio recorders may still experience clock drift unless they share synchronization or are corrected in post-production.

Is the preview out of sync because my computer is slow?

Possibly. Editors may drop preview frames or delay audio when the system cannot play a complex project in real time. Create a short test export before modifying synchronized source files.

Keep your podcast synchronized from the start

An out-of-sync podcast is not one problem with one solution.

First determine whether you have a fixed offset, progressive drift, or a sudden jump. Then apply the appropriate repair: reposition the track, adjust its duration, transcode variable-frame-rate footage, or rebuild the affected section.

The better solution is to prevent synchronization problems during recording.

Boomcaster captures every participant locally in studio-quality audio and up to 4K video, creates isolated tracks, synchronizes the files, and monitors recording and upload progress throughout the session.

Explore Boomcaster’s remote recording studio or start recording with Boomcaster.