Privacy Policy and Terms of Service
Legal
By using fpstest.co ("Site"), you agree to these terms.
Last updated:
What the test measures
All measurement happens in your browser. The Site counts animation frames and reads the gap between them, and it asks your browser for a few facts about your display — screen size, pixel ratio, colour depth, the graphics renderer name, the number of CPU threads. Those values are used to draw the numbers on screen and are gone when you close the tab. They are not stored, not uploaded, and not sent to us or to anyone else.
The Site keeps two things in your browser's local storage on your own device: whether you picked the light or the dark theme, and whether the sidebar is collapsed. That is the lot. There is no account, no login, and no session cookie of our own.
Your use
Use the Site at your own risk. Do not use the Site for illegal purposes or attempt to integrate it into other applications.
The results are for reference only. A browser test is capped by your display and by whatever else your machine happens to be doing, so it is not a certified or calibrated measurement of your hardware, and it should not be used on its own to judge whether a device, a monitor or a repair is faulty. If you are testing something you are about to return or dispute, back the reading up with a second tool and a second run.
Changes, service & disclaimer
We may change these terms or the Site, and reserve the right to change or cease any services at fpstest.co, at any time, without notice. The Site is provided "as is" without any guarantees.
Contact us
For anything wrong with the Site — a reading that looks incorrect, a page that will not load, or a privacy question — write to [email protected].
For everything else, including feedback and suggestions for a tool you would like to see, use [email protected].
We read everything and answer most messages within a few working days. There is no contact form because the Site keeps no session, no database and no cookie of its own, and a form would need all three.
Reporting a problem
Almost every report we cannot act on is missing one of these. Including them turns a guess into a fix:
- Which page you were on, and the address in the bar.
- Your device and browser — "iPhone 14, Safari" is enough.
- What you expected to see, and what you saw instead.
- The refresh rate the page reported, and the confidence figure next to it.
- Whether the browser was fullscreen, and whether anything heavy was running in another window.
Two things are worth checking before you write. A frame rate that stops dead on a round number — 60, 120, 144 — is not a bug: the browser paints in step with your display, so the display is the ceiling. And a laptop or phone on battery very often halves its own refresh rate, which is the single most common cause of "my 120 Hz screen only shows 60".