Video Processing

The Secrets of Frame Rate: The Cinematic 24fps vs. the Fluid 60fps

2026/7/1028 views

Why do movies at 24fps feel smooth while a 30fps game feels choppy? The answer isn't the frame rate itself, but what each frame looks like.

A movie theater shows just 24 frames per second, and no one complains about choppiness; a PC game dropping from 60fps to 30fps has players up in arms. The broadcast industry standardized on a bizarre fractional number—29.97. A smartphone clip dragged into editing software gradually drifts until voices no longer match lip movements. Behind these seemingly unrelated phenomena is the same parameter: frame rate—a specification with far more story to it than "pictures per second."

What Frame Rate Is: The Speed of the Motion Illusion

One second at 24/30/60 fps: higher rates sample time more densely

Video is, at its core, a rapid sequence of still images (frames) that exploits persistence of vision to create the illusion of motion. Frame rate is simply how many frames are shown per second, in fps (Frames Per Second).

Common frame rates and their camps:

Frame rate	Camp	Origin and use
24fps	Cinema	Standard set in the late 1920s with the arrival of sound film, balancing film stock cost against watchability
25fps	PAL	Television standard in Europe, China, and elsewhere—tied to 50Hz mains electricity
29.97fps	NTSC	Television standard in the US, Japan, and elsewhere (explained below)
30fps	Online video	The integer approximation of NTSC; one of the de facto standards for web content
50/60fps	High frame rate	Sports, gaming, and anything prioritizing fluidity
120fps+	Slow-motion capture	High sampling reserved for slow playback

29.97: A Number Born of Engineering Compromise

Why not a clean 30? This is the most famous "historical baggage" in video engineering:

