Why Your Video Stutters, and Whether the File Is to Blame

Kinds of stutter and what they suggest

Watch a section with steady motion, such as a slow camera pan or scrolling text, and describe what you see. The pattern narrows the cause before you open any settings.

• Regular, rhythmic judder throughout. Often a frame-rate mismatch, either converted into the file or between the video and the display.
• Freezes in busy scenes while audio carries on. The decoder is falling behind on demanding frames.
• Smooth at the start, worsening over time. Heat, power throttling or a slow drive struggling to keep up.
• Stutter only after seeking. Seeking to a point between keyframes forces extra decoding work.
• Hitches at the same timestamps every time. Problem frames in the file itself.
• Random hitches that change from one viewing to the next. Playback load or background activity.

Tell a file problem from a playback problem

1. Play the file on a different, preferably more powerful, device. Smooth playback there points to the first device.
2. Watch the same section twice. If the hitches land at exactly the same moments, the file is the likely cause.
3. Step through a stuttering section frame by frame. In VLC, the E key advances one frame. If you see the same image repeated, or motion that jumps unevenly between frames, the problem is in the file.
4. Check the player's statistics. VLC's media information window reports displayed and lost frames, and browsers and video sites have their own diagnostic views. Rising lost-frame counts mean playback is dropping frames.
5. Copy the file to the computer's internal drive and play it from there. If it becomes smooth, the storage or network was too slow.

Playback causes

Decoding limits

High resolutions, 10-bit video or codecs such as HEVC and AV1 without hardware support force slow software decoding

High bitrate

Camera originals and production codecs can need far more data per second than a laptop or connection can supply smoothly

Slow storage

USB 2 drives, network shares, memory cards and cloud folders that download files on demand

Power and thermal limits

Battery saver modes and hot laptops reduce processor and graphics speed

Browser settings

Hardware acceleration turned off, many tabs open, or extensions competing for resources

Display refresh mismatch

24 or 25 frames per second shown on a 60 Hz screen cannot be displayed with perfectly even frame durations

The display mismatch deserves a note. A 60 Hz screen refreshes 60 times a second, so a 24 frames per second film must show frames alternately for three and two refreshes, an uneven rhythm that some viewers notice in slow pans. It is not a defect in the file; some TVs and players switch the display rate to match the content. Codec support issues, especially with phone footage, are covered in HEVC compatibility.

File causes

Variable frame rate. Phones and screen recorders often vary the frame rate as conditions change. Many players handle this well, but some players and editors do not, and the result looks jerky or drifts out of sync. The explainer on variable frame rate covers how to spot and convert it.

Frame-rate conversion baked in. Converting 24 frames per second footage to 30 by repeating frames creates a regular judder, and converting 60 to 25 discards frames unevenly. Blended conversions avoid judder but add ghosting on movement. Once exported this way, the pattern is permanent in that file.

Dropped frames during recording. A recorder that could not keep up, from a slow card or a busy computer during screen capture, may have skipped frames. They cannot be recovered.

Encoding at too low a bitrate. Fast motion at a starved bitrate can look smeared and blocky, which some people describe as choppy even when every frame is present. The guide to shrinking a video file covers sensible bitrate choices.

Fixes for playback problems

• Turn hardware acceleration on in the browser or player, and update the graphics driver.
• Plug in the laptop and switch off battery-saving modes while watching or editing.
• Copy files from network drives, cloud folders and memory cards to the internal drive before playing them.
• Use a player with efficient decoders for the codec in question, or lower the playback resolution if the player allows.
• In editing software, lower the preview resolution or use proxy files, smaller copies used only for editing.
• Close other heavy applications and browser tabs during playback.

Fixes for file problems

If the file itself stutters, or must play smoothly on modest devices, make a delivery copy. Choose a widely supported codec, a constant frame rate that matches the source, and a bitrate suited to the content:

ffmpeg -i input.mov -vf fps=30 -c:v libx264 -crf 20 -preset slow -pix_fmt yuv420p -c:a aac -b:a 160k delivery.mp4

Set the fps value to the frame rate the footage was actually shot at, or to an exact divisor of it: halving 60 to 30 discards every second frame cleanly, while forcing 24 into 30 creates judder. If the original was converted badly, go back to the source and export again at its native rate rather than trying to repair the converted copy. Motion interpolation can smooth an awkward conversion but invents in-between frames and can produce warping around moving edges.

A worked example: a screen recording that stutters on staff laptops

Mistakes and limits when fixing stutter

• Converting frame rates you did not need to. Every conversion that is not an exact division adds judder, blending or interpolation artefacts.
• Re-encoding a file that is fine because one device struggles. A delivery copy is sensible; replacing the original is not.
• Expecting re-encoding to restore dropped frames. Missing frames stay missing; interpolation only guesses at them.
• Judging smoothness in an editor's timeline. Timeline playback depends on preview settings, effects and caching, so judge the exported file in a normal player.
• Ignoring the display. A file can be perfect while the screen's refresh rate makes some motion look uneven.

What mydubly changes, and what it does not

mydubly never re-encodes the picture. To make a translated video, the browser copies the original video packets into a new file alongside the dubbed audio track, so frame rate, frame timing and resolution are exactly those of the source. That is good news for quality and sync, but it also means a file that stutters because of how it was recorded will stutter in the translated version too, and a file too demanding for a viewer's device will be just as demanding. If the codec cannot go into MP4, the output is MKV, which may not play inline in every browser.

Processing decodes the audio, and the picture is copied rather than decoded and re-encoded, so a file that plays choppily on your device can usually still be translated. On low-memory devices, mydubly may offer the translated audio track only, which you can combine with the video in an editor. If your audience needs a lighter file, make the delivery copy first and translate that, as described in the guide on how to translate a video.

Next step: settle the file, then translate it

Decide whether the stutter is in the file or in playback using the tests above, make a delivery copy if the file needs one, and then run that copy through the video translator. Check the translated video on the same devices your viewers use.