Frame Rate Explained: 24 vs 30 vs 60 fps (and When to Use Each) — 2026

Frame rate is the number of still images ("frames") a video shows every second, measured in frames per second (fps). 24fps looks cinematic, 30fps looks like broadcast TV and web video, and 60fps looks hyper-smooth and is used for sports, gaming, and slow motion. Higher is not automatically better: the "right" frame rate depends on the look you want and the platform you publish to.

That is the whole idea in one paragraph. But frame rate is also where more edits quietly break than almost anywhere else: mismatched clips that stutter, phone footage that drifts out of sync, "why does my video look like a cheap soap opera," and export settings nobody explains. This guide fixes all of that. Keep the one-line version open in the frame rate glossary entry; this is the deep dive.

What is frame rate?

Frame rate is how many individual images play per second to create the illusion of motion. Film and video are not really "moving" — they are a fast slideshow. Show enough still frames per second and your brain fuses them into smooth movement.

The unit is fps (frames per second) or Hz (hertz, the same idea for displays). A 30fps video shows 30 pictures every second. A 60fps video shows 60. The frames are the same size (that is resolution); frame rate is only about how often a new one appears.

The persistence-of-vision threshold — the point where separate images start to look like motion — is roughly 12-16 fps. Everything above that is a spectrum of "how smooth" and, just as importantly, "how it feels." Frame rate is not only a technical setting. It is a creative one.

Frame rate vs resolution vs bitrate

These three get confused constantly, and they control completely different things:

You can have 4K at 24fps or 720p at 60fps. You can shoot smooth 60fps and still export a low-bitrate file that looks blocky. They are independent dials. When someone says "high quality," ask which dial they mean — because raising frame rate does nothing for sharpness, and raising resolution does nothing for smoothness.

How frame rate actually works

Two things ride along with frame rate and explain most of the "why does this look wrong" questions: shutter speed and motion blur.

Shutter speed and the 180-degree rule

Each frame is a photo, and every photo has an exposure time (shutter speed). The film convention is the 180-degree shutter rule: set shutter speed to roughly double your frame rate. At 24fps you shoot at ~1/48s; at 30fps, ~1/60s; at 60fps, ~1/120s.

This ratio produces a natural amount of motion blur per frame — the blur your eye expects from movement. Break it and footage looks wrong in specific ways:

• Too fast a shutter (e.g. 1/1000s at 24fps) freezes each frame razor-sharp, creating a stuttery, "Saving Private Ryan" staccato look.
• Too slow a shutter smears motion into mush.

So frame rate and shutter are a pair. If you only remember one thing: shutter ≈ 2× frame rate.

Motion blur is a feature, not a bug

Motion blur is why 24fps film looks smooth even though it is "only" 24 images. The blur inside each frame bridges the gap to the next one. Videos with too little motion blur (high shutter, or frame-interpolated footage) can look juddery or unnaturally sharp even at high frame rates. This is central to why higher fps does not always look "better" — more on that below.

24 vs 30 vs 60 fps: what each frame rate is for

Here is the practical decision table. Match the frame rate to the feeling and the platform, not to "bigger number = better."

A useful mental model:

• 24/25fps = "cinema." The slight strobe and heavy per-frame blur read as "movie."
• 30fps = "television and the web." Neutral, clean, what most viewers unconsciously expect from a talking-head or tutorial.
• 60fps = "reality/live." Feels immediate and smooth — great for sports and games, sometimes too real for storytelling.

Most creators publishing talking-head, interview, or short-form content are safe defaulting to 30fps, and switching to 24fps only when they specifically want a cinematic mood or 60fps only when there is fast motion or planned slow motion.

Why 60fps can make your video look "cheap"

Here is the counterintuitive part that trips people up: shooting or displaying at 60fps can make narrative content look less premium, not more. This is the "soap opera effect."

Motion smoothing at high frame rates removes the subtle strobe and blur we associate with film. Because decades of expensive cinema were shot at 24fps and decades of cheap studio soap operas and daytime TV were shot on high-frame-rate video, our brains learned an association: 24fps = film/expensive, high-fps-smooth = cheap TV/live broadcast.

That is why:

