Ghosting Test
Watch moving blocks, bars, text and lines for ghosting trails, motion blur and overdrive halos.
See the refresh rate your monitor, laptop or phone is running at right now, estimated in Hz from how often your browser draws a frame over 3 seconds. A moving bar shows how smooth that rate looks.
—Hz
Not measured yet
Median frame time: — · Frames sampled: —
Pick the rate your monitor is sold at to check whether it is running at it.
Run the test to get a result you can copy or share.
The estimate comes from how often the browser paints, not from the display hardware. Battery saving, browser limits and background load can lower it.
Runs entirely in your browser. Test results, audio and video never leave your device.
Refresh rate is how many times per second a screen updates its image, measured in hertz (Hz). A 60 Hz screen updates 60 times a second and a 144 Hz screen 144 times, so motion looks smoother on the faster one, as long as the computer, console or phone supplies a new frame for each refresh.
The large number is the rate your browser is drawing at, in Hz, estimated from 3 seconds of frames. Under it are the closest common rate, the dropped-frame count, the median frame time and the number of frames sampled. Copy or Share puts the result in one sentence you can paste.
The browser measures how often it draws, not a value read from the display. Battery saving, the browser’s own power settings and the display settings can all hold it below what the screen supports, so a low reading tells you where to look rather than that the monitor is faulty.
Choose the rate your monitor is sold at under Your monitor’s rated refresh rate. After a measurement the page compares the two, allowing 2 percent (at least 1.5 Hz) for timing jitter, so 143.9 Hz counts as 144 Hz but 165 Hz does not count as 170 Hz. It then says the screen is running at its rated rate, below it, or faster than the rate you picked.
The rated rate is on the box, in the manual or on the maker’s product page, often written as 144Hz or 165Hz. In Windows 11, the rate in use is under Settings > System > Display > Advanced display, next to Choose a refresh rate.
Source: Microsoft Support: Change the refresh rate on your monitor in Windows. Checked October 6, 2026.
Stuck at 60 Hz? A reading below the rate your screen is sold with usually means a setting, a cable, a power mode or the browser itself is holding it back. The same checks apply to 120, 165 and 240 Hz screens. Press Measure again after each change.
Sources: Microsoft Support: Change the refresh rate on your monitor in Windows; Apple Support: Change the refresh rate on your MacBook Pro or Apple display; NVIDIA Control Panel Help: To select a screen refresh rate; AMD: How to enable AMD FreeSync with AMD Software: Adrenalin Edition; Intel: How to fix a flickering screen with Intel Graphics; Apple Support: refresh rate of an external display on Mac; HDMI Licensing Administrator: HDMI cable types. Checked October 6, 2026.
Frame time is 1000 ms divided by the refresh rate. The median frame time in your result should be close to the one listed for your screen's rate.
| Refresh rate | Time per frame | Where you usually find it |
|---|---|---|
| 60 Hz | 16.7 ms | Office monitors, and many laptops, TVs and phones |
| 75 Hz | 13.3 ms | Budget and office monitors |
| 90 Hz | 11.1 ms | Some phones and tablets |
| 120 Hz | 8.3 ms | Many recent phones and tablets, some laptops and TVs |
| 144 Hz | 6.9 ms | Gaming monitors and laptops |
| 165 Hz | 6.1 ms | Gaming monitors and laptops |
| 240 Hz | 4.2 ms | Fast gaming monitors |
| 360 Hz | 2.8 ms | Esports monitors |
A new image every 16.7 ms. In the motion test the bar moves 480 px a second, and fast movement, such as a quickly moved mouse pointer, shows visible steps.
Twice as many images as 60 Hz, one every 8.3 ms. Scrolling and pointer movement look clearly smoother, as long as the device draws a new frame for each refresh.
One image every 6.9 ms, the usual rate for gaming monitors. A game needs about 144 frames per second to use every refresh; at a lower frame rate some refreshes repeat the last image.
About 6 ms per image, a modest step above 144 Hz that many current gaming monitors and laptops offer. Pick the exact rate in the list above, since the two are close.
4.2 ms per image at 240 Hz and 2.8 ms at 360 Hz. These rates need a matching frame rate, and a cable and input that carry them at your resolution; the monitor’s manual says which input supports the top rate.
Open this page on the phone and press Start measuring. Phones with 90 Hz or 120 Hz screens often lower the rate to save power, so a reading of 60 Hz can come from a setting or the browser rather than the screen. Check these, then measure again.
For 3 seconds the test records the timestamp of every frame the browser draws (requestAnimationFrame), skips the first 10 and takes the median gap between them. The estimate is 1000 divided by that median, shown to 0.1 Hz and matched to the nearest of 17 common rates from 30 to 480 Hz. Gaps over 1.5 times the median count as dropped frames. A hidden tab, or 5 seconds without a frame, pauses the run.
The motion test moves a 24 px white bar exactly 8 px per frame, so its speed follows the rate: 480 px/s at 60 Hz, 1152 px/s at 144 Hz.
Because the estimate comes from frame timing and is shown to 0.1 Hz. Timing jitter, fractional rates such as 59.94 Hz and browsers that round their timestamps give readings a little off the round number. Compare the closest common rate, shown under the reading, with your screen's rate.
Hz is how often the screen updates; FPS (frames per second) is how many images the computer, game or browser produces. A 60 Hz screen updates 60 times a second however many frames a game renders, so smooth motion needs both a high refresh rate and a frame rate to match.
No. YouTube and most streaming sites play video at 60 frames per second or less, so a video cannot show whether a screen runs faster than that. A live test that draws a new frame on every refresh, like the one above, can.
A dropped frame is a gap between frames much longer than usual, typically because the browser or device was busy. A few are normal; many point to background load. The count covers frames the browser missed, not frames an overclocked monitor skips, which need a camera-based test.
A 3-second run picks up whatever else the device is doing, and adaptive screens, common on phones and some laptops, change rate with content and power state. Run it two or three times with the tab in front, and go by the closest common rate that repeats.