FPS Calculator and Checker: Test How Many FPS You'll Get

An FPS calculator estimates how many frames per second a PC will hit in a game, worked out before you spend money on the game or the parts. You give it your graphics card, processor, resolution and settings, and it hands back a number. A 'Can I run it' checker only says yes or no. This tells you roughly how well it runs.

It starts from real measured frame rates for that game on known graphics cards, pulled from benchmark tests, and saves them as a per-game constant. Pick your card and it scales that constant to match, then adjusts for resolution, the settings preset, ray tracing, upscaling and memory. It also works out the frame rate your processor can hold, and reports the lower of the two. So a fast card can still show a modest number in a game that leans on the CPU.

Frames per second is how many complete images your PC draws each second, so 60 fps means 60 finished frames. Whichever part finishes its work slowest sets the pace: the graphics card rendering the picture, or the processor preparing each frame. Resolution, in-game settings, ray tracing and memory all move that balance. This tool weighs each of those rather than reading a single score.

Frame time is 1000 divided by the frame rate. So 60 fps works out to about 16.7 milliseconds a frame, 144 fps to about 6.9 ms, and 30 fps to 33.3 ms. A lower frame time means the game reacts sooner. It is also how smoothness gets judged, since an uneven run of frame times feels like stutter even when the average fps reads fine.

They work as a guide, not a guarantee. A good one puts you in the right ballpark for a given card, game and setting, which is enough to compare parts and set expectations. It cannot match a benchmark on your exact system, because your driver, the scene, background apps, heat and memory speed all nudge the number. Reviews of the same card from different outlets already differ by 10 to 15 percent, so this tool shows a range instead of one false-precise figure.

Plenty moves frame rate that no calculator can see. Your driver version, the exact spot you are standing in, background apps, a hot CPU or GPU throttling itself, your memory speed, the settings you tweaked by hand. Busy scenes full of characters and effects run slower than the calm ones benchmarks often use. The estimate is an average across normal play, so real numbers swing above and below it.

Most games hide a frame-rate counter in their video or gameplay settings. Steam has its own counter you switch on in Settings, and the NVIDIA app and AMD Adrenalin both add an overlay you toggle with a shortcut. Windows carries one too, in the Game Bar under Win plus G. For the full picture, including 1 percent lows, MSI Afterburner with RivaTuner puts frame rate next to CPU and GPU load, which is how you confirm which part is the limit.

On Steam, open Settings, go to In Game, and drop the in-game FPS counter into a corner. On a GeForce card, open the NVIDIA app, turn on the Statistics overlay, and toggle it in game with Alt plus R. On a Radeon card, open Adrenalin, enable the Metrics overlay, and toggle it in game with Ctrl plus Shift plus O. On Windows, press Win plus G, open the Game Bar, and pin the Performance widget. Any one of them puts a live number on screen.

The live test higher up this page counts how many frames per second your browser and monitor push right now. On most setups that equals your screen's refresh rate, so 60, 120 or 144Hz. It is not your in-game FPS, which the calculator estimates, because the browser is held to your display's refresh. Use it to confirm what your monitor is actually running.

That depends on the game and the settings. Turn the resolution and detail up and the graphics card sets the ceiling, so a stronger card means more frames. In competitive shooters on low settings, or in strategy and simulation games with a lot happening, the processor caps you first and a faster card barely helps. The calculator names which one is holding you back so you know where to spend.

A bottleneck is whichever part runs out of headroom first, capping your frame rate while the other coasts. Graphics card pinned at full load, CPU with room to spare? That is a GPU bottleneck, and it is the healthy one for gaming. CPU maxed while the card sits half idle is a CPU bottleneck, and a better card would not add frames. Our bottleneck calculator lays out the balance between any two parts.

60 fps is the target most people aim for. It feels smooth and responsive on any standard monitor. Under 30 the game turns choppy. In fast shooters, 120 to 144 fps on a matching high-refresh screen is a real step up, and competitive players go for 240 or more. There is no single right answer, since it rides on your monitor and the kind of game you play.

Yes. 60 fps is the comfortable standard for most games and matches the 60Hz screens most people already have. It looks smooth and responds fast enough for anything short of serious competitive play. A 120Hz or 144Hz monitor will show you the benefit of going higher, but 60 is a solid goal to build around.

Only if your monitor can show it. A 144Hz or 240Hz panel displays more of those frames, so motion looks clearer and aiming feels more direct in fast games. On a 60Hz screen the extra frames mostly go to waste, apart from a small cut in input lag. Shooters and racing gain the most from high frame rates. Slower games are fine at 60.

Higher frame rate does trim input lag, because each new frame carries your latest mouse and key movement, so the game feels more immediate. In fast shooters that is a genuine edge. It does not speed your character up or change the game's pace, and it has nothing to do with ping, which is the delay out to the server. More frames feel snappier without making you quicker in the world.

Not in any harmful way. Past your monitor's refresh rate the extra frames never get shown, so they mainly burn power and heat and can cause screen tearing unless you use VSync or a frame limiter. Running far above your refresh also keeps the card at full tilt for little you can see. Capping a touch above your refresh rate, or turning on a sync setting, is usually smoother.

No. Frame rate is how fast your PC draws the game. Ping is the round-trip time between your PC and the game server. One will not touch the other: a high frame rate cannot lower your ping, and a low ping cannot raise your frames. A game feels laggy from either a low frame rate or a high ping, which is why the two get mixed up, but they come from different places.

There is no hard ceiling, and the old line about the eye stopping at 30 or 60 is a myth. People pick out 60 against 120 easily, and plenty can feel 144 against 240 in fast motion, mostly through smoother movement and lower input lag than by counting frames. The gains shrink as the numbers climb, but more frames keep paying off in fast games well past 60.

