Does Reduce Motion Break Springy Overlay UIs?

A spring-physics open animation on a clipboard shelf is a designer's delight. The shelf slides in from the edge, overshoots by a few pixels, settles back, and rests. On a 60 Hz display the overshoot reads as a single, smooth gesture. On a 144 Hz display it reads as a distinct bounce, and for a small subset of users it produces vestibular discomfort — a brief, sub-second sensation of motion sickness that is not severe but is real. The fix is older than the problem: Windows has a Reduce Motion setting under Accessibility, and well-behaved applications honor it. When the setting is on, the spring is replaced by a simple fade or a no-animation instant open. This guide covers what the Reduce Motion setting does, how applications should detect it, and what to do for users who want the bounce off regardless of the setting.

For neighbouring topics, see quiet hours: sound effects on a clipboard app and always-on-top apps that fight each other.

What the Reduce Motion setting does

Windows exposes a Reduce Motion setting under Settings → Accessibility → Visual effects. When enabled, the setting instructs the OS to minimize animations: window open/close animations become instant or near-instant, the Win+Tab view transitions more abruptly, and the taskbar slide animations are shortened. The setting is part of the broader accessibility surface that also includes Remove Animations, Hide Scrollbars, and Transparency Effects.

The Reduce Motion setting is distinct from the older "Show animations in Windows" toggle that appeared under the same settings page in earlier Windows 10 builds. In Windows 11 the two are unified under the Visual effects page; turning animations off disables both the OS animations and the signal that applications use to detect the preference.

Applications detect the preference by calling SystemParametersInfo with the SPI_GETCLIENTAREAANIMATION parameter, or by reading the UserPreferences flag in the registry. The recommended approach is SystemParametersInfo, which is the supported API and works across Windows versions.

How applications should respond

A well-behaved application calls SystemParametersInfo(SPI_GETCLIENTAREAANIMATION, ...) on startup and again on the WM_SETTINGCHANGE message with the SPI_SETCLIENTAREAANIMATION parameter. The result is a boolean: animations are enabled or disabled. When animations are disabled, the application should:

• Replace spring physics with a linear or ease-out animation. A 200 ms fade-in is acceptable; a spring is not.
• Shorten the animation duration. A 200 ms fade is fine; a 600 ms fade is excessive.
• Remove parallax and depth effects. Parallax on scroll, depth on hover, and other effects that imply motion should be removed.
• Remove the bounce. The overshoot-and-settle that defines a spring is the most vestibularly problematic element and should be the first to go.

The application should not require the user to configure this separately; the OS-level setting is the source of truth, and the application should follow it.

Why springs specifically

Spring physics animations are particularly prone to causing vestibular discomfort because they imply a deceleration that the user's eyes do not experience. The user's eyes track the shelf as it slides in; the shelf overshoots and the eyes have to reverse direction to follow; the shelf settles and the eyes have to reverse again. The mismatch between the visual motion and the absence of bodily motion is the same mismatch that produces motion sickness in cars and boats.

The effect is small for a single open animation. It compounds when the shelf is opened frequently — 50 times per hour during active work is enough for sensitive users to notice a low-grade discomfort by the end of the day. Users who have reported vestibular issues with macOS's spring-heavy UI are the same users who report issues with Windows spring UIs.

Linear and ease-out animations do not have this problem. They imply a single deceleration, which the eyes track smoothly. The user may not even notice the animation, which is the right outcome for a tool that is supposed to be invisible.

How to disable springs in your shelf

For users who want springs off regardless of the OS setting, three patterns exist:

• The shelf's own settings. A well-designed shelf exposes an "Animation style" setting with options like "Spring," "Fade," and "None." The user picks one and the shelf respects it.
• The OS Reduce Motion setting. The user enables Reduce Motion in Windows settings, and the shelf follows. This is the recommended pattern; it is the user's existing preference and the shelf should honor it.
• A registry override. Some shelves read a registry key under HKCU\Software\<vendor>\<app> to override the OS setting. This is the least user-friendly pattern and should be a last resort.

For Framer Motion specifically — the animation library Edge-Drop uses — the spring can be replaced with a tween by passing type: "tween" instead of type: "spring". The tween can use an ease-out curve over 200 ms, which is visually similar to a spring without the overshoot. Framer Motion also exposes a useReducedMotion hook that reads the OS preference directly; using it is the recommended pattern.

