-webkit-overflow-scrolling worked on Safari iOS 5 to 12 and Samsung Internet 5 to 19. iOS 13 removed it. Learn the values, deprecation, and alternatives.

Prince Dewani
May 6, 2026
-webkit-overflow-scrolling is a non-standard WebKit CSS property that controls momentum-based scrolling on touch devices. It works in Safari iOS 5 to 12, Samsung Internet 5 to 19, and Android WebView 4.4, while Chrome, Edge, Firefox, and Opera on desktop never added support, and Apple removed the effect in iOS 13.
This guide covers what -webkit-overflow-scrolling is, the browsers that support it, the auto and touch values, the deprecation in iOS 13, the modern alternatives, and the known issues.
-webkit-overflow-scrolling is a CSS extension that the WebKit team added to control whether a scrollable element uses momentum-based scrolling on a touch device. It accepts two values, auto and touch, and shipped only on iOS Safari, Samsung Internet, and the Chromium-based Android WebView.
Only iOS Safari, Samsung Internet, and the Android WebView ever shipped -webkit-overflow-scrolling. Every desktop browser ignored it, and modern iOS Safari has removed the effect.
Chrome does not support -webkit-overflow-scrolling on Windows, macOS, Linux, ChromeOS, or Android. Blink ignores the property silently, and Chrome already paints native momentum scrolling on every overflow:auto and overflow:scroll element on touch hardware. No flag in chrome://flags turns the property on.
Microsoft Edge does not support -webkit-overflow-scrolling on any version. Chromium-based Edge 79 and later inherit Blink's behavior and ignore the property. Legacy EdgeHTML versions, Edge 12 to 18, also lacked support, and Edge on iOS rides on the WebKit engine that has already removed the effect.
Firefox does not support -webkit-overflow-scrolling on any desktop, ESR, or Android release. Mozilla never added the WebKit prefix and there is no about:config flag to turn it on. Gecko paints its own momentum scrolling natively on Firefox for Android, so no rule is required.
Safari on macOS never supported -webkit-overflow-scrolling, since the property only ever shipped in mobile WebKit. Safari on iPhone and iPad supports the property from Safari 5 on iOS through Safari 12 on iOS 12. Apple removed the effect in Safari on iOS 13 and later, where the property still parses but does nothing on the page.
Opera does not support -webkit-overflow-scrolling on Windows, macOS, Linux, or Android. Opera 15 and later inherit Blink and ignore the property. Opera Mini renders pages on a server proxy, so the rule never reaches the device. Opera Mobile does not paint a custom momentum effect either.
Samsung Internet supports -webkit-overflow-scrolling from Samsung Internet 5 through Samsung Internet 19 on Galaxy phones and tablets. Samsung Internet 4 did not recognize the property. Newer Samsung Internet builds ride on the same Chromium upgrade that dropped the effect, so they parse the rule but ignore it.
The legacy Android Browser supports -webkit-overflow-scrolling from Android 3.0 through Android 4.4 on the AOSP WebKit engine. Android WebView switched to Chromium in Android 4.4, after which the property is parsed but ignored. Chrome for Android and Firefox for Android have never supported it.
Internet Explorer does not support -webkit-overflow-scrolling on any version, from IE 6 through IE 11. Microsoft has retired Internet Explorer. Trident has its own scrollbar model and never adopted the WebKit prefix, so the property is dead code on every IE-mode user still on Windows.
Note: -webkit-overflow-scrolling behaves differently on iOS Safari, Samsung Internet, and Android WebView, and is dead code on every desktop engine. Test it on real browsers and OS with TestMu AI. Try TestMu AI free!
-webkit-overflow-scrolling accepts two values, auto and touch. Each one tells mobile WebKit how to handle the scroll after the user lifts their finger.
The snippet below shows the legacy iOS pattern, an explicit auto opt-out, and the modern overscroll-behavior replacement. Paste it into a stylesheet and the rules take effect on the next paint.
/* Legacy iOS pattern: turn on momentum scrolling on a vertical list. */
.scroll-list {
overflow-y: auto;
-webkit-overflow-scrolling: touch;
}
/* Disable momentum scrolling on a panel. The scroll stops the moment the finger lifts. */
.no-momentum {
overflow-y: auto;
-webkit-overflow-scrolling: auto;
}
/* Modern replacement: native momentum plus a clean overscroll boundary. */
.feed {
overflow-y: auto;
overscroll-behavior-y: contain;
}-webkit-overflow-scrolling is non-inherited, has no shorthand, and has no animation type. Setting touch on a child of overflow:hidden has no effect, since the child is not a scrollable element to begin with.
Yes. -webkit-overflow-scrolling is deprecated and the effect is gone from modern WebKit. Apple removed the implementation in Safari on iOS 13 and later, and the Safari 13 release notes describe the change directly.
Drop the property and lean on the browser. Modern Safari, Chrome, Firefox, and Edge paint momentum scrolling on overflow:auto and overflow:scroll without any opt-in. For finer control over the scroll edge, use standard CSS that every modern engine supports.
-webkit-overflow-scrolling has the smallest cross-browser footprint of any CSS scroll control. The painful edge cases land on iOS Safari, fixed positioning, and the new stacking context the touch value creates.
In my experience, the cleanest cross-browser pattern is to remove -webkit-overflow-scrolling entirely from new stylesheets and pair overflow: auto with overscroll-behavior: contain. Modern iOS Safari paints momentum natively, every Chromium and Firefox build does too, and the bounce control lands on a standard property that a linter will not flag.
All -webkit-overflow-scrolling version numbers and platform notes in this guide come from these primary sources:
Did you find this page helpful?
More Related Hubs
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance