First Identify Where the Cap Appears
If FPS Tester stays near 60 FPS, it is reporting this browser page’s animation cadence. Browsers normally synchronize visual updates with the active display, so about 60 callbacks per second is expected on a 60 Hz path. That number does not mean the GPU can render only sixty game frames. The lightweight page is measuring scheduling, not maximum graphics throughput.
If a native game stays at 60 FPS, inspect that game and system separately. It may have an in-game limiter, V-Sync, driver cap, display-mode choice, windowed compositor behavior, laptop power rule, or application profile. FPS Tester cannot detect those settings automatically because the browser has no access to the game process.
Check the Active Refresh-Rate Setting
A monitor marketed for 120, 144, 165, or 240 Hz can still operate at 60 Hz when the operating-system mode is set that way. Open the system’s advanced display settings, choose the correct monitor, and review the selected refresh rate. Resolution, color format, port, adapter, dock, and cable can affect which modes are available.
After changing the mode, wait for the display to settle, move the browser fully onto that monitor, and run the refresh-rate test. A browser-observed estimate near the selected standard is a useful confirmation, but it is not a direct hardware read. Fractional rates such as 59.94 can be labeled close to 60.
Confirm the Browser Is on the Intended Display
Multi-monitor systems commonly mix refresh rates. If a window spans a 60 Hz and 144 Hz display, the browser and compositor must select a scheduling strategy that may not match your assumption. Drag the entire window onto the high-refresh monitor, avoid leaving even a large portion on another display, and restart the test after a moment.
Laptop screens and external monitors can also use different graphics paths. A dock, remote desktop session, screen mirroring mode, or capture software may constrain presentation. Test locally with the window on one display before diagnosing browser code or hardware. Fullscreen can simplify placement but does not create an exclusive native-game presentation mode.
Power Saving, Dynamic Refresh, and System Load
Battery saver and vendor power profiles may choose a 60 Hz display mode or limit browser work to preserve energy. Some laptops dynamically switch refresh rates depending on power, motion, or content. Plug in the device if appropriate, select the intended performance profile, and confirm the mode again. Respect thermal and battery constraints rather than forcing settings the device does not support.
Heavy CPU or GPU work can also cause a browser cadence below target, but a clean line near exactly 60 usually points first to synchronization rather than insufficient performance. Close recording software and unusually heavy tabs, update the browser, and repeat. A noisy result with long intervals deserves frame-time analysis instead of being described simply as a cap.
If a Native Game Is Capped at 60
Review the game’s display mode, resolution, refresh-rate choice, V-Sync setting, foreground and background FPS limits, menu caps, and configuration files. Then check the graphics-driver application profile for a maximum frame rate or synchronization override. Laptop control software may have per-game battery or acoustic limits. Cloud streaming and remote play can impose service or stream caps.
Change one option at a time and keep a record. Disabling every synchronization feature at once can introduce tearing without revealing which control created the cap. If the game reports a high FPS but the display still appears to update at 60 Hz, verify the actual monitor mode. If only one title is affected, use that title’s current official support documentation.
Browser Behaviors That Look Like a Cap
Foreground requestAnimationFrame() generally follows presentation cadence. Hidden or occluded documents can be throttled heavily, and privacy or battery policies may change scheduling. Some systems historically synchronized mixed-refresh windows differently. Browser extensions, accessibility features, remote environments, or virtual machines can introduce additional limits. None of these make browser FPS a GPU benchmark.
FPS Tester stops an active test when hidden so a tab switch does not become a false frame-time spike. The next start adds warm-up and begins fresh results. If results disagree across current browsers, record the browser version, window position, display mode, and power state. The difference is a useful scheduling clue, but it does not by itself identify a faulty component.
A Reliable Order of Checks
Start with operating-system refresh rate and active display. Next remove spanning or mirroring ambiguity, review power mode, and run the browser refresh estimate. For a native game, review its limiter and V-Sync, then the driver profile and vendor utilities. Check cable or dock capability only after verifying that the desired mode is actually supported at the chosen resolution.
Do not use random registry edits or third-party unlockers as a first step. A stable 60 FPS browser result on a selected 60 Hz mode is normal. A game-specific cap needs game-specific telemetry. The question “why is my FPS capped at 60?” becomes manageable once browser cadence, native render FPS, and display Hz are treated as separate measurements.