24 FPS vs 30 FPS vs 60 FPS: What Frame Rate Should You Use?

When you choose a video, you may notice labels such as 24 FPS, 30 FPS, or 60 FPS alongside the resolution.

But what do those numbers actually mean?

Frame rate is one of the most important parts of how motion looks in a video. It affects how frequently new frames appear, how smooth fast movement can look, how much data may be needed, and how much work a playback device may have to do.

The important part is that higher FPS is not automatically better.

A 60 FPS version can be an excellent choice for sports or gaming, while 24 FPS may be exactly what you want for a film. A 30 FPS video can be a practical middle ground for everyday content.

The right choice depends on the original content, the amount of motion, your viewing purpose, storage and data limits, and the device playing the video.

What Is Frame Rate?

Frame rate is the number of individual video frames shown or encoded during one second.

It is normally expressed as frames per second, or FPS.

Think of a video as a sequence of still images. Each frame captures the scene at a particular moment. Playing those frames one after another creates the appearance of continuous motion.

For example:

• 24 FPS means 24 frames are represented during one second.
• 30 FPS means 30 frames are represented during one second.
• 60 FPS means 60 frames are represented during one second.

That means 60 FPS samples motion more frequently than 30 FPS, and 30 FPS samples motion more frequently than 24 FPS.

The result can be noticeably different when something moves quickly across the screen. MDN describes frame rate as primarily affecting perceived motion smoothness and notes that higher frame rates can eventually reach diminishing returns.

What Does FPS Mean?

FPS stands for frames per second.

In video, it describes how many frames are used for each second of playback or encoded media.

The term can also appear in gaming, where FPS may describe how many frames a computer or console is rendering each second. That is related to the same basic idea, but recorded video and real-time game rendering are not exactly the same process.

For a downloaded video, the frame rate is normally part of the source video itself. You are not simply choosing a number that makes the file “higher quality.”

Instead, you are choosing between available versions of the source.

24 FPS vs 30 FPS vs 60 FPS at a Glance

24 FPS

• Commonly associated with film and cinematic production.
• Preserves the motion cadence of many film-style sources.
• Makes sense when maintaining the original cinematic presentation is important.
• Usually requires less temporal data than a comparable higher-frame-rate version.

30 FPS

• A common general-purpose frame rate.
• Useful for many everyday videos, online content, presentations, and tutorials.
• Provides more motion samples than 24 FPS without going all the way to 60 FPS.
• Often makes a sensible middle-ground choice.

60 FPS

• Provides twice as many frames per second as 30 FPS.
• Can make fast movement appear smoother.
• Useful for sports, gaming, action, and some screen recordings or tutorials.
• Can increase data and processing requirements, depending on the codec and encoding settings.

These are not strict quality rankings. They describe different ways of representing motion.

YouTube's current upload guidance lists 24, 25, 30, 48, 50, and 60 FPS among common frame rates and recommends uploading content at the same frame rate at which it was recorded.

What Does 24 FPS Look Like?

At 24 FPS, the video contains fewer temporal samples than 30 or 60 FPS.

That does not mean the video is poor quality.

Twenty-four FPS is widely associated with film and cinematic production. MDN notes that motion picture film is typically 24 FPS, while Adobe explains that frame rate determines how quickly individual frames are presented and how motion is perceived.

For a narrative film, documentary, interview, or other controlled content where preserving the source's original motion style is the priority, 24 FPS can be exactly the right choice.

Fast movement can look different at 24 FPS because there are fewer frames describing the movement over the same period.

That difference is part of the visual character of the footage, rather than simply a defect.

When 24 FPS makes sense

Choose or preserve 24 FPS when:

• The source was originally recorded at 24 FPS.
• You are watching a film-style production.
• Maintaining the original motion cadence matters.
• The video does not depend heavily on extremely fast movement.
• Storage or data efficiency is more important than maximum temporal smoothness.

The key idea is preserving the source, not automatically choosing the smallest number.

