What Is Rubber Banding in Online Games?

Why Client Prediction Exists (and Why It Causes Rubber Banding)

Without client-side prediction, every movement would feel delayed by your ping. If you press W to move forward, your client would have to send the input to the server, wait for the server to process it, and wait for the server to send back your new position — adding a full round-trip of lag to every movement.

Client prediction solves this: your client immediately moves your character locally based on your input, before hearing back from the server. The server processes the same input and also moves your character. Under normal conditions, the server and client agree on the resulting position and nothing visually odd happens.

Rubber banding occurs when server and client disagree on the result:

• High ping: Your client has predicted many frames of movement that the server hasn't yet confirmed. When the server's confirmation arrives late, it may contradict the local prediction — the server's position is authoritative, so the client snaps to it.
• Packet loss: Your input packet didn't reach the server. The server thinks you didn't move; your client thinks you did. When the next server update arrives, it snaps you to the server's (non-moved) position.
• Ping spike: A brief latency burst causes a backlog of unconfirmed predictions. When connectivity recovers, the server sends its authoritative positions and the client corrects, causing a rapid snap.

Rubber Banding vs Teleporting

Rubber banding specifically refers to the snap-back of your own character due to server-client position disagreement. Teleporting is when other players appear to jump positions — caused by lost or late updates about their position, which your client extrapolates incorrectly until the real position arrives. Both stem from the same causes (latency, packet loss) but affect different perspectives.

Diagnosing Rubber Banding

• Enable the in-game network debug display (most competitive games have one via developer console: net_graph in CS, graph.net in Valorant). Look for packet loss % and ping variance.
• Run PingPlotter or WinMTR to your game server's IP during a gaming session. Look for jitter and periodic loss that correlates with rubber banding events.
• If rubber banding affects all players simultaneously, it's server-side overload — not your connection.
• If rubber banding only affects you, it's your network path.

Fixes for Network-Caused Rubber Banding

• Switch from Wi-Fi to wired Ethernet — Wi-Fi jitter is the most common cause of rubber banding on otherwise healthy connections.
• Reboot your router — routers under sustained load can develop packet queuing issues that increase jitter.
• Use QoS on your router to prioritize game traffic, preventing downloads or streaming from causing jitter during gaming.
• Select a geographically closer server region to reduce base ping and therefore the magnitude of snap corrections.

Frequently Asked Questions

Why does rubber banding happen even when my ping looks normal?

In-game ping shows average or smoothed RTT. Rubber banding is caused by ping spikes — brief bursts of high latency. A connection averaging 30ms but spiking to 200ms periodically will rubber band despite looking healthy on the scoreboard. Jitter (ping variance) predicts rubber banding better than average ping. Monitor with PingPlotter during gaming to detect spike patterns.

Is rubber banding always a network problem?

No — overloaded game servers also cause rubber banding when they can't process ticks fast enough. The server falls behind, then catches up by sending corrected positions that snap all clients. This affects all players on the server simultaneously. If everyone is rubber banding at the same moment, it's server-side, not your connection.