Riot has published the exact math behind why peeking wins gunfights it shouldn’t. In their own technical breakdown of VALORANT’s netcode, the baseline edge a peeker holds over a stationary defender comes out to roughly 141 milliseconds — and even after years of server optimization, about 101ms of that edge is still baked into every duel[1]. Almost no peeking guide mentions this number. Most just tell you to “peek fast” and hope the reader figures out what “fast” means for their specific gun. It doesn’t mean the same thing holding a Sheriff as it does holding an Operator, and this guide is built around that gap.
Version note: all weapon stats, fire rates, and map-pool references below are verified against Patch 13.00 (June 23, 2026)[7]. Riot tunes weapon spread and movement penalties almost every patch, so re-check the official wiki if you’re reading this more than a few patches later.
Quick Start: 7 Things to Decide Before You Move
- Pick your peek type before you step out — info (jiggle), bait (shoulder), or commitment (wide swing). Indecision mid-peek is what gets people killed, not slow reflexes.
- Pre-aim head height at the exact spot you expect the enemy to be standing, before you start moving.
- For a jiggle: expose no more than roughly a meter of your model and pull back inside 150-200 milliseconds — see the gun-by-gun table below for why that number changes per weapon.
- For a wide swing: clear the corner fully, stop dead to reset your spread to its stationary value, then burst-fire in short controlled bursts.
- Check what gun the enemy is likely holding. Their fire rate is your real margin for error if your first read is wrong — a missed shot against a Sheriff costs them 250ms before shot two; against a Phantom it costs under 100ms.
- Never peek without knowing your retreat line. Decide the exit before you decide the entry.
- Use flashes, smokes, or recon utility to strip the defender’s information before you commit to a wide swing — it’s the cheapest way to cancel their reaction-time advantage entirely.
Jiggle, Shoulder, Wide Swing, and Counter-Peek — What Each One Actually Does
These four terms get used loosely, but they solve different problems. Mixing them up — jiggling when you meant to commit, or wide-swinging when you only wanted information — is the single most common peeking mistake in ranked lobbies below Diamond.
| Peek Type | Goal | Exposure Target | Best Used By |
|---|---|---|---|
| Jiggle Peek | Gather info, bait a reaction shot | ~150-200ms, minimal body exposure | Whoever is checking an unknown angle |
| Shoulder Peek | Bait a committed shot from a holder | A single frame of model visibility | Player provoking an Operator or awper-style hold |
| Wide Swing | Take the duel outright | Full exposure, stop-and-shoot | Player who already knows or strongly suspects the angle |
| Counter-Peek | Cancel the peeker’s timing edge | Defender moves into the peeker instead of holding still | Holder who reads the peek coming |
The 101ms Reason Peekers Win Duels They Shouldn’t
Riot’s engineers frame peeker’s advantage as a simple inequality: the time a holder has to react and land a shot equals their raw reaction time minus the combined network latency and buffering delay between the two clients[1]. In their published baseline — a 35ms round-trip target, roughly two frames of server buffering, and about three frames of client buffering — that gap works out to about 141ms. Riot’s own infrastructure work (their private Riot Direct network, global servers, and a 128-tick rate with buffering trimmed to half a frame server-side and one frame client-side) closes about 40ms of that, a 28% reduction, leaving a residual advantage of roughly 100ms in the standard scenario. Players on a 144fps client see the reduction climb to about 49%, pushing the residual closer to 71ms[1].
Put plainly: if a defending player’s honest reaction time is around 200-250ms — genuinely fast for a human being — subtracting a 100ms head start means they functionally have somewhere in the 100-150ms range to register you, aim, and fire before you’ve already retreated. That’s an inhumanly tight window, and it’s why a clean jiggle peek statistically wins info duels even against a player who is, in raw terms, a better shot.
A wide swing throws that math away. The moment you fully commit and stop to shoot, you’re no longer exploiting a latency gap — you’re in a symmetric aim duel where both players are stationary, both have full accuracy, and the winner is whoever pre-aimed the correct head-height spot and reacts first in a straight crosshair-placement contest. The 100ms netcode edge still exists, but it’s a much smaller factor once both players are shooting at full accuracy for a full second or more instead of a fraction of one.
A counter-peek is the holder’s answer to a suspected wide swing. Instead of waiting to be exposed to the peeker’s information advantage, the defender pushes into the same angle at the same moment. This converts the fight from “peeker sees me first with a head start” into a genuine 50/50 aim duel where neither side is stationary — but it only works if the counter-peeking player’s crosshair is already on the correct spot. Guess wrong by even a head’s width while moving, and you’ve handed the original peeker a free kill instead of neutralizing their edge.
Jiggle-Peek Timing and Distance, Calibrated to Each Gun
This is the part every other peeking guide skips: the safe exposure window for a jiggle isn’t one universal number. It’s a function of how fast the weapon you’re worried about can recover between shots, and how far your own gun lets you move in the time you’re exposed.
| Weapon | One-tap headshot range | Fire rate | Recovery between shots | Run speed (holding) | Distance in a 150ms jiggle |
|---|---|---|---|---|---|
| Operator | All ranges (255 hd)[6] | 0.6 rounds/sec[6] | ~1.67s[6] | 5.13 m/s[6] | ~0.77m |
| Vandal | All ranges (160 hd)[3] | 9.75 rounds/sec[3] | ~0.10s[3] | 5.4 m/s[3] | ~0.81m |
| Phantom | 0-20m (156 hd), falls to 140 beyond[2] | 11 rounds/sec[2] | ~0.09s[2] | 5.4 m/s[2] | ~0.81m |
| Spectre | 0-15m (78 hd), falls to 60 beyond 30m[5] | 13.33 rounds/sec[5] | ~0.075s[5] | 5.73 m/s[5] | ~0.86m |
| Sheriff | 0-30m (159 hd), falls to 145 beyond[4] | 4 rounds/sec[4] | 0.25s[4] | Sidearm — no rifle movement penalty[4] | Near base run speed |
The mechanism behind this table matters more than the numbers themselves. Your ~100ms residual netcode advantage is worth far more against a slow-firing weapon than a fast one. Bait a miss from an Operator holder and you’ve bought over a second and a half of total safety before their next shot is even physically possible — plenty of time for a teammate to trade or for you to fully reposition. Bait a miss from a Phantom or Vandal and their follow-up shot is ready again in under a tenth of a second, so your jiggle window needs to stay inside roughly that residual 100ms advantage or the very next bullet in their burst simply catches you on the way back to cover. Against a Spectre, the calculation shifts on range instead of fire rate — inside 15 meters it’s nearly as dangerous as a rifle, but past 30 meters even a clean headshot deals only 60 damage, so a jiggle at range against a Spectre carries real margin a jiggle at the same range against a Vandal does not.
Scoped weapons compound this further. An Operator holder who is actively zoomed in moves at only 72% speed (about 3.69 m/s) while adjusting their scope[6], and re-tracking a target through a 2.5x or 5x zoom is mechanically harder than through a rifle’s normal field of view. A pre-aimed, fully stationary Operator hold is close to the worst-case scenario for a peeker — but the instant you force that player to reacquire you after a miss, you’re fighting the slowest weapon in the game on your terms, not theirs.
Which Peek Fits Your Rank
| Player Type | Priority |
|---|---|
| New player | Master the jiggle and shoulder peek only. Skip wide swings until your crosshair placement is consistent — the frame-advantage math above only helps you if your first shot lands when it matters. |
| Casual player | Default to two-person wide swings with a teammate clearing the same angle together, backed by one piece of utility. It converts an even aim duel into a numbers advantage without needing frame-perfect execution. |
| Hardcore / optimizer | Learn counter-peek reads — recognizing when a defender is about to push into your jiggle — and calibrate exposure time per weapon matchup rather than using one generic jiggle speed for every gun. |
| Completionist | Catalogue off-angle jiggle spots per map and per site, since an off-angle breaks the defender’s pre-aim entirely and forces them into the same reaction-time deficit a standard corner peek does. |
Watch a handful of high-rank VODs and the pattern repeats: the losing peek is almost never the slower player — it’s the player who never decided which of the four peek types they were executing before they moved. A rifle round with a fast trigger finger and no plan loses to a slower player running the correct peek for the situation, consistently.
3 Mistakes That Cancel Any Peeking Advantage
Peeking without pre-aim first is the most common one. The entire ~100ms netcode edge assumes the peeker already knows where to put their crosshair the instant the enemy appears — if you’re still swinging your mouse to find the target, you’ve given that edge straight back. Building consistent crosshair placement habits at head height on common angles matters more than reaction speed for this reason.
Wide-swinging before your movement inaccuracy resets is the second. Patch 9.10 increased running inaccuracy penalties across rifles specifically to punish shooting mid-strafe, and both the Vandal and Phantom still carry a running spread penalty of roughly +6° on top of their base spread[2][3]. If you’re still decelerating when you fire, your bullets are landing somewhere your crosshair isn’t. Drilling stop-and-shoot timing in aim-training routines closes this gap faster than repetition in live rounds — see our aim training guide for specific drills.
Ignoring what the enemy can afford to hold is the third. A full-buy round against an eco round changes which peeks are even worth the risk — jiggling casually into a site where the defense could have bought an Operator is a very different decision than jiggling into a round where their economy can’t support one. Our Valorant economy guide breaks down how to read the opposing buy before you commit to an aggressive peek.
FAQ
Does peeker’s advantage mean I should always push instead of hold?
No. The advantage only applies while the defender is stationary and the peeker is moving with full information. A holder who reads the peek coming and counter-pushes at the right moment converts the fight into a symmetric aim duel, erasing most of that edge. Passive holding without a read is what loses to peekers — holding with a plan doesn’t.
Why do my jiggle peeks still get punished even when I execute them fast?
Usually one of three things: your pre-aim wasn’t already on the correct spot, you jiggled the exact same angle and timing repeatedly until the defender’s reaction time effectively became a read instead of a reaction, or the shot that killed you came from a teammate holding a different angle you didn’t account for.
Should I ever wide-swing an Operator holder?
Only after removing their sightline first with a flash, smoke, or recon reveal. A blind wide swing into a pre-aimed Operator is one of the worst trades in the game because their one-shot kill radius covers the entire map at full damage[6]. Strip the angle with utility first, then the fight becomes about aim rather than about who peeked first.
Does higher frame rate actually reduce peeker’s advantage in ranked play?
Yes, according to Riot’s own published figures — the reduction in peeker’s advantage climbs from roughly 28% at standard settings to about 49% at 144fps, which is a meaningfully smaller window for the peeker to exploit[1]. It doesn’t eliminate the edge, but it’s one of the few competitive advantages that comes from hardware and settings rather than mechanical skill alone.
New to the agent or economy fundamentals this guide assumes? Start with our full Valorant Beginner’s Guide 2026 for starter agents, ranked basics, and the economy system this article builds on.
Sources
- Riot Games. Peeking into VALORANT’s Netcode. Riot Games Technology Blog
- Riot Games. Phantom. VALORANT Wiki
- Riot Games. Vandal. VALORANT Wiki
- Riot Games. Sheriff. VALORANT Wiki
- Riot Games. Spectre. VALORANT Wiki
- Riot Games. Operator. VALORANT Wiki
- Riot Games. VALORANT Patch Notes 13.00
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.