Run a live frame rate test, watch a 10-second FPS graph, and compare 30, 60, 120, 144, and 240 FPS motion in the same browser window.
Uses requestAnimationFrame in your browser. No install required.
This page measures browser-rendered FPS and estimates display cadence. It does not read your monitor hardware directly.
Measure browser-rendered FPS, compare motion against controlled presets, and understand whether your current session looks smooth, capped, or inconsistent.
Keyboard: Tab moves through every control in order, and Enter or Space activates the selected button.
No samples yet. Start the test to fill the rolling ten-second graph.
Use this plain-language snapshot if the graph is hard to read or you are navigating with assistive technology.
The graph reads left to right across the latest ten seconds. A flatter line means steadier pacing, while sharp dips or wide swings point to visible drops or inconsistent frame timing.
Start the test to measure browser-rendered FPS, estimate the observed cadence, and compare it with the reference presets.
Current preset: 60 FPS.
Reference animation is for visual comparison and can still be limited by your browser, device, and display.
Browser FPS tells you how often this page is actually producing frames. Estimated refresh rate is a best-fit cadence from recent frame timings, which is useful context but still not a direct hardware readout.
Estimated refresh rate is derived from recent browser timing only, so ambiguous readings stay labeled as low confidence instead of pretending to detect hardware directly.
This frame rate test measures how often your browser is rendering visible frames right now. It uses requestAnimationFrame timing, which makes it a practical browser FPS test rather than a claim about your monitor specification. That distinction matters. A browser can show lower or less stable FPS than your screen is capable of if the tab is throttled, the system is in battery saver mode, another app is competing for resources, or the browser itself is capped. The live readout, frame time, and rolling graph work together so you can see both the current number and the recent pattern. That makes this page useful as an FPS checker, frame rate checker, dropped frames test, and quick browser rendering test in one place. If you want a simple answer, watch the average FPS and stability label. If you want more detail, use the graph to see whether the motion performance stays flat, dips in bursts, or rides a clear cap such as 60 FPS or 120 FPS.
Frame rate and refresh rate are related, but they are not the same measurement. Frame rate describes how many frames the browser is actually producing each second. Refresh rate describes how often the display can refresh the image each second. That is why a 144 Hz monitor can still show a lower browser FPS if the page, browser, GPU path, or power mode is limited. This frame rate test estimates display cadence from recent timing, but it stays honest about uncertainty because the browser cannot directly read the monitor hardware tier with perfect authority. Think of FPS as the output you are getting in the current browser session, and refresh rate as the ceiling the display path might support. When people search for refresh rate vs fps, fps vs hz, or monitor fps test, they are usually trying to answer one practical question: is my motion smooth because the display is fast, because the browser is keeping up, or because both are aligned? This page answers that by pairing the live FPS test with an estimated cadence label and plain-language interpretation.
The graph shows the latest ten seconds of measured browser FPS. A flatter line usually means steadier frame pacing. Small wiggles are normal, especially on busy pages or laptops shifting power states. What matters more is the pattern. If the line sits close to one tier, such as 60 FPS, 120 FPS, or 144 FPS, you are likely looking at a stable cap. If the line falls sharply and recovers, that points to brief dropped frames or short rendering stalls. If it swings widely across the whole window, the session is unstable enough that smoothness may look inconsistent even when the headline number seems acceptable. Use the minimum FPS and average frame time to sanity-check what your eyes are telling you. A clean browser FPS test is not only about the highest number. It is also about frame consistency, judder control, and whether the experience feels predictable. That is why this page works as a frame pacing test, frame consistency test, and FPS graph viewer rather than only a live counter.
A capped result does not automatically mean something is broken. Many browsers, operating systems, and devices intentionally hold animation near a common tier. The most familiar cap is 60 FPS, but 90 FPS, 120 FPS, and 144 FPS are also common depending on device class and display path. Battery saver mode, mirrored displays, external docks, power plans, thermal limits, and browser background behavior can all lower the observed number. Some users run this page expecting a high refresh rate test and are surprised when the frame rate test settles lower than the monitor specification. In practice, that often means the browser is not getting the same conditions as a game engine or native app. This tool is still useful because it shows what your browser session is actually doing today. If the graph repeatedly hugs a tier with little variance, treat that as a real cap in the current environment. Then compare it with the refresh rate test to see whether the browser-measured cadence and the live FPS line tell the same story.
The comparison presets exist to make frame pacing easier to see with your eyes. At 30 FPS, motion often looks noticeably choppy, especially in fast horizontal travel. At 60 FPS, many users feel the experience is acceptable, but panning and motion still look less fluid than on higher tiers. At 120 FPS and 144 FPS, the jump is obvious on capable displays because the moving object advances in smaller steps and the path feels cleaner. At 240 FPS, the benefit becomes more dependent on the browser, panel, and how sensitive you are to motion clarity. The preset viewer does not claim to bypass your actual browser or screen limits. It is a controlled reference, not proof that you are truly seeing every one of those frames. Use it as a visual smoothness test, UFO FPS test, and motion performance test that sits next to the measured browser FPS. When the live number and the reference preset feel aligned, interpretation becomes much easier.
For a more honest reading, keep the test in the foreground, disable battery saver or low power mode, and close heavy background tabs or GPU-intensive apps. If you use an external monitor, confirm the operating system is set to the refresh tier you expect and avoid mirrored-display setups while testing. Let the page run for at least ten seconds so the rolling window can stabilize before you judge the result. If you are sensitive to motion, start with slower presets and only increase them when the display feels comfortable. The best way to use this browser performance test is as a practical checkpoint, not as a laboratory claim. Start here, then move to the refresh-rate-test when you need more cadence context, and to the ghosting-test when motion blur or trailing seems worse than the FPS number suggests. For broader panel checks, the backlight bleed test and dead pixel test help you inspect the rest of the display cluster without leaving the same diagnostic workflow.
It measures browser-rendered frame timing with requestAnimationFrame. In plain terms, it shows how often this page is producing frames in your current browser session, not a direct read of monitor hardware.
No. FPS is how many frames the browser is rendering. Refresh rate is how often the display can update. They can line up, but they often differ when the browser or system is capped.
Common causes include browser caps, battery saver mode, background load, mirrored displays, external adapters, and tabs that are not getting full rendering priority.
The large number is smoothed so it stays readable. The graph exposes small pacing changes, short drops, and noise that are easy to hide in a single rounded value.
It can estimate browser-observed cadence and usually get close to common refresh tiers, but it should be treated as an honest estimate rather than hardware certification.
Browsers do not always schedule animation the same way. Power-saving behavior, compositing differences, extension load, and background policies can all change the observed FPS.
Yes. Low power states often reduce or stabilize animation at lower tiers, which can make the frame rate test show a cap that reflects the current environment rather than the panel limit.
Most browsers throttle background tabs. That protects battery life and CPU time, but it also makes background measurements unsuitable for judging real motion performance.
No. Games use their own render loop, engine settings, and GPU workload. This page measures browser motion performance, which is useful but not identical to game performance.
Check OS refresh settings, disable battery saver, keep the tab in front, reduce background load, and verify cables or adapters if you use an external monitor. Then compare with the refresh rate test and ghosting test for follow-up diagnosis.