Windows-style middle-button drag autoscroll for Linux.

Hold the middle mouse button and drag. The page scrolls in that direction, faster the farther you drag from where you pressed, like Windows 10/11. Release to stop. A quick middle click without dragging still works as a normal middle click (paste, open link in new tab). Diagonal drags scroll both axes, so it pans wide pages too.

Prefer clicking to holding? Turn on toggle mode (in the settings GUI or TOGGLE_MODE = true) for the Windows-Explorer / Firefox style instead: one middle click starts autoscroll, the cursor moves freely, and any click stops it.

It works in every app, on Wayland and X11, because it operates at the kernel input layer (evdev in, uinput out) instead of hooking any particular desktop or toolkit.

Details:

• The speed curve is Chromium/Edge's actual Windows autoscroll formula (0.000008 * distance^2.2 px/ms, 15 px per-axis dead zone): tiny drags crawl, a full-screen drag flies.
• While scrolling, the real pointer stays anchored at the press point, so the scroll stays locked to the window you started in. Dragging "over" the taskbar or another window can't steal it.
• It still looks like Windows while you do it: a badge with a vertical-arrows icon stays locked at the press point, and a ghost cursor follows your hand from there - a copy of your own pointer, read from your cursor theme. The ghost is only drawn: it can't click, hover or focus anything, which is what lets the scroll stay put while you see where you are (KDE Plasma Wayland; see notes below).
• Apps that use middle-drag themselves (FreeCAD, OrcaSlicer and Minecraft by default) are blacklisted by window class: while one of them is focused, midscroll pauses itself and the middle button behaves natively.
• The desktop and panels are left alone by default: while a desktop shell (plasmashell, xfdesktop, waybar, GNOME Shell, ...) is focused midscroll pauses, so a middle-drag can't hijack the desktop. Turn on Enable on desktop & panels (DESKTOP_SCROLL = true) if you want it there too.

./packaging/fedora/build-rpm.sh
sudo dnf install ./dist/midscroll-*.noarch.rpm

./packaging/debian/build-deb.sh
sudo apt install ./dist/midscroll_*_all.deb

Needs a release with gtk4-layer-shell packaged (Debian 13 "trixie", Ubuntu 24.04+). kdotool isn't in the Debian/Ubuntu repos, so the scroll badge needs it built from source; everything else works without it.

cd packaging/arch
makepkg -si

kdotool (for the scroll badge) is in the AUR.

sudo ./install.sh copies the files and enables the services directly; sudo ./uninstall.sh reverses it. You'll need the dependencies installed: python3-evdev, and for the badge overlay PyGObject, GTK 4, gtk4-layer-shell, librsvg and kdotool.

All methods install two services: midscroll (system, the scroll daemon) and midscroll-overlay (per-user, the badge). Package installs enable both; the overlay starts at your next login, or immediately with systemctl --user start midscroll-overlay.

Search your app menu for midscroll Settings (or run midscroll-settings) for a GTK window that changes every setting - speed, dead zone, event rate, natural scrolling, the ghost cursor, the app blacklist, toggle mode and the desktop/panels toggle - with sliders and switches. It also lists your input devices with a switch each, so you can add a device midscroll didn't recognise as a mouse, or tell it to leave one alone. Clicking Apply asks for admin authorization (via pkexec, using midscroll's own polkit action, so the prompt is scoped to writing this one config file), writes /etc/midscroll.conf and restarts the daemon for you.

Prefer a text file? Edit /etc/midscroll.conf, then sudo systemctl restart midscroll:

DEADZONE_PX = 15          # per-axis dead zone in pixels
SPEED_MULT = 0.008        # overall speed (bigger = faster everywhere)
SPEED_EXP = 2.2           # curve shape (bigger = more extreme at long drags)
PX_PER_NOTCH = 55         # px one wheel notch scrolls in your apps
TICK_HZ = 90              # scroll event rate (higher = smoother)
NATURAL = false           # true = inverted / touchscreen-style direction
TOGGLE_MODE = false       # true = click to start/stop instead of hold-drag
DESKTOP_SCROLL = false    # true = also autoscroll over the desktop and panels
GHOST_CURSOR = true       # draw a cursor that follows your hand while dragging
GHOST_SCALE = 1.0         # how far it travels per unit of mouse motion
BLACKLIST = freecad, orcaslicer, minecraft
                          # window-class substrings that pause midscroll
                          # (apps with native middle-drag); '' disables

Values are validated on load: rates and multipliers must be strictly positive, and anything out of bounds is rejected with a logged error while the default is kept. Because this file also decides which devices the daemon opens (below), it is only read when root owns it and nobody else can write it.

Every tunable can also be overridden per run on the command line, which is handy for trying values without editing the config:

sudo systemctl stop midscroll
sudo midscroll --speed-mult 0.012 --tick-hz 120 --debug
midscroll --help          # full option list

--debug turns on debug logging (device probing, focus changes, scroll starts); --blacklist "app1, app2", --natural / --no-natural, --toggle-mode / --no-toggle-mode, --desktop / --no-desktop (autoscroll over the desktop and panels) and --ghost-cursor / --no-ghost-cursor toggle the corresponding behaviors. --list-devices prints the device list and exits.

midscroll picks up anything that looks like a plain relative mouse. To use something it doesn't recognise - a trackball, a receiver's second interface, an odd HID collection - or to leave one of your mice alone, use the switches in the settings GUI, or the two config keys directly:

EXTRA_DEVICES = /dev/input/by-id/usb-Kensington_Expert-event-mouse
IGNORE_DEVICES = 046d:c548

Each entry is a /dev/input path (the by-id and by-path links are the ones that survive a reboot), a hex vendor:product, or part of the device name. IGNORE_DEVICES wins over EXTRA_DEVICES. To see every device with its identifier and what midscroll does with it:

sudo midscroll --list-devices

The same lists work per run as --extra-device SPEC and --ignore-device SPEC, both repeatable.

Keyboards are refused even when you list one, because that would have a root daemon reading every key on it, and it would lose key repeat and its LEDs passing through the virtual mirror. If you really want one, set ALLOW_KEYBOARDS = true in /etc/midscroll.conf as root - the settings GUI deliberately cannot (SECURITY.md explains why).

Apps in BLACKLIST pause midscroll automatically while focused. For everything else:

sudo systemctl stop midscroll     # pause manually
sudo systemctl start midscroll
sudo dnf remove midscroll         # or apt remove / pacman -R

• The badge and ghost cursor are KDE-specific: the anchor position comes from kdotool, which uses KWin's scripting API, and they are drawn via wlr-layer-shell. On other desktops the daemon still scrolls fine; there's just nothing drawn. Wayland doesn't let a background process change or hide the real pointer image, so the real cursor is still there under the badge, and the ghost is a second cursor drawn beside it rather than the real one moving. That's also why it can't interact with anything: it isn't a pointer, it's a picture of one on a click-through surface.
• The ghost is your actual pointer image, loaded from the Xcursor theme in XCURSOR_THEME or KDE's cursorTheme, at the size the compositor would use, and drawn at 85% opacity so you can tell it apart from the real one. Themes are read once at startup - restart midscroll-overlay after changing yours. A theme that can't be read falls back to a plain drawn arrow.
• The app blacklist needs the focused window's class, which the root daemon can't see itself: the midscroll-overlay session service polls it (once a second, only on change is it sent) via kdotool on KDE Wayland or xprop on X11, and reports it to the daemon over the state socket. The daemon only trusts reports from a logged-in user's helper, so another local process can't feed it a fake focus and pause it. No helper running (or another Wayland desktop) just means the blacklist is inactive.
• Switching into a blacklisted app takes effect within about a second (the poll interval), and stops an in-progress scroll too. If you press the middle button in that brief window right after switching, a short scroll may start before the daemon sees the new focus and stops it.
• Pointer speed: each mouse is re-emitted through its own uinput mirror that copies the real mouse's name and vendor/product IDs, so libinput and KDE keep applying that mouse's own pointer-speed and acceleration settings. If a specific mouse still loses its speed after enabling midscroll, set it once more in System Settings -> Mouse while midscroll is running (KDE stores it per device in kcminputrc) and it will stick.
• If Firefox's built-in autoscroll is enabled (general.autoScroll in about:config), turn it off so the two don't fight. It's off by default on Linux.
• Why not a flatpak: the sandbox forbids the raw input-device and uinput access this needs, and flatpaks can't run boot-time services.
• Logs: journalctl -u midscroll -f and journalctl --user -u midscroll-overlay -f.

midscroll runs a background daemon that reads every mouse (and writes a virtual one) at the kernel input layer. That is a lot of trust to hand a program you found online. Don't take my word that it's safe - read it. It's deliberately small and dependency-light so you can:

• midscroll (the daemon) and midscroll-overlay (the session cursor and focus helper) are single, commented Python files - skim them start to finish.
• midscroll-apply is the only thing that runs as root on demand (via pkexec from the settings GUI); it validates every value and only ever writes /etc/midscroll.conf.
• Both systemd units are sandboxed - see systemd/*.service. The daemon runs with no capabilities at all. Run systemd-analyze security midscroll.service and systemd-analyze --user security midscroll-overlay.service to see the exposure score for yourself.

SECURITY.md goes through it properly: what each part trusts, why the config file must be root-owned, why keyboards can only be added by a root edit and never from the GUI, what the state socket does and doesn't hand out, and what keeps a full-screen overlay from ever eating your clicks.

Found something sketchy or a way to harden it further? Open an issue or PR - security review is genuinely welcome.

Public domain (the Unlicense): use, copy, modify, sell or distribute freely. The badge icon is move-vertical from Lucide (ISC license).