Best osu! Settings: Raw Input, FPS, Offset & More

Most of the settings menu in osu! is cosmetic, but a small cluster of options genuinely changes how the game feels under your hand: how raw your input is, how often the screen updates, and whether the hitsounds line up with the music. Get those three right and everything else is preference. This guide walks through each one with concrete recommendations, then closes with a survival kit for low-end machines. Everything below applies to both the legacy osu!(stable) client and the modern osu!(lazer) client unless noted.

Input: raw input and killing OS mouse acceleration

The single most important toggle for mouse and tablet players is Raw Input (Options > Input). Raw input reads movement data straight from the device and bypasses everything Windows does to your cursor along the way: pointer-speed scaling, smoothing, and acceleration. The result is a 1:1 relationship between physical movement and on-screen movement, which is exactly what you want when your aim is muscle memory.

To disable acceleration at the OS level on Windows: Settings > Bluetooth & devices > Mouse > Additional mouse settings > Pointer Options tab, then uncheck "Enhance pointer precision." While you are there, set the pointer speed slider to the 6th of 11 notches (the exact middle). 6/11 is the only setting at which Windows applies a 1:1 pixel multiplier with no rounding, so it is the most accurate option for desktop use.

Cursor sensitivity vs. raw sensitivity

In-game the "Cursor sensitivity" / "Raw input sensitivity" slider scales movement on top of your hardware. The overwhelming community consensus for mouse players is to keep this at 1.00x and do all sensitivity changes through your mouse DPI instead. A high in-game multiplier amplifies sensor jitter; a low one throws away resolution. Pick a DPI you like (800 is the de-facto standard), set the slider to 1.00x, and leave it.

Tablet area basics

Graphics tablets are absolute-positioning devices: a spot on the tablet maps to a spot on the screen, with no acceleration ever. The thing to configure is the active area. A smaller area means a larger cursor-to-hand ratio (faster, twitchier, more forgiving of small wrist movement); a larger area means more arm travel and finer control. Beginners should start somewhere in the 40-60mm width range and shrink it over weeks as their hand learns the map. Always lock the aspect ratio to your monitor (16:9) so circles do not feel stretched horizontally, and disable any driver-level smoothing/filtering for the lowest latency.

• Mouse: Raw Input ON, in-game sensitivity 1.00x, DPI 800, Windows accel OFF, pointer speed 6/11.
• Tablet: lock area to 16:9, start ~50mm wide, shrink gradually, disable driver smoothing.
• Never stack two sensitivity multipliers (DPI x in-game x driver) — pick one source of truth.

FPS: unlimited vs. frame limiter vs. "Reduce dropped frames"

Higher frame rates lower the delay between a movement and seeing it on screen, which is why osu! players obsess over FPS. But chasing literally unlimited frames is counter-productive: the overhead of allocating and garbage-collecting a frame thousands of times per second causes stutter, heat, and on laptops, throttling. The clients reflect this. In osu!(lazer) the option formerly called "Unlimited" was renamed "Basically Unlimited" and now caps draw and update at 1,000 Hz, because nothing useful happens above that — input hardware itself only polls at 125-1,000 Hz.

osu! exposes frame limiters as multiples of your monitor refresh rate (2x, 4x, 8x). The 8x option targets eight times your refresh, capped at 960 FPS, and is the sweet spot for most people: very low input latency without pinning the GPU at maximum. On stable, the equivalent labels are "VSync," "60fps (power saving)," "120fps," "240fps," and "Unlimited."

The "Reduce dropped frames" toggle (stable) prioritises consistent frame pacing over the absolute lowest latency. If your gameplay feels jittery — frames arriving unevenly even at a high average FPS — turn it on; the tiny latency cost is worth the smoothness. If your hardware is comfortable and frames are already even, leave it off. osu!(lazer) ships a Latency Certifier mini-game that has you pick which of two panels feels more responsive; it then recommends the lowest limiter you can actually perceive, so you stop wasting hardware on frames your eyes cannot use.

Audio offset: the calibration nobody does (and should)

Every audio chain — your headphones, DAC, Bluetooth stack, monitor speakers — introduces a small delay between when the game decides a sound should play and when you hear it. If hitsounds feel consistently late or early across every single map, that is your universal (global) offset, and it is fixable in one place.

"

If the music feels off on one map, fix that map. If it feels off on every map, fix the universal offset.

The universal offset shifts the appearance of hit objects relative to the audio for all beatmaps at once. Negative values move gameplay earlier; positive values move it later. The cleanest way to set it is the built-in Offset Wizard (lazer) / offset calibration in stable, which plays a metronome and asks you to tap along; the client measures your average error and suggests a value. Re-run it whenever you change audio devices, because wired headphones and a Bluetooth headset will not share the same number.

Per-map (local) offset

Some maps are simply mapped or timed slightly off, or were encoded with a small lead-in. For those, use the local offset, which is stored per-beatmap and stacks on top of the universal offset to produce the total offset. During gameplay you can nudge it with the +/- keys (default), or set it from the beatmap options. Rule of thumb: only ever touch local offset for the one map that feels wrong; if many maps feel wrong, the universal offset is the real culprit.

Gameplay feedback: the toggles worth turning on

• Hit error bar (error bar) — ON. The single best practice tool: shows early/late tendency in real time so you can fix timing and offset.
• Always show key overlay — ON. Confirms taps register and exposes accidental double-taps; essential for diagnosing missed inputs.
• Background dim — 70-90%. High dim improves note readability on busy backgrounds; lower it only if you genuinely play better with art visible.
• Snaking sliders (sliders snake out as they appear) — preference; OFF can slightly improve readability on dense maps. In lazer, sliders also snake while you drag them in the editor, which cannot be reverted via Classic mod.
• Show approach circle on first hidden object — ON if you play Hidden, so you have one reference circle to anchor timing.

Low-end PC survival kit

If you are on integrated graphics or an old laptop, the goal is consistent frames, not maximum frames. A steady 144 FPS beats a spiky 400. Work down this list until gameplay is smooth.

Finally, give your settings a few days before judging them. Raw input, a fresh offset, and a new frame cap all feel "wrong" for an hour because your timing was compensating for the old behaviour. Lock the configuration in, play normally, and let the hit-error bar tell you the truth.