• A cinematic wedding film or brand ad is almost always 24fps.
• Motion-smoothing ("TruMotion," "Motionflow") on TVs makes Hollywood movies look like a home video, and enthusiasts turn it off.
• 60fps is right for a Fortnite montage or an NBA highlight but usually wrong for a moody founder story.

The lesson: 60fps is a tool, not an upgrade. Use it when smoothness serves the content (motion, sports, gaming, slow-mo). Reach for 24fps when you want the audience to feel "cinema."

PAL, NTSC, and drop-frame timecode

Frame rates are not just round numbers, and this history still breaks edits today.

• NTSC (North America, Japan) settled on 29.97fps and 59.94fps, not exactly 30/60. The odd decimals date back to fitting color into the black-and-white TV signal. Cinema in these regions is 23.976fps (often just called "24").
• PAL (Europe, much of Asia, Australia, Africa) uses 25fps and 50fps.

Two practical consequences:

1. Drop-frame timecode. Because 29.97 is not exactly 30, timecode would slowly drift from real clock time. Drop-frame timecode (written with semicolons,

   00;00;01;00

   ) skips certain frame numbers — not actual frames — to stay accurate to the wall clock. Non-drop uses colons (

   00:00:01:00

   ). You rarely need to touch this, but now you know what the semicolons mean.
2. Mixing regions. Drop a 25fps PAL clip into a 29.97fps NTSC timeline without conforming and you can get stutter or audio drift. This is one of the most common "why does one clip look janky" causes.

For 2026 web publishing, none of this matters much day to day — you can safely author at a clean 24, 30, or 60 — but it explains the weird decimals in your export dialog.

Variable frame rate: the phone-footage trap

This is the single most common frame-rate problem in modern editing, and almost nobody warns you about it.

Phones, screen recorders (OBS, QuickTime), and many webcams often record in variable frame rate (VFR) — the fps fluctuates to save space, dropping frames in dark or static scenes and adding them in bright, busy ones. Professional cameras record constant frame rate (CFR) — a rock-steady, unchanging fps.

Editors and NLEs assume constant frame rate. Feed them VFR and you get:

• Audio drift. Lips slowly go out of sync, worse the longer the clip.
• Stutter and duplicated/dropped frames.
• Clips that report "30fps" but aren't really.

The fix is transcoding to constant frame rate before editing (many editors do this automatically on import; tools like HandBrake or ffmpeg can force CFR). If you have ever fought "my audio slowly desyncs and I can't figure out why," VFR is almost certainly the culprit. This also affects stitching clips recorded on different devices.

What frame rate should you use? (by platform)

There is no single answer, but there are strong defaults. Match your source frame rate to your intended look, then export at a frame rate the platform likes.

The golden rule for slow motion: capture at a high frame rate and play it back at a low one. Shoot 120fps, drop it on a 24fps timeline, and you get smooth 5× slow motion. You cannot create real slow motion from 24fps footage after the fact — there simply aren't enough frames (AI frame interpolation can fake it, with artifacts).

How to choose and set your frame rate

Decide once, at the start, and keep it consistent across a project. Mixing frame rates is where trouble starts.

Step 1: Pick your delivery frame rate first

Start from where the video will live. Cinematic piece for YouTube? 24. Standard tutorial or social video? 30. Sports/gaming/action? 60. This is your project's "base" frame rate and your timeline should match it.

Step 2: Shoot at (or above) your delivery rate

Match your camera to the delivery rate for normal footage. For anything you might slow down, shoot higher (60/120/240) so you have frames to spare. Set shutter speed to roughly double the fps you are shooting.

Step 3: Record constant frame rate when you can

On phones and screen recorders, choose settings that force constant frame rate, or plan to transcode. This one step prevents the audio-drift nightmare described above.

Step 4: Set the timeline/project to your base rate

In your editor, create the sequence at your delivery frame rate before importing. Everything you add will conform to it. Dropping a 60fps clip on a 30fps timeline is fine (it plays at normal speed or can be slowed); the timeline rate is what you deliver.

Step 5: Conform mismatched and slow-mo clips deliberately

For slow motion, interpret/retime high-fps clips to your base rate. For mismatched sources, let the editor conform them — and check for stutter. This is exactly the kind of unification an AI editor can automate.

Step 6: Export at a platform-friendly frame rate

Match export fps to your project. Do not "upgrade" 24fps to 60fps on export — it just duplicates frames and can introduce judder. Keep frame rate consistent from shoot to export.