What can go wrong

• The shelf uses spring physics and does not check the OS setting. Symptom: the shelf bounces on every open, even with Reduce Motion enabled. Fix: the shelf should call SystemParametersInfo(SPI_GETCLIENTAREAANIMATION, ...) and disable the spring when the setting is off.
• The shelf checks the setting on startup but does not re-check on WM_SETTINGCHANGE. Symptom: changing the OS setting does not take effect until the shelf is restarted. Fix: handle WM_SETTINGCHANGE and re-query the setting.
• The shelf replaces the spring with a 600 ms fade. Symptom: the shelf feels sluggish, even with springs off. Fix: shorten the fade to 200 ms or less.
• The shelf removes all animation, including the open/close fade. Symptom: the shelf appears and disappears with no transition, which can be jarring. Fix: keep a short fade even with springs off; only the spring itself is the problem.

Multi-monitor and transparency interaction

The Reduce Motion setting interacts with two other settings: transparency effects and multi-monitor behaviour. When transparency effects are off (also under Accessibility → Visual effects), the shelf's transparent background becomes opaque, which is a separate visual change but does not affect animation. When the shelf is on a multi-monitor setup, the animation should be consistent across monitors — the shelf should not bounce on one monitor and fade on another.

For the multi-monitor discussion, see clipboard tools on multi-monitor Windows setups and always-on-top apps that fight each other.

The high-refresh-rate multiplier

A spring that reads as a single smooth gesture at 60 Hz becomes a visibly discrete bounce at 144 Hz or 240 Hz. The same code, the same physics, produces a different visual result because the frame rate changes how the overshoot is sampled. Users on high-refresh-rate gaming monitors report the bounce as more pronounced even when the spring parameters are unchanged from a 60 Hz reference machine.

The clean answer is to tune the spring against the monitor's reported refresh rate, or to ship a spring that is subtle enough to remain subtle at 240 Hz. For the related discussion of refresh rate and hover behaviour, see high refresh pointers and hover dwell times.

Honest positioning

Edge-Drop, the Windows hover-activated clipboard shelf, uses Framer Motion for its open and close animations. The shelf honors the OS Reduce Motion setting via Framer Motion's useReducedMotion hook, which replaces spring physics with a tween when the setting is on. The shelf does not currently expose a per-user "animation style" setting; the assumption is that the OS setting is the source of truth and the shelf should follow it. For users who want springs off regardless of the OS setting, the recommendation is to enable Reduce Motion in Windows, which is the supported way to express the preference and which other applications will also honor. The shelf's springs are tuned to be subtle (small overshoot, short duration) even when the setting is off, to minimize the vestibular impact for users who do not enable Reduce Motion.

What to check

If your shelf's animations are causing discomfort, work through these:

1. Open Settings → Accessibility → Visual effects.
2. Turn off "Animations" (or "Show animations in Windows," depending on Windows version).
3. Open the shelf and observe the animation. The spring should be replaced by a fade or instant open.
4. If the spring persists, the shelf is not honoring the OS setting. Check the shelf's own settings for an animation option.
5. If the shelf has no animation option and does not honor the OS setting, replace the shelf with one that does.

The right answer is for the shelf to honor the OS setting without requiring a per-app configuration. Shelves that do not honor the OS setting are accessibility regressions and should be reported to the vendor.

Background for this constraint is Integrated GPUs and Transparent Windows.

Related reading

• Always-On-Top Apps That Fight Each Other
• Integrated GPUs and Transparent Windows
• Clipboard Tools on Multi-Monitor Windows Setups
• Win+V Not Working on Windows 11: 9 Fixes

Sources

• Microsoft Learn — SystemParametersInfo — Win32 reference for the SPI_GETCLIENTAREAANIMATION parameter that applications use to detect the Reduce Motion setting
• Microsoft Support — Accessibility in Windows — official user-facing guide to Windows accessibility settings, including Visual effects and Reduce Motion
• Microsoft Learn — WM_SETTINGCHANGE message — Win32 reference for the message Windows sends when a system-wide setting changes
• W3C — Animation and motion sickness guidance — W3C WCAG 2.1 guidance on animation from interactions and the vestibular disorder accessibility requirement
• Framer Motion — useReducedMotion — Framer Motion documentation for the hook that reads the OS reduce-motion preference

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support