Chrome on Windows

Smooth Chrome mouse-wheel scrolling without changing every app

Chrome can animate scrolling on its own, but a Windows-level profile gives you one place to tune wheel distance, easing, acceleration, and modifier behavior.

Free for supported use cases. No telemetry. Windows 10 and 11 supported.

Short answer

SmoothScroll can smooth mouse-wheel input in Chrome on Windows by processing wheel ticks before Chrome receives them. You can assign Chrome its own profile and keep Ctrl + wheel pass-through enabled so browser zoom remains immediate instead of being stretched across the smoothing animation.

Browser smooth scrolling and system-level smoothing solve different problems

A browser can decide how its own pages react to wheel events. That helps inside the browser, but it does not make File Explorer, VS Code, or another desktop app use the same motion. SmoothScroll operates at the Windows input layer, so the same engine can cover Chrome and the rest of your wheel-driven workflow.

The useful part is not stacking every possible animation. It is choosing one predictable profile. If Chrome already feels good natively, exclude it. If its wheel distance or deceleration feels inconsistent with the rest of your apps, give Chrome a dedicated SmoothScroll profile.

Keep Ctrl + wheel zoom raw

Chrome uses Ctrl + wheel for page zoom. Smoothing those command-style wheel ticks can make zoom feel delayed, so SmoothScroll includes Ctrl + wheel pass-through and an option to clear pending inertia when a modifier is pressed.

That means ordinary page scrolling can remain eased while zoom stays immediate. The same idea applies to design tools and editors that attach commands to modifier-plus-wheel input.

Make Chrome fast enough for navigation and soft enough for reading

For long pages, a moderate step size with a softer tail can reduce the stop-start feeling between notches. For web apps with dense lists or code views, shorten animation time so the viewport settles sooner.

Because the profile is per app, you do not need to compromise between Chrome and a code editor. Tune each for the way you actually use it.

A practical starting setup

  1. 1

    Create or select a profile for Chrome and start with SmoothScroll’s default step size, animation time, and easing.

  2. 2

    Keep Advanced → Pass-through Ctrl + wheel enabled so browser zoom receives raw wheel ticks.

  3. 3

    If Chrome feels too floaty, shorten animation time before increasing scroll distance.

  4. 4

    If you prefer Chrome’s native scrolling, exclude Chrome and use SmoothScroll only in the Windows apps that need it.

Frequently asked questions

Does SmoothScroll replace Chrome’s own smooth-scrolling behavior?

SmoothScroll works at the Windows wheel-input layer rather than changing Chrome’s code. You can use a SmoothScroll Chrome profile, or exclude Chrome if its native behavior already feels right to you.

Will SmoothScroll make Ctrl + wheel zoom lag in Chrome?

It does not have to. SmoothScroll provides Ctrl + wheel pass-through so zoom can receive raw wheel ticks, and it can clear pending inertia when the modifier is pressed.

Can Chrome have different scroll settings from VS Code?

Yes. Per-app profiles let Chrome use one step size, duration, and easing setup while VS Code or another application uses a different profile.

Related Windows scrolling guides