4 Jul 2026

Raw Input Explained for Valorant, CS2, and FPS Games

Raw input lets a game receive mouse movement more directly from the device instead of relying only on the normal Windows pointer path. For FPS games, that usually means you should turn raw input on when the option exists, then tune DPI and in-game sensitivity from there.

That is the clean version. The messy version is that every game labels input settings differently. Valorant, CS2, Apex, Overwatch, and aim trainers may expose raw input, raw input buffer, mouse smoothing, or no visible option at all.

If you are cleaning up your setup, start with the broader best mouse settings for gaming, then use this guide to understand what raw input is actually doing.

Key Takeaways

  • Raw input helps games read mouse movement more directly than normal pointer messages.
  • In supported FPS games, raw input should usually be on.
  • Raw input does not replace good DPI, eDPI, polling rate, or frame pacing.
  • Windows settings still matter for menus, launchers, desktop tests, older games, and games without raw input.

The Short Answer: Turn Raw Input On When It Is Stable

For most FPS players, raw input should be on if the game offers it. It gives the game a cleaner path to mouse movement, but it will not fix bad sensitivity, a weak wireless connection, a dirty sensor, or stuttering frames.

Use this starting point:

SettingRecommendation
Raw inputOn, if available
Mouse accelerationOff in Windows
Mouse smoothingOff, unless the game requires it
DPIOne known value
In-game sensitivityTune with eDPI

After changing raw input, test in a practice range or aim trainer. Do not judge it from one fight where your FPS dropped or your hand was cold. Input settings need repeatable testing.

What Raw Input Actually Means

Microsoft Learn describes raw input as a way for Windows applications to receive and process device input. For mice, raw input can use WM_INPUT messages, while normal pointer movement can use WM_MOUSEMOVE.

That sounds dry, but the gaming meaning is useful:

  • WM_MOUSEMOVE is good for a normal desktop pointer.
  • WM_INPUT is better for high-definition mouse movement in games.
  • Pointer acceleration can be applied to normal pointer movement.
  • Raw mouse data is better for an FPS camera because it preserves more direct movement.

Microsoft’s high-definition mouse movement article says WM_INPUT data is read directly from the Human Interface Device stack and reflects high-definition results. It also notes that normal pointer movement receives Windows pointer behavior, which is useful for desktop cursor control but not ideal for a first-person camera.

In plain English: a desktop cursor and an FPS camera are not the same job. A cursor should feel comfortable across Windows. A camera should respond consistently to mouse deltas.

Raw Input vs Windows Pointer Speed

Raw input is not the same as Windows pointer speed. Windows pointer speed changes desktop cursor movement. Raw input is an input path a game can use to read device movement more directly.

This is why your FPS sensitivity may feel unchanged when you change Windows pointer speed in a raw-input game. The game may be using mouse movement separately from the desktop cursor.

Still, do not use that as an excuse to leave Windows settings messy. Keep your Windows pointer setup stable because not everything uses raw input:

  • Game menus can behave differently from gameplay.
  • Launchers and overlays use desktop pointer behavior.
  • Browser-based tools depend on pointer behavior.
  • Older games may not expose raw input.
  • Some aim trainers let you choose input modes.

If Windows pointer speed is the part confusing you, read Windows pointer speed for gaming. If acceleration is still on, fix that first with turn off mouse acceleration in Windows 11.

Raw Input in Valorant, CS2, and Other FPS Games

In modern FPS games, the safest assumption is that you want the game reading mouse movement as directly as it can. If the game has a raw input option, start with it enabled.

Valorant players may also see discussions around raw input buffer. Treat that as a game-specific setting, not a universal “better aim” switch. If a buffer option exists, test it in your own setup with your real polling rate and frame rate. Higher polling mice can expose differences that a basic 1000Hz mouse will not.

CS2 players should be careful with old Counter-Strike advice. CS:GO-era console commands, launch options, and forum habits do not always map cleanly to CS2. Use the current settings menu first, keep Windows acceleration off, and test sensitivity in a private server or training map.

For other FPS games, look for settings named:

  • Raw input
  • Mouse input
  • Raw mouse input
  • Mouse smoothing
  • Mouse acceleration
  • Input buffer

If raw input feels worse, test both modes, restart the game if needed, and keep every other setting identical.

Does Raw Input Lower Latency?

