Refresh rate describes how often a display updates its image over time. An application's frame rate describes how often it produces new frames; the two measurements are related but are not interchangeable.
How the pieces connect
The display link transmits images according to its timing arrangement. Applications and the operating system schedule when new content becomes available for presentation. Fixed and variable-refresh paths handle that coordination differently. Even with a fast display, a workload that produces fewer new frames cannot supply a unique completed image for every possible refresh.
An everyday example
A desktop may use a high refresh setting while a video contains a lower number of frames per second. Some refreshes then present repeated or otherwise scheduled content. Conversely, an application can generate frames faster than the display's selected timing. Presentation policy determines which frames are shown and how the mismatch is managed.
Reading the information in context
Refresh rate alone does not describe pixel response, input delay, or image quality. The available choices also depend on resolution and the complete connection path. The corresponding guide explains where Windows presents this information when relevant. This reference does not recommend custom timing overrides or promise that choosing the largest number will improve every application.
Display & Graphics
Note these before you change anything
Useful facts to have to hand while reading about refresh rate and frame delivery.
- Current driver version and date from the adapter's Driver tab
- Resolution, refresh rate and scaling for each monitor
- Which port and cable each display uses
- Any per-application graphics settings you changed
Display & Graphics: Drawing a frame (output)
- Applicationrequests drawing
- Graphics APIfor example DirectX or Vulkan
- Display driveruser and kernel parts
- GPUrenders the frame
- Monitorover the display cable
