Screen tearing test
A hard vertical edge moving across the screen, which is the pattern a torn frame cannot hide in.
Esc to exit · space starts and stops · H hides the controls
- Frames drawn
- 0
- Observed rate
- —
- Bar travel
- 1400 px/s
The frame counter and observed rate come from the animation itself. They describe what this page is presenting, which is not necessarily what your display is receiving.
How to run this test
- Press Go full screen. A tear is a horizontal break in a moving edge, and you need the whole panel to see where it lands.
- Watch the leading edge of the moving bar, not the middle of it. A tear shows as a step where the top half of the edge is ahead of the bottom half.
- Raise the speed. Faster movement makes the offset at a tear larger, so a tear that was invisible at low speed becomes obvious.
- Watch for a few seconds. A tear line that drifts slowly up or down the screen means the frame rate and the refresh rate are close but not locked.
- Compare with the measured refresh rate on the refresh rate test. A browser that is presenting at a rate your display does not share is the usual cause of what you are seeing.
What a problem looks like
- A clean horizontal step in the moving edge
- A torn frame: the display started sending a new image partway down the screen, so the top and bottom belong to different frames. In a browser this normally means the compositor has been told not to synchronise, which happens with some driver settings and in some remote sessions.
- A tear line that slowly drifts up or down
- The presentation rate and the refresh rate are close but not equal, so the split point walks across the screen. This is the classic look of vertical sync being off with a frame rate near the refresh rate.
- Several tear lines at once
- More than one frame is being presented per refresh. In a browser this is unusual and normally points at a compositor or driver problem rather than anything you can change on the page.
- The bar stutters instead of tearing
- That is dropped or unevenly spaced frames, which is a different fault with a different cause. The frame rate test measures pacing directly and will tell you far more about it than watching an edge will.
- No tearing at all
- The expected and correct result in a browser. Browsers composite in step with the display by default, so a clean edge here means the path from the page to your panel is behaving. It does not tell you whether a game will tear.
What to do next
If the edge tears, look at the graphics driver vertical sync setting and at any remote-desktop or capture software in the path. If it does not, your browser and compositor are in step, which is what you want, and it says nothing about how a game will behave.
Questions people actually ask
What is screen tearing?
Your display refreshes by drawing an image from top to bottom. If a new frame arrives partway through that scan, the top of the screen shows the old frame and the bottom shows the new one, with a visible horizontal seam between them. That seam is a tear.
Why might a browser not tear when my games do?
Because browsers normally hand finished frames to the compositor, which presents them in step with the display. A game usually talks to the graphics driver directly and can present whenever it likes unless vertical sync or a variable refresh rate mode is holding it back. This page therefore tests your browser and compositor, not your game.
So what is this test actually good for?
Finding a system where synchronisation is broken. If a hard edge tears here, something in the chain is out of step, and that will affect everything you watch and not just games. It is also the clearest possible demonstration of what tearing looks like, which is useful when you are trying to work out whether what you are seeing has a name.
Will variable refresh rate fix tearing?
That is what it exists for. FreeSync and G-Sync make the display wait for the frame rather than the frame wait for the display, which removes tearing without the input lag that vertical sync adds. Whether it is active is a system and display setting, and no web page can see it.
Can this page tell me whether vertical sync is on?
No. There is no API for it. What you have is an edge and your eyes: if it tears, synchronisation is not happening somewhere in the path to your screen. If it does not tear, the path is synchronised while this page is running. Neither is a reading of a setting.