How to Fix Screen Recording Audio Out of Sync

You finish a 30-minute tutorial recording, scrub through the timeline, and notice the audio drifts further out of sync with every passing minute. By the end, lips move a full second before words arrive. The recording is unusable, and you have no idea what went wrong.

Audio-video sync issues are one of the most frustrating problems in screen recording because they are invisible during capture and only reveal themselves in playback or editing. The root causes are technical, but the fixes are straightforward once you understand what is happening at the container and codec level.

This guide breaks down the four primary causes of audio drift and walks through targeted fixes for each one.

Why Audio Drifts: The Technical Foundation

Audio and video are recorded as separate streams, then multiplexed into a single container file (MP4, MOV, MKV). Each stream has its own clock: video timestamps derive from frame capture timing, while audio timestamps derive from the sound card's sample clock. When these two clocks disagree about how much time has passed, drift accumulates.

A perfectly synchronized recording requires three conditions:

1. Constant frame rate (CFR) on the video stream
2. Matched sample rates between input device and recording software
3. Sufficient CPU headroom so neither stream drops data

Violate any of these, and sync degrades proportionally to recording duration.

Cause 1: Variable Frame Rate (VFR) Encoding

What Happens

Most screen recorders, including macOS built-in tools and many third-party apps, default to variable frame rate encoding. VFR adjusts the frame rate dynamically: when the screen is static, fewer frames are written; when there is motion, more frames appear. This saves disk space but creates timestamp irregularities.

Video players and editors interpret VFR timestamps differently. QuickTime Player may play a VFR file correctly, but Premiere Pro, DaVinci Resolve, or Final Cut Pro may assume constant timing between frames. The result is progressive audio drift that worsens over time.

How to Diagnose

Use MediaInfo (free, available via Homebrew) to check your recording:

brew install mediainfo
mediainfo --Inform="Video;%FrameRate_Mode%" your-recording.mp4

If the output says Variable, you have a VFR file.

The Fix: Convert VFR to CFR with HandBrake

1. Open HandBrake and load your recording
2. Go to the Video tab
3. Set Framerate to your target (30 or 60 fps)
4. Select Constant Framerate (not "Peak Framerate")
5. Start the encode

HandBrake will interpolate timestamps to produce evenly-spaced frames while preserving the audio stream. After conversion, import the CFR file into your editor.

Prevention: Choose a recorder that outputs CFR by default. Screenify Studio records at constant frame rate with Metal-accelerated encoding, so the file is editor-ready without conversion. If you are using OBS, go to Settings, then Output, then Recording, and confirm the encoder is set to a constant frame rate profile.

Cause 2: Sample Rate Mismatch (44.1 kHz vs 48 kHz)

What Happens

Audio hardware and software each have a preferred sample rate. USB microphones often default to 48 kHz (the video production standard), while some audio interfaces and Bluetooth devices operate at 44.1 kHz (the CD audio standard). When your mic runs at 44.1 kHz but the recorder captures at 48 kHz, the software resamples on the fly. Under load, resampling introduces micro-gaps that accumulate into audible drift.

The math: a 44.1-to-48 kHz mismatch means the recorder expects 48,000 samples per second but receives only 44,100. Over one hour, the accumulated timing error can reach 200 to 400 milliseconds, depending on how the recorder's resampling buffer handles the deficit.

How to Diagnose

On macOS, open Audio MIDI Setup (Applications, then Utilities). Select your input device and check its sample rate. Then check what your recording software expects.

If they differ, you have found the problem.

The Fix: Align Sample Rates

1. Open Audio MIDI Setup
2. Select your microphone in the left sidebar
3. Set the Format dropdown to 48,000 Hz (or whatever your recorder uses)
4. If using an audio interface, also match the rate in the interface's control software

For OBS users: go to Settings, then Audio, and set the Sample Rate to match your device. For most screen recording, 48 kHz is the correct choice because video containers expect it.

Cause 3: CPU Overload During Recording

What Happens

When CPU usage spikes (compiling code, running virtual machines, rendering previews), the recording software may not get enough processing time to encode both streams in real time. Video frames get dropped, audio buffers overflow or underflow, and the two streams fall out of alignment.

This is especially common with software encoders (x264, x265) that compete for the same CPU cycles as your workflow. Hardware encoders (Apple VideoToolbox, NVIDIA NVENC) are far more resilient because they offload encoding to dedicated silicon.

How to Diagnose

Open Activity Monitor during recording and watch CPU usage. If total CPU exceeds 80 to 90 percent consistently, your recorder is likely dropping frames. You can confirm by checking the recording file with MediaInfo:

mediainfo --Inform="Video;%FrameRate/String%\n%FrameCount%" your-recording.mp4

Compare the actual frame count against the expected count (duration in seconds multiplied by frame rate). A significant shortfall means frames were dropped.

The Fix: Reduce Encoding Load

Immediate fixes:

• Close unnecessary applications during recording
• Reduce recording resolution from 4K to 1080p if your workflow allows it
• Lower the frame rate from 60 to 30 fps for non-motion content
• Quit browsers with many open tabs (each tab consumes CPU)

Architectural fixes:

• Switch to a hardware-accelerated encoder. On Mac, recorders using Apple's VideoToolbox API offload H.264/H.265 encoding to the media engine, leaving the CPU free for your work
• Record to a separate drive (external SSD) so disk I/O does not compete with your system drive
• If using OBS, switch the encoder from x264 to Apple VT H264 Hardware Encoder under Settings, then Output

Screenify Studio uses Metal-accelerated encoding on Apple Silicon, which means the dedicated media engine handles compression while the CPU remains available for your workflow. This eliminates the CPU contention that causes drift in software-encoded recordings.

