In dev builds of Chrome, they've implemented, refined, and released two-finger swipes left/right in order to browse back/forward in the browser history. Unfortunately, you can accidentally trigger it while you're in the middle of a long down/up scroll, which needless to say occurs often.

I generally like the gesture, and things like Preview, Safari, and other application have implemented it much better, where you cannot blindly navigate back/forward so long as you have begun to scroll up/down.

How do I selectively disable two-finger back/forward navigation in Chrome?

  • 8
    This sounds like a poor implementation on Chrome's part. Have you considered filing a bug? – jtbandes Aug 9 '11 at 22:43
  • Actually, I just tried to reproduce this and it doesn't seem to be happening for me in the latest dev build. Are you sure you're up to date? – jtbandes Aug 9 '11 at 22:45
  • I'm on the latest dev build and I can confirm this error. I would file a bug with the Chrome team. code.google.com/p/chromium/issues/list – Nathan Walker Aug 9 '11 at 23:50
  • If you don't have to be on the dev version, it's less sensitive in the beta channel – bringel Aug 10 '11 at 13:38
  • 3
    That's not a suitable answer by virtue of the fact that (in theory), any other channel will eventually have the current state of the dev channel. – Jason Salaz Aug 10 '11 at 16:37

I know its over a year later, but I had the same question, and then figured out the answer myself.

Open terminal and type:

defaults write com.google.Chrome AppleEnableSwipeNavigateWithScrolls -bool FALSE

Then restart Chrome.

Now you can have it enabled system wide, and just disabled for chrome. By the way, this works for any app, just replace com.google.Chrome with the bundle identifier of the target app.

If your interested in how it works, the AppleEnableSwipeNavigateWithScrolls is the global setting, that can be overwritten for any specified app.

Hope this helps someone in the future.

  • 21
    Oh yes. Oh my god yes. This is EXCELLENT. It helped me, NOW. THANK YOU! – Jason Salaz Jan 28 '13 at 3:00
  • 13
    I want to create a hundred accounts just to keep upvoting this answer as many times as humanly possible. – Scott Jul 16 '13 at 13:11
  • 19
    This no longer works. Chrome 30 on Mavericks. The other system preferences solution does work: apple.stackexchange.com/a/28998/8041. – timoxley Nov 4 '13 at 3:36
  • 7
    Works for me on Mavericks without the .plist – Billy Moon Nov 12 '13 at 11:06
  • 6
    Tried this in Yosemite and it doesn't seem to work (even after restarting Chrome). This is super annoying - especially when I am entering information (say, writing an answer on SE), and scroll to check something - it's rather easy to end up going back, and losing your edit. Does this answer need an update for Yosemite? – Floris Dec 29 '14 at 15:52

I went into the System Prefs and changed the Page change gesture from two fingers to three (OSX Lion). The three finger swipe seems to be more responsive at any rate and I'm usually only using two fingers for everything else.

System Preferences > Trackpad > More Gestures > Swipe between pages

  • 24
    ...this works, though you're also changing the setting for every other app (including Preview). I like this solution and it's what I'm doing, but I'm hoping the Chrome people will read this thread and see that they need to offer a fix within the browser. – Eric Mar 27 '12 at 17:04
  • 1
    Also works for Mountain Lion. – Nakilon Aug 4 '13 at 16:56
  • 3
    IMHO this is a better solution than changing the Chrome defaults with the command line command. – Steve Bennett Nov 26 '14 at 2:13
  • 2
    Works in Mavericks when the command line option did not. – atwixtor Dec 12 '14 at 15:12
  • Works fine in Yosemite also. Some people might like the swiping/gesture stuff but I don't really, so I changed it to three-finger swipe (which should avoid false positives). – Per Lundberg Jul 23 '15 at 19:59

There are two different properties, one is for the Trackpad: AppleEnableSwipeNavigateWithScrolls, the other is for the Mouse/Magic Mouse: AppleEnableMouseSwipeNavigateWithScrolls.

So you need to execute one or both of these commands:

