How to Shoot in Valorant on Laptop: The Left-Click Key and Full Input Chain

To shoot in Valorant on a laptop, press the primary mouse button, which is bound to Fire by default. If you are on a trackpad, tap the trackpad surface with one finger. The keyboard does not contain a default fire key. Your shots register through a chain: mouse or trackpad input, operating system, Riot client, server tick, then hit registration.

That answer assumes the standard bindings and an unmodified configuration. Most "my gun will not fire" problems trace to one of five links in that chain rather than to the game itself. The sections below walk through each link, the numbers that govern shot timing, and the settings changes that fix the common failures.

What the fire input actually binds to

Valorant separates firing into a primary and an alternate action. Primary Fire sits on Mouse Button 1, the left click. Alternate Fire sits on Mouse Button 2, the right click, and it changes behavior by weapon: it scopes the Operator and Marshal, controls spray for Vandal and Phantom bursts, and triggers the secondary mode on some sidearms. Both bindings live under Settings, Controls, then the Action Bindings list, under the Combat category.

The game reads these as discrete input events, not analog signals. A press generates a down event, and the release generates an up event. For automatic weapons, holding the button keeps the fire state active until release or until the magazine empties. For semi-automatic weapons, each shot needs a fresh down event, so holding the button produces exactly one shot. This distinction explains why new players sometimes think their Vandal is "stuck" when they are actually holding fire on a semi-auto sidearm.

One layer deeper, the input path matters. A USB mouse sends HID reports at a polling rate the device supports, commonly 125 Hz to 1,000 Hz, meaning one report every 8 ms down to every 1 ms. A Bluetooth mouse batches reports and adds latency. A laptop trackpad reports through the operating system's precision touchpad driver, which can coalesce movement and delay taps. The fire command itself only needs a down event, so tap-to-fire on a trackpad works, but the timing precision is far below a mouse.

Why registration depends on the server tick

Valorant servers run at a 128-tick rate, meaning the simulation updates 128 times per second, roughly every 7.8 ms. Your client also simulates locally at a high frame rate, then reconciles with the server. When you press fire, the client sends the input to the server stamped with a timestamp, and the server resolves whether the shot happened before or after other events in that tick window.

This is why hit registration can feel inconsistent on a laptop with unstable performance. If your frame rate collapses during a fight, the client has fewer samples to align your crosshair position with the moment of the fire event. The server still fires the shot, but the position it associates with that shot may lag your visual crosshair. The practical effect is a shot that looks on-target but counts as a miss, or the reverse on the receiving end.

The counterintuitive detail: raising your frame rate can change how a shot feels more than changing your mouse does. At 60 frames per second, a frame lasts about 16.7 ms, longer than two full server ticks. At 144 frames per second, a frame lasts about 6.9 ms, shorter than one tick. The client interpolates between frames, but the density of samples still affects how cleanly your aim and fire events line up. Pros target high, stable frame rates for this reason, not because raw frames win fights by themselves.

Quantified context: weapon timings and input thresholds

Fire rate determines the minimum interval between shots. The Vandal fires at 9.75 rounds per second, so consecutive shots are spaced about 103 ms apart. The Phantom fires at 11 rounds per second, about 91 ms apart. The Operator fires roughly once every 1.5 seconds, about 1,500 ms, and its scope adds a brief equip delay before the shot is ready.

These intervals interact with your input device. A 125 Hz mouse reports every 8 ms, which is far faster than any weapon's fire interval, so polling rate is never the limiting factor for fire rate. The limiting factors are the weapon's own timing and, for semi-automatic weapons, how fast you can generate distinct clicks. A mouse with tactile switches and a short actuation distance helps here; a mushy switch or a trackpad tap adds variability.

Latency stacks across the chain. Display latency, mouse latency, and network round-trip time all add up. A typical wired gaming mouse contributes roughly 1 to 2 ms of click latency. A 60 Hz monitor adds up to about 16.7 ms of display latency. Network round-trip to a nearby server might be 10 to 30 ms. None of these individually breaks shooting, but they compound, and they explain why the same player feels different on different laptops.

The table is qualitative on purpose. Exact latency figures vary by hardware, driver, and firmware, and no authoritative body publishes a single standard for gaming input latency. Treat the ranges as directional.

Edge cases that stop the gun from firing

