What is frame rate and why does it matter more than resolution?
Frame rate is how many complete images your system draws each second, measured in frames per second (fps). Resolution is how many pixels each of those images contains. They trade against each other, because both consume the same finite GPU budget.
Why frame rate often matters more:
It determines how responsive the game feels. At 30fps a new frame appears every 33 milliseconds; at 60fps every 16.7ms; at 120fps every 8.3ms. That interval is dead time between your input and any visible response, and it sits on top of every other source of delay. Halving it is immediately noticeable in a way that extra pixels are not.
Motion clarity depends on it. A higher frame rate means smaller changes between frames, so moving objects stay legible instead of smearing. In fast games this affects whether you can actually track a target.
Consistency matters more than the average. A stable 60fps feels far better than an average of 80 that repeatedly dips to 40. This is why 1% low figures — the worst 1% of frames — are a better quality measure than the headline number, and why stutter is more objectionable than a modestly lower cap.
Where resolution wins: static detail, text legibility, distant objects, and large screens viewed closely. On a big display, 1080p upscaled looks soft no matter how smooth it is.
The practical hierarchy most people arrive at: hit a stable frame rate matching your display's refresh rate first, then spend what is left on resolution, then on settings. Anything above your refresh rate is largely wasted unless you are chasing input latency competitively.
Console "performance" and "quality" modes are exactly this trade-off exposed as a toggle — usually 60fps at lower resolution versus 30fps at higher.