Cause 4: Bluetooth Audio Latency

What Happens

Bluetooth audio codecs introduce inherent latency. The standard SBC codec adds 150 to 250 milliseconds of delay. AAC over Bluetooth adds 90 to 150 milliseconds. AptX Low Latency reduces this to around 40 milliseconds, but most Mac-compatible devices do not support it.

When you monitor audio through Bluetooth headphones during recording, the latency is constant and your brain adapts. But when the recorder captures audio from a Bluetooth microphone, the variable buffering in the Bluetooth stack can cause inconsistent timestamp gaps in the audio stream.

How to Diagnose

If you are recording with AirPods, Beats, or any Bluetooth headset as the input device, Bluetooth latency is almost certainly contributing to sync issues. The simplest test: record the same content with a wired mic and compare the sync.

The Fix: Use Wired Audio

For recording, always prefer wired connections:

• USB microphone connected directly (not through a hub)
• 3.5mm headset using the Mac's headphone jack
• Audio interface with XLR or TRS inputs, connected via USB or Thunderbolt

If you must use Bluetooth for monitoring (listening), ensure the input device is still wired. macOS allows different input and output devices in System Settings, then Sound.

Fixing Sync Issues in Post-Production

If you already have a recording with audio drift, here are repair strategies:

Manual Offset in Your Editor

1. Find a reference point early in the recording (a click sound, a keystroke, a visible action with an audible result)
2. Zoom into the timeline and measure the offset between the visual event and its audio
3. Shift the audio track by that amount
4. Check another reference point later in the recording

If the drift is constant (same offset throughout), a single shift fixes it. If the drift is progressive (gets worse over time), you need the VFR-to-CFR conversion described above before the offset will be consistent.

Using FFmpeg for Automated Correction

For a constant offset, FFmpeg can shift the audio stream without re-encoding:

# Delay audio by 200ms
ffmpeg -i input.mp4 -itsoffset 0.2 -i input.mp4 -map 0:v -map 1:a -c copy output.mp4

For VFR-to-CFR conversion with audio passthrough:

ffmpeg -i input.mp4 -r 30 -c:v libx264 -preset fast -c:a copy output-cfr.mp4

DaVinci Resolve Auto-Sync

DaVinci Resolve's Edit page has an auto-sync feature: right-click clips on the timeline, select Auto Align Clips, then choose Based on Sound. This uses audio waveform matching to align tracks automatically.

Prevention Checklist

Before every recording session, run through this checklist:

• Recording software set to constant frame rate
• Audio input sample rate matches recorder setting (48 kHz recommended)
• Microphone connected via USB or wired connection
• CPU usage under 70% before starting
• Sufficient disk space (at least 50 GB free for long recordings)
• Hardware encoder enabled (VideoToolbox / Metal)
• Test recording of 2 minutes, reviewed before the real session

These seven checks take under a minute and eliminate the vast majority of sync problems.

Related Reading

If you are troubleshooting other recording issues, these guides cover adjacent problems:

• Screen recording lag and performance optimization
• How to screen record on Mac with audio capture
• Complete guide to screen recording on Mac

FAQ

Q: Why does audio sync get worse the longer I record?

Progressive drift almost always indicates variable frame rate encoding. Each dropped or duplicated frame shifts the video timeline by one frame duration (33ms at 30fps), and these errors accumulate. Convert to constant frame rate to fix existing recordings, and configure your recorder for CFR to prevent it.

Q: Does recording resolution affect audio sync?

Indirectly, yes. Higher resolutions (4K, ultrawide) require more CPU and GPU resources for encoding. If the encoder cannot keep up, frames drop, and sync degrades. Recording at 1080p instead of 4K significantly reduces the chance of sync issues on older hardware.

Q: Can I fix audio sync in iMovie?

iMovie has limited audio offset controls. You can detach the audio track (right-click the clip, select Detach Audio) and drag it manually. However, iMovie does not handle VFR-to-CFR conversion, so if progressive drift is the issue, convert the file with HandBrake first.

Q: Why is my OBS recording audio out of sync but the stream is fine?

OBS uses different encoding paths for streaming and recording. The stream uses the real-time encoder with strict timing, while the recording may use a different encoder or container. Check that your Recording output uses the same encoder as your Stream output, and ensure Constant Framerate is enabled in the Output settings.

Q: Does Apple Silicon eliminate sync issues?

Apple Silicon's dedicated media engine makes hardware encoding significantly faster and more reliable, which reduces CPU-related sync problems. However, VFR encoding and sample rate mismatches can still cause drift regardless of hardware. The silicon handles the encoding, but the software still controls the frame rate mode and audio pipeline.

Q: My audio syncs fine in QuickTime but drifts in Premiere Pro. Why?

QuickTime Player is lenient with VFR files and dynamically adjusts playback timing. Premiere Pro (and most professional editors) assume constant frame rate and map frames to a fixed timeline. The file has always been VFR; QuickTime was just compensating for it. Convert to CFR before importing into Premiere.

Q: How much audio drift is noticeable?

Most people perceive audio-video desynchronization at around 45 to 90 milliseconds. Lip sync becomes noticeably wrong at 100+ milliseconds. Professional broadcast standards require sync within plus or minus 15 milliseconds. For screen recordings, keeping drift under 50 milliseconds ensures a professional result.

Q: Will using an external audio recorder and syncing in post avoid these issues?

Recording audio separately (with a dedicated recorder or phone) and syncing in post is a reliable workaround. Use a clap or audible marker at the start, align the waveforms in your editor, and the sync will be frame-accurate. This is common in professional video production and works well for screen recordings with voiceover.