What Is Frame Rate in Video?

Gameplay footage at 120 fps looks silky on your monitor. Export it at full rate for a five-minute bug report and the attachment can fail. Frame rate is not a quality slider, but it directly controls how much data each second of video must carry.

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 frames (or blends them, depending on settings). Motion may look slightly less smooth, but file size often drops because fewer frames remain.

A slide with a blinking cursor 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, many phone defaults, 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 can stabilize playback and compression.

Editors sometimes place 23.976 fps footage on a 30 fps timeline with pulldown or blending. Match project FPS early to avoid duplicate frames inflating export size.

How frame rate affects file size

At the same resolution, codec, and quality 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 settings.

Frame rate interacts with bitrate. If you halve FPS but keep the same CRF, the encoder may allocate more bits per frame, which partially offsets 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 often saves space without visible loss. Fast camera pans need higher FPS or higher bitrate to avoid strobing.

Frame rate vs shutter speed and motion blur

FPS is not shutter speed. Shutter angle controls motion blur within each frame. Short shutter looks crisp; long shutter smears motion.

When you reduce FPS in post, avoid odd cadence: converting 60 to 24 needs blending or selective drops, or motion can look 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.

Practical order:

1. Trim dead time first.
2. Export at 1080p30 instead of 1080p60 when motion allows.
3. Adjust bitrate or quality if the file is still too large. For a fixed megabyte cap, see compress video to target size on Mac .

Export walkthroughs: how to compress video on Mac or on Windows . Some recorders let you pick FPS before capture, which saves disk during recording as well as at export.

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 high-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 . Estimate bytes with the video file size calculator .

When a default export FPS is enough

Leaving the source frame rate alone can work when the file already fits the destination and motion looks correct.

Lower FPS when attachment caps force a choice and motion does not need every frame. GetCompress shows source FPS in preview, lets you trim before export, and can apply presets that balance resolution, frame rate, and quality for common sharing targets. Exact target file size is a video workflow. It does not replace an NLE timeline for complex frame-rate conforming across mixed B-roll.