Motion Blur Test

Watch a high-contrast target move at adjustable speeds and compare how motion looks on your display.

Press Start motion, then watch the moving edge. Adjust speed and compare one display setting at a time.

How to use this motion blur test

Press Start motion and watch the black-and-white target as it crosses the patterned track. Begin around 480 CSS pixels per second, then use the speed slider to compare a slower and faster pass. Change direction if the movement is easier to follow the other way. Full screen provides a larger viewing area; press Escape or use Exit full screen to return. Pause the animation before changing other monitor settings so you can make one change at a time.

For a useful comparison, sit at a normal distance and follow the target with your eyes without moving your head. Notice whether its edges remain distinct or appear smeared, doubled, or followed by a faint trail. Repeat the same speed and direction after each setting change. The slider reports CSS pixels per second for this browser pattern, not the physical speed of an object on every monitor. Screen size, scaling, and display density affect the apparent movement.

What motion blur and ghosting mean

Motion blur describes loss of edge clarity while an object is moving. A moving image can look less sharp even when the display is working as designed, because pixels take time to change and because the eye follows motion across frames that are held on the screen. Ghosting is commonly used for a visible trailing or repeated edge behind a moving object. Similar artifacts can come from panel response, overdrive behavior, refresh timing, frame delivery, motion processing, or the rendered content.

This page creates a simple animated high-contrast pattern in the browser so you can compare one setup with another. It does not generate a precisely synchronized camera exposure or measure pixel transitions. The W3C CSS Animations specification defines how web animations are presented by a browser, but it cannot guarantee a particular frame cadence on a loaded device. Treat what you see as a qualitative observation for this browser and display combination.

Choose a repeatable speed

Different movement speeds emphasize different visual effects. A slower pass gives you time to inspect the shape; a faster pass can make trails or loss of clarity more apparent. There is no single speed that represents every game, video, or desktop task. Choose one that resembles the motion you are troubleshooting and keep it fixed for each comparison. If you want a quick baseline, start at 480 CSS pixels per second and then compare nearby slider settings.

The number shown is a setting for the CSS animation distance and duration. It is not a measured refresh rate, frame rate, response time, or pursuit-camera result. The browser may schedule frames differently when the tab is hidden, the system is under load, or the display refresh mode changes. Keep this tab in the foreground, allow the pattern to run smoothly, and repeat the same pass if another app or notification interrupted it.

Compare display settings carefully

Change one display control at a time. If you are checking overdrive or response-time settings, compare each available level using the same speed, direction, and viewing position. Stronger overdrive can reduce some trails but may introduce bright or dark overshoot; this browser tool cannot name or score that behavior reliably. Motion smoothing, backlight strobing, variable refresh rate, HDR, and game modes can also alter what you see. Note the setting name and whether the change improved the specific motion you care about.

Use the display's recommended resolution and refresh mode when establishing a baseline. If your computer offers multiple refresh rates, select the mode you normally use before comparing. A dock, adapter, remote desktop, capture path, or power-saving mode can affect frame delivery. For a fair check, keep the signal path constant and avoid changing a graphics setting and a monitor control in the same pass.

Understand browser and display limits

A browser animation passes through page rendering, the operating system compositor, graphics hardware, and the display. The browser does not read the monitor's pixel response specification, overdrive state, or actual panel refresh behavior. This page also does not use a high-speed camera, photodiode, or calibrated motion benchmark. Therefore, a visible trail is not proof of a faulty monitor, and a clean appearance does not prove that a display meets a particular response-time claim.

Fullscreen mode asks the browser to enlarge the tool for a closer view. The Fullscreen API standard defines this user-initiated page capability; it does not lock refresh rate or bypass the graphics pipeline. If full screen is unavailable, the pattern still runs in the tester card. For formal response-time or motion-resolution measurements, use a test method designed around the required camera, photodiode, or timing equipment.

When a motion pattern looks uneven

If the target jumps instead of moving smoothly, keep the tab visible and close demanding background applications before repeating. Check that the computer is not in a low-power mode and that the browser is not throttling a background tab. Try another current browser using the same display settings. A change that appears only in one browser or under heavy system load may be related to frame scheduling rather than panel response.

If trails change when you alter a monitor setting, repeat the comparison several times and return to the original setting once. Look for a consistent difference rather than a single frame or brief visual impression. If only a particular game or video looks blurry, inspect its frame rate, motion blur effect, scaling, and connection path separately. A browser pattern is a starting point for comparison, not a substitute for troubleshooting the application where the symptom occurs.

Related display checks

For static panel observations, use the Dead Pixel Test, the Gray Banding Test, or the Gray Uniformity Test. They inspect solid colors, gradients, and flat gray fields. Motion blur is a separate visual question, so compare the pages independently instead of combining their observations into a hardware score.

Frequently asked questions

What should I look for in a motion blur test?

Watch the moving target edge and compare how clearly it appears while moving. A browser animation is a visual comparison, not an instrument reading of pixel response time or refresh behavior.

What speed should I use?

Start around 480 CSS pixels per second, then compare slower and faster settings that resemble the motion you care about. Keep the pattern, direction, display mode, and viewing position consistent.

Does visible ghosting prove my monitor is faulty?

No. Browser frame timing, refresh rate, panel response, overdrive, motion processing, graphics load, and vision all affect the appearance. Compare another mode or display before drawing a conclusion.