Frame-rate guide

Variable Frame Rate (VFR) and Video Editing: What It Means

A video can average 30 fps and still be variable frame rate. What changes is the timing between frames, which can matter for sync, proxies, scrubbing and export consistency in some editing workflows.

✓ Reviewed September 10, 2026✓ Source-linked✓ Safe troubleshooting

Quick answer

What to do first

VFR is not automatically bad. First verify whether the file is actually VFR. If the footage imports, scrubs and stays in sync, you may not need to convert it. If timing, proxy or sync problems appear, keep the original and create a separate constant-frame-rate edit copy.

Common symptoms

When this guide applies

  • Audio and video slowly drift out of sync.
  • Proxy timing does not match the source reliably.
  • Scrubbing or frame-accurate navigation feels inconsistent.
  • An export has timing or frame-duplication differences from the timeline.

Inspect first

Facts that narrow the cause

  • FrameRate_Mode: Constant or Variable.
  • Average frame rate.
  • Minimum and maximum reported frame rates when available.
  • The actual source: phone, screen recording, stream capture or another recorder.
  • Whether the problem exists in the real editing workflow rather than only in metadata.

Average FPS is not the same as frame timing

A VFR file can report an average close to 30 or 60 fps while individual frame intervals change across the recording. MediaInfo can expose Frame Rate Mode and, in many files, minimum and maximum frame rates.

This is why ClipCompat does not infer CFR from a familiar-looking average frame-rate number.

VFR is still an active Premiere workflow issue in 2026

In February 2026, a Premiere Product Manager asked users for real VFR problem files and specifically listed sync drift, stuttering playback, unexpected frame duplication, audio misalignment and export mismatches among the issues the team was investigating.

That current request is strong evidence that VFR is not merely an old forum myth, while also showing why the correct verdict is “editing risk,” not “this file is broken.”

Convert only when the workflow benefits

Converting every VFR file wastes time and can introduce another generation of compression. The safer policy is conditional: preserve the original, test it, and create a CFR edit copy when the actual workflow shows timing-related trouble.

Safe troubleshooting

Recommended sequence

  1. 1

    Run the source through the VFR Checker.

  2. 2

    If it is CFR, troubleshoot the editing problem elsewhere.

  3. 3

    If it is VFR but edits normally, keep working with the original.

  4. 4

    If sync, proxy or timing problems occur, create a separate CFR edit copy and preserve the original.

  5. 5

    Retest the new copy before replacing project media.

FAQ

Short answers to the next questions.

Is 29.97 fps automatically CFR?

No. 29.97 can be the average frame rate of either a constant or variable-timing file. Check the frame-rate mode.

Are phone videos always VFR?

No. Phones commonly produce VFR in some modes and circumstances, but you should inspect the actual file rather than assume.

Does Premiere support VFR?

Premiere can work with VFR media, but Adobe is still actively improving the editing experience and documents real-world timing issues. Whether conversion is necessary depends on your actual file and workflow.

Verify with a file

Use the checker and reproducible cases.

The guide explains the symptom. The checker reads the actual source, and the Lab Cases show how known inputs are classified.

Sources

Primary references used for this guide

Compatibility changes over time. These links are included so the current editor/vendor documentation can be checked directly.

Last reviewed: September 10, 2026