When should you change a video's frame rate?
Matching an editing timeline. Mixing 25 fps footage into a 30 fps project, or 60 fps phone clips into a 24 fps film edit, makes the editor convert on the fly, sometimes badly. Converting clips to the timeline rate first gives you predictable cuts and frame-accurate sync.
Meeting a delivery spec. Broadcasters, agencies and some ad platforms ask for an exact rate such as 25 or 29.97 fps. Pick it here and the file reports exactly that rate, as a constant frame rate stream.
Shrinking screen recordings. A 60 fps screen capture of a slide deck or a code walkthrough rarely needs 60 fps. Dropping it to 30 fps keeps every other frame, text stays perfectly sharp, and the file usually gets smaller. For bigger savings, run the result through the video compressor afterwards.
Fixing audio drift in editors. If a screen recording or phone video slowly slides out of sync in your editor, it is often variable frame rate. Converting it to a constant rate, even the same nominal rate, usually solves it.
Judder, and why whole-number ratios look best
Going from 30 to 60 fps shows each frame exactly twice, and going from 60 to 30 keeps exactly one in two. The rhythm is even, so motion looks just like the source. Going from 24 to 30 fps is different: four source frames have to fill five output frames, so one frame in every four is held twice. That uneven cadence is judder, a small hitch that is most visible on slow camera pans and scrolling text. It is the progressive video cousin of the 3:2 pulldown used to show 24 fps film on 60 Hz televisions. Blend frames hides judder behind softer motion, and Motion interpolation replaces it with newly drawn frames. When you control the destination, the cleanest fix is to keep the original rate.
Exactly what the converter runs
For transparency, here is the ffmpeg pipeline. Drop or repeat uses fps=fps=30000/1001 (for a 29.97 target), Blend uses framerate=fps=30000/1001, and Motion interpolation uses minterpolate in motion-compensated mode with bilateral motion estimation, after scaling the video down to at most 1280x720 worth of pixels. Interpolation is limited to clips up to 30 seconds and targets up to 60 fps because it is many times slower than the other two methods. Every output is H.264 in yuv420p at CRF 20 with AAC audio at 160 kbps and +faststart, so it plays in browsers, phones and editors and starts streaming immediately. No setpts or atempo is applied, which is why length and audio sync are untouched.
Related tools
Want the video to actually play faster or slower? Use the video speed controller or the slow motion video maker. Need a different container or codec rather than a different fps? The video converters handle that. Planning a recording? The recording size calculator shows how frame rate, resolution and length add up to file size.
If you are converting screen recordings so a teammate or a client can watch them, you can skip the file juggling entirely: record with Clipy, share a link, and the recording comes with a transcript that coding agents like Claude Code and Codex can read.