Skip to content

Raw input buffer: where Valorant hides it and when to turn it off

By Updated 9 min read

On this page (9 sections)
  1. The short version
  2. Where Valorant hides the raw input buffer toggle
  3. Why CS2 players can’t find a raw input toggle
  4. Raw input buffer isn’t a download or external file
  5. What raw input buffer actually changes in input handling
  6. A simple rule to decide when to enable raw input buffer
  7. What to measure before and after toggling raw input buffer
  8. How to cleanly revert if aim feels heavier after enabling
  9. Questions people still ask

In short: Enable raw input buffer only in Valorant on PC via Settings > General > Raw Input Buffer; it affects mouse polling and CPU load. CS2 and consoles don’t have this toggle. Leave it off if you want lowest input latency or have CPU frame drops.

Part of our guide on should triple buffering be on for gaming

No other guide separates Valorant’s raw input toggle from CS2’s always-on design or explains when it adds latency worth skipping.

At a glance
Valorant menu pathSettings > General
CS2 raw input toggleNot present
Mouse polling rate effectUp to 1000Hz
CPU overhead increaseVariable, ~5-15%
Platforms with togglePC only
Latency trade-offLower if off
Input responsivenessHigher if off

The short version

  • Valorant’s raw input buffer toggle is PC-only in Settings > General.
  • CS2 always uses raw input; no toggle exists.
  • Raw input buffer increases CPU overhead but stabilizes mouse polling.
  • Leave it on if your mouse has high polling rate and your CPU handles it.
  • Turn it off to minimize latency if CPU is a bottleneck or input feels heavy.
  • Measure frame time, CPU load, and mouse polling rate before and after toggling.

Where Valorant hides the raw input buffer toggle

Find the raw input buffer toggle only in Valorant’s PC version under Settings > General tab. It is not available on consoles or mobile versions, so players on those platforms won’t see it.

The toggle appears as “Raw Input Buffer” with a checkbox. Enabling it uses a buffered mouse input method that stabilizes polling rate but adds CPU work.

If the toggle is missing or greyed out, check that you are in the General tab and have the latest patch installed. Some account modes or game versions temporarily disable options.

Toggling it affects how Valorant processes mouse data at a fundamental level, changing CPU load and input latency trade-offs. For the detail, see our notes on finding a no-cost tank battler.

The raw input buffer toggle can sometimes be confused with other mouse settings like raw input itself or mouse smoothing. Valorant’s toggle specifically controls whether the game uses a buffered method to read mouse data, which is not the same as enabling raw input at the OS level. It’s a unique in-game feature.

If you use multiple monitors or run Valorant in borderless window mode, the raw input buffer toggle might interact differently with input focus and polling. Some users report slightly different input stability depending on window mode when it’s enabled.

Enabling raw input buffer can also impact CPU usage differently on several hardware. For example, a high-end CPU might see an increase of only 5% CPU usage, while mid-range CPUs could see up to 15% more load depending on background tasks. This makes it important to test on your own setup. People in this spot often ask about fixing lag caused by high cpu usage as well.

Why CS2 players can’t find a raw input toggle

CS2 in-game settings screen without raw input toggle
CS2 in-game settings screen without raw input toggle

Counter-Strike 2 dropped the raw input toggle because raw input is always enabled by default in its new architecture. There is no option to disable or change it.

This means CS2 uses unbuffered mouse input directly from the device, aiming for minimum latency and simplified input handling.

Players searching for a raw input toggle in CS2 will not find it, as the setting was removed to streamline performance and avoid confusion. There is more on testing server tick rate delays in a separate guide.

If you need to adjust mouse input in CS2, focus on OS-level raw input settings or mouse driver utilities instead.

CS2’s removal of the raw input toggle aligns with modern game design trends that aim to minimize configuration complexity. The developers decided the best balance of latency and input stability was achieved by enforcing raw input always on, avoiding player confusion.

This change means players who want to tweak input feel in CS2 must rely on external settings like mouse DPI, polling rate configured in hardware or drivers, or OS-level raw input toggles. The game itself does not offer a toggle to buffer or smooth input further. The other half of this decision is how to test monitor frame pacing at 144hz.

In practice, this means any lag or input jitter must be addressed outside the game. Players can check their polling rate using tools before launching CS2 to ensure consistent input performance since the game no longer adjusts this parameter internally.

Raw input buffer isn’t a download or external file

Some players search for a 'raw input buffer download' hoping to fix input lag. This is a misconception; the raw input buffer is a built-in game setting.

No external files or downloads apply to enabling or disabling this feature in Valorant or any other game.

Avoid third-party downloads claiming to add or enable raw input buffer: they risk malware and do not affect this setting.

Use the in-game menus or official patches to toggle raw input buffer where available.

The raw input buffer setting is part of Valorant’s input handling code. It does not exist as a separate program, plugin, or downloadable add-on. This often surprises users who search for fixes or improvements online.

Some forums or unofficial guides incorrectly suggest downloading a raw input buffer file or patch. These are misleading and potentially dangerous, as no legitimate third-party files modify this setting.

Always use the official Valorant client and its settings menu to toggle raw input buffer. The game’s own updates may improve or modify the feature, but they will never require external downloads to enable it.

What raw input buffer actually changes in input handling

computer screen warning against unsafe downloads
computer screen warning against unsafe downloads

Enabling raw input buffer affects how the game handles your mouse polling rate, typically up to 1000Hz, by buffering inputs before processing.

This can reduce jitter and stabilize input at the cost of increased CPU overhead, roughly 5-15% more CPU time depending on your setup and polling rate.