$ defaults write com.google.Chrome AppleEnableMouseSwipeNavigateWithScrolls -bool false
$ defaults write com.google.Chrome AppleEnableSwipeNavigateWithScrolls -bool false
  • Thanks so much for this! Couldn't figure out for the life of me why this was working for everyone else but me—it was because I'm using a Magic Mouse and needed AppleEnableMouseSwipeNavigateWithScrolls. – Derek Shockey Apr 10 '19 at 19:57
  • This is the answer needed if you're using an Apple Magic Mouse 2. – Simone Manganelli Aug 29 '20 at 7:29
  • awesome, I almost got crazy about this, when some pages needed vertical scrolling and instead it navigated ... – Karl Adler Sep 5 '20 at 11:30
  • Thanks for this. – Siniša Šašić Nov 11 '20 at 17:57


It looks like Google Chrome uses Apples default gestures, so by disabling Apples gestures you disable Chromes. However, you probably still love some gestures like I do. For that get BetterTouchTools.

Disable Google Chromes Gestures

You can disable chromes gestures by going to System Preference > Mouse OR Trackpad > More Gestures > and uncheck Swipe between pages.

Keep the Gestures You Want

I still love gestures so I downloaded BetterTouchTools which allows me to make the gestures I want. I disabled all apples gestures then created my own. You can get very custom with gestures this way. Or if you prefer, leave some of apples gestures on and use BetterTouchTools for the more custom ones.

  • great, this works. – gilzero Feb 17 '12 at 3:32
  • How do you enable the Swipe between pages gesture for other applications?? The gesture is missing in the BetterTouchTools. – Petr Peller Sep 26 '12 at 13:48
  • @PetrPeller Each application should have its own keyboard shortcut for swiping between pages. In BetterTouchTools you can setup custom gestures for each application. Setup an new application, use whatever gesture you want for a swipe, then enter that applications keyboard shortcut for the gestures action. Make sense? – zechdc Sep 26 '12 at 15:50
  • @zechdc But that way I would have to set up every single application separately and I would miss the animation as the gesture would be translated into keyboard shortcut. It's a pity that the BetterTouchTools can't just disable the 2-finger swipe gesture for Google Chrome and leave default behaviour for different apps. – Petr Peller Sep 26 '12 at 18:04
  • 1
    @DavidAmmouial, true. When I wrote this answer BetterTouchTools was free. I no longer use it because this hasn't been an issue for more anymore. At the time, 9 years ago, it worked well. – zechdc Sep 6 '20 at 3:57

Chrome Canary users should use:

defaults write com.google.Chrome.canary AppleEnableSwipeNavigateWithScrolls -bool FALSE
  • 2
    During my testing the com.google.Chrome.canary.plist should be com.google.Chrome.canary. – darkbaby123 Sep 5 '14 at 3:08
  • I used com.google.Chrome.dev to enable it on the dev version (which now has it disabled by default) thanks for the inspiration – Sodj Dec 14 '20 at 18:40

I also tried the terminal command on Yosemite, it didn't work for me.

And then I tried uncheck "Swipe between pages" in mouse settings, and it worked.

enter image description here

  • 2
    It didn't work for you since you are using a Magic Mouse, and not a Magic Trackpad. Note @Fredy-Muñoz's answer. The instructions in this answer disable the feature for all apps. If this works for you, great. However, in my post / the original Question, I asked about selectively disabling it for Chrome. See the accepted answer or Fredy's for more information. – Jason Salaz Oct 19 '15 at 11:22

The only way I'm currently of is two disable two-finger page swiping system-wide, from the Trackpad section of System Preferences. I wait patiently for Chrome to either fix its implementation, or at least provide an app preference for disabling the feature.

  • 1
    I don't expect them to ever fix this. They've been arguing in favor of an even stupider mis-feature for years, where hitting the [delete] key will go back a page if no fields have focus. From a usability perspective, Chrome is a steaming pile 💩. It's main redeeming factors are (1) a superior Inspector, and (2) more and better extensions. Otherwise it would be worthless. – iconoclast Dec 2 '15 at 23:19

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .