Recorded Video Plays Fine but Stutters in the Editor? Variable vs Constant Frame Rate Diagnosis Guide

Key Summary
The same recording plays smoothly in a media player but stutters on the editing timeline, with audio drifting further out of sync toward the end. The cause is usually the file's frame rate mode: variable frame rate timestamps do not fit the editor's fixed frame grid. This guide uses player comparisons, drift measurement, and MediaInfo to confirm it.
The Shape of the Problem: Smooth in the Player, Stuttering in the Editor
This guide covers one specific shape, and the shape itself is the whole diagnosis. A recording — from a phone, a tablet, a screen recorder, a game bar, or a graphics card overlay — plays completely smoothly in a media player such as VLC, PotPlayer, or Windows Media Player. The same file is dragged onto the timeline in Premiere Pro or DaVinci Resolve, and it stutters: playback hesitates, frames seem to jump, and the audio drifts further and further out of sync with the picture as the clip goes on. The picture itself is not broken — there is no green screen, no torn image, no corrupted frame. It simply does not play smoothly, and the sound and the picture stop matching.
That combination is what makes this symptom different from its neighbours. A recording that stutters in the player as well belongs with a playback decoding diagnosis. A timeline that stutters because the machine cannot decode the footage fast enough belongs with a decoding-load diagnosis, where the file's frame rate is even and the problem is the weight of the decoding. A recording that stutters while it is being made belongs with a live-encoding diagnosis, where the encoder is overloaded in real time. This guide is about the fourth combination: the recording is already finished, the file plays smoothly in a player, and the same file stutters in the editor. The fault is in the file's timestamps, not in the recording and not in the playback.
The first conclusion most owners reach is that the file must be fine because the player plays it smoothly, and the second is that the editor must be too heavy for the machine because the timeline stutters. Both conclusions miss the same fact: the player and the editor read the same file in two different ways. A file can be perfectly readable by one method and unreadable by the other, and both results can be true at the same time. The question is not whether the file is good or the machine is strong enough. The question is whether the file's frame timing fits the way the editor lays frames out.
One honest gap should be stated up front. The guidance in this guide rests largely on Adobe's own FAQ for variable frame rate media in Premiere Pro, on published guides that describe the mechanism, and on user reports for DaVinci Resolve. No official Blackmagic documentation on variable frame rate has been found — one published guide states this plainly — so the DaVinci Resolve parts of this guide rest on user reports, not on an official statement, and they are labelled as such where they appear. The method is presented as a diagnostic assembly, not as official guidance from any editor maker.
Why a Player and an Editor Read the Same File Differently
A video file is not a strip of film with evenly spaced frames. It is a sequence of frames, each carrying a timestamp that says when it should be shown, and a separate audio track recorded against its own steady clock. How a program uses those timestamps decides whether the file plays smoothly.
A media player follows the timestamps. It shows each frame at the moment its timestamp says, and if the gaps between frames are uneven, the player simply waits the right amount of time between each one. A frame that arrives late is shown late; a frame that arrives early is shown early. The player does not care whether the gaps are even, because it never assumes they are. That is why a file with uneven frame spacing can play perfectly smoothly in VLC or PotPlayer: the player is doing exactly what the timestamps tell it to do.
An editing timeline works differently. It is built around a fixed frame grid: at 30 frames per second, every frame is assumed to last exactly one thirtieth of a second, and the timeline lays frames out slot by slot on that grid. The editor does not place frames by their timestamps; it places them by their position in the sequence — first frame in the first slot, second frame in the second slot, and so on. When the frames in the file are evenly spaced, the two methods agree, and the timeline plays smoothly. When the frames are unevenly spaced, the two methods disagree, and the timeline stutters: some frames are held too long, some are skipped, and the picture hesitates.
The audio makes the mismatch visible, and it gets worse as the clip goes on. Audio is recorded against a steady clock, so it stays even. Video with uneven timestamps does not. The editor lines the two up on the same fixed grid, and the small error in each frame adds up over the length of the clip. At the start the error is tiny and unnoticeable. By the end of a long clip it can be seconds. That is why the drift is worst at the end of the clip, and why a short clip can look almost fine while a long clip from the same recording is badly out of sync. As one published guide puts it, the drift is arithmetic, not a bug: if the editor assumes every frame lasts one thirtieth of a second, but the file's real average is 29.7 frames per second, a forty-minute clip accumulates roughly twenty-four seconds of error. The numbers are an example of the mechanism, not a universal formula — the actual error depends on how far the real average frame rate sits from the assumed rate, and on how long the clip is.
The file's frame rate mode is what decides which of these two situations applies. A constant frame rate file — CFR — has every frame spaced exactly evenly: at 30 frames per second, every frame is exactly one thirtieth of a second after the one before it. A variable frame rate file — VFR — has each frame carrying its own timestamp, and the gaps between frames are uneven: some frames are close together, some are far apart, and some moments have no frame at all. VFR is a legitimate way to write a file. Phones, tablets, and screen recorders use it to save power and save space: when the picture is still, they write fewer frames; when the light is dim, they lower the frame rate. The file is not damaged. It is simply written in a way that suits a player and does not suit an editor.
The Deciding Forks: Four Questions That Narrow the Field
The whole guide turns on four forks. Each fork is a comparison, and each comparison removes a whole set of possibilities. They should be done in order, before any file is converted, because converting the file before the fork is tested destroys the evidence the fork would have given.
Fork One: Does the Player Really Play It Smoothly?
The first fork is the premise itself. Play the same file in two different media players, and then drag it onto the editor timeline and play it there. If the players play it smoothly and the editor stutters, the fault is locked to the file's timestamp layer: the players and the editor read the same file differently, and the difference is the evidence. If the players stutter too, leave this guide — the fault is in the playback decoding layer or the decoding-load layer, and the file's frame rate mode is not the first suspect.
Fork Two: Does the Drift Get Worse Toward the End?
The second fork is inside the timestamp layer. Find an obvious sound-and-picture moment near the start of the clip — a clap, a door closing, a word spoken on camera — and another near the end, and compare the error at the two ends. If the error at the end is larger than the error at the start, the drift is accumulating with the length of the clip, and it points at variable frame rate: each frame's small timing error adds up over time. If the error is the same at both ends, it is not accumulating drift, and the fault points elsewhere — toward the decoding-load layer, where the timeline stutters evenly from start to finish.
Fork Three: What Does MediaInfo Say?
The third fork is the direct reading. Open the file in MediaInfo and look at the Video section, at the field called Frame rate mode. If it says Variable, the file is variable frame rate, and the diagnosis is confirmed. If it says Constant, the file is not variable frame rate, and this guide no longer applies — the fault belongs with the decoding-load diagnosis. Note the minimum and maximum frame rate shown alongside it: the wider the gap between them, the larger the effect of the variable frame rate, and the worse the stutter and drift are likely to be.
Fork Four: Does Converting to Constant Frame Rate Change the Result?
The fourth fork is the confirmation test. Convert a copy of the file to constant frame rate — using HandBrake with the Constant Framerate option, or FFmpeg — and drag the converted copy onto the timeline. If it plays smoothly and the audio no longer drifts, the frame rate mode layer is confirmed. If it stutters the same way, that layer is cleared, and the fault belongs with the decoding-load layer. This step is a comparison test, not a repair of anything: it proves the problem is in the file's timing, and the graphics card was never at fault. Keep the original file — the conversion re-encodes the video, and the picture quality and file size will change.
The Five Suspicion Layers
A file that plays smoothly in a player but stutters in the editor can fail at five layers, and they must be kept separate. Converting the file, opening proxy media, and clearing the cache all at once and finding the timeline smooth proves nothing about which change did the work, and the stutter will return the next time only one of those conditions is present. The layers below run from the file itself outward to the machine, and each one has its own deciding evidence.
| Layer | What it covers | Deciding evidence |
|---|---|---|
| 1. File frame rate mode layer | Variable frame rate (VFR) against constant frame rate (CFR) — uneven frame timestamps against evenly spaced frames | MediaInfo shows Frame rate mode: Variable, and the drift grows toward the end of the clip |
| 2. Recording source layer | Phone and tablet recording, screen recording, game bar and graphics card overlay recording, some webcams | The source is one that writes VFR to save power or space — confirmed by MediaInfo, never assumed from the tool name |
| 3. Decoding and proxy load layer | H.264 and H.265 inter-frame compression, 4K resolution, no proxy media | The file stutters evenly from start to finish, with no accumulating drift |
| 4. Audio clock layer | Audio recorded on its own steady clock, video on uneven timestamps, the two aligned on a fixed frame grid | The audio-video error is larger at the end of the clip than at the start |
| 5. Recording settings layer | Frame rate locking and the CFR option in the recording tool, capture frame rate | The setting exists for the next recording; it cannot change a file that is already recorded |
Layer One: The File Frame Rate Mode Layer
The first layer is the file itself. In a variable frame rate file, each frame carries its own timestamp, and the gaps between frames are uneven. In a constant frame rate file, every frame is spaced exactly the same. The editor's timeline assumes the second kind: it lays frames out on a fixed grid, one slot per frame, and it does not read the timestamps to place them. When the file is variable frame rate, the grid and the timestamps disagree, and the timeline stutters.
The evidence for this layer is the MediaInfo reading and the drift measurement. MediaInfo showing Frame rate mode as Variable, together with audio drift that grows toward the end of the clip, points at this layer. The minimum and maximum frame rate matter too: a file whose frame rate swings between, say, a low minimum and a high maximum has more uneven spacing than a file whose range is narrow, and the stutter is likely to be worse. Adobe's own FAQ for variable frame rate media in Premiere Pro describes exactly this: from Premiere Pro 12.0.1 onward, right-clicking a clip and choosing Properties shows "Variable Frame Rate Detected" for such files, and in MediaInfo's tree view the Video section's Frame Rate Mode field shows Variable.
One published guide states the consequence plainly: a file can play fine in a media player, but editors such as Premiere Pro and DaVinci Resolve are built around a constant frame rate, so a variable frame rate file can stutter or drift out of sync with its audio. The player follows the timestamps; the editor follows the grid. The same file, two readings, two results.
Layer Two: The Recording Source Layer
The second layer is where the file came from. Phones and tablets record in variable frame rate to save power and space: when the picture is still, they write fewer frames, and when the light is dim, they lower the frame rate. Screen recorders do the same. Some game bar captures and graphics card overlay recordings are often variable too. Some webcams write variable frame rate as well. The source explains why the file is variable frame rate, but it never proves it — the proof is always the MediaInfo reading of the file itself.
This layer has a genuine conflict in the sources, and both sides are given below. Adobe's FAQ lists OBS Studio among the sources of variable frame rate media. A different published guide, based on testing, states the opposite: OBS Studio with default settings writes a constant frame rate, repeating the previous frame when the game has not drawn a new one, and lists phone screen recorders as variable and some GPU overlay recorders and game-bar capture as often variable. Both sources are second-hand summaries, and neither settles the question for any particular file. The position taken here is the only safe one: it depends on the recording tool and its settings, and the file itself must be checked with MediaInfo. Do not assume a recording from OBS, a phone, or a game bar is certainly variable frame rate, and do not assume it is certainly not — check the file.
Layer Three: The Decoding and Proxy Load Layer
The third layer is the weight of decoding the file. H.264 and H.265 use inter-frame compression: most frames are stored as differences from other frames, so the machine must decode a chain of frames to show any one of them. A 4K file at a high bit rate is heavy to decode, and without proxy media the editor must do that heavy decoding in real time while also playing the timeline. This layer is the home territory of the companion guide on timeline preview stutter, and it is covered there in full. It appears here only as the exclusion test: if the file stutters evenly from start to finish, with no drift that grows toward the end, and if converting it to constant frame rate changes nothing, the fault belongs with this layer, and the investigation should move to that guide.
The two layers can look alike at first glance, and the drift measurement is what separates them. Decoding load stutters evenly. Variable frame rate stutters with drift that accumulates. A file can also suffer from both at once, which is why the conversion test in fork four matters: it removes the frame rate mode from the picture, and whatever stutter remains after conversion belongs to the decoding layer.
Layer Four: The Audio Clock Layer
The fourth layer is the audio clock. Audio is recorded against its own steady clock, and it stays even. Video in a variable frame rate file is recorded against uneven timestamps. The editor aligns the two on the same fixed frame grid, and the small error in each frame adds up over the length of the clip. The longer the clip, and the more uneven the recording was while it was being made, the larger the drift at the end.
The evidence for this layer is the drift measurement in fork two. A clear sound-and-picture moment at the start of the clip and another at the end, with the error larger at the end, points at this layer. Adobe's FAQ describes a feature called Preserve Audio Sync, which can align the audio and video — but it also states that for some variable frame rate files the feature may not work as intended, and those files need to be converted to constant frame rate. The audio clock layer is therefore a place where the editor has a tool, but the tool does not always work, and the conversion remains the reliable comparison.
Layer Five: The Recording Settings Layer
The fifth layer is the recording settings, and it points forward, not backward. Some recording tools have a frame rate lock or a constant frame rate option in their settings. Setting it for the next recording prevents the next file from being variable frame rate. It cannot change a file that is already recorded — the settings layer is a prevention direction, not a repair direction. An already-recorded variable frame rate file stays variable frame rate until it is converted, and no setting in the recording tool will change the file that already exists.
The Seven Diagnostic Steps
The steps below are comparison tests. Each one changes one variable and records the result. Converting the file, opening proxy media, and changing the recording settings all at once and finding the timeline smooth proves nothing about which change mattered. Write down each result before moving on.
Step 1: Record the Baseline
Before anything is changed, record the baseline. Where the file came from — which phone, which recording tool, which settings — and its format and codec. How long the clip is. Whether it plays smoothly in a player, and how it stutters in the editor: hesitating playback, audio out of sync, or drift that gets worse toward the end of the clip. Which editor and which version. Without this record, later comparisons have nothing to compare against, and a file that behaves differently in a second editor will look like a new problem when it is the same file being read by a different program.
Step 2: Compare the Player Against the Editor
Play the same file in two different media players, then drag it onto the editor timeline and play it there. If the players play it smoothly and the editor stutters, the fault is locked to the file's timestamp layer. If the players stutter too, this guide no longer applies — move to the playback decoding or decoding-load diagnosis. Do not skip the second player: a single player can have its own decoding quirk, and two players agreeing is stronger evidence than one.
Step 3: Measure the Drift
Find an obvious sound-and-picture moment near the start of the clip — a clap, a door closing, a word spoken on camera — and another near the end, and note whether the error is the same at both ends. If the error at the end is larger than the error at the start, the drift is accumulating, and it points at variable frame rate. If the two ends show the same error, it is not accumulating drift, and the fault points toward the decoding-load layer. This measurement is the cheapest test in the guide and the most informative: it separates the timestamp layer from the decoding layer without any software beyond the editor itself.
Step 4: Check the File in MediaInfo
Open the file in MediaInfo and read the Video section's Frame rate mode field. Variable means variable frame rate, and the diagnosis is confirmed. Constant means it is not variable frame rate, and the investigation moves to the decoding-load guide. Record the minimum and maximum frame rate shown alongside it: the wider the gap, the larger the effect of the variable frame rate is likely to be. This is the direct reading, and it replaces any guess based on which tool recorded the file.
Step 5: Compare a Short Clip from the Start Against One from the End
Cut out the first thirty seconds of the clip and the last thirty seconds, and drag each onto the timeline separately. If the opening section plays smoothly and the closing section stutters, the drift is accumulating, and it points at variable frame rate. If both sections stutter the same way, the fault points toward the decoding-load layer. This step is a smaller, faster version of the drift measurement, and it is useful when the full clip is long and the drift is hard to judge in one viewing.
Step 6: Convert to Constant Frame Rate as a Comparison
Convert a copy of the file to constant frame rate — in HandBrake, choosing the Constant Framerate option, or in FFmpeg — and keep the original file untouched. Drag the converted copy onto the timeline. If it plays smoothly and the audio no longer drifts, the frame rate mode layer is confirmed. If it stutters the same way, that layer is cleared, and the fault belongs with the decoding-load layer. The conversion re-encodes the video, so the picture quality and the file size will change, and this step is a comparison test, not a statement that the original file was damaged. One technical point matters here: do not use a stream copy to fix variable frame rate. A stream copy keeps the original timestamps, so the drift stays exactly as it was. The conversion must re-encode with a constant frame rate mode — in FFmpeg, the current option is `-fps_mode cfr`, which replaces the older, deprecated `-vsync cfr`.
Step 7: Check the Recording Settings, Then Prepare for Inspection
Check the recording tool's frame rate lock or constant frame rate option, and set it for the next recording. Then assemble the three-sentence conclusion: what the symptom is, which variable made the symptom appear or disappear, and which possibilities are still not ruled out. Bring that record, with the baseline from step one, the MediaInfo reading, and the results of every comparison, to inspection. A record that says "the file plays smoothly in two players, stutters in the editor, MediaInfo shows Variable frame rate, and the converted copy plays smoothly" is worth far more than a record that says "the timeline stutters."
Six Misconceptions That Mislead This Diagnosis
Misconception 1: If the Player Plays It Smoothly, the File Must Be Fine
A player plays a file smoothly when the file's timestamps are readable, and it follows those timestamps frame by frame. An editor does not follow the timestamps — it lays frames out on a fixed grid. The same file can be perfectly readable by the player's method and unreadable by the editor's method. Smooth playback proves the file plays in a player. It proves nothing about how the file behaves on a timeline.
Misconception 2: If the Editor Stutters, the Machine Must Not Be Powerful Enough
Decoding load is one cause of timeline stutter, and it is covered in the companion guide on that shape. But a variable frame rate file stutters on a powerful machine just as it does on a weak one, because the problem is not computing power — it is that the file's timestamps do not fit the editor's frame grid. No amount of processing power makes uneven timestamps even. The drift measurement and the MediaInfo reading are what separate a power problem from a timestamp problem, and they should be done before any hardware is blamed.
Misconception 3: Proxy Media Will Always Fix Timeline Stutter
Proxy media solves decoding load: it gives the editor a lighter file to decode while editing. It does not solve the frame rate mode. Adobe's FAQ states this directly: if proxy, consolidate, or transcode workflows are planned, it is better to transcode variable frame rate material to a constant frame rate before editing. Opening proxy media on a variable frame rate file leaves the timestamp mismatch in place, and the stutter and drift remain. The order matters: convert the frame rate mode first, then use proxy media for the decoding load if it is still needed.
Misconception 4: Converting to Constant Frame Rate Means the Graphics Card Is Fixed
Converting a file to constant frame rate is a file preparation step. It proves the problem was in the file's timing, and it says nothing about the graphics card — because the graphics card was never broken. A file problem should not be written up as a hardware problem, and a file preparation step should not be presented as a repair of anything. The card was reading the file exactly as it was written; the file was simply written in a way the editor could not use.
Misconception 5: Recordings from OBS Are Always Variable Frame Rate
This is wrong, and the sources disagree on it. Adobe's FAQ lists OBS Studio among the sources of variable frame rate media, while a published guide based on testing states that OBS with default settings writes a constant frame rate, repeating the previous frame when the game has not drawn a new one. The only safe position is that it depends on the recording tool and its settings, and the file itself must be checked with MediaInfo. Never guess the frame rate mode from the name of the tool that recorded the file.
Misconception 6: Variable Frame Rate Means the File Is Damaged
Variable frame rate is a legitimate way to write a file. Phones and screen recorders use it deliberately, to save power and save space, by writing fewer frames when the picture is still and lowering the frame rate when the light is dim. The file is not corrupted and it is not broken. It is simply written in a way that suits a player and does not suit an editor. Calling it damaged leads to the wrong response — trying to repair a file that was never broken, instead of converting its frame rate mode for editing.
What the Sources Disagree About
The published sources do not agree with each other, and both sides are given below.
The first disagreement is about OBS Studio. Adobe's FAQ lists OBS Studio as a source of variable frame rate media. A published guide based on testing states that OBS with default settings writes a constant frame rate, repeating the previous frame when the game has not drawn a new one. Both sources are second-hand summaries, and Adobe is the official FAQ while the other is a testing-based guide. This guide does not choose one side: it depends on the recording tool and its settings, and the file itself must be checked with MediaInfo.
The second disagreement is about whether conversion before editing is necessary. One published guide states that dropping a variable frame rate clip onto the timeline and exporting it as it stands will produce a constant frame rate finished file, implying that conversion beforehand is unnecessary. Adobe's position is the opposite: before using proxy, consolidate, or transcode workflows, it is better to transcode variable frame rate material to a constant frame rate first. This guide follows Adobe's position: convert before editing, and do not rely on the export to correct the timing.
The third point is a gap, not a disagreement. One published guide states plainly that it found no Blackmagic documentation on variable frame rate. The DaVinci Resolve parts of this guide therefore rest on user reports, not on an official statement, and Premiere Pro's official guidance should not be presented as though it were Blackmagic's position. The two editors are different programs, and what is documented for one is not automatically true of the other.
There is a fourth disagreement, about how to describe the conversion step. Third-party tutorials often describe converting to constant frame rate as a repair. This site's position is that the conversion is a file preparation and comparison step: it proves the problem is in the file's timing, and it is not a repair of the graphics card or of anything else. This guide follows that position throughout: no comparison step is presented as a fix.
When to Stop, and What to Keep
Stop converting and re-testing once the comparison has given a clear result. A converted copy that plays smoothly has confirmed the frame rate mode layer, and converting the same file again with different settings adds nothing. Keep the original file before any conversion: the conversion re-encodes the video, the picture quality and the file size will change, and the original is the only copy that still holds the recording exactly as it was made. Do not treat the converted copy as a replacement for the original unless the original is no longer needed — keep both until the edit is finished.
Tool menus and command options change between versions. The HandBrake option and the FFmpeg option named in this guide should be checked against the current official documentation for the version in use, and no menu path or command should be treated as permanent. If a menu looks different from the description here, the current official documentation is the reference.
What to Bring for Inspection
If the comparisons point nowhere conclusive, or if the timeline stutters even after conversion to constant frame rate, the next step is a professional inspection. Bring the full record: the file's source, format, codec, and length; the MediaInfo reading, including the frame rate mode and the minimum and maximum frame rate; the results of the player comparison, the drift measurement, and the conversion comparison; and the editor and version in use. The three-sentence conclusion from step seven is the summary of that record.
Inspection and repair pricing follows the site's published three-tier scale of HK$400 to HK$2,800, with the actual quote given after inspection. No price in this guide should be read as a quote for a particular fault, and no fee is stated here for any specific repair.
The workshop is at Room 1209, Dali Plaza, Shek Mun. The telephone number is 2186 8010, and the WhatsApp number is 6558 6806. There is no Mong Kok shop, and there is no on-site service — inspection is carried out at the workshop.
Frequently Asked Questions
My recording plays fine in VLC. Does that mean the file is fine?
No. A media player follows the file's timestamps, showing each frame when its timestamp says to. An editor lays frames out on a fixed grid and does not follow the timestamps. The same file can play smoothly in a player and stutter on a timeline, and both results can be true at the same time.
The timeline stutters, so is my computer too slow?
Not necessarily. Decoding load is one cause of timeline stutter, but a variable frame rate file stutters on a powerful machine too, because the problem is not computing power — it is that the file's timestamps do not fit the editor's frame grid. Check the drift and the MediaInfo reading before blaming the hardware.
Will proxy media fix the stutter?
No, not for this shape. Proxy media solves decoding load, not the frame rate mode. Adobe's FAQ states that before using proxy, consolidate, or transcode workflows, variable frame rate material should first be converted to a constant frame rate. Convert the frame rate mode first, then use proxy media if the decoding load still needs it.
Will converting to constant frame rate damage the original file?
No — as long as the original is kept untouched. Keep the original file before converting and do not overwrite it. The conversion re-encodes the video, so the picture quality and the file size will change. This step is a comparison test and file preparation, not a statement that the original file was damaged. Keep the original so that if there is a problem after conversion, the original is still there to try another approach.
When converting with FFmpeg, can I use stream copy?
No. A published guide warns against using stream copy for variable frame rate files, because a stream copy keeps the original timestamps and the drift stays exactly as it was. The conversion must re-encode. On the settings, one guide mentions `-fps_mode cfr`, which replaces the deprecated `-vsync cfr`. Tools change version, so menu paths and settings should be checked against the current official documentation.
Does converting to constant frame rate fix my graphics card?
No. Converting a file to constant frame rate is a file preparation step, and it proves the problem was in the file's timing. The graphics card was never broken, and a file problem should not be written up as a hardware problem.
Are recordings from OBS always variable frame rate?
No. The sources disagree: Adobe's FAQ lists OBS Studio as a variable frame rate source, while a testing-based guide states that OBS with default settings writes a constant frame rate. It depends on the recording tool and its settings, and the file itself must be checked with MediaInfo — never guess from the tool name.
Is phone footage always variable frame rate?
Usually, but not every phone and not every setting. Phones write fewer frames when the picture is still and lower the frame rate in dim light to save power and space, so what they write is usually variable frame rate. But the only reliable method is still to check the file itself in MediaInfo — never guess from the source.
Is a variable frame rate file damaged?
No. Variable frame rate is a legitimate way to write a file. Phones and screen recorders use it deliberately to save power and space, by writing fewer frames when the picture is still. The file is not corrupted. It is simply written in a way that suits a player and does not suit an editor.
How do I check whether my file is variable frame rate?
Open it in MediaInfo and look at the Video section's Frame rate mode field. Variable means variable frame rate; Constant means it is not. Record the minimum and maximum frame rate shown alongside it — the wider the gap, the larger the effect is likely to be. In Premiere Pro 12.0.1 and later, right-clicking a clip and choosing Properties also shows "Variable Frame Rate Detected" for such files.
I converted the file and it still stutters. What does that mean?
It means the frame rate mode layer is cleared, and the fault belongs with the decoding-load layer. The file's timestamps are no longer the cause, so the stutter is coming from the weight of decoding — the codec, the resolution, or the absence of proxy media. That diagnosis is covered in the companion guide on timeline preview stutter.
Should I delete the original file after converting it?
No. The conversion re-encodes the video, so the picture quality and the file size change. Keep the original file until the edit is finished — it is the only copy that still holds the recording exactly as it was made.
Does Blackmagic have official documentation on variable frame rate for DaVinci Resolve?
No official documentation has been found: one published guide states plainly that it could find no Blackmagic documentation on variable frame rate, and that for DaVinci the only material is forum user reports. Do not treat Premiere Pro's official statements as DaVinci's official position. The diagnostic process is the same in both editors — only the source backing it differs.
Sources
- Adobe Community, "How to work with Variable Frame Rate (VFR) media in Premiere Pro?" (official FAQ) — https://community.adobe.com/questions-729/faq-how-to-work-with-variable-frame-rate-vfr-media-in-premiere-pro-1349720
- quickveed, "Variable Frame Rate: Fix VFR in Premiere and Resolve" — https://quickveed.com/blogs/variable-frame-rate
- formatif, "VFR to CFR in FFmpeg: Fix Audio Desync (2026 Guide)" — https://formatif.net/blog/vfr-to-cfr-audio-desync-fix
- h4tools, "Constant vs Variable Frame Rate for Gameplay Video" — https://h4tools.com/guides/constant-vs-variable-frame-rate/
- timebolt, "Why is my audio out of sync with video? Probably Variable Frame Rate" — https://www.timebolt.io/blog/how-to-edit-variable-frame-rate-videos-and-fix-out-of-sync-audio-video