HandBrake Audio Out of Sync After Encode: How to Fix It

When HandBrake audio is out of sync after an encode, the first task is to identify the type of synchronization error. Audio that remains ahead of or behind the picture by the same amount has a constant offset. Audio that begins correctly but gradually moves out of sync has progressive drift. These symptoms usually point to different causes, including irregular source timestamps, variable frame rate video, an unsuitable frame rate setting, a problematic audio track, hardware encoder behavior, or playback software. The steps below help Windows, macOS, and Linux users isolate the cause without repeatedly changing unrelated settings.

1. Confirm the Symptom With a Small Test Encode or Preview

Do not begin by re-encoding an entire movie or long recording. A short, carefully selected test can reveal whether the problem comes from HandBrake, the source, or the player while saving substantial time.

1.1 Determine Whether the Problem Is Offset or Drift

Play the output near the beginning, middle, and end. Look for visible events that have matching sounds, such as speech, clapping, a door closing, or an object striking a surface.

• Constant offset: The audio is early or late by approximately the same amount everywhere.
• Progressive drift: The audio starts close to correct but becomes increasingly early or late.
• Sudden sync change: Synchronization is acceptable until a particular edit, damaged section, or timestamp discontinuity.

A constant offset may originate in the selected audio track, an existing delay in the source, or the way a player interprets timestamps. Progressive drift more often suggests irregular timing, variable frame rate handling, damaged timestamps, or missing and duplicated frames. A sudden change points toward a damaged segment or discontinuity in the source.

Once you classify the symptom, stop changing settings unrelated to that category. For example, bitrate and picture quality usually do not correct a consistent timing offset.

1.2 Test the Source and Output in Multiple Players

Open both the original source and the HandBrake output in at least two capable media players. VLC is a useful cross-platform option, but it should not be the only test if another reliable player is available. On Windows, you might compare VLC with the built-in Media Player. On macOS, compare VLC with QuickTime Player when the format is supported. Linux users can compare VLC with mpv or another established player.

If the output is synchronized in one player but not another, the encode may be valid. The failing player could have a demuxing, decoding, audio-device, or hardware acceleration problem. Update or reset that player before re-encoding. Also disable its audio-delay feature if it was previously adjusted.

If the source is already out of sync in every player, HandBrake cannot reliably reconstruct timing that is absent or incorrect. The source may need to be repaired, remuxed, or captured again before conversion.

1.3 Create a Short Test That Includes the Failure

Use HandBrake's range controls to encode a short chapter, a limited time range, or a representative section. For progressive drift, a test from only the first minute may look perfect, so include a section near the end or make a long enough sample for the drift to appear. For a sudden sync change, test across the exact point where synchronization breaks.

A successful test remains synchronized before and after the problem area in multiple players. When that happens, use the same settings for the complete encode and stop making changes.

2. Check the HandBrake Settings Directly Related to This Problem

Most HandBrake controls do not affect synchronization. Focus on frame rate mode, audio track selection, audio passthrough, and any settings that change the timing path.

2.1 Understand Variable, Peak, and Constant Frame Rate

Screen recordings, phone videos, video calls, game captures, and some camera files commonly use variable frame rate. Frames do not necessarily arrive at perfectly even intervals. Instead, timestamps tell the player when each frame should appear.

HandBrake's frame rate controls include options that preserve variable timing or produce a constant frame rate output. When the frame rate is set to Same as Source, Peak Frame Rate allows the output to remain variable up to the selected limit. Constant Frame Rate creates evenly timed output frames at the chosen rate, duplicating or dropping frames when necessary.

For a normal source with valid timestamps, Same as Source with Peak Frame Rate is a sensible first test because it avoids imposing an arbitrary cadence. However, some editing programs, devices, or workflows require constant frame rate. For problematic screen recordings or phone footage, test Same as Source with Constant Frame Rate. This can normalize the timeline, though it cannot restore missing timing information from a severely damaged source.

Do not choose a random frame rate simply because it is common. Converting 25 fps footage to 30 fps, for example, can introduce unnecessary frame duplication. Start with Same as Source. If a fixed rate is required, choose the rate that accurately represents the source.

Success means lip movements and impact sounds remain aligned from the beginning through the end, with no growing delay. If the constant-frame-rate test works, retain it and stop experimenting with unrelated video quality controls.

2.2 Test Audio Passthrough Against Converted Audio

Audio passthrough copies a compatible compressed audio stream instead of decoding and encoding it again. This preserves the original stream, but it can also preserve unusual timing behavior or create compatibility issues with a particular container or playback device.

If the failing encode uses passthrough, make a test with the audio converted to a broadly supported format such as AAC. Choose a normal sample rate setting, typically Auto unless your workflow requires a specific value. If converted audio is out of sync but passthrough works, test a different audio encoder or container and inspect the log for audio-related warnings.