Raw input can help avoid unnecessary pointer processing, but total mouse latency is bigger than one setting. Your input chain includes the sensor, firmware, USB polling, wireless receiver, CPU scheduling, game engine, frame rate, display refresh, and monitor response.

That is why a raw-input toggle may feel subtle compared with fixing a bad frame-rate cap or unstable polling rate.

Use this mental model:

LayerWhat it affects
Raw inputHow the game receives mouse movement
Polling rateHow often the mouse reports updates
Frame rateHow often the game can show new input
Display refreshHow often the monitor updates
SensitivityHow much camera movement each mouse movement creates

If your mouse feels delayed, raw input is worth checking. But if the game is dropping frames, the receiver is far away, or the mouse is in Bluetooth mode, raw input will not solve the full problem.

For polling-rate testing, use the Mouse Polling Rate Tester. If a future guide is already on your reading list, how to test your mouse polling rate is the natural next step.

How to Test Raw Input Without Guessing

Do not test raw input in a live ranked match. Use a repeatable routine.

  1. Write down your DPI, polling rate, and in-game sensitivity.
  2. Turn Windows Enhance pointer precision off.
  3. Open the same practice range, map, or aim trainer scenario.
  4. Test raw input on for 10 minutes.
  5. Restart the game if the setting requires it.
  6. Test raw input off for 10 minutes.
  7. Compare tracking, flick recovery, and micro-adjustments.

Keep the test boring. Stand in the same place, use the same weapon, and aim at the same targets.

For Valorant and CS2, include both slow micro-adjustments and fast turns. Raw input issues can show up differently depending on movement speed, polling rate, and frame pacing.

If you cannot feel a difference, leave raw input on if the game behaves normally. The value is not always a dramatic feeling. Often, it is about removing hidden desktop pointer behavior from the chain.

Raw Input Does Not Fix Bad Sensitivity

Raw input can make movement cleaner, but it does not choose your sensitivity. That still comes from DPI and in-game sensitivity.

For FPS games, use eDPI:

eDPI = DPI x in-game sensitivity

Examples:

DPISensitivityeDPI
4000.70280
8000.35280
16000.175280

All three examples land at the same eDPI. Raw input controls how the game receives movement. eDPI controls the final sensitivity scale.

If you are still guessing at sensitivity, use the Mouse eDPI Calculator and then follow a real testing routine. The guide on finding your perfect mouse sensitivity for Valorant and CS2 is where to go after the input path is clean.

When Raw Input Can Feel Worse

Raw input can feel worse if another part of the setup is unstable. That does not always mean raw input itself is bad.

Check these first:

  • Your polling rate is too high for the game or CPU.
  • The game needs a restart after changing input settings.
  • Mouse smoothing is still enabled.
  • Windows acceleration is still enabled.
  • Your wireless receiver is too far from the mouse.
  • Your frame rate is unstable.
  • An overlay or capture tool is interfering.

High polling rates deserve special attention. If the game stutters at 4000Hz or 8000Hz, test 1000Hz before blaming raw input.

A Clean Raw Input Setup

Use this setup if you want a stable baseline:

  1. Set your mouse to one DPI stage, such as 800.
  2. Set polling rate to 1000Hz.
  3. Turn off Windows Enhance pointer precision.
  4. Keep Windows pointer speed consistent.
  5. Enable raw input in the game.
  6. Disable mouse smoothing if the game offers it.
  7. Tune in-game sensitivity with eDPI.
  8. Save the profile.

Once that feels stable, test one change at a time. Try a higher polling rate. Try a slightly different sensitivity. Try a raw input buffer option if the game offers it. Do not change everything at once.

The best mouse setup is not the one with the most exotic settings. It is the one you can reproduce tomorrow.

FAQ

Should raw input be on for FPS games?

Yes, start with raw input on when an FPS game offers it. It usually gives the game a cleaner mouse movement path than normal desktop pointer movement.

Does raw input ignore Windows sensitivity?

It can bypass normal desktop pointer movement for gameplay, but Windows settings still matter outside that path. Keep pointer speed stable and acceleration off.

What is raw input buffer?

Raw input buffer is usually a game-specific setting for how raw mouse input is queued or processed. Test it in the game where it appears rather than assuming it helps every setup.

Does raw input change DPI?

No. DPI is a mouse sensor setting. Raw input changes how the application receives mouse movement.

Sources

Share on