Refresh rate and frame rate are related measurements, but they describe different parts of the display pipeline. Refresh rate is how often a display can update its image; frame rate is how often a computer or application produces new frames. A 144 Hz monitor does not guarantee 144 frames per second, and a browser FPS reading is not a calibration certificate for the monitor.
What the two numbers mean
Refresh rate is measured in hertz (Hz), meaning cycles per second. A display set to 60 Hz can refresh about 60 times per second; at 144 Hz, it can refresh about 144 times per second. The actual mode depends on the monitor, cable, graphics hardware, operating system settings, and display configuration.
Frame rate, usually written as frames per second (FPS), describes how many frames an application renders or presents over time. A game, animation, or browser page may render fewer frames than the display can refresh. If the app produces 60 new frames each second on a 144 Hz display, some refresh cycles may show a repeated frame. Technologies such as variable refresh rate can alter how display updates are coordinated, subject to compatible hardware and settings.
The values can differ in both directions. A browser may render more frames than a 60 Hz display can show as distinct refreshes; a high-refresh display may be set to a lower operating mode. Neither number alone describes input latency, pixel response time, frame pacing, or visual quality.
What a browser test can and cannot show
A browser frame-rate test estimates how frequently the page receives rendering opportunities or callbacks while its animation is running. The browser may throttle work in background tabs, under power-saving modes, or when the page is not visible. CPU and GPU load, browser scheduling, extensions, thermal limits, and other applications can affect the reading.
A refresh-rate test may infer display timing from changes or animation behavior, but it does not have direct access to every panel’s internal electronics. The result can be affected by browser APIs, compositing, variable refresh behavior, synchronization settings, and the test’s method. Treat the number as a useful comparison under stated conditions, not an authoritative hardware measurement.
Toolsnix provides a Refresh Rate Test and an FPS Tester. Run them separately and read each tool’s notes. If the browser test reports an unexpected result, compare it with the operating system’s display settings and the monitor’s on-screen menu.
Make a repeatable comparison
Before measuring, close unnecessary high-load apps, connect the display directly as intended, and set the operating system to the refresh mode you want to inspect. On a laptop, connect power if battery-saving mode changes performance. Use the same browser, window size, and test conditions for repeated runs.
A practical sequence:
- Confirm the display is set to its intended resolution and refresh mode in system settings.
- Check that the correct monitor is selected if multiple displays are connected.
- Run the browser refresh test in a visible, foreground tab.
- Run the FPS test separately; avoid interpreting its result as the panel’s refresh rate.
- Repeat the measurement after a short pause and note whether the estimate is stable.
- Compare with the monitor’s documentation or on-screen information, recognizing that these report configuration or capability rather than necessarily the browser’s rendered performance.
If you see a value close to half or a common divisor of the expected refresh rate, consider sync settings, frame caps, browser throttling, or load. Do not assume a specific cause without checking those settings.
Frame pacing matters too
Two applications can both average 60 FPS while feeling different. One may deliver frames at fairly even intervals; another may alternate between quick and slow frames. The average hides these pauses. A single FPS number is a summary, not a full description of smoothness.
For a game, inspect its own frame-time graph or performance overlay where available. For a browser animation, check whether the page is doing expensive layout or scripting work. For video playback, the source frame rate and playback cadence are different again. Compare like with like: an animation test cannot diagnose every application’s rendering pipeline.
Common reasons for unexpected numbers
- The display is configured below its maximum. The monitor may support a mode that the operating system has not selected.
- The wrong monitor is being measured. A browser window may be on a secondary display with a different refresh mode.
- The tab is hidden or unfocused. Browsers reduce background work to save power.
- The page is under load. Other tabs, video, or CPU/GPU-heavy tasks can reduce rendering opportunities.
- A sync or frame cap is active. Software may intentionally limit frame production.
- Variable refresh is enabled. The display’s timing may adapt to presented frames, complicating simplistic estimates.
- The browser’s test method has limitations. Web APIs do not reveal every physical display behavior.
Read results in context
A test result should include the setup that produced it. Note the display model if known, selected resolution and refresh mode, operating system, browser, window placement, power state, and whether another monitor is connected. This context matters when a later run differs; without it, “the test used to show 144” is difficult to interpret.
If the test is running in a window, the browser window may have moved between displays with different refresh rates. Some operating systems expose per-display settings and may apply a mode only after you confirm it. Check the active display menu rather than relying on a sticker or product page listing the maximum supported refresh.
A simple arithmetic example can clarify the distinction: if an app produces 60 new frames per second while a display refreshes at 120 Hz, the display has more refresh opportunities than the app provides new frames. If the app produces 240 frames per second on a 60 Hz display, the display still cannot show 240 distinct full refreshes each second. The actual presentation and latency depend on synchronization and pipeline behavior.
Compare like-for-like measurements
Use the refresh test to investigate the display mode, and the FPS test to investigate rendering opportunities. Do not compare the refresh test’s number directly with an in-game frame counter without checking what each one reports. A game overlay may show average FPS, a browser test may count animation callbacks, and a monitor menu may show its configured input mode.
If your goal is smoothness, inspect frame-time consistency and visible behavior in the application that matters. If your goal is the monitor’s maximum capability, consult its documentation and confirm the operating system and cable support the required mode. If your goal is low latency, investigate the whole chain, not just refresh or frame rate.
Account for environmental variation
Test with the browser tab visible and wait for the page to settle. Background tabs can be throttled; browser extensions and open video streams can add work. On a laptop, power-saving mode can affect CPU/GPU behavior. A test result from a battery-constrained session may not match a plugged-in session.
Do not run multiple measuring pages simultaneously. They compete for the same rendering and scheduling resources and can alter one another’s result. Close the test fully before comparing a second tool, and repeat the run if a sudden system task interrupted it.
Diagnose a discrepancy without guessing
Suppose a monitor is advertised for a high refresh mode, but a browser test shows a lower number. Check the operating system’s advanced display settings first. Confirm the active display, resolution, and selected refresh mode. Some combinations of resolution and refresh rate require a particular cable, port, or graphics configuration; the monitor’s manual and graphics hardware documentation are better evidence than a browser number.
If the operating system already shows the expected mode, close background work and repeat the browser measurement. Move the browser window to the display being checked. Use a direct connection where practical and compare with the monitor’s on-screen display. If only one browser reports a different value, compare a second supported browser and note any extensions or power settings.
For low FPS, investigate the application separately. A browser animation test does not reproduce a game scene. Inspect the game’s resolution, graphics settings, frame cap, synchronization, and performance overlay. Change one setting at a time, because changing resolution, quality, and sync together makes the cause difficult to isolate.
Choose the right measurement for the question
| Question | Better evidence | |---|---| | What mode is currently configured? | Operating system display settings and monitor on-screen display | | How many frames does this game render? | The game’s performance tools under the same scene and settings | | Does the browser page animate smoothly? | Browser frame and performance tools during that page’s workload | | Is the display capable of a listed mode? | Manufacturer documentation and a compatible system configuration | | Does the setup feel responsive? | A repeatable end-to-end test in the target application |
No one measurement answers all five questions. A manufacturer’s maximum mode describes capability under specified conditions; a browser estimate describes observed behavior during a particular run. Keep those evidence types separate in your troubleshooting notes.
Record findings so the next run is meaningful
A useful comparison note might say: “Windows reports the external display at 120 Hz, browser refresh test varied between two nearby estimates in a visible tab, while the FPS test reported 60 during this page animation. Repeated after closing video playback.” This wording separates configuration from observation and avoids claiming that one number disproves another.
If the monitor menu, operating system, and browser disagree, resolve the basic configuration first. Confirm the cable and port capabilities from documentation and test at the intended resolution. A benchmark result is easier to interpret once the system’s selected mode is known.
FAQs
Is 120 Hz the same as 120 FPS?
No. 120 Hz describes a display refresh mode; 120 FPS describes an application’s rendered frame rate. They can match, but they are measured at different parts of the system.
Can a 60 Hz monitor show 120 FPS?
An application can render at a higher rate, but the display cannot show 120 distinct full refreshes each second in a 60 Hz mode. Higher rendering rates can still affect latency depending on the pipeline, but the result depends on the system.
Why does a browser test show less than my monitor’s rated Hz?
The display may be configured to a lower mode, the page may be throttled or under load, or the test may not measure the panel directly. Verify system settings and repeat under consistent conditions.
Does a high refresh rate reduce input lag?
It can reduce the time between refresh opportunities, but total input-to-photon latency also includes input sampling, application work, rendering, synchronization, pixel response, and display processing. The refresh number alone does not give the complete latency.
Next step
Confirm the display mode in your operating system, then measure refresh behavior and application frame rate separately. If the readings disagree, compare settings and repeat the test before concluding that the monitor is faulty.