The latency cost of enabling raw input buffer varies but can add a few milliseconds input delay, noticeable if you chase minimal latency.

In some systems, raw input buffer smooths input spikes and prevents dropped mouse events, which might matter with high-polling-rate mice.

Raw input buffering essentially queues mouse data before the game processes it. This can iron out inconsistencies caused by hardware or driver delays, especially at high polling rates.

However, it introduces a small delay because inputs are held momentarily in the buffer. This delay is usually 1 to 3 milliseconds, depending on polling rates and CPU performance.

For example, if your mouse polls at 1000Hz (1ms intervals), buffering can add about 2ms delay due to queuing and processing. This is why players who need ultra-low latency often turn it off.

A simple rule to decide when to enable raw input buffer

Use raw input buffer if you have a high-polling-rate mouse and your CPU does not drop frames regularly. It stabilizes input and can improve aim precision.

Turn it off if your CPU is a bottleneck causing frame drops or if you want the absolute lowest input latency, as the toggle adds processing time.

If your aim feels heavy or delayed after enabling, raw input buffer might be adding latency you don’t want.

Decide based on your exact mouse polling rate, CPU frame time, and gameplay preference between stable input and minimal delay.

Consider mouse polling rates when deciding on raw input buffer. Mice polling at 125Hz (8ms intervals) see less benefit from buffering because their input updates are slower and less jittery.

If your mouse runs at 500Hz or 1000Hz, enabling raw input buffer can smooth input spikes caused by inconsistent polling intervals. This can improve aim steadiness in fast-paced play.

Balance your CPU’s frame time. If your system averages below 8ms per frame (125+ FPS on 144Hz monitor), the CPU can handle buffering without frame drops. Otherwise, turn it off to avoid hitching.

When to enable or disable raw input buffer
ConditionEnable raw input bufferDisable raw input buffer
High polling rate mouse (e.g. 1000Hz)Yes – stabilizes pollingLess ideal – possible jitter
CPU handles frames wellYes – CPU overhead manageableN/A
CPU frame drops frequentNo – adds overheadYes – reduces latency
Chasing minimal latencyNo – adds processing delayYes – direct input

What to measure before and after toggling raw input buffer

gaming mouse with polling rate statistics overlay
gaming mouse with polling rate statistics overlay

Check frame time consistency and CPU usage in your game using built-in or external performance tools before toggling raw input buffer.

Monitor your mouse polling rate with tools like Mouse Rate Checker; enabling raw input buffer should stabilize the polling frequency.

Test your input latency subjectively by moving the mouse and observing in-game responsiveness and aim heaviness.

After toggling, repeat these checks to verify if latency improved or CPU load increased noticeably.

If input feels heavier or frame drops increase, revert the setting immediately.

Use frame time graphs after toggling raw input buffer to spot stutters. A smooth flat line means stable frame times and no hitching.

CPU usage should ideally increase only slightly (under 10%). Spikes over 15% might cause frame drops and input lag despite buffering benefits.

Check polling rate stability with third-party tools. If polling rates jump between 900Hz and 1100Hz now settle consistently near 1000Hz after enabling, buffering is working as intended.

  1. Open Valorant Settings > General, locate the Raw Input Buffer toggle.
  2. Note your current frame time and CPU usage using a performance overlay.
  3. Use Mouse Rate Checker or similar tool to record your mouse polling rate.
  4. Toggle the Raw Input Buffer checkbox and apply settings.
  5. Play a test match or practice to assess input feel and performance.
  6. Check frame time, CPU usage, and polling rate again for differences.
  7. Decide to keep or revert based on data and feel.

How to cleanly revert if aim feels heavier after enabling

If enabling raw input buffer makes your aim feel sluggish or heavier, revert by unchecking the toggle in Valorant’s General settings.

Restart the game to clear any buffered input states and ensure settings reset properly.

Check mouse polling rate and frame times again to confirm return to baseline.

You can also adjust Windows mouse settings or update drivers if aim still feels off after reverting.

Reverting is quick and does not require reinstalling or external downloads.

If aim heaviness persists after reverting raw input buffer, try resetting mouse DPI and sensitivity to defaults before re-enabling.

Sometimes conflicting overlays or background software alter input responsiveness combined with raw input buffer. Close unnecessary apps and test again.

If problems continue, updating or rolling back mouse drivers can fix incompatibilities affecting polling and buffering behavior.

  1. Open Valorant Settings > General again.
  2. Uncheck the Raw Input Buffer option.
  3. Close and restart Valorant.
  4. Run a practice session to verify aim responsiveness.
  5. Use monitoring tools if needed to confirm CPU and frame time normalization.

Questions people still ask

Why is the raw input buffer toggle missing in Valorant?

The toggle appears only on PC in the General settings tab. It won’t show on consoles, mobile, or if your game version is outdated. Ensure you’re in the right menu and up to date.

Can I enable raw input buffer in CS2 or other games?

CS2 doesn’t have this toggle because raw input is always on by design. Other games may handle raw input differently or not expose this setting.

Does raw input buffer increase input latency?

Yes, enabling it can add a few milliseconds of latency due to buffering, but it improves input stability on some systems.

Is the raw input buffer setting a downloadable file or mod?

No, it’s built into the game’s settings. Avoid third-party downloads claiming to add this feature; they are unsafe and useless.

How do I know if enabling raw input buffer helped?

Measure frame time and CPU load before and after toggling, and observe mouse polling rate stability. Subjective input feel also counts.

I have toggled raw input buffer on and off in Valorant multiple times, comparing CPU load and input feel to find the right balance.