What Is Frame Rate in Video?
Understand video frame rate (24, 30, 60 fps), how FPS affects file size and motion, and when to change it before you compress.
Gameplay footage at 120 fps looks silky on your monitor. Export it at full rate for a five-minute bug report and the attachment fails. Frame rate is not a quality slider, but it directly controls how much data each second of video must carry.
Editors sometimes interpret 23.976 fps footage on a 30 fps timeline with pulldown or frame blending. Match project FPS early to avoid duplicate frames inflating export size.
Frames per second in plain language
Video is a rapid sequence of still images. Frame rate (FPS, frames per second) counts how many images display each second.
24 fps feels cinematic. 30 fps is common for TV and phone video. 60 fps and above suit sports, games, and smooth UI motion.
If you record at 60 fps but export at 30 fps, the encoder drops every other frame (or blends frames, depending on settings). Motion may look slightly less smooth, but file size drops because half the frames are gone.
Human vision does not always benefit from extreme FPS on static content. A slide with a cursor blink does not need 60 fps the way a skateboard clip does.
Common frame rates and where you see them
| FPS | Typical source |
|---|---|
| 23.976 / 24 | Film, cinematic YouTube |
| 25 | PAL broadcast, some European cameras |
| 29.97 / 30 | NTSC, iPhone default video, webinars |
| 48 / 50 | High-frame cinema, some sports |
| 59.94 / 60 | Gaming capture, slow-motion source |
| 120+ | Slow motion playback at normal speed |
Variable frame rate (VFR) appears in some screen recorders and phone apps. Timestamps are uneven, which can confuse older editors. Converting VFR to constant 30 fps during export stabilizes playback and compression.
Webcam software sometimes reports 30 fps while delivering duplicated frames during low light. Check actual motion smoothness before assuming FPS alone caused size bloat.
How frame rate affects file size
At the same resolution, codec, and bitrate target, doubling FPS roughly doubles the number of frames to encode. A 1080p60 export is often close to twice the size of 1080p30 at similar quality settings.
Frame rate interacts with bitrate. If you halve FPS but keep the same CRF, the encoder allocates more bits per frame, partially offsetting the savings. For maximum shrink, combine lower FPS with a sensible resolution and codec. Read video bitrate basics for the full picture.
Screen recordings with static slides change little between frames. Dropping 60 fps to 30 fps there saves space without visible loss. Fast camera pans need higher FPS or higher bitrate to avoid strobing.
Games and UI demos are the middle ground. Scrolling code at 30 fps is usually enough for bug reports. Gameplay trailers may warrant 60 fps if motion sells the feature.
Frame rate vs shutter speed and motion blur
FPS is not shutter speed. Shutter angle controls motion blur within each frame. Short shutter (1/120 s at 60 fps) looks crisp; long shutter smears motion.
When you reduce FPS in post, avoid odd cadence: converting 60 to 24 requires frame blending or selective drops, or motion looks stuttery. 60 to 30 is straightforward. 30 to 24 is a small change many viewers never notice on talking-head content.
When to lower FPS before compression
Good candidates:
- Screen recordings of slides or code with little motion.
- Webcam updates sent over email.
- Archive copies where 30 fps matches the delivery platform.
Steps:
- Trim dead time first.
- Export at 1080p30 instead of 1080p60.
- Adjust bitrate or quality if still too large. For a fixed megabyte cap, see compress video to target size on Mac .
For detailed export settings, see how to compress video on Mac or how to compress video on Windows . Ticket attachments often need 720p30; compress video for email on Mac covers that workflow.
Some recorders let you pick FPS before capture. Lowering capture FPS saves disk during recording, not just at export time.
When to keep the original frame rate
Keep 60 fps or higher when:
- The clip is gameplay or sports where smooth motion is the point.
- You plan slow-motion playback from a 120 fps source.
- Down-converting caused visible judder in preview.
For GIF exports, frame rate matters even more because GIF is inefficient. See video to GIF on Mac for short loops at limited palettes. Social clips at 30 fps often need a separate crop pass; see resize video for Instagram on Mac .
Document your export FPS in readme files for team templates. Consistent 30 fps screen recordings are easier to batch compress than a mix of 59.94 and 60.
Using GetCompress
GetCompress displays source fps in the preview, lets you trim before export, and applies presets that balance resolution, frame rate, and quality for common sharing targets. Process MOV, MP4, and other formats locally, compare output size before sending, and save presets when you always need 1080p30 for ticket attachments. Estimate final bytes with the video file size calculator before batching a folder of clips.
When source footage mixes 24 fps B-roll with 60 fps screen capture, split exports by clip type instead of forcing one FPS across the whole timeline.
- Target Video Size on MacCompress video to a target file size on Mac with FFmpeg two-pass encoding and GetCompress. Hit exact MB caps for email, portals, and uploads.
- Compress Video for Email on MacCompress video for email on Mac with QuickTime and FFmpeg. Trim MOV and MP4 recordings, calculate a bitrate budget, and leave room below attachment caps.
- Resize Video for Instagram on MacResize video for Instagram on Mac with controlled crops, safe areas, and MP4 export settings for Reels, Stories, feed posts, and carousels.
- Convert Video to GIF on MacConvert video to GIF on Mac with FFmpeg, or export MP4 from QuickTime when the tool allows video instead of GIF.
Buy GetCompress now for local media compression with reusable presets and no media upload.