FPSCalc › Mousepad Swipe Room Calculator
Your sensitivity and your mousepad have to agree. This turns a cm/360 into centimetres of real mouse travel, subtracts the mouse body, and tells you whether a 180 — or a full spin — actually fits.
Mouse travel for one full spin. Lower is faster.
A flick behind you is 180; a full spin is 360.
Don't know your cm/360? Derive it from your settings
Equals 34.6 cm/360
Published sizes, rounded. Pick Custom to type your own.
Only the body footprint matters here.
Off by default. Most players keep the whole mouse on the pad, but wide-arm low-sens players often overhang.
| Metric | Value | How it is worked out |
|---|
| Turn | cm | inches | From centre | From edge |
|---|
| Mousepad | Size (mm) | Usable width | Slowest cm/360 that fits | Yours |
|---|
Usable width subtracts your mouse's body. The last column asks whether your current sensitivity fits a turn of the size chosen above, starting from the centre of the pad.
Because the mouse body occupies part of the pad. A 450 mm pad with a 63.5 mm wide mouse gives you 386.5 mm of travel for the sensor, not 450. On a small pad that difference is a large fraction of the total, which is why 250 mm pads cannot host a low-sensitivity 180.
The centre, if you want to flick in either direction without thinking. Starting centred you only have half the usable width to work with, so a centred 180 needs twice the pad that an edge-to-edge 180 does. This page reports both.
Not on its own. Room is decided by cm/360, which is DPI multiplied by in-game sensitivity. Doubling DPI and halving sensitivity leaves the answer identical. That is why cm/360 is the only number worth arguing about.
Three common reasons: you let the mouse overhang the pad edge, you lift and recentre mid-flick without noticing, or your mouse's lift-off distance lets it keep tracking slightly above the surface. Tick the overhang box to model the first one honestly.
Put the mouse against a ruler, push it in a straight line until the view turns exactly 360°, and read off the distance. Do it slowly and with acceleration disabled. If you know your DPI and sensitivity instead, the box above derives it from published per-game constants.