Ping / Latency Converter
Convert ping in milliseconds to frames of delay at 60Hz, 120Hz, and 144Hz refresh rates.
See how latency affects competitive gaming and server response time.
Ping (also called latency) is the round-trip time for a data packet to travel from your device to a game server and back, measured in milliseconds (ms). It directly determines how responsive an online game feels and whether actions register before opponents react.
Round-trip time formula: RTT (ms) = 2 × One-Way Propagation Delay + Processing Time
Propagation delay (speed of light through fiber): Delay (ms) = Distance (km) / 200 km/ms (Light travels at ~200,000 km/s through fiber-optic cables — roughly ⅔ the speed in vacuum.)
Game server ping estimation: Expected Ping ≈ Distance to Server (km) / 100 (Rough approximation accounting for routing overhead and server processing.)
Jitter = variability in latency: Jitter = Max RTT − Min RTT (over a measurement window)
High jitter is often more problematic than high average ping — it causes inconsistent movement, rubber-banding, and missed inputs.
Ping quality thresholds for gaming:
| Ping | Classification | Experience |
|---|---|---|
| < 20 ms | Excellent | Virtually imperceptible lag |
| 20–50 ms | Good | Smooth for all game types |
| 50–100 ms | Acceptable | Fine for casual play |
| 100–150 ms | Marginal | Noticeable in competitive FPS/fighting games |
| 150–300 ms | Poor | Significant disadvantage in action games |
| > 300 ms | Unplayable | Severe rubber-banding, lost connections |
Worked example: A player in London connecting to a server in New York City (~5,570 km via fiber routing). Theoretical minimum = 5,570 / 200 = 27.85 ms one-way → ~56 ms RTT Real-world ping (with routing hops, server processing) typically 70–120 ms
Reducing ping: Use wired Ethernet (reduces jitter by ~5–15 ms vs. Wi-Fi). Choose servers closest geographically. Use a gaming-optimized router with QoS. Avoid peak ISP congestion hours. VPNs typically increase ping unless using a gaming-optimized proxy service.