AVMint

Fix Audio Out of Sync After Video Conversion

Audio drift after conversion is a common headache, especially with variable frame rate (VFR) source files from screen recorders, phones, or game capture tools. CloudConvert, HandBrake, and even some desktop apps can introduce drift if they don't handle VFR cleanly. AVMint can re-mux the file to a constant frame rate and re-align the audio.

1

Upload the out-of-sync file

Open AVMint's Convert tool and drop the problem file. AVMint reads the actual frame rate and audio sample rate from the container.

2

Convert to MP4 with H.264

Choose MP4 as the output. AVMint re-encodes to a constant frame rate, which resets the per-frame timestamps and re-anchors the audio track to the video clock — the most reliable fix for VFR-induced drift.

3

Verify the output

Download the result and play it back. The lip-sync should match the original recording. If a small constant offset remains, you can offset the audio in a video editor — but variable drift will be gone.

Tip

Audio drift is almost always caused by VFR sources, not the converter itself. Screen recorders like OBS (in default settings) and many phone apps record VFR, which not all tools handle gracefully.

FAQ

Why does CloudConvert cause audio drift?

Server-side converters often copy the audio stream as-is while re-encoding video to a fixed frame rate. If the source was VFR, the audio timing references break. Re-encoding both tracks together (as AVMint does) avoids this.

Will I lose quality re-encoding?

There's a small generation loss from re-encoding, but AVMint uses high-quality defaults (192kbps audio, optimized video bitrate). For most footage the difference is invisible, and a synced video beats a desynced one.

Files never leave your device

Upload the out-of-sync file