A frame-rate handoff should leave a new user with a repeatable baseline, not a mysterious collection of toggles. The goal is to document what the computer, display, operating system, and game are actually doing together, then show which setting to change when smoothness, responsiveness, heat, or image quality needs adjustment.

Separate the two numbers first

Frames per second, or FPS, describes how often a game renders a new frame. Refresh rate, measured in hertz, describes how often the display can update. They interact, but they are not the same setting. A game reporting 120 FPS does not prove that the monitor is refreshing at 120 Hz, and selecting a high refresh rate does not guarantee that the game can render at that rate.

Start the handoff by recording both values separately. Note the display model and connection, the Windows display resolution and refresh rate, the game's display mode and frame-rate limit, and whether variable refresh rate is enabled. Also record the exact game scene or benchmark used for comparison. Without a repeatable scene, two performance readings may describe different workloads.

Microsoft defines refresh rate as the number of times per second an image refreshes on screen. In Windows, the available choices depend on what the display supports, and some refresh-rate selections can change the display resolution. The current mode and variable-refresh-rate information appear under Advanced display. Those details make Microsoft's refresh-rate instructions a useful source to keep with the handoff.

Establish a conservative baseline

Set the monitor to a supported native resolution and a refresh rate that remains available without forcing an unintended resolution change. In the game, begin with its default or recommended graphics preset. Turn on its built-in frame-rate counter if one is available, choose a repeatable scene, and observe performance for several minutes. Record a range or a representative result instead of preserving only the highest number seen.

If frame delivery is unstable, adjust one category at a time. Resolution scale, shadows, reflections, and effects can affect performance differently, so changing everything at once hides the cause. Keep notes that say what changed, where it was changed, and whether a restart was required. A new user should be able to reverse each experiment.

Variable refresh rate can help a compatible display adapt its refresh timing to the content. Microsoft also documents a Windows 11 feature called Optimizations for windowed games, which can reduce frame latency and enable variable refresh rate for supported DirectX 10 and 11 games running in windowed or borderless-windowed modes. The feature is app-selectable, so record whether it is on globally or overridden for a particular game. See Microsoft's windowed-game optimization guide before changing it.

Match the setup to the user's priorities

Ask what the new user values. A competitive player may prefer a lower graphics preset that holds a steadier rate. Someone playing a slower single-player title may prefer richer visuals with a lower limit. A laptop user may choose a cap that reduces unnecessary load when running on battery. These are preferences, not universal rankings. Preserve one known-good profile before creating alternatives.

Name profiles by their purpose, such as `Native 60 - quality`, `Native 120 - balanced`, or `Battery - capped`, rather than by vague labels like `best`. For every profile, record resolution, refresh rate, frame-rate cap, display mode, variable-refresh setting, main graphics preset, and the game version tested. If the user is sensitive to motion or flicker, let that person assess the result directly and make changes in small steps.

Run a handoff test

Have the incoming user do the following without prompting:

  1. Open Windows Advanced display and read back the active resolution and refresh rate.
  2. Open the game's display menu and identify the display mode and frame-rate limit.
  3. Load the named test scene and observe the frame-rate behavior.
  4. Switch to one documented alternate profile and explain the tradeoff.
  5. Restore the known-good baseline.

Finish with a short troubleshooting map. If the expected refresh option is missing, recheck the selected display, cable path, resolution, and documented display capabilities. If the game's FPS falls, return to the repeatable scene and reverse only the most recent change. If a Windows or driver update changes behavior, record the version and rerun the baseline instead of silently redefining success.

A good frame-rate handoff does not promise the largest possible number. It gives the new user a verified starting point, the vocabulary to distinguish rendering from display refresh, and a safe method for making one reversible change at a time.

Sources

  1. Change the refresh rate on your monitor in Windows — Microsoft Support
  2. Optimizations for windowed games in Windows 11 — Microsoft Support

Related reading