Common frame rate mistakes

Most frame-rate problems are avoidable with a little planning:

• Mixing frame rates in one project without conforming. The classic stutter. Pick a base rate and conform everything to it.
• Ignoring variable frame rate on phone/screen footage. Causes slow audio desync. Transcode to CFR first.
• Assuming 60fps is "higher quality." It is smoother, not sharper, and can look cheap for narrative. Match fps to intent.
• Forgetting the shutter rule. High shutter at low fps = stutter; the footage looks "off" and you cannot fix it in post.
• Shooting slow motion at your delivery rate. You cannot make real slow-mo from 24fps. Capture high.
• Upscaling frame rate on export. Exporting 24fps footage as 60fps duplicates frames and adds nothing.
• Mismatched export causing judder. 24fps footage forced into a 30fps container without proper conforming introduces uneven cadence.

How AI video editors handle frame rate

Frame rate is exactly the kind of invisible, technical, error-prone task AI editing is good at removing.

Modern AI video editors automatically detect the frame rate of every clip you upload — including catching variable-frame-rate phone and screen recordings — and conform them to a single project frame rate so nothing stutters and audio stays in sync. When you stitch clips from a DSLR, a phone, and a screen recorder into one video, the editor unifies the frame rates for you instead of leaving you to debug desync by hand.

In Loopdesk (full disclosure: Loopdesk is our product), this is handled during ingest: mixed-source footage is unified to a consistent timeline frame rate automatically, and export presets apply the right frame rate per platform so you are not guessing in the export dialog. We wrote about the engineering behind this in taming the timeline: fps unification and collision-free placement. The point of automating it is simple: frame rate should be a creative choice you make once, not a bug you chase for an hour.

If you want the wider technical picture, pair this with video codecs explained (the compression side of export) and optimizing video for every platform. Frame rate is one stop on the full video editing terminology map.

Frequently Asked Questions

What is frame rate in simple terms?

Frame rate is how many still images a video shows every second, measured in frames per second (fps). More frames per second means smoother-looking motion. 24fps looks cinematic, 30fps looks like standard web/TV video, and 60fps looks very smooth.

Is 24fps or 30fps better?

Neither is universally better. 24fps looks cinematic and is used for films, ads, and moody content. 30fps looks clean and "video," and is the safe default for talking-heads, tutorials, and most social content. Choose based on the look you want, not the number.

Why does 60fps look weird or cheap?

Because our brains associate the ultra-smooth, low-motion-blur look of high frame rates with cheap live TV and soap operas, while 24fps is associated with expensive cinema. This "soap opera effect" is why 60fps can feel less premium for narrative content, even though it is technically smoother.

What frame rate should I use for YouTube?

30fps is a safe neutral default for talking-heads and tutorials. Use 24fps for a cinematic look, and 60fps for gaming, sports, or fast motion. YouTube supports 24, 25, 30, 48, 50, and 60fps.

What frame rate is best for slow motion?

Shoot at a high frame rate (60, 120, or 240fps) and play it back on a lower-frame-rate timeline (24 or 30fps). Shooting 120fps and delivering at 24fps gives smooth 5× slow motion. You cannot create real slow motion from 24fps footage after recording.

What is variable frame rate and why is it a problem?

Variable frame rate (VFR) means the fps fluctuates during recording to save space — common on phones and screen recorders. Editors assume constant frame rate, so VFR footage often drifts out of audio sync. The fix is transcoding to constant frame rate (CFR) before editing.

What is the difference between 29.97 and 30 fps?

29.97fps is the real NTSC broadcast frame rate (North America, Japan), a leftover from fitting color into old TV signals; "30fps" is the rounded name for it. For web video you can usually treat them as the same, but 29.97 is what shows up in professional export settings.

Does higher frame rate mean higher quality?

No. Frame rate controls smoothness, not sharpness. Sharpness is resolution (1080p vs 4K), and file quality is bitrate. A 60fps video can look worse than a 24fps one if it has low resolution or low bitrate. They are independent settings.

---

Editing footage shot at different frame rates? Open Loopdesk and it unifies mixed-source clips to one clean frame rate automatically — no manual conforming, no mystery audio drift — then exports at the right fps for each platform.