What Does 30 FPS Look Like?

30 FPS provides 30 frames for every second of video.

It sits between 24 and 60 FPS and is widely used for general video content.

For everyday viewing, tutorials, presentations, talking-head videos, online content, and many other situations, 30 FPS can provide a useful balance between motion smoothness and data requirements.

It is also common enough that many video workflows and services support it directly. YouTube lists 30 FPS among its common supported frame rates.

When 30 FPS makes sense

30 FPS is a sensible choice when:

• The source was recorded at 30 FPS.
• You are watching general-purpose video.
• The video contains some movement but does not require maximum temporal smoothness.
• You want a practical balance between smoothness, data, storage, and device workload.
• You are working with tutorials, presentations, interviews, or ordinary online video.

For many people, 30 FPS is the easiest default when the source itself is 30 FPS.

What Does 60 FPS Look Like?

60 FPS represents 60 frames every second.

Because there are more frames describing movement, 60 FPS can provide smoother temporal motion, especially when objects move quickly across the screen.

This is particularly useful for:

• Sports.
• Gaming.
• Fast action.
• Camera movement.
• Certain tutorials and demonstrations.
• Some screen recordings.
• Content where small changes in motion need to remain easy to follow.

YouTube explicitly supports high-frame-rate playback and notes that high-frame-rate video must have been uploaded or live-streamed at a high frame rate to be played back that way.

But 60 FPS is not automatically the best choice.

If a film was originally produced at 24 FPS, converting it to 60 FPS does not suddenly give the original camera 36 additional moments of captured motion every second.

Why Do Different Frame Rates Exist?

Different frame rates exist because video has different requirements.

A film may prioritize a particular motion cadence.

A sports recording may prioritize following rapid movement.

A game capture may benefit from more frequent motion samples.

A screen recording may need enough frames to make cursor movement, scrolling, animations, or interface changes easy to follow.

There are also technical and historical reasons for frame-rate standards in different video systems.

Apple's current HLS authoring specification supports natural VOD frame rates including 23.976, 24, 25, 29.97, 30, 50, 59.94, and 60 FPS. It also recommends that VOD content use a natural frame rate appropriate to the content.

So the existence of multiple frame rates is not an accident. Different rates solve different production, delivery, and playback requirements.

How Frame Rate Affects Motion and Smoothness

The most important thing frame rate changes is temporal sampling.

Imagine a car moving across the screen.

At 24 FPS, the video records a certain number of moments during that movement.

At 30 FPS, there are more samples.

At 60 FPS, there are many more.

When the movement is fast, those additional samples can make the progression from one position to another appear smoother.

This does not mean that higher FPS automatically creates sharper images.

Frame rate is primarily about when the video samples motion.

Resolution describes spatial dimensions.

Bitrate describes the amount of encoded data used over time.

Codec describes how that information is compressed.

These factors work together rather than replacing one another.

Frame Rate vs Refresh Rate: FPS and Hz Are Not the Same

This is one of the most common sources of confusion.

Frame rate describes the video.

Refresh rate describes how frequently a display can refresh.

Frame rate is normally expressed in FPS.

Display refresh rate is expressed in Hz.

For example:

• A video can be encoded at 24 FPS.
• A display can operate at 60 Hz.
• Another display may support 120 Hz.
• A device can potentially change its display refresh behavior to better match the content.

A 60 Hz display is therefore not the same thing as a 60 FPS video.

Android's documentation specifically discusses this distinction. For example, an Android device can have a 60 Hz display while an app is playing 24 FPS video, and the platform may choose another supported refresh rate to improve presentation. Android even recommends passing the video's exact frame rate to the platform rather than simply rounding values such as 29.97 to 30.

A simple way to remember it is:

FPS = how often the video provides frames.

Hz = how often the display can refresh.

They interact during playback, but they are different measurements.

How Frame Rate Interacts With Bitrate