Laptop users hit a specific set of failure modes that desktop players rarely see. The most common is the function key row. Many laptops map media and brightness functions to the top row and require the Fn key to reach the standard function keys. If you rebound fire to a key that collides with a function-layer action, the press may trigger brightness or volume instead of firing.

Trackpad palm rejection is the second. While typing, the laptop may ignore trackpad input to prevent accidental clicks. If your fire is bound to a trackpad tap and you rest your palm near the pad, the tap can be swallowed. Tapping with a deliberate single finger, away from the palm zone, avoids this.

The third is the Riot client overlay and Windows game mode. Occasionally the game window loses focus or an overlay captures the click. The fix is to run the game in fullscreen, disable unnecessary overlays, and check that the client is the foreground window.

Red-flag warnings:

Do not bind fire to a key that also triggers a laptop function-layer action such as brightness or airplane mode. Do not rely on a trackpad tap for competitive play; palm rejection and driver coalescing create unreliable fire events. Do not assume a wireless mouse is fine if it is Bluetooth; use a 2.4 GHz dongle or wired connection for consistent input. Do not ignore a sudden change in fire behavior after a Windows or driver update; input devices can be remapped silently. Do not rebind fire to the spacebar or another key without checking for conflicts with jump or ability binds.

Misconceptions about the fire key and aim

Several beliefs circulate that do not survive contact with the input chain. The first is that the keyboard has a default shoot key. It does not. Valorant ships with fire on Mouse Button 1 and alternate fire on Mouse Button 2. Any keyboard fire binding is a user change, and it is a common source of confusion when a player follows an old guide that assumed a different layout.

The second is that clicking faster always wins. Fire rate is capped by the weapon, so clicking faster than the weapon's interval does nothing. For automatic weapons, holding fire is correct. For semi-automatic weapons, the cap is your click cadence, and exceeding it wastes clicks without producing shots.

The third is that sensitivity settings change where the bullet goes. Sensitivity changes how far your view rotates per unit of mouse movement. It does not change spread, recoil, or hit registration. A player who blames sensitivity for missed shots is usually describing a crosshair-placement or timing problem.

The fourth is that a higher polling rate or a gaming mouse "aims for you." Input devices reduce latency and jitter. They do not compensate for crosshair placement, counter-strafing, or spray control. The professional caveat here is that equipment improvements have diminishing returns; a stable 144 Hz laptop with a basic wired mouse beats a 60 Hz laptop with premium peripherals for most players.

Practical actions to make fire reliable on a laptop

Work through these steps in order. Each one isolates a different link in the chain.

Confirm the binding. Open Settings, Controls, Action Bindings, Combat, and verify Primary Fire is Mouse Button 1. If you rebound it, note the new key and check it for function-layer conflicts. Test the input device. Fire a weapon in the Range. If it fires, the binding and device are working. If it does not, switch to a wired mouse and retest to isolate the device. Stabilize frame rate. Cap your frame rate slightly below your laptop's sustained average to avoid thermal throttling drops. A stable 120 frames per second beats a fluctuating 60 to 180. Set the display to its native refresh rate in Windows display settings. Many laptops default to 60 Hz even when the panel supports 144 Hz or higher. Disable unnecessary overlays and run the game in fullscreen. Check that the Riot client has foreground focus. For trackpad users, enable tap-to-click only if you must, and practice deliberate single-finger taps away from the palm zone. A cheap wired mouse is a better investment.

Reconciling thresholds: the frame-rate and refresh-rate numbers are separate. Your monitor refresh rate caps how often you see frames, and your frame rate caps how often the client simulates. Match them where possible. A 144 Hz panel with a stable 144 frames per second gives the cleanest alignment between what you see and when your shot registers.

Limitations and what the numbers cannot tell you

The mechanisms above are stable and well understood: discrete input events, a 128-tick server, weapon-specific fire intervals, and latency accumulation. What is not stable is your specific hardware. Laptop models vary widely in trackpad drivers, thermal behavior, and USB controller quality, and those differences change the practical experience more than any single setting does.

Riot does not publish per-device latency figures, and no authoritative body standardizes gaming input latency measurement. Treat any specific millisecond claim about a particular mouse or laptop with caution unless it comes from a controlled, reproducible test. The ranges in this article are directional and drawn from general hardware behavior, not from a single validated dataset.

Finally, shooting is one input in a larger system. Crosshair placement, movement accuracy, and game sense determine most outcomes. The fire key is necessary but not sufficient. Getting the input chain right removes a source of noise so that your actual skill has room to show.