Home / Device & Media Tools / Refresh Rate Test

Device & Media Tools

Refresh Rate Test

Keep the tab visible and avoid heavy background work. The result describes browser frame cadence, not a direct electrical measurement of panel timing.

Sample length

Status

ReadyKeep this tab visible while the browser samples animation frames.

—Median frame time

—Average Hz

—P10–P90 spread

0Samples

—Nearest common target

—Frame-time stability

—Long frames

VisibleTab state

Browser-visible estimaterequestAnimationFrame follows browser rendering cadence. Background throttling, power saving, variable refresh, compositor behavior, and other load can affect results; this is not a hardware oscilloscope measurement.

Inspect frame-time distribution Inspect motion clarity Check resolution

What the browser can measure

Start with a functional check, measure only what the browser can actually expose, then retest after one change.

ConnectChoose the actual browser-visible device or grant permission when required.

TestConfirm basic signal, input, output, preview or display behavior.

MeasureUse browser-exposed levels, timing, resolution, FPS, axes or event data.

DiagnoseCompare the symptom with the specific diagnostic instead of relying on one number.

RetestRepeat after changing the device, cable, permission, browser or system setting.

Pre-call Mic Webcam Keyboard Mouse Gamepad Display Permissions

Browser boundary
These tools observe browser APIs and local media/event streams. They cannot certify hardware condition, bypass denied permissions, or expose measurements the browser/OS does not provide.

Refresh-rate frame-budget audit

Compare observed and target Hz, frame time and tolerance without confusing display refresh with rendered FPS.

Display evidence

Target refresh Hz

Observed Hz override

Measure	Value	Meaning

Live frame-time trace

See the browser callback intervals behind the final Hz estimate. Tall spikes show delayed callbacks that a single average can hide.

—Latest frame

—P95 frame time

0Late frames

—Longest frame

Start the existing refresh-rate test above to populate the trace.

What this tool checks

Estimate browser-visible display cadence from requestAnimationFrame timing with median interval, jitter and stability context.

How to use the result

Keep the tab visible and avoid heavy background work. The result describes browser frame cadence, not a direct electrical measurement of panel timing.

Privacy & browser limits

Device streams and input events used by this page are handled in your browser unless the page explicitly says otherwise. Permission, label, timing and hardware-field availability depend on the browser and operating system.

Refresh-rate output remains a browser rendering-cadence estimate

The review distinguishes requestAnimationFrame cadence from a monitor hardware timing instrument and records visibility, spread and long-frame conditions that can make a run unreliable.

Practical guide and verification

Keep the tab visible throughout the sample

The test uses requestAnimationFrame timestamps. Background tabs can be throttled or paused, so a hidden-tab run can report a cadence unrelated to the foreground display behavior you are trying to measure.

Read the frame-time trace with the Hz estimate

A median near 6.94 ms corresponds to about 144 Hz and 16.67 ms to about 60 Hz, but occasional tall spikes reveal delayed frames that a single average can hide. Use the live trace to separate steady cadence from intermittent stalls.

Treat late frames as diagnostic evidence

A long callback interval can come from browser work, compositor scheduling, power saving, variable refresh, another application, or tab movement between displays. A late frame is evidence to retest, not proof that the monitor itself dropped a hardware refresh.

Compare repeated runs after one system change

Keep the browser, window position, sample length, and workload similar when comparing a cable, display setting, power mode, or hardware-acceleration change. Repeated stable results are more informative than one unusually smooth or noisy run.

Use fullscreen or a motion test for visual confirmation

Timing statistics describe browser cadence but do not directly show motion clarity, response time, or ghosting. Pair the numerical result with a fullscreen or moving-object test when the practical question is whether motion looks smoother.