Frame rate and bitrate are closely related, but they are not the same setting.

A higher frame rate means there are more frames to represent over the same amount of time.

That can increase the amount of encoded data required, but the exact result depends heavily on the codec, encoder settings, resolution, scene complexity, and other factors.

MDN notes that higher frame rates generally result in larger compressed video sizes when the frame rate is not reduced during encoding.

Apple likewise identifies frame rate, codec, resolution, encoder implementation, content complexity, and desired quality as factors affecting the bitrate required for video encoding.

This is why you should not use a rule such as:

“60 FPS always needs exactly twice the bitrate.”

That is not technically reliable.

The relationship depends on the content and encoding method.

YouTube's current upload recommendations illustrate the relationship without making it universal. For example, its H.264 recommendations for 1080p list 8 Mbps for 24/25/30 FPS and 12 Mbps for 48/50/60 FPS. These are YouTube's upload recommendations, not a universal bitrate formula for every video.

How Frame Rate Interacts With Resolution

Frame rate and resolution describe different properties.

Resolution describes the number of pixels in the video frame.

Frame rate describes how many frames are represented each second.

That means two videos can both be 1080p while having different frame rates.

For example:

• 1080p24
• 1080p30
• 1080p60

All three have the same nominal vertical resolution.

But their motion sampling is different.

A 4K video can also be 24, 30, or 60 FPS.

Increasing resolution does not automatically determine the frame rate, and increasing frame rate does not automatically increase resolution.

The two settings simply interact within the overall encoding and playback system.

Apple's documentation treats resolution and frame rate as separate but related factors when determining video encoding requirements.

Does Higher FPS Mean a Larger Video File?

It often can, but there is no universal multiplier.

If everything else were held constant, representing more frames per second gives the encoder more temporal information to process.

MDN states that higher frame rates cause larger compressed video sizes when the frame rate is not reduced during encoding.

However, modern codecs do not simply store every frame as a completely independent image.

Video compression can compare neighboring frames and encode changes between them. MDN's WebCodecs documentation explains that codecs can use temporal compression and motion compensation to represent differences between successive frames efficiently.

So the final file size depends on more than FPS.

Important variables include:

• Frame rate.
• Bitrate.
• Codec.
• Resolution.
• Encoder configuration.
• Scene complexity.
• Motion.
• Noise and texture.
• Duration.
• Audio.

That is why you should compare actual file information instead of assuming that 60 FPS will always be exactly 2.5 times the size of 24 FPS or exactly twice the size of 30 FPS.

How FPS Affects Download Size and Download Time

For someone saving videos, this is especially practical.

Suppose two versions of the same video are available at the same resolution, but one is 30 FPS and the other is 60 FPS.

The 60 FPS version may contain more encoded data and therefore may be larger.

If it is larger, it can also take longer to download over the same connection.

But the relationship is not determined by FPS alone.

A smaller 60 FPS file can exist if it uses a more efficient codec or lower bitrate than another 30 FPS file.

Similarly, a 30 FPS video can be very large if it uses a high bitrate, high resolution, or a less efficient encoding configuration.

This is why frame rate should be considered together with file size and bitrate, rather than used as a standalone quality ranking.

How Frame Rate Affects Playback and Device Workload

Higher-frame-rate video can require the playback system to process and present more frames during each second.

That can matter on devices with limited decoding or rendering capabilities.

Android's Media3 documentation notes that playback can stutter when a device cannot decode content quickly enough, with bitrate, resolution, and high-frame-rate content among the factors that can contribute to playback problems.

Modern phones, laptops, TVs, and desktops can handle a wide range of video formats, but capabilities still vary.

A powerful computer may have no trouble with a high-frame-rate video.

An older phone may behave differently, particularly when high frame rate is combined with high resolution, demanding codecs, or high bitrate.

So if a video plays poorly, choosing a lower-complexity version can sometimes provide a better experience than simply choosing the highest available number.

Can Frame Rate Affect Battery Life?

