What a frame is
A video game does not show continuous motion. It shows a rapid series of still pictures, each called a frame, and your eyes and brain blend them into the impression of movement. This is the same principle behind film and animation, with one big difference: a film frame is recorded in advance, while a game frame has to be calculated on the spot, using your latest input and the current state of the game world.
Frame rate is simply how many of those pictures the game produces each second. It is usually written as frames per second, or FPS. A higher frame rate means more pictures per second and, usually, motion that looks and feels more fluid. A lower one means each picture stays on screen longer before the next arrives, so movement looks more like a flip-book.
Frame time: the same idea, seen differently
Frame rate is an average over a second. Frame time looks at each picture individually: how long it took to produce, usually measured in milliseconds. The two are linked by simple arithmetic. If a game delivers 60 frames every second, each frame gets about one sixtieth of a second, which is roughly 16.7 milliseconds. At 30 frames per second, each frame gets about 33.3 milliseconds.
This matters because an average can hide problems. A game can report a healthy-looking average while a few frames in every second take far longer than the rest. You feel those slow frames as hitches, even though the headline number looks fine.
Frame rate and refresh rate are different things
Your display has its own rhythm. Its refresh rate is how many times per second the screen redraws what it shows, measured in hertz. A display that refreshes 60 times per second can show at most 60 different pictures each second, no matter how many frames the game produces.
So there are two numbers to keep apart. Frame rate belongs to the game and the hardware running it. Refresh rate belongs to the screen. When the two do not line up well, problems can appear, such as a split picture or uneven motion. Those mismatches, and the options that manage them, are covered in the article on screen tearing. The point here is only that a fast game on a slow screen cannot show you all its frames, and a fast screen cannot invent frames the game never made.
How smoothness is perceived
People do not have a single threshold at which motion suddenly becomes smooth. Perception depends on the person, the kind of motion, the brightness and contrast of the scene, and what you are doing. Slow, steady scenes can look acceptable at modest frame rates, while fast camera turns and quick lateral movement expose low frame rates more readily.
There is also a difference between seeing smoothness and feeling it. A game that updates more often can respond to your controller or mouse sooner, which many players notice as a more direct connection to the action. That responsiveness is related to input latency, which has several other causes besides frame rate.
Because individual sensitivity varies, be wary of anyone who states that a single frame rate is universally good enough or universally necessary. Genre matters too. A slow strategy game and a fast competitive shooter ask very different things of the same hardware.
Why steady pacing matters
Consistency is often more important than the average. Imagine two games that each average the same frame rate. In the first, frames arrive at nearly equal intervals. In the second, most frames are quick but some take much longer. The first feels even; the second feels jerky. The visible effect of uneven delivery is usually called stutter.
Stutter can come from many places: the game loading new data, the processor being busy with another task, a graphics card waiting on memory, or the system slowing itself down because it is running hot. Some of these are explained in articles on thermal throttling and video memory. Keeping frames evenly spaced is a large part of what people mean when they say a game “runs well”.
For this reason, many reviewers report more than the average. They often look at how bad the slowest moments are, sometimes described as the “low” frames, or they show a frame time graph. A flat, steady line on such a graph is usually a better sign than a high but spiky one.
What limits frame rate
Producing a frame involves several parts of a computer or console working in sequence. The processor prepares the scene: game logic, physics, artificial intelligence and instructions about what to draw. The graphics card then turns those instructions into an actual image. Memory and storage supply the data both of them need.
Whichever part takes longest sets the pace for the whole chain, which is the idea of hardware bottlenecks. Raising the screen’s pixel count mostly loads the graphics card, as the discussion of screen resolution explains. Switching on advanced lighting such as ray tracing adds still more graphics work. Techniques like image upscaling try to give some of that time back. Which setting helps depends on where the limit actually is.
Frame rate caps and settings
Many games let you limit frame rate on purpose. A cap can keep delivery steady, reduce heat and noise, and avoid producing frames the screen cannot display anyway. Others offer a frame rate target that the game tries to hold by lowering detail on the fly. Console games are often built around a fixed target so that the experience is consistent, which is one reason some titles offer a choice between a mode that favors visual quality and one that favors smoother motion.
Trade-offs like these are common. Quality, speed and consistency compete for the same limited hardware time, and the right balance is partly a matter of taste.
Reading frame rate claims carefully
Frame rate figures appear everywhere in marketing and reviews, and they are easy to over-read. A few cautions help:
- A number means little without the settings, resolution and scene it was measured in.
- Averages hide stutter, so look for some measure of consistency.
- Results from one game rarely transfer neatly to another.
- Your display may be unable to show everything the game produces.
- Personal comfort differs, so a figure that satisfies one player may not satisfy another.
The most useful habit is to treat frame rate as one piece of evidence about how a game feels, alongside frame time, display behavior and the type of game you are playing. When something feels wrong, ask what kind of problem it is: slow average delivery, uneven delivery, a screen mismatch or a delay in how quickly the game reacts. Each has a different cause and a different remedy, and sorting them out is usually the quickest route to a better experience.