To confirm that your monitor is running at 240Hz, select the correct display in Windows Advanced display settings and check its active refresh rate. Then cross-check the monitor’s signal information, where available, and verify that your game has not selected a different display mode.
A smooth cursor or a 240 FPS counter is not enough on its own. I would verify the operating-system mode first, the incoming monitor signal second, and actual game performance third. Those checks answer three different questions.
Start with what your monitor actually supports
Read the exact model’s specification and supported timing table. A product name containing “240” is not a replacement for documentation, and some displays reach their highest rate only at a particular resolution or through selected inputs.
Check your source device as well. A laptop’s USB-C connector might support display output, but its available mode depends on the port implementation and any dock in the path. A desktop’s motherboard display connector is not interchangeable with every dedicated graphics-card output.
My preferred baseline is a direct connection, the intended native resolution, and the manufacturer-supported high-refresh mode. Keep that baseline stable while testing. If you begin with several adapters and a non-native resolution, a missing option becomes harder to explain.
Select 240Hz in Windows
Open Settings, System, Display, then Advanced display. Choose your gaming monitor from the display selector. Review the display information and the available refresh-rate options, then select 240Hz when it is supported at your intended resolution.
If the option changes the resolution, check what has happened before accepting the result. The goal is the correct combination, not simply finding the largest number in a dropdown. After applying, confirm that the display remains stable and readable.
A fractional value close to 240Hz may be normal timing reporting rather than a fault. Do not confuse a small decimal difference with being stuck at 120Hz. I would focus on the supported mode and stable operation rather than trying to force an exact rounded number through custom settings.
| Check | What it proves | What it does not prove |
|---|---|---|
| Windows Advanced display | Selected display mode | Game renders 240 FPS |
| Monitor signal information | Recognized input timing | Every pixel changes instantly |
| Game FPS counter | Reported frame production or presentation | Monitor is configured for 240Hz |
| Motion test | Useful visual comparison | Precise end-to-end latency |
Use the monitor menu as a cross-check
Many gaming monitors provide an information screen that identifies the current input, resolution, and signal frequency. Open the manual if you cannot find it; menu names differ between models.
Some on-screen counters show the current variable-refresh cadence rather than a fixed maximum input mode. That number may change as the frame rate changes. Read the explanation for your model before treating a fluctuating counter as proof that Windows has ignored your setting.
A useful verification record is simple: Windows reports the intended mode, the monitor recognizes the expected input signal, and the picture remains stable. If the two disagree, check whether you selected the wrong screen, whether a game changed modes, or whether the overlay is displaying a different kind of measurement.
Check the game without confusing FPS and Hz
Refresh rate is the display’s update cadence. FPS is the rate at which the game produces frames. A display can be configured for 240Hz while a game renders at 90, 120, or another rate.
Open the game’s video settings and inspect the selected monitor, display mode, resolution, and any refresh-rate option. Some games expose separate fullscreen settings; others follow the desktop more closely. A retained configuration from an older monitor can be worth correcting.
Check frame caps and synchronization after confirming the display mode. A cap can be intentional for steadier delivery, lower power use, or a preferred variable-refresh setup. Do not remove every limiter just to make a counter larger. Decide whether your goal is correct 240Hz configuration, high rendered FPS, or a particular synchronization behavior.
Microsoft’s Advanced display settings provide the authoritative Windows path for checking and changing refresh rate.
Interpret variable refresh and dynamic refresh correctly
Variable refresh rate allows compatible hardware to coordinate display updates with frame delivery within a supported range. Its operation can make a monitor’s live refresh counter change during play without changing the display’s advertised maximum capability.
Dynamic Refresh Rate in Windows is a separate supported feature that can switch behavior according to activity. If a game appears restricted while that feature is enabled, investigate it as a controlled test rather than assuming that every refresh-related feature is the same thing.
I would write down the setting before changing it and compare the same game afterward. The purpose is to explain the observed limit. Turning off useful features permanently without confirming the cause can trade one problem for tearing, unnecessary power use, or less consistent presentation.
Use motion tests as supporting evidence
A motion test or browser animation can help reveal an obvious difference between 60Hz and a higher rate, but it is not a complete measurement of the display pipeline. Browser scheduling, animation frame rate, compositor behavior, and system load can influence what you see.
For a practical check, close heavy background tasks and compare a known motion pattern at two supported display rates. Keep browser zoom and window placement consistent. Treat the result as a visual aid alongside Windows and monitor information.
A phone recording can introduce shutter and rolling-scan artifacts, so avoid using a casual video as a precise latency measurement. Likewise, frame generation can increase presented-frame counts without making game simulation and input sampling behave like the same native render rate. Specify what any counter represents before using it as evidence.
Understand what a settings screenshot proves
A screenshot showing 240Hz is useful evidence of the selected mode at that moment. It does not prove that every game uses the same mode, that frame delivery is stable, or that the monitor’s pixel transitions are exceptionally fast.
Keep the screenshot with a note of the selected display and connection if you are diagnosing a recurring issue. When the problem returns, compare like with like. A screenshot from a different port or display arrangement can look contradictory while describing a different setup.
I would use this evidence to establish configuration, not to advertise a measured performance result. If you are recording a tutorial, show the display selector as well as the refresh field so viewers can see which screen is being changed. That small detail prevents a common mistake in multi-monitor systems: changing the laptop panel while leaving the gaming display untouched.
Test your normal multi-monitor arrangement
After confirming 240Hz with a simple connection, restore the other displays you actually use. Check the mode again in the final arrangement. A test with one monitor is a diagnostic baseline, but your daily setup may include another screen, a capture device, or a dock.
Use extended display mode if that suits your workflow and check each screen independently. If duplication is required for a particular task, inspect what modes remain available in that arrangement rather than assuming the earlier single-screen result still applies.
I would test the workflow that matters: game on the main monitor, recording or browser tools on the second, and the same resolution settings you intend to keep. If a restriction appears only then, you have isolated a configuration condition. That is more useful than repeatedly applying 240Hz in a simplified setup and wondering why the problem returns.
Keep a stable configuration instead of chasing counters
Once the display is correctly configured, decide which performance information you genuinely need. A permanent collection of overlays can distract from normal play and make harmless fluctuations look like faults. Keep a frame counter when diagnosing, then remove it if it no longer helps.
Record the cable and port that work, especially when several inputs look similar. If you switch between a work laptop and a gaming PC, expect their supported modes to differ. The monitor does not need to show the same rate for every source to be operating correctly.
My recommendation is to recheck after a relevant change or an observed problem, not before every session. A stable picture, the correct documented mode, and satisfactory game behavior are the practical goals. The number is a configuration tool rather than an activity you need to monitor continuously.
Recheck after changes that can reset the mode
A new graphics driver, different cable, changed input, new dock, or switched display arrangement can alter the available mode. If motion suddenly feels different, repeat the basic checks before changing game settings extensively.
Sleep and wake behavior are also worth testing on a new setup. Confirm that the monitor returns to the intended configuration and that the correct display remains selected when several screens are attached.
My final check is a normal gaming session, not just a settings screenshot. The display should remain stable, the game should use the expected mode, and the system should deliver an acceptable frame rate. Once those conditions hold, keep the working configuration and enjoy it instead of repeatedly chasing the same dropdown number.
For a shared computer, keep a brief note of which display is the gaming monitor and which input it uses. Another person switching ports or reconnecting a work dock can change the setup without changing the hardware. That note turns a future recheck into a short, predictable process instead of another round of trial and error across every graphics setting.
Common questions
Is 239.96Hz a problem?
A nearby fractional timing can be normal. Check the documented mode and stable operation rather than forcing a rounded label.
Why does my monitor counter move below 240?
It may be showing variable refresh activity. Check your model’s explanation and compare it with the active display mode.
Can a 240 FPS game run on a 120Hz display?
A game can render faster than the display updates. That does not turn a 120Hz display mode into 240Hz.