On this page
- 01The short answer
- 02VFR is a timing behaviour
- 03Find where sync first breaks
- 04Measure instead of repeatedly nudging
- 05Preserve the original
- 06Test a constant-frame-rate copy
- 07Conversion is different from interpreting footage
- 08Be careful with older fixes
- 09Relink only after the test passes
- 10A conversion can fail for a useful reason
- 11Sources
- 12Cite this page
The short answer
Short answer
If video and audio drift in an editor, compare the original file, the editing preview and a short export. Check whether the recording uses variable frame rate, then test a constant-frame-rate copy if the editor handles that source poorly. VFR is one possible cause; it is not proof that every sync problem needs conversion.
A constant offset, growing drift and a single bad cut are different problems. Diagnose the pattern before moving an audio track or re-encoding hours of footage.
VFR is a timing behaviour
A variable-frame-rate file can change how many video frames represent each interval. Constant frame rate uses one rate throughout. HandBrake's documentation distinguishes VFR, CFR and peak frame rate. HandBrake frame-rate modes
A fractional rate such as 29.97 fps is not, by itself, evidence of VFR. The important question is whether frame timing varies, not whether the displayed rate is a whole number.
Likewise, the average rate shown in a file summary may not describe every section of the recording. Use a tool or editor view that explicitly identifies frame-rate mode when available.
Find where sync first breaks
Original and export are correct, preview is wrong
- Investigate first
- Playback performance, editor handling or preview settings
Original is correct, export drifts
- Investigate first
- Export path and treatment of the source
Original already drifts
- Investigate first
- Capture, source timing or separate audio recording
All speech is late by the same amount
- Investigate first
- A fixed offset
Drift begins at one cut
- Investigate first
- An edit, missing segment or changed playback speed
Drift grows through a continuous clip
- Investigate first
- Timing interpretation, VFR handling or clock differences
| Observation | Investigate first |
|---|---|
| Original and export are correct, preview is wrong | Playback performance, editor handling or preview settings |
| Original is correct, export drifts | Export path and treatment of the source |
| Original already drifts | Capture, source timing or separate audio recording |
| All speech is late by the same amount | A fixed offset |
| Drift begins at one cut | An edit, missing segment or changed playback speed |
| Drift grows through a continuous clip | Timing interpretation, VFR handling or clock differences |
Choose a visible and audible event: a hand clap, a spoken consonant with a clear mouth movement, or a recorded click whose sound is in the same source.
Use several reference points. Do not declare success after aligning only the first one.
Measure instead of repeatedly nudging
For a hypothetical twenty-minute interview, suppose the beginning matches but speech is one second late at the end.
That error describes drift, not a fixed one-second delay. Moving the whole audio track one second earlier would make the beginning wrong.
Write down the mismatch at the beginning, middle and end. If it grows evenly, the pattern is different from one sudden jump after a missing section.
For separate audio, investigate the source recording and its duration before stretching it. Different capture paths can introduce issues that changing video frame-rate mode will not resolve.
If only subtitles are wrong while the picture and speech remain aligned, use the subtitle sync guide instead.
Preserve the original
Before testing a conversion:
- 1Keep the original media unchanged.
- 2Save a project copy or checkpoint.
- 3Choose a short representative section for an initial test.
- 4Record the current duration and relevant media settings.
- 5Create a new converted file with an explicit name.
This protects your ability to compare the result. If you replace the original without a reference, it becomes harder to determine whether the conversion fixed timing or introduced another change.
Test a constant-frame-rate copy
In HandBrake, choose the frame rate needed for the editing workflow and explicitly select Constant Frame Rate. Its documentation distinguishes that setting from Peak Frame Rate, which limits peaks while allowing lower rates to remain variable. HandBrake frame-rate options
For the test, keep unrelated changes modest. Preserve the frame size you need, choose adequate quality and check the selected audio track.
Then import the new file into a clean test sequence or project and inspect the same reference points. Confirm the output duration and motion still suit the footage.
Do not assume a preset selected CFR just because you chose a familiar frame-rate number. Verify the mode and inspect the converted file.
The HandBrake documentation page identifies itself as a draft. Its mode descriptions are useful for configuration, but the result still needs validation in your version and editor.
Conversion is different from interpreting footage
Changing how an editor interprets a clip's frame rate can change playback speed and duration. It is not automatically a conversion that reconstructs constant-rate timing.
Adobe's current guidance describes changing clip frame rate as a playback change, including effects on audio. Use it only when that change is intended. Adobe: change a clip's frame rate
If the goal is to preserve the original real-time performance while creating an editing-compatible copy, inspect the result's actual duration and sound. Do not choose a different interpretation solely to make a number match your sequence.
Be careful with older fixes
Historical troubleshooting guides may describe application limitations that have changed. Penn State's 2017 guide documents an older Premiere workflow and suggests CFR conversion, but it also includes a file-extension workaround. Penn State's historical sync guide
Do not apply that extension rename as a general modern repair. Changing a filename suffix does not itself convert the media.
Use the current documentation for your editor and version. A current release may handle a source differently from a tutorial written years earlier.
Relink only after the test passes
If the converted test behaves correctly:
- Check a full-length converted copy before replacing references.
- Confirm beginning, middle and ending sync.
- Confirm the expected audio channels are present.
- Review motion and important visual detail.
- Save the conversion settings.
- Relink in a duplicate project first.
Check clips around edits after relinking. A timeline built against one source can depend on its exact start point and duration.
Generate final captions from the accepted edit or verify existing captions against it. Replacing the source does not guarantee that every derived file remains correct.
A conversion can fail for a useful reason
If the new CFR copy still drifts, stop treating VFR as the only explanation.
Check whether:
- The original audio has a different duration.
- A section was removed from only one track.
- Playback speed changed.
- The wrong microphone file was attached.
- The player is struggling with preview.
- The error comes from the capture itself.
Describe the failing boundary when seeking help: “original is aligned, editor preview drifts, exported file is aligned” is more actionable than “the audio is broken.”
For a fresh software recording, begin with a saved-file audio test. For existing footage, preserve the source and test the smallest change that addresses the measured timing problem.
Sources
- HandBrake frame-rate modesChecked October 13, 2026. See the linked documentation and the claim it supports in the article.
- Adobe: change a clip's frame rateChecked October 13, 2026. See the linked documentation and the claim it supports in the article.
- Penn State's historical sync guideChecked October 13, 2026. See the linked documentation and the claim it supports in the article.
Cite this page
Last verified: Oct 13, 2026
Patel, O. (2026, October 13). Variable frame rate and audio sync: diagnose before converting. Rushilo. https://rushilo.com/blog/variable-frame-rate-audio-sync
About the author
Founder, Rushilo
Om Patel is the founder of Rushilo, a desktop video editor driven by the user's own AI, and of BigIdeasDB, a research platform that reads real complaints and reviews to help founders validate products. He writes Rushilo's research articles with the same method: primary sources, dated numbers and the words real users write.
