Variable frame rate (VFR) is a method of recording video where the number of frames captured per second changes throughout the clip rather than staying fixed. Instead of locking in at exactly 30 or 60 frames per second, a VFR recording adjusts on the fly: fewer frames during still or simple scenes, more frames when there’s fast motion or complex detail. Each frame is timestamped individually so the video player knows exactly when to display it.
How VFR Differs From Constant Frame Rate
With constant frame rate (CFR), every second of video contains the same number of frames regardless of what’s happening on screen. A 30 fps CFR video always delivers 30 evenly spaced frames per second, whether the camera is pointed at a blank wall or a car chase. The frame duration never changes.
VFR flips that logic. When nothing is changing on screen, the encoder skips generating redundant frames. When there’s lots of motion or visual complexity, it adds frames to keep playback smooth. The frame duration stretches or shrinks dynamically based on the content of each moment. This is why a VFR file might report a frame rate like 29.910988 or 29.970030 instead of a clean 30 fps. The number you see is an average, not a constant.
Why Your Phone Records in VFR
Smartphones are the most common source of VFR video. The reason comes down to practical constraints: phones have limited storage, limited battery life, and processors that heat up quickly. By dropping unnecessary frames during low-motion scenes, VFR recording saves storage space and reduces the processing load on the device. Variable bitrate encoding works alongside VFR to give you more control over file size without obvious quality loss during normal playback.
Screen recording software like OBS, Loom, Zoom, and Microsoft Teams also produces VFR files. When you’re recording your screen or a video call, system resources fluctuate constantly. Your CPU might briefly spike to handle a background task, and the recorder compensates by dropping a frame or two rather than crashing or stuttering. OBS users have reported that even with zero dropped frames showing in the stats window, a recording can still contain a handful of VFR frames triggered by actions like toggling the replay buffer or pausing the recording. Webcam recordings and gameplay captures behave similarly.
The Audio Sync Problem
VFR plays back perfectly fine in most media players. The timestamps on each frame tell the player exactly when to show it, and modern players handle this without issue. The problems start when you bring VFR footage into a video editor.
Most professional editing software expects every frame to arrive at perfectly even intervals. When the gaps between frames are irregular, the editor’s timeline can’t line up the audio track properly. The result is audio drift: your video and audio start in sync, then gradually separate over the length of the clip. A 10-minute screen recording might end up with audio running a full second or more ahead of or behind the video by the end. You might also see stuttering playback, unexpected frame duplication, or export files that don’t match what you saw on the timeline.
Some editors handle this better than others. iMovie and Final Cut Pro automatically re-render VFR footage to a constant frame rate on import, so you may never notice the issue. Adobe Premiere Pro added VFR support in 2018, but the experience is still imperfect. A Premiere product manager acknowledged in late 2024 that VFR footage continues to cause sync drift, stuttering, audio misalignment, and export mismatches in real-world workflows. The team is actively collecting problem files to improve support. Premiere also only exports in CFR, so any VFR quirks need to be resolved before or during editing.
How to Check if Your File Is VFR
The free tool MediaInfo is the standard way to check. Open your video file in MediaInfo and look for the “Frame rate mode” field. It will display either “CFR” or “VFR” as a simple label. If you’re using the extended view, you can also find a “variable rate” flag in the frame metadata. FFmpeg’s ffprobe command can detect VFR as well, though MediaInfo’s interface is more straightforward for a quick check.
Converting VFR to Constant Frame Rate
If you need to edit VFR footage in software that doesn’t handle it well, the standard fix is transcoding the file to CFR before importing it into your editor. HandBrake, a free and widely used transcoding tool, makes this straightforward. Under its frame rate settings, select “Constant Frame Rate” and choose “Same as Source.” HandBrake will detect the average frame rate of your original file and produce a new version where any variable portions are locked to that rate. This preserves the look of your video while giving your editor the evenly spaced frames it needs.
You can also set a specific target frame rate if needed, like 30 or 60 fps. HandBrake will conform the entire video to the new rate by duplicating or dropping frames as necessary. This is useful when you’re importing into an editor that requires a specific frame rate for your project timeline, but it can introduce slight visual artifacts in clips where the original frame rate varied significantly.
FFmpeg is another option for users comfortable with command-line tools. It can remux or transcode VFR files quickly, and many editors’ recommended workflows for handling VFR point to FFmpeg as the fastest conversion method.
Recording in CFR From the Start
If you control the recording setup, you can often avoid VFR entirely. In OBS, recording to MOV format tends to produce constant frame rate output more reliably than MKV or MP4. One important consideration with MP4 and MOV formats: they store critical metadata at the end of the file, so if the recording is interrupted by a crash or power loss, the entire file can be permanently corrupted and unplayable. MKV is more resilient to crashes but more prone to introducing stray VFR frames.
For phone recordings, some third-party camera apps let you force CFR recording, though this uses more storage and battery. The built-in camera apps on most phones don’t expose this setting. If you regularly shoot phone footage for editing, transcoding after recording is usually the more reliable path.