Yes, frame rate can be relevant to power consumption, although it is not the only factor.

More frames can mean more processing and rendering work, and the display may also operate at a higher refresh rate depending on the device and playback system.

Apple has specifically documented that video frame rate affects the work performed during playback and recommends considering 24 or 30 Hz video for performance and power in certain spatial-video scenarios.

Apple also explains that higher display refresh rates can use more power on devices with ProMotion displays.

Android similarly documents frame-rate management as a way to balance smoothness and power usage, including cases where a lower frame rate can reduce unnecessary high-refresh-rate operation.

This does not mean that every 60 FPS video will drain a phone's battery by a fixed amount.

Battery consumption depends on the entire playback pipeline, including:

• Display technology.
• Display refresh rate.
• Video codec.
• Hardware decoder.
• Resolution.
• Brightness.
• Device hardware.
• Operating-system behavior.
• Other applications running in the background.

The practical lesson is simply that a higher frame rate can have a power cost, so there is little reason to choose 60 FPS when the content does not benefit from it and battery efficiency is important.

What Happens When You Convert 24 FPS to 60 FPS?

If the original video was captured at 24 FPS, converting it to 60 FPS does not recreate the missing original camera frames.

You have only 24 original frames for each second.

To produce a 60 FPS output, software must decide what to do about the additional frames.

It can duplicate existing frames.

It can blend frames.

Or it can use more sophisticated motion-based interpolation to estimate what intermediate frames might look like.

The important distinction is between changing the output frame rate and capturing more original motion information.

Changing 24 FPS into 60 FPS changes the output cadence.

It does not travel back in time and make the camera capture the missing moments.

Frame Interpolation vs Native Frame Rate

Frame interpolation is a technique for generating intermediate frames between existing frames.

Apple's VideoToolbox documentation describes frame interpolation as producing intermediate frames between a previous frame and a source frame.

FFmpeg also provides a minterpolate filter specifically for frame-rate conversion using motion interpolation. Its implementation supports techniques such as frame duplication, blending, and motion-compensated interpolation.

This can make a 24 FPS source appear smoother when output at a higher frame rate.

But interpolated frames are generated estimates, not additional frames originally captured by the camera.

That distinction matters.

If the goal is to preserve the original recording faithfully, keeping the native source frame rate is often preferable.

If the goal is a specific playback effect or processing workflow, interpolation may be appropriate.

Which Frame Rate Should You Choose?

There is no universal winner.

Start with the source.

Then consider motion, viewing purpose, storage, data usage, and playback hardware.

When 24 FPS Makes Sense

Choose 24 FPS when:

• The original video is 24 FPS.
• You are watching a film or film-style production.
• The original cinematic motion cadence is important.
• The content has controlled or moderate movement.
• You want to avoid unnecessary frame-rate conversion.
• Storage or data efficiency matters and the content does not need higher temporal sampling.

If a source is naturally 24 FPS, there is usually no reason to convert it to 60 FPS simply because 60 is a larger number.

When 30 FPS Makes Sense

Choose 30 FPS when:

• The source is naturally 30 FPS.
• You are watching general-purpose online video.
• You are watching interviews, presentations, tutorials, or ordinary everyday content.
• You want a middle ground between 24 and 60 FPS.
• You do not need the extra temporal sampling of 60 FPS.

For many everyday videos, 30 FPS is a practical choice.

When 60 FPS Makes Sense

Choose 60 FPS when:

• The original source was recorded at 60 FPS.
• You are watching sports.
• You are watching gameplay.
• The video contains rapid movement.
• You are following fast camera movement.
• You are watching certain screen recordings where smooth cursor or interface movement matters.
• You specifically value smoother motion enough to justify the additional data and processing.

The advantage is strongest when there is actually enough motion for the additional frames to matter.

Best Frame Rate for Different Devices and Uses

Phone Viewing

For ordinary phone viewing, 30 FPS is often a practical default when the source is 30 FPS.

