Anker Mouse Button Mapping

How Anker Mouse Buttons Actually Work

Anker mice don't have native button remapping software. That's the first thing you need to understand. The mouse itself is a dumb peripheral — it sends standard HID signals to your computer, and that's it. You remap the buttons using third-party software on your operating system, not anything Anker built into the device. This means your Anker Mouse Button Mapping setup lives entirely in software, which also means it moves with your computer, not the mouse. Here's how I actually do it in practice. I start by checking what the mouse is registering as before I touch any software. I open the native input settings on my OS — on Windows, that's Settings > Bluetooth & devices > Mouse, and I click each button to confirm the OS sees the hardware response. With my M381, the side buttons registered as mouse 4 and mouse 5, which is standard. If a button isn't showing up there, nothing you do in remapping software will fix it. That's usually a driver issue or the button is hardwired for a gesture like scroll-to-back. From there I use either Microsoft PowerToys or AutoHotkey, depending on the setup. PowerToys is the faster option for a one-off remap — I installed it, opened the Keyboard Manager module, and remapped mouse button 4 to Alt+Tab in about three minutes. AutoHotkey is what I reach for when I need conditional remapping, like having the side button do different things depending on which application is in focus. A script like this handles it:

#IfWinActive, ahk_exe chrome.exe
XButton1::^Tab
#IfWinActive

This maps the side button to Ctrl+Tab only in Chrome, and leaves it alone everywhere else. I've been doing this exact thing for years across different Anker models — M622, M390, M347 — and the workflow hasn't changed because the mice themselves haven't changed. They're still sending standard HID codes. The two tools that actually cover 99% of use cases are PowerToys for simple remaps and AutoHotkey for anything conditional or complex. PowerToys is from Microsoft itself, available from the Microsoft Store or GitHub, and it's free. AutoHotkey v2 is also free and open-source from autohotkey.com. There's no Anker-specific software for this — I've searched for it multiple times, checked support forums, looked at the Anker website, and confirmed there's nothing from them. Any site selling "Anker Mouse Button Mapping software" is just reselling generic remapping tools with a branded landing page. The setup with PowerToys goes like this: install it, open it, go to Mouse Utilities, then Keyboard Manager. Click Remap a button, select Mouse Button from the dropdown, pick the physical button on your Anker mouse, and assign it a new keystroke or shortcut. It applies immediately. No restart, no driver install, no reboot. I had a full remap done — side buttons to previous/next track in Spotify, middle click to paste in browsers — in under four minutes.

AutoHotkey takes longer to set up but gives you control PowerToys doesn't. You write a .ahk script, run it, and it sits in your system tray. The learning curve is real but shallow for basic stuff. Here's a more complete script I use for my M622 with three clickable buttons plus two side buttons:

#SingleInstance Force
#NoTrayIcon

; Side button 1 - previous track in media players
XButton1::Send {Media_Prev}

; Side button 2 - next track
XButton2::Send {Media_Next}

; Middle click - paste without context menu
MButton::Send ^v

; Right click - custom behavior in file explorer
RButton::
    IfWinActive, ahk_exe explorer.exe
        Send ^c
    Else
        Send {Click Right}
return

This script replaces the right-click context menu with copy in File Explorer while keeping normal right-click behavior elsewhere. That's the kind of specificity PowerToys can't handle without jumping through layers of app detection. I wasted about an hour once trying to get Anker Mouse Button Mapping to work on a Mac with their M347, and the problem turned out to be something nobody warns you about. macOS doesn't expose mouse button remapping through any native API that third-party tools can easily hook into. I tried SteerMouse, which is the most popular mouse utility for macOS, and it saw the Anker mouse fine — all five buttons registered — but the remapping only applied to the primary buttons. The side buttons were completely ignored. The software was reading them as navigation gestures instead of standard mouse buttons, which is how macOS handles them by default. The workaround was ugly but functional. I switched to a utility called Mos, which is open-source and designed specifically for mouse acceleration and button remapping on macOS. Mos treats all buttons as raw input and lets you remap them without the gesture layer interfering. I configured it with a simple config file:

{
  "rules": [
    {
      "product": "Anker Wireless Mouse",
      "buttons": {
        "4": "key.left",
        "5": "key.right"
      }
    }
  ]
}

This mapped the side buttons to browser back and forward. It took me maybe twenty minutes to get working after an hour of dead ends with SteerMouse. I still use this setup today on my MacBook Pro. Another thing that catches people off guard: some Anker mouse firmware updates can break existing remaps. I had a colleague whose Anker M390 started sending different HID codes after a firmware update through the Anker website. His AutoHotkey script that was working perfectly suddenly stopped responding to the side buttons. The fix was updating the script to use the new button numbers instead of going back to the manufacturer — the firmware change was undocumented, and Anker support told him they didn't track HID code changes across versions.

Limitations You Should Know About

Remapping software has real constraints that make it unsuitable for some workflows. First, the remap is per-computer, not per-mouse. If you switch your Anker mouse to another machine, all your custom mappings are gone. You have to redo them or copy your config files over manually. This isn't a dealbreaker for most people but it matters if you move between computers frequently. Second, many gaming applications detect and ignore remapped input from PowerToys and similar tools. If you're remapping side buttons for competitive gaming, you'll likely find they don't register inside the game. I tried this with Valorant once and the side buttons were completely inert while working fine everywhere else on the desktop. AutoHotkey has a harder time with this too — the game's anti-cheat blocks synthetic input injection. For gaming, the only reliable approach is using software that operates at the driver level, and even then it's not guaranteed. Third, remapping doesn't help if the mouse hardware doesn't report the button press correctly. Some budget Anker models use capacitive touch surfaces instead of mechanical switches for the primary buttons, and these sometimes don't register consistent HID events. I've seen this with certain M347 units where the left click fires double events or misses entirely under fast clicking. No software can fix hardware-level input errors. If your mouse is dropping button presses, remapping won't help — you'd need a replacement.

For most people, PowerToys on Windows covers everything in five minutes. AutoHotkey adds the precision for power users. On macOS, Mos is the tool to use after SteerMouse proves insufficient. The Anker Mouse Button Mapping process is really just standard OS-level input remapping — the mouse brand doesn't change how any of this works.