This is a diagnostic comparison, not a rule that one mode is always better. Success means one audio path plays in sync across multiple players. Once identified, use that path for the complete job.

2.3 Verify the Selected Audio Track

DVDs, Blu-ray sources, broadcast recordings, and multilingual files can contain several audio tracks. Some tracks may be commentary, descriptive audio, alternate cuts, or streams with different delays. Confirm the language, codec, channel layout, and track number in HandBrake before encoding.

Encode the same short range with one audio track at a time. If only one track fails, the issue belongs to that stream rather than the entire video. Select the working track or repair the problematic stream before conversion.

2.4 Remove Unnecessary Variables

During testing, avoid complex presets, custom command-line options, multiple audio tracks, and unnecessary filters. Use a built-in preset close to your delivery needs, then alter only the setting being tested.

Video filters can change frame processing, but ordinary deinterlacing or scaling should not be treated as the first suspect without evidence. Likewise, raising the bitrate or using a slower quality preset will not normally repair timestamps.

3. Check Source, Hardware, Subtitle, and Playback Factors

An encode can appear to be a HandBrake failure even when the underlying cause is outside HandBrake. Examine the source, storage path, hardware path, subtitle behavior, and playback chain.

3.1 Inspect Screen Recordings and Phone Videos Closely

Screen recorders may reduce or vary frame delivery when the computer is overloaded. Phones may alter frame timing in response to lighting, heat, stabilization, or processing demands. These files can play normally in tolerant software while exposing timing irregularities during transcoding.

Try a Same as Source encode first, then compare Peak Frame Rate with Constant Frame Rate. If both drift, inspect the source in another analysis or playback tool. If the source itself shows discontinuities, repair or normalize it before asking HandBrake to perform the final conversion.

3.2 Look for Damaged or Discontinuous Timestamps

Video and audio streams use timestamps to maintain synchronization. Interrupted recordings, incomplete downloads, concatenated clips, damaged containers, capture failures, and poorly authored discs can contain timestamps that jump backward, leap forward, or reset.

Symptoms include a sudden sync shift, a frozen section followed by accelerated playback, missing frames, or a player reporting an unexpected duration. HandBrake may compensate by dropping or duplicating video frames, but compensation has limits when the source timeline is contradictory.

If the same point fails with multiple HandBrake settings, repair or remux the source using an appropriate trusted media tool before encoding. Remuxing rewrites the container without necessarily re-encoding the streams and can correct some container-level timing problems. Severely damaged streams may require re-encoding, recapturing, or obtaining a clean lawful source.

3.3 Compare Hardware and Software Video Encoders

Hardware encoders use dedicated capabilities provided by Intel, NVIDIA, AMD, or Apple hardware. They are generally fast, but drivers and hardware-specific paths add variables. If the problem occurs with a hardware video encoder, repeat the short test with a software encoder such as an x264 or x265 option available in HandBrake.

If software encoding stays synchronized while hardware encoding does not, update the operating system and graphics driver from the hardware or computer manufacturer. You can continue with the software encoder if speed is acceptable. If both paths fail identically, the source timing or audio path is more likely responsible.

3.4 Test Without Subtitles

Subtitles normally do not alter audio timing, but burned-in subtitles require video processing, and malformed subtitle timing can complicate diagnosis. Create one test without subtitle tracks. If that works, add the required subtitle track back and test again.

Also make sure you are not mistaking inaccurate subtitle timing for audio drift. Compare speech directly with facial movement rather than comparing spoken words only with subtitle appearance.

3.5 Eliminate Storage and Playback Device Problems

Encode to a local internal drive with adequate free space. Avoid a network share, unstable external drive, cloud-synchronized folder, or removable device during the diagnostic test. Storage trouble more commonly causes failed or corrupted output than smooth progressive drift, but removing it simplifies the test.

Disconnect Bluetooth headphones or speakers and test through built-in or wired audio. Bluetooth introduces playback latency, although a stable device delay usually creates constant offset rather than progressive drift. If only one television, receiver, browser, or streaming device is out of sync, investigate that playback chain before changing the encode.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake's Activity Log records the source scan, selected streams, frame rate decisions, encoder details, warnings, and final statistics. Save the log immediately after a failing encode because it provides more useful evidence than a screenshot of the main window.

4.1 What to Look for in the Log

Read the source scan and encode summary, then search for warnings and timing-related messages. Useful clues include:

• The detected video frame rate and selected output frame rate mode
• The exact audio track and codec selected
• Whether audio is passed through or encoded
• The video encoder, including whether it is hardware-based
• Messages about timestamp discontinuities or decoding errors
• Final counts showing duplicated or dropped frames
• Read errors associated with a disc, file, or storage device