Use 60 FPS when the source is genuinely high-frame-rate and the smoother motion is useful, such as sports or gameplay.

If mobile data or battery life matters, do not assume you need the highest frame rate available.

A well-encoded 24 or 30 FPS video can be a very sensible choice for ordinary viewing.

Modern mobile operating systems can adapt display behavior to video frame rates, but the exact behavior depends on the device. Android, for example, supports frame-rate APIs that allow apps to communicate the video's intended frame rate to the platform.

Laptop and PC Viewing

A laptop or desktop usually gives you more processing headroom than an older mobile device, but that does not make 60 FPS automatically better.

For movies, preserve 24 FPS when that is the source.

For ordinary online video, 30 FPS is often sufficient.

For gaming, sports, demonstrations, and fast movement, 60 FPS can be more useful.

The display's refresh rate also matters. A 60 FPS video and a 120 Hz monitor are not equivalent settings, but a higher-refresh-rate display can provide more opportunities to present high-frame-rate content smoothly.

TV Viewing

For television viewing, preserving the source frame rate is usually a sensible starting point.

Modern TVs can support different refresh rates and may perform their own processing.

Android's media documentation illustrates why matching video timing with display refresh behavior can reduce judder in some situations.

For a film originally produced at 24 FPS, choosing 60 FPS simply because your television supports 60 Hz does not make the source a 60 FPS production.

Gaming

Gaming is a special case because FPS can describe real-time rendering rather than a fixed video file.

For recorded gameplay, 60 FPS can be useful because game movement and camera motion can change rapidly.

For a downloaded gameplay video, the important question is whether the source was actually captured at 60 FPS.

A 30 FPS recording converted to 60 FPS does not contain the same original temporal information as a native 60 FPS capture.

Sports and Action

Sports and fast action are among the clearest situations where higher frame rates can be useful.

Rapid movement gives you more opportunities to see intermediate positions of the moving subject.

That can make tracking a ball, player, vehicle, or other fast-moving object easier.

If the source is natively 60 FPS, that can make 60 FPS a worthwhile choice.

If the source was originally 30 FPS, simply converting it to 60 FPS does not recreate the missing captured moments.

Tutorials and Screen Recordings

Frame-rate choice depends on what is happening on the screen.

A talking-head tutorial may not need 60 FPS.

A software tutorial involving smooth scrolling, animation, cursor movement, drawing, or other rapid interface changes can benefit from a higher frame rate.

Apple's ScreenCaptureKit documentation, for example, allows screen capture to be configured with a minimum frame interval and gives 60 FPS as an example of a 1/60-second frame interval.

The best setting is therefore related to how quickly the screen content changes.

Limited Storage or Mobile Data

When storage or mobile data is limited, think about the entire file rather than FPS alone.

Ask:

• Is 60 FPS actually useful for this video?
• Is the source native 60 FPS?
• How much larger is the available 60 FPS file?
• What resolution is being offered?
• What codec is being used?
• What is the actual estimated or reported file size?
• How important is motion smoothness for this particular content?

If you are downloading a slow-moving interview, a 60 FPS version may provide little practical benefit.

For fast sports footage, the difference may be much more noticeable.

This is why content type should come before the FPS number.

How MediaFetches Handles Frame Rate

The current MediaFetches project does not expose a manual FPS selector in its quality interface.

The video selector is based on available source quality/resolution options such as 144p, 240p, 360p, 480p, 720p, 1080p, 1440p, and 2160p when those source heights are available.

It can also expose non-standard source heights and a “Best available” option when the source does not provide enough resolution information.

The project does not provide a user-facing choice such as:

• 24 FPS
• 30 FPS
• 60 FPS

So a MediaFetches user should not expect to force a source video to 60 FPS through the current quality selector.

Instead, the available quality options are built from the formats reported by the source. The project selects formats primarily by video height and available audio/video streams.

This distinction is important because two videos can both be 1080p while having different frame rates.

For example, a source can provide:

• 1080p24
• 1080p30
• 1080p60

while all three are still described as 1080p in terms of resolution.

The current MediaFetches interface does not expose those FPS values as separate user-selectable quality rows.

That means the practical approach is to choose the available source quality that fits your needs rather than assuming that a particular resolution automatically means a particular frame rate.

For responsible downloads, only save media you own or have permission to save.

Common Frame-Rate Questions

Is 60 FPS better than 30 FPS?

Not automatically.

60 FPS can look smoother during fast movement, but 30 FPS may be perfectly appropriate for ordinary video.

The best choice depends on the content and viewing purpose.

Is 24 FPS lower quality?

No.

Frame rate and image quality are different concepts.

A 24 FPS video can have excellent image quality.

Quality also depends on factors such as resolution, bitrate, codec, source quality, and encoding settings.

Does 60 FPS mean higher resolution?

No.

FPS and resolution measure different things.

60 FPS tells you how frequently frames are represented.

Resolution describes the spatial dimensions of those frames.

Does 60 FPS always mean a bigger file?

No fixed rule applies.

Higher FPS can increase encoded size, but the final result depends on bitrate, codec, resolution, compression, scene complexity, duration, and encoder settings. MDN specifically notes that frame rate affects output size while also emphasizing that codec and content characteristics influence the result.

Does 60 FPS require exactly twice the bitrate of 30 FPS?

No.

There is no universal 2× rule.

Encoding systems can use different bitrates for different frame rates, and actual requirements depend on the content and codec.

Apple explicitly identifies several variables that affect the bitrate required for video, including frame rate, resolution, codec, encoder implementation, content complexity, and desired quality.

Can I turn a 24 FPS video into 60 FPS?

Technically, yes.

Video-processing software can convert the output to 60 FPS using frame duplication, blending, or motion interpolation.

But converting the frame rate does not recreate the original camera frames that were never captured.

Is 120 FPS better than 60 FPS?

Not necessarily.

The same principle applies.

Higher frame rates can be valuable for specific applications, especially fast motion or specialized capture, but they also introduce additional processing and data considerations.

The right question is not “What is the highest FPS?”

It is “What frame rate does this content actually benefit from?”

Why does my 60 FPS video sometimes look worse than a 30 FPS video?

Frame rate is only one part of video quality.

The 60 FPS version may use a different bitrate, codec, compression level, resolution, source, or encoding configuration.

A lower-frame-rate video can therefore look better overall if it has better encoding or more data allocated per frame.

Does a 60 Hz screen play 60 FPS video?

It can display 60 FPS video, but 60 Hz and 60 FPS are not the same thing.

Hz describes the display's refresh behavior.

FPS describes the video's frame rate.

Playback quality depends on how the player and display handle those two timing systems.

Should I download 60 FPS whenever it is available?

Not necessarily.

Choose it when the source is genuinely high frame rate and the smoother motion is useful.

For films, ordinary interviews, slower tutorials, or limited-data situations, 24 or 30 FPS may be more sensible.

Related MediaFetches guides

For related guidance, see video bitrate guide and video resolution guide.

Final Takeaway

Frame rate is fundamentally about how frequently motion is sampled and represented over time.

24 FPS, 30 FPS, and 60 FPS each have legitimate uses:

• 24 FPS makes sense when preserving film-style or native source motion is the priority.
• 30 FPS is a practical general-purpose choice for many everyday videos.
• 60 FPS is especially useful when smooth, fast motion matters.

But the highest number is not automatically the best.

Frame rate interacts with bitrate, resolution, codec, compression, file size, download time, playback hardware, display refresh rate, and power consumption. A higher frame rate can be valuable for one video and unnecessary for another.

For downloaded media, the most important rule is simple:

Choose frame rate based on the original content, motion, viewing purpose, storage/data constraints, and playback environment—not simply because a higher FPS number looks better.