Match your monitor first, so 144 fps on a 144Hz screen. Committed players in Counter-Strike, Valorant or Fortnite chase 240 and up on 240Hz and 360Hz panels, where the lower input lag makes fast flicks feel sharper. These games go easy on the graphics card, so your processor is usually what sets the number.

Competitive shooters like Counter-Strike 2, Valorant and Fortnite lean on the processor, and so do strategy games, city builders and big simulations. Heavy single-player games with demanding graphics, Cyberpunk 2077 or Black Myth Wukong for instance, lean on the graphics card at normal settings. Push the resolution up and almost any game tips toward being GPU-bound.

That comes down to your parts, so drop them into the calculator above and choose the game. Roughly, Valorant, CS2 and Fortnite run fast on modern mid-range hardware and usually bump into the processor's limit first. Heavy single-player games like Cyberpunk 2077 lean on the graphics card and land lower. The picker covers each of these games on its own, anchored to real benchmarks.

Usually the card is not the culprit. A weak or old processor caps the frame rate in CPU-heavy games however strong the card is. The other usual suspects are running out of video memory on high textures, a stale driver, a background app chewing up the CPU, heat throttling, or a power plan that stops the card boosting. Check whether the calculator flags you as CPU-limited before you blame the GPU.

A lot. It is one of the biggest levers you have. Going from 1080p to 1440p asks the card to draw about 78 percent more pixels, and 4K is roughly four times 1080p, so frame rates drop to match. When the card is the limit, lowering resolution is the quickest way to buy frames. When the processor is the limit, it does far less.

Up to a point. Too little memory makes the game swap data constantly, which wrecks frame rate and causes stutter, so 16GB is the floor for modern gaming and 8GB now drags some games down. Jumping from 16GB to 32GB rarely lifts the average by itself; it mainly helps heavy multitasking and smooths the odd dip. The calculator docks you below 16GB and adds nothing above it, which is how memory actually behaves.

It can, mostly when the processor is the limit. Faster memory feeds the CPU quicker, so in CPU-bound games a step up from slow to fast RAM, or DDR4 to DDR5 on a modern board, can add a few percent across a lot of frames and lift the 1 percent lows. In GPU-bound games it barely shows. It is real enough that blunt calculators which ignore memory tend to run optimistic in CPU-heavy titles.

No, storage does not change your average frame rate. An SSD loads levels and textures faster, which cuts loading screens and the pop-in and hitching you get when a game streams off a slow hard drive, but the frames while you play come from the CPU and GPU. Some newer games do need an SSD to run properly, so it is worth having for that, not for a bigger number.

The gap is small in most games, often within a few percent either way. Windows 11 brings gaming extras like Auto HDR and DirectStorage, and a handful of games run slightly better, but the operating system on its own will not hand you a real frame-rate jump. A current graphics driver and an updated game matter far more than which Windows you run.

Ray tracing is expensive. Switching it on usually costs 40 to 60 percent of your frame rate depending on the game and how hard it leans on the effect, and path tracing costs much more again. That is what the ray tracing toggle is for: flip it on to see the lower number, then pair it with DLSS or FSR, which is how most people win the frames back. Older cards without ray tracing hardware take a far bigger hit.

Yes. DLSS, FSR and XeSS render the game at a lower internal resolution and rebuild it up to your screen, which usually adds 30 to 50 percent more frames on the Quality setting for a small hit to sharpness. The catch is that they only ease the graphics card side. If the processor is already your limit, upscaling does little, and the calculator will tell you when that is the case.

Frame generation slots extra frames between the real ones, drawn by the graphics card rather than rendered by the game, to lift the on-screen number and smooth out motion. It can roughly double the figure you see, but those inserted frames do not react to your input, so the game does not feel more responsive the way real frames do, and it needs a decent base frame rate to look right. Treat it as smoother-looking motion, not extra performance. This calculator estimates real rendered frames, not inserted ones.

The average hides the dips. The 1 percent low is roughly your frame rate in the worst moments, the stutters and the busy scenes, and it is what you actually feel as smoothness. A game can average 90 fps and still feel rough if its 1 percent lows fall to 40. We show an approximate 1 percent low beside the average, and it sinks further when the processor is the limit, which is when the deepest dips turn up.

For 1080p high settings at a steady 60 in most current games, a card around an RTX 4060, RTX 3060 or RX 6600 is the entry point, paired with a modern six-core CPU. For 1440p at 60, aim for something like an RTX 4070 or RX 7700 XT. For 4K at 60 you are into high-end cards like an RTX 4080 or better, often with upscaling on. Feed your exact card and game into the calculator to see where you actually land.

Upgrade whichever the calculator flags as your limit in the games you play. If it says GPU-limited, a new graphics card is what adds frames. If it says CPU-limited, the processor is the fix and a new card would mostly sit idle. For the bigger picture on how a pairing balances, run both parts through our bottleneck calculator.

Yes, within reason. The GTX 1060 6GB still plays most current games at 1080p on low to medium, often in the 30 to 50 fps range, and it handles older and lighter titles comfortably. It struggles with the newest heavy releases, which want features it lacks and more video memory than it has. Enter it in the calculator with your game for a realistic number.

Average FPS is the mean across a session, and it is the headline figure most tools quote. Stable, or 1 percent low, is how the game holds up in its worst moments, and that is what decides whether it feels smooth or stuttery. A high average with weak lows feels worse than a slightly lower average that stays steady. We show both, because the peak on its own tells you nothing about how the game feels.

Yes, free to use, no sign-up, no download. Pick your parts and game and it returns an estimate in the browser, and the refresh-rate test runs right on the page. It exists to give you honest numbers and point at what limits your frame rate, not to sell you anything.