Early black-and-white television ran at 30fps (synchronized with North America's 60Hz mains power to avoid flicker);
When color was introduced in 1953, engineers slotted the color subcarrier into gaps in the existing spectrum so old black-and-white sets could keep receiving broadcasts—but the subcarrier interfered with the sound carrier;
The fix was to reduce the frame rate by 0.1%: 30 × 1000/1001 ≈ 29.97fps, shifting the interference away.

A compromise made for 1950s television sets persists to this day: American broadcast and cable TV still run at 29.97fps, and many cameras record 29.97 by default rather than 30. The same logic ties PAL's 25fps to 50Hz mains power.

A 0.1% difference sounds trivial, but over a one-hour program it accumulates to 3.6 seconds—which is why broadcast invented "drop-frame timecode" to keep timecode aligned with wall-clock time (it drops timecode numbers, not actual frames).

Why 24fps Doesn't Feel Choppy but 30fps Gaming Does: The Secret of Motion Blur

This is the most counterintuitive question in the frame-rate discussion, and the answer lies not in the rate itself but in what each frame looks like:

Camera-captured reality: while the shutter is open, moving objects smear across the film or sensor, creating natural motion blur. Every frame contains "the path the object traveled during this slice of time," and adjacent frames transition continuously—your brain happily interpolates 24 frames per second into fluid motion.
Game-rendered frames: each frame is a perfectly sharp freeze of objects at a single instant, with zero blur. Frames jump discretely from one to the next; the brain detects the "teleportation," and far higher frame rates (60fps and up) are needed to restore the sensation of fluidity.

Photography describes the degree of motion blur with shutter angle: a 180° shutter (the cinema standard) means the exposure lasts half the frame interval. 24fps with a 180° shutter equals a 1/48-second exposure—just the right amount of blur, and a major ingredient of the so-called "cinematic look." Conversely, shooting 24fps video with a 1/1000s fast shutter (think the beach assault in Saving Private Ryan) freezes every frame, producing a tense, staccato jitter—motion blur is an artistic language you can deliberately deploy.

High Frame Rates: Fluidity at the Cost of "Not Looking Like Film"

Raise the frame rate to 48/60/120fps and motion does become silkier—but audiences often say it looks "like a soap opera or security footage." This is the soap opera effect, and it follows from the same logic: high frame rates plus short exposures make every frame too crisp, erasing cinematic motion blur and rendering the image "too real."

The controversy around Peter Jackson shooting The Hobbit at 48fps is the famous case study, and the reason film lovers despise TVs' "motion smoothing" features (which interpolate 24fps up to 120fps) is exactly the same thing.

But high frame rates are irreplaceable in their home turf:

Sports broadcasts: fast action needs more frames to remain trackable;
Gaming: as explained, blur-free rendered frames demand high rates for compensation;
Slow-motion capture: shooting at 120/240fps provides raw material for slow playback in post (see Video Speed Change in this series).

VFR vs. CFR: The Real Culprit Behind Out-of-Sync Phone Footage

Closely related to frame rate—but rarely discussed—is the single biggest source of everyday editing disasters:

CFR (Constant Frame Rate): the camera outputs a strictly fixed number of frames every second, evenly spaced. The standard for professional cameras and cinema.
VFR (Variable Frame Rate): the recording dynamically adjusts how many frames are produced—fewer for static scenes, more for action. Smartphone video, screen recordings, and many webcams use VFR by default (to save power and bitrate).

VFR files play back fine (players honor each frame's timestamp), but many editing programs and conversion tools assume a constant frame rate. They estimate the rate as "total frames ÷ duration" and lay out frames evenly—so the frames' actual timestamps gradually diverge from the software's assumption, showing up as audio and video drifting further apart the deeper into the clip you go.

The fix: transcode VFR footage to CFR (resampling the frame sequence at a constant rate) before importing it into your editor, and sync problems disappear entirely. This is the technical reason behind the workflow advice "run phone footage through a converter before editing."

Frame-Rate Conversion: The Most Underestimated Quality Killer

Converting video from one frame rate to another is far more dangerous than it looks:

Integer relationships (30→60): each frame can simply be repeated—safe;
Non-integer relationships (24→30, 50→60): frames must be periodically repeated or dropped, producing judder—panning shots hitch and stutter. The classic 3:2 pulldown (24→30) alternates frames in a "3-field, 2-field" rhythm, giving pans their characteristic tremble;
Motion-interpolated conversion: algorithms (optical flow) generate intermediate frames—natural-looking but slow, and prone to warping artifacts in fast motion or complex occlusion.

The principle: keep one frame rate from shoot to delivery, and never convert mid-pipeline. Decide at the start of a project (25 or 50 for Chinese platforms; 24/30/60 for international ones), and keep all footage, the editing timeline, and the output consistent.

Common Misconceptions

"Higher frame rate means sharper video." Frame rate governs fluidity, not clarity. Clarity is about resolution and bitrate (see articles 17 and 18 in this series).
"24fps is obsolete and should be retired." 24fps with a 180° shutter is part of a century of film language; "smoother" does not mean "better."
"Converting a 24fps film to 60fps makes it smoother." Interpolated frames are algorithmic guesses—panning judder is ironed out, but so is the cinematic feel, and artifacts may creep in.
"If the phone says 30fps, it really is 30fps." Most phone recording is VFR—the labeled 30fps is only an average. Transcode to CFR before editing.
"29.97 and 30 are interchangeable." For short clips you won't notice; over long videos the sync offset accumulates. Mixed-frame-rate footage must be conformed to one timeline.

Practical Tips

Let content decide: 24/25fps for narrative and vlogs chasing a cinematic feel; 50/60fps for tutorials, games, and sports where clarity of motion matters. Don't switch midway.
Match your region's standard: 25/50 for PAL-region platforms (also avoids 50Hz lighting flicker), 30/60 for NTSC-region and international platforms.
Avoid flicker indoors: mains-powered lights flicker at 100/120Hz; avoid shutter speeds that fight it (use 1/50 or 1/100 second in 50Hz regions).
Transcode phone footage to CFR first: unify to a constant frame rate before editing to eliminate progressive audio drift.
High frame rates serve slow motion: shoot 60fps+ for shots you plan to slow down, then deliver at the project frame rate (see Video Speed Change).
Output follows the timeline: always export at the timeline's frame rate—never convert frame rates at the export step.