Flashbangs convert aim duels into free kills when timing is correct — and convert full buys into 4v5 disasters when they are not. In Counter-Strike 2, subtick throw registration and Source 2 flash angle math reward players who understand pop flash timing, not just players who buy two flashes every round.
This guide is the utility pillar for flash play: how blind duration scales with look angle and distance, pop flash mechanics that blind enemies without blinding you, self-flash entries for solo queue, team flash voice protocols, two-flash execute sequences, and map-specific entries on Mirage, Dust2, and Inferno. For throw physics and bounce behavior, start with our grenade mechanics guide; for smoke setup before flashes, cross-reference Inferno smokes, the Dust2 guide, and the Mirage guide.
After every Counter-Strike patch, re-test your highest-value pop flashes in a private server. Flash detonation timing and bounce paths shift subtly — a palace pop that worked last month may detonate too early today.
Quick answer: CS2 flashbang discipline
- Pop flash: detonates as you peek — enemy gets full blind, you peek from off-angle.
- Full blind at 0–3 m with direct view lasts ~2–3 s; partial blind at 10 m+ is not entry-worthy.
- Call 'flashing' + direction before every team throw — see team communication.
- Two-flash entry beats one: first clears AWPs, second punishes adjusters.
- Self-flash only with a planned wide swing within 0.3 s of detonation.
- Right-click underhand for indoor pop flashes; left-click overhand for long lobs.
- Configure jump-throw binds via config and binds guide for long flash lineups.
- Save one flash for post-plant retake denial — do not dump both on a failed entry.
Key takeaways
- Blind duration scales with look angle and distance — back-turned enemies take near-zero effect.
- Pop flashes beat straight overhand throws because you peek from an off-angle at detonation.
- Team flashes require voice comms — silent flashes destroy entry confidence.
- Two-flash sequences clear AWPs on first pop and punish repositioning on second.
- Self-flash is high risk — only use with a rehearsed wide swing and trade partner.
- Map-specific entries need 2–3 flash timings per map, not twenty niche lineups.
- CT counter-flash awareness and varied execute timing beat predictable flash cadences.
- Flash through smokes to force AWPs off angle — pair with anti-rush utility on CT.
Table of contents
- Key takeaways
- How flash blind scales: angle, distance, and look direction
- Pop flash mechanics — timing that wins entries
- Full blind setups for site executes
- Self-flash techniques — high risk, high reward
- Team flash timing and voice protocols
- Two-flash execute sequences
- Map-specific flash entries: Mirage, Dust2, and Inferno
- CT defensive flashes and counter-flash awareness
- Common flashbang mistakes
- Frequently asked questions
- Conclusion
How flash blind scales: angle, distance, and look direction
Flash effectiveness in CS2 depends on three variables: distance from detonation center, whether the target is looking at the flash, and line-of-sight exposure. A player staring directly at a center detonation at close range can be fully blinded for 2–3 seconds. A player facing away takes minimal effect — sometimes only a brief white edge at the screen periphery.
This angle math is why pop flashes work. The enemy holding an angle sees the flash origin and receives full effect. You peek from an off-angle or behind cover and avoid direct exposure. Straight overhand lobs over a wall blind everyone in radius — including teammates who forget to turn.
| Look angle | Distance | Blind duration (approx.) | Entry worthy? |
|---|---|---|---|
| Direct view of flash | 0–3 m | 2.0–3.0 s full white | Yes — swing at pop |
| Direct view | 5–8 m | 1.0–2.0 s | Yes — standard execute flash |
| Direct view | 10 m+ | 0.5–1.0 s partial | No — fake or distraction only |
| 90° off-angle | Any | 0.3–0.8 s partial | No — do not rely alone |
| Back turned | Any | Near zero | Why pop timing beats lob throws |
| Through smoke | 3–5 m | 1.0–2.5 s | Yes — forces AWPs off angle |
Pop flash mechanics — timing that wins entries
A pop flash detonates just as you peek a corner — the enemy receives full blindness while you swing from an off-angle that avoids direct flash exposure. The throw is typically a right-click underhand toss that bounces once off a wall or doorframe, or a left-click lob timed to airburst at the corner edge.
The critical skill is synchronizing your peek with detonation — not with the throw moment. Most ranked players throw, wait half a second, then peek. By then the blind is fading and the AWPer has adjusted. Swing at the pop sound, not after it.
- Identify the bounce surface — palace wall, long corner, apps doorframe.
- Right-click underhand for indoor one-bounce pops; left-click for outdoor lobs.
- Throw while moving toward the corner — do not stand still and throw.
- Peek the frame the flash pops — your crosshair should be on the angle as white fills the enemy screen.
- Have a trade partner pre-aiming the same angle — pop flash without trade is a coin flip.
- Practice 10 reps per entry in an empty server before ranked.
Full blind setups for site executes
Full blind means the enemy anchor sees only white for 2+ seconds — enough time for two players to wide swing and trade. Full blind requires direct line-of-sight between the flash detonation and the enemy's camera, at entry range (under 8 m). Lob flashes over walls rarely produce full blind at competitive distances.
Execute flashes should target the most dangerous angle first — AWPer long, CT default, pit, or jungle. A flash that blinds the site player but not the AWPer loses the round before entry begins.
| Execute type | Flash target | Throw style | Entry timing |
|---|---|---|---|
| A site execute | Default + CT angle | Pop off wall + overhand backup | Swing on first pop; trade on second |
| B site execute | Site anchor + back plat | Underhand bounce + lob over door | Rush on second flash pop |
| Mid take | Connector + window | Pop mid + flash through smoke | Cut cat on blind window player |
| Post-plant deny | Retake path choke | Lob over box/smoke | Hold angle — do not peek into retake |
Full blind setups pair with smokes on every execute — flash clears the angle the smoke does not block. On Inferno, smoke apps then pop flash door; on Dust2, smoke cross then pop long corner. Smoke lineups live in map-specific guides — Inferno smokes and the Dust2 guide cover the smoke half of each execute.
Self-flash techniques — high risk, high reward
Self-flash means detonating a flashbang close enough to blind you briefly while you wide swing immediately after. The enemy receives full blind; you receive partial blind but are already moving and shooting. Self-flash works in solo queue when no teammate is available to pop for you, and on fast B rushes where timing beats coordination.
The window is narrow: swing within 0.3 seconds of detonation. Wait longer and you are blind longer than the enemy. Right-click underhand at your feet or off the doorframe you are about to peek is the standard self-flash throw.
- Self-flash B tunnels on Dust2 — underhand off tunnel wall, wide swing on pop.
- Self-flash palace on Mirage — bounce off palace wall, swing ramp as white clears.
- Self-flash apps on Inferno — underhand off doorframe, swing into site.
- Never self-flash without a pre-aimed crosshair — you will shoot blind.
- Self-flash without a trade partner is a coin flip — use only when isolated.
Team flash timing and voice protocols
Team flashes fail when throwers and entries are not synchronized on voice. The minimum protocol: thrower calls 'flashing [direction]' two seconds before release, entry confirms 'ready', thrower counts 'three-two-flash', entry swings on detonation. Entries who peek before the call or throwers who release without warning cause team flashes — the most common ranked utility mistake.
Teammates not entrying should look away from the flash origin or hold off-angle positions that avoid line-of-sight to the detonation. Lurkers pushing the same site during a flash execute get blinded and killed — coordinate lurk timing separately.
| Role | Voice call | Action during flash | Common error |
|---|---|---|---|
| Thrower | 'Flashing palace' + countdown | Throw on 'flash' | Silent throw — entry not ready |
| Entry | 'Ready' then swing on pop | Wide swing at detonation | Peeking before pop — dies to AWPer |
| Trade | 'Trading [angle]' | Pre-aim entry angle | Watching flash origin — gets self-blinded |
| Lurk | 'Lurking cat' (separate timing) | Hold off-angle, no flash exposure | Pushing same site during execute |
| IGL | 'Two-flash execute A' | Coordinate both throws | Calling execute without utility check |
Two-flash execute sequences
One flash clears one angle. Good CT setups hold two angles — AWPer long plus site anchor, or pit plus default. Two-flash sequences address both: first flash forces the AWPer off long or into a bad reposition, second flash punishes the site anchor who adjusted toward the first pop.
Space the two flashes 1–2 seconds apart — not simultaneous. Simultaneous flashes blind the same player twice instead of clearing two angles. First flash targets the hardest angle; second flash targets the reposition.
- Flash 1: hardest angle (AWPer, default, pit) — entry swings on pop.
- Wait 1–2 s for CT reposition toward flash 1 origin.
- Flash 2: second angle or repositioned CT — trade fragger swings.
- If both CTs turn away from flash 1, flash 2 catches the turn-back.
- Save a third flash for post-plant only if execute succeeds with man advantage.
Against teams that counter-flash by turning away, vary which angle receives flash 1 across rounds. Predictable flash-1-long every round lets CTs pre-turn. For CT-side counter-flash and anti-push utility, read anti-rush strategies.
Map-specific flash entries: Mirage, Dust2, and Inferno
Learn two to three flash timings per map you ranked queue — not twenty niche lineups. The entries below cover 80% of ranked execute scenarios on the three most common Active Duty maps.
| Map | Entry | Throw | Timing | Deep guide |
|---|---|---|---|---|
| Mirage | Palace A execute | Underhand bounce off palace wall | Entry swings ramp on pop | Mirage guide |
| Mirage | B apps rush | Overhand over apps door | Wide swing door on detonation | Mirage guide |
| Mirage | Mid to connector | Pop flash through mid smoke | Cut connector on blind | Mirage guide |
| Dust2 | Long A take | Pop off long corner wall | Swing long on pop; short flashes cat | Dust2 guide |
| Dust2 | B tunnels execute | Self-flash off tunnel wall | Rush site on pop | Dust2 guide |
| Dust2 | Cat split | Pop flash over cat wall | Cut cat while long player swings | Dust2 guide |
| Inferno | Apps execute | Underhand off doorframe | Wide swing apps on pop | Inferno smokes |
| Inferno | Banana take | Pop flash over sandbags | Swing banana on pop after molly | Inferno smokes |
| Inferno | A short split | Overhand flash over short wall | Split with pit flash backup | Inferno smokes |
CT defensive flashes and counter-flash awareness
CTs use flashes defensively to delay pushes, gather info, and counter T executes. A well-timed CT flash over a smoke forces Ts to turn or eat full blind during a push. Incendiary plus flash on a choke is the core CT anti-rush pattern — flash on contact after molly delay.
When you hear a flash bounce as CT, turn away from the origin or use partial cover. Count flashes — if Ts used two on entry, they have none for post-plant. Off-angle after expected flash timing catches entries who swing on autopilot.
- CT flash over smoke on banana — forces T push delay or blind entry.
- Counter-flash: turn away on bounce, re-peek after 1.5 s when blind fades.
- Off-angle hold after expected flash timing — entries swing on autopilot.
- Count enemy flashes on execute — zero left means weak post-plant.
- Pair CT flash with incendiary on choke — full anti-rush in anti-rush strategies.
Common flashbang mistakes
| Mistake | What happens | Fix |
|---|---|---|
| Silent throw — no voice call | Entry not ready; team flash on lurker | Call 'flashing [dir]' + countdown every time |
| Peek before pop | Die to AWPer holding angle | Swing on detonation sound, not throw sound |
| One flash vs two CT angles | AWPer survives; entry dies | Two-flash sequence — hardest angle first |
| Overhand lob over wall | Self-blind + partial enemy blind | Pop flash off wall at entry range |
| Self-flash without wide swing | Blind longer than enemy | Swing within 0.3 s of detonation |
| Dump both flashes on failed entry | No post-plant utility | Save one flash if execute breaks |
| Same flash timing every round | CTs pre-turn; counter-flash free | Vary flash 1 target and cadence |
| Flash without smoke setup | AWPer sees throw; turns before pop | Smoke angle first, flash second |
Most flash mistakes are communication failures, not mechanical failures. Fix voice protocol first — then drill pop timing in an empty server. For the physics behind why flashes fail at range, review grenade mechanics. For execute structure beyond flashes, cross-reference team communication and map guides for Mirage, Dust2, and Inferno smokes.
Frequently asked questions
How long do flashbangs blind in CS2?
Full blind at direct view and 0–3 m lasts approximately 2–3 seconds. At 5–8 m with direct view, expect 1–2 seconds. At 10 m+ or with off-angle view, blind drops to partial or near-zero. Distance and look angle both matter — see the blind scaling table in this guide.
What is a pop flash in CS2?
A pop flash detonates just as you peek a corner, blinding the enemy holding the angle while you swing from an off-angle that avoids direct flash exposure. Right-click underhand bounces off walls are the standard indoor pop throw. Timing is keyed to detonation, not throw release.
Should I self-flash before entry?
Only when no teammate can pop for you and you have a rehearsed wide swing within 0.3 seconds of detonation. Self-flash is a solo-queue and rush tool — coordinated team pop flashes are safer and produce longer enemy blind.
How do I avoid flashing my teammates?
Call 'flashing [direction]' before every throw. Non-entry players look away from the flash origin or hold off-angles. Never throw while the entry is already wide swinging. Full voice protocols are in our team communication guide.
Why do my flashes not work on AWPs?
AWPers off-angle or at long range take partial blind only. Pop flashes at entry range (under 8 m) with direct line-of-sight produce full blind. Flash through smokes to force AWPs off angle — they cannot turn away from a flash they cannot see coming.
Are flash lineups map-specific?
Yes. Learn two to three flash timings per map you ranked queue — palace and apps on Mirage, long and tunnels on Dust2, apps and banana on Inferno. Map execute context lives in the Mirage guide, Dust2 guide, and Inferno smokes guide.
One flash or two on entry?
Two when CTs hold two angles — AWPer plus site anchor. First flash clears the hardest angle; second punishes reposition. One flash is enough only when you confirm a single anchor via info or earlier round reads.
Conclusion
CS2 flashbangs reward timing and communication over raw throw volume. Pop flashes at entry range produce full blind; lob throws at distance produce fakes at best. Call every throw, run two-flash sequences against double setups, and save one flash for post-plant.
Next reads: grenade mechanics for Source 2 physics, Inferno smokes and Dust2 / Mirage guides for execute context, config binds for jump-throw setup, and team communication for execute callouts.