A small number of duplicated or dropped frames is not automatically proof of a fault, particularly when converting variable timing to constant timing. Large or repeated corrections, especially near the failure point, support the theory that the source cadence or timestamps are irregular.

4.2 Compare Logs From Working and Failing Tests

Change one variable at a time and label each output clearly. For example, compare a hardware-encoder log with a software-encoder log, or an audio-passthrough log with an AAC log. If the successful test differs in only one meaningful setting, you have actionable evidence.

Stop changing settings when a repeatable test stays synchronized in at least two players and the log contains no unexplained read or decode failures. Continuing to alter quality, filters, and container options after reaching that point can reintroduce uncertainty.

5. Run a Clean Temporary Encode With Minimal Settings

If the cause remains unclear, create a controlled test rather than modifying the existing queue item repeatedly.

1. Copy the source to a reliable local drive if it is currently on removable or network storage.
2. Open the source directly in HandBrake and select a standard built-in preset.
3. Choose a simple MP4 or MKV container appropriate for your players.
4. Select only the main video and one known audio track.
5. Disable subtitles for the first test.
6. Set frame rate to Same as Source and begin with Peak Frame Rate.
7. Convert the audio to AAC instead of using passthrough.
8. Use a software video encoder for the diagnostic run.
9. Encode a range long enough to reveal the original problem.
10. Test the result in at least two players and review the Activity Log.

If this clean encode works, add required features back one at a time. Test passthrough, then subtitles, then the preferred hardware encoder. The first addition that recreates the problem identifies the relevant path.

If the clean encode still drifts, repeat it with Same as Source and Constant Frame Rate. If that also fails at the same points, stop cycling through HandBrake settings. The source likely requires timestamp repair, remuxing, or replacement.

6. Quick Fix Checklist

• Confirm whether the error is a constant offset, progressive drift, or sudden change.
• Play the original and output in at least two media players.
• Test a short range that includes the point where synchronization fails.
• Verify that HandBrake selected the intended audio track.
• Compare audio passthrough with AAC conversion.
• Try Same as Source with Peak Frame Rate first.
• Test Constant Frame Rate for irregular phone or screen recordings.
• Compare hardware video encoding with a software encoder.
• Temporarily remove subtitles and extra audio tracks.
• Encode from and to reliable local storage.
• Check the Activity Log for decode errors, discontinuities, and frame corrections.
• Repair, remux, recapture, or replace a source with damaged timing.

The fix is complete when the output stays synchronized at the beginning, middle, and end in multiple players. At that point, preserve the working settings and avoid changing unrelated controls.

7. Frequently Asked Questions

7.1 Why Does HandBrake Audio Start in Sync and Drift Later?

Progressive drift usually indicates that the audio and video timelines are advancing at different effective rates. Common causes include irregular variable frame rate timing, damaged timestamps, missing frames, capture interruptions, or an unsuitable frame rate conversion. Test Same as Source settings, compare Peak and Constant Frame Rate, and inspect the Activity Log for duplicated or dropped frames.

7.2 Why Is the Audio Out of Sync by the Same Amount Everywhere?

A stable offset is more likely to come from an existing source delay, the selected audio track, a player setting, Bluetooth or receiver latency, or timestamp interpretation. Test multiple players and audio outputs before re-encoding. If every player shows the same offset in both the source and output, the source timing needs correction.

7.3 Should I Always Use Constant Frame Rate?

No. Constant Frame Rate is useful for editors, devices, or workflows that require evenly timed frames, and it can normalize some irregular captures. Peak Frame Rate with Same as Source often preserves valid source timing more naturally. Use the mode that passes your representative sync test and meets the destination's requirements.

7.4 Can Audio Passthrough Cause Sync Problems?

Passthrough can preserve an unusual delay or expose compatibility problems in a container or player. It does not inherently cause bad synchronization. Compare a passthrough test with converted AAC audio. If only one fails across multiple players, use the working audio path or investigate the original track.

7.5 What If the File Is Synchronized in VLC but Not on My Television?

The television, streaming application, receiver, or connection path may be mishandling the file. Test a simpler container and widely supported video and audio codecs, and disable audio-delay or motion-processing options on the device. If several computer players remain synchronized, repeatedly changing HandBrake's frame rate may make the diagnosis worse rather than better.

7.6 When Should I Repair the Source Before Using HandBrake?

Repair the source when it is already out of sync, reports the wrong duration, contains timestamp jumps, fails at the same location in every test, or produces repeated decode and read errors. HandBrake is a transcoder, not a universal damaged-media repair tool. A clean remux may solve container-level timing issues, while severe corruption may require re-encoding, recapturing, or obtaining another lawful copy.