Frame-rate guide
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.
Quick answer
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.
Decision checklist
Use an observable sync event—a clap, a spoken consonant or a screen action with sound—at several points. One correct frame at the start does not rule out cumulative drift.
If you observe 1
Try: Keep the original and check a representative export. There is no need to convert solely to make the metadata read CFR.
Check the outcome: Check beginning, middle and end of the full recording, including any long pause or capture slowdown.
If you observe 2
Try: Check alignment and recording latency before blaming variable timing. Compare the same event at several positions.
Check the outcome: A constant offset and increasing drift are different observations. CFR conversion is not a universal audio-alignment repair.
If you observe 3
Try: Create a CFR edit copy before building new proxies. In HandBrake’s Video tab, select a deliberate frame rate and Constant Framerate, then use a new output filename.
Check the outcome: Analyze the output mode and test sync again. Use the intended capture/timeline rate; do not round 29.97 to 30 simply because it looks simpler.
If you observe 4
Try: Treat timing as unknown. Test the actual workflow and inspect the file independently if you need stronger timing evidence.
Check the outcome: An average of 30 or 60 fps does not establish uniform frame intervals. ClipCompat does not perform an exhaustive frame-timestamp audit.
Accept the CFR copy only after duration, motion, sync and export checks. Conversion can duplicate/drop frames; changing Interpret Footage is not equivalent to making a timing-normalized copy.
These are diagnostic suggestions. They are not reports of editor tests performed by ClipCompat. Choose a remux, transcode or proxy and verify the copy →
Common symptoms
Inspect first
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.
A CFR conversion builds a new timing-normalized media file; a clip interpretation setting changes how an editor treats the source rate. Choose a CFR edit copy when a measured timing problem needs that change, and test motion and audio again before relinking. A familiar average FPS does not prove constant timing.
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.
Observed analyzer evidence
These synthetic files were analyzed on 2026-10-11 using MediaInfo WASM and the same normalization and compatibility rules used by the checker. This run used Node.js; it was not an import or playback test in Premiere or Resolve.
MediaInfo reports a constant frame rate of approximately 30 fps.
Evidence: media factNext action: Try the original in your installed editor. If import fails, investigate the app version and source integrity before converting.
Download the same sampleThe reported frame rate varies from approximately 15 to 30 fps.
Evidence: media factNext action: If your editor shows sync, proxy or timing problems, keep the original and create a separate constant-frame-rate edit copy.
Download the same sampleA readable codec is not a guarantee of editor support. Test Required records a limit of the current rules; Supported is not an editor benchmark. Download raw MediaInfo output, normalized facts, checksums and full findings (JSON). Read the methodology.
Safe troubleshooting
Run the source through the VFR Checker.
If it is CFR, troubleshoot the editing problem elsewhere.
If it is VFR but edits normally, keep working with the original.
If sync, proxy or timing problems occur, create a separate CFR edit copy and preserve the original.
Retest the new copy before replacing project media.
FAQ
No. 29.97 can be the average frame rate of either a constant or variable-timing file. Check the frame-rate mode.
No. Phones commonly produce VFR in some modes and circumstances, but you should inspect the actual file rather than assume.
A VFR clip may edit correctly. Judge the actual import, sync, proxy and export behavior instead of converting every file with variable timing metadata.
Verify with a file
The guide explains the symptom. The checker reads the actual source, and the Lab Cases show how known inputs are classified.
Sources
Compatibility changes over time. These links are included so the current editor/vendor documentation can be checked directly.
Last reviewed: October 11, 2026