Reading a swipe threshold as a share
A swipe only counts once the finger has traveled a set distance. Fixing that distance in px alone makes it too short on large screens and too long on small ones, so converting it into a share of the screen width makes it easier to compare. Enter the threshold you chose and you get the share, the vw value, the allowed angle and the speed needed.
How it is calculated
Share = threshold divided by area width, times 100, and the vw value is the same ratio. The allowed angle is arctan(vertical drift divided by threshold) in degrees, meaning only movement inside that angle at the threshold point counts as horizontal. The required average speed is the threshold divided by the time limit.
Limits
As of October 2026 there is no official standard for a swipe threshold, so this tool proposes no px value and does not judge whether yours is appropriate. Device pixel density, momentum, touch coordinate smoothing and browser gestures that claim the swipe first are not modeled. Always pair a swipe-only action with an alternative such as a button.
Frequently Asked Questions
No official standard exists. It depends on the platform, the gesture and whether one-handed use matters, so this tool proposes no value and only converts what you enter into a share and an angle.
Fingers travel diagonally, so looking only at horizontal distance catches vertical scrolls as swipes too. Accepting a swipe only inside the angle formed by the threshold and the vertical drift reduces that conflict.
If you want to accept short, fast flicks, distance and time are read together. Enter a time limit and you get the average speed needed to cover the threshold within it, which can serve as the flick test.