B · SHARPNESS & TECHNICAL
Frame rate
Frames per second — and the feel each number carries.
By Thomas Linck, founder · Updated June 2026
Frame rate is how many frames your video captures and shows per second. 24 fps reads cinematic, 30 fps is the standard for talking content, and 60 fps suits fast motion, gaming and sports. It is a creative choice in a technical costume: pick the feel first, then keep the number consistent.
WHY IT MATTERS
Two rules carry most of it. Keep your shutter speed near 1/(2 × fps) — the 180° rule — so motion carries the natural blur the eye expects; a far faster shutter makes movement look stuttery. And never mix frame rates on one timeline: the editor has to stretch or drop frames to fit, and your eye reads the result as judder on every pan.
TARGET · STANDARD
| 24 fps | cinematic | film look, storytelling |
| 30 fps | talking content | the safe default |
| 60 fps | fast motion | gaming, sports, slow-mo |
How CutScore measures it
CutScore reads the frame rate of every clip deterministically with ffmpeg, checks the motion cadence frame by frame, and timestamps the judder a mixed timeline leaves behind — so a single 24 fps clip on a 30 fps sequence gets caught before your viewers feel it.
QUESTIONS
Frequently asked.
Neither is better — they feel different. 24 fps reads filmic and suits vlogs and storytelling; 30 fps is the safe default for talking heads and tutorials. YouTube accepts both, so pick the feel you want and keep it consistent through to the export.
The editor throws away half the frames to make it fit, and the frames that survive were shot with a faster shutter, so they carry less motion blur than a native 30 fps clip. Motion reads crisp and steppy. Match the project to the footage, or retime deliberately.