DEV Community: TrackStudio

The Mac trackpad settings worth changing

TrackStudio — Tue, 03 Nov 2026 19:13:25 +0000

The Mac trackpad is tuned for the average user, which means it is usually wrong for you. These are the changes worth making, in the order that removes the most misfires.

Start with the misfires

Click pressure. If the trackpad clicks when you rest your hand, set it to Firm. This fixes more accidental clicks than any other setting.

Tap to click. Turn it off for a day if you get clicks you did not intend. If you miss it, turn it back on; if you do not, you just removed a class of errors.

Look up & data detectors. This is the popup that interrupts text selection. It is not Force Click, and turning it off does not disable pressure. Set it to Off, or move it to a three-finger tap.

Force Click. If you press hard while dragging, turn the deeper press off. You lose the system haptic click with it, so most people should fix Look Up first.

Then the speed

Tracking speed. One notch below maximum is the precision setting. Maximum feels fast for a day and twitchy for a year.

Do not change tracking and scroll speed in the same session. You will not be able to tell which one caused the overshoot.

The gestures

Swipe between pages. Keep it. Two fingers, two pages, it works in every browser.

Mission Control. Pick three or four fingers and stay there. Switching between them is how people end up saying gestures are unreliable.

Three-finger drag. It lives in Accessibility, Pointer Control, Trackpad Options, not in the Trackpad pane. Enable it only if you drag windows or select long passages all day; it collides with three-finger swipes and Look Up.

Do not enable every gesture just in case. A gesture you do not use is a gesture that fires by accident.

Where macOS stops

macOS gives you one global layout. It cannot give Safari and Figma different controls, and it cannot put brightness and volume on the pad edges. Those need a third-party layout app. If the settings above are enough, stop there.

The full version, with the exact paths and the conflict table, is here: https://trackstudio.xyz/blog/best-mac-trackpad-settings

Middle click on a Mac trackpad: what actually works

TrackStudio — Tue, 03 Nov 2026 17:15:07 +0000

macOS has no middle click. Not a hidden setting, not a defaults write, not a checkbox in System Settings. A trackpad has one physical click and a two-finger click for the secondary button. Button 3 exists in the event model, but nothing maps a trackpad contact to it.

That surprises people coming from Linux or from a mouse with a wheel, because middle click is load-bearing in those environments: open a link in a new tab, close a tab, paste a selection, pan a canvas.

If you want it on a Mac, something has to synthesize the event. Here is what actually works, what fails, and how the plumbing looks if you are building it yourself.

The three approaches

Approach	What it does	Cost	The catch
An input utility (BetterTouchTool, Karabiner-Elements, a dedicated middle-click app)	Binds button 3 to a gesture, key, or corner	Free to about $25	Another background app; synthetic clicks are ignored by some targets
A mouse with a wheel	A real button 3	Hardware	Not the trackpad
A trackpad surface app	Maps regions and gestures to actions, not mouse buttons	Varies	Usually does not emulate button 3 at all

There is no fourth option. Apple has never shipped a middle-click mapping for the trackpad.

What most people actually wanted

Before installing anything, check which job you were doing:

Open a link in a new tab: Command-click does it in Safari, Chrome, Arc, Firefox, and Orion.
Close a tab: Command-W. Reopen: Command-Shift-T.
Paste a selection: macOS has no primary-selection buffer. This is the one that genuinely needs button 3 or a clipboard manager.
Pan a canvas: most Mac apps use space-drag or a two-finger scroll, not middle-drag.

Two of those four have native shortcuts. If the habit is the only thing missing, the shortcut is cheaper than a utility.

How the event actually works

If you are writing the app, the relevant AppKit entry point is otherMouseDown. The button number for the middle button is 2:

override func otherMouseDown(with event: NSEvent) {
    if event.buttonNumber == 2 {
        // middle button
    }
}

To synthesize one, build a CGEvent and post it:

let down = CGEvent(mouseEventSource: nil, mouseType: .otherMouseDown,
                   mouseCursorPosition: point, mouseButton: .center)
let up = CGEvent(mouseEventSource: nil, mouseType: .otherMouseUp,
                 mouseCursorPosition: point, mouseButton: .center)
down?.post(tap: .cghidEventTap)
up?.post(tap: .cghidEventTap)

Two things bite immediately.

Permission. Posting events into other apps requires Accessibility access. A global monitor for the gesture that triggers it usually needs it too. Without the grant, your code runs and nothing happens, which is the worst failure mode to debug.

Targets that ignore synthetic input. Secure input fields suppress event taps, some games read HID directly, and a few apps filter events by source. Your middle click will work in Safari and do nothing in the app you actually cared about. Test there first, not in a demo.

If you are choosing a utility

Pick the gesture last. The trigger is the easy part; the conflicts are what make a trackpad utility annoying.

A three-finger tap is the usual choice, and it is also the gesture macOS uses for Look Up, and the one many apps use for drag or navigation. A corner click is less discoverable but far less likely to fire while you are selecting text. Whatever you pick, give the gesture exactly one owner: one app, one action.

Test in three places before you trust it: a browser link, a text field, and the app where you originally wanted it. If it fails in the third, the utility is not the problem; the target is.

The honest summary

Need button 3 specifically: an input utility or a mouse.
Want fewer reaches in the browser: Command-click and Command-W cover most of it.
Want the trackpad to do more in general: a surface app is a better shape than a single mouse button.

I make TrackStudio, a Mac trackpad control surface with edges, corners, custom areas, per-app scenes, and haptics. It deliberately does not emulate a middle click, because that is a different job. The longer version of this post, including the settings paths and the failure cases, is here: https://trackstudio.xyz/blog/middle-click-mac-trackpad

Per-app trackpad scenes: the missing layer in Mac input

TrackStudio — Tue, 03 Nov 2026 16:24:38 +0000

Your Mac trackpad is the best input device on the machine, and macOS still treats it as a rectangle for moving a pointer.

The gestures are global. Three fingers up. Two fingers swipe. Pinch. They work everywhere, which is exactly why they cannot be specific to anything. The same swipe that means "go back" in a browser means nothing in Figma, and the edge that would make a good volume slider is ignored by the system.

A per-app scene is a different model. Instead of starting with a gesture, you start with the app in front of you and arrange the surface: edges, corners, custom areas, a center gesture. The layout changes when the app changes. A default scene covers everything else.

I have been building TrackStudio around this model. This post is about the model, not the product.

Why global layouts break

A global layout assumes every app wants the same controls. They do not.

A browser wants navigation. An editor wants windows and screenshots. A terminal wants restraint. A video editor wants transport and a way back to Mission Control. If the layout never changes, you either build a lowest-common-denominator surface or a surface that is wrong in half your apps.

The second problem is conflict. Two apps can claim the same gesture, or an app can claim a gesture the utility also wants. Scenes reduce the overlap by giving each app its own map.

What a scene actually is

A scene is a saved layout bound to an app. The mechanics are similar across implementations:

Detect the frontmost app.
Apply the layout for that app.
Fall back to a default when there is no match.
Yield when the app needs the input.

The fallback is the part people forget. If every app needs a scene before the trackpad works, the system is too heavy. Start with a good default, then add scenes only where the default is wrong.

The hard parts

Frontmost app detection is cheap. macOS gives you NSWorkspace notifications; the switch itself is not the problem.

The problems are at the edges:

Secure input fields can suppress event taps.
Accessibility and Input Monitoring permissions decide which actions work.
Games and remote desktops often capture input directly.
A layout switch has to feel instant; a visible delay makes the surface feel broken.
Haptics have to carry information. A detent says a value changed. A tick says an action ran. Decorative haptics become noise.

None of this is exotic. It is the unglamorous work that separates a demo from something you keep using.

A worked example: Figma

Figma is a keyboard-first app, so a useful scene stays around the edges of the work.

Left edge: brightness, for comparing colors.
Right edge: volume, if you listen while you work.
Bottom edge: media scrub, if music is part of your day.
Top-left corner: Mission Control.
Top-right corner: screenshot.
Two small areas: undo and redo.
Center gesture: command palette, if you prefer a press-and-drag to the keyboard shortcut.

The point is not to replace Figma's shortcuts. The point is to remove the reaches around them: the window switch, the screenshot, the brightness change.

What not to do

Do not map a destructive action to a single edge tap. Do not put a control where your palm rests. Do not duplicate a shortcut you already type faster. And do not buy a scripting tool for a layout problem, or a layout tool for a scripting problem.

The takeaway

The trackpad is not only a gesture surface. It is a layout surface. Once the layout can follow the app, the interesting design question changes from "which gesture should I memorize?" to "which controls belong in this app?"

That is the layer macOS does not provide. It is also the layer that makes the trackpad feel like hardware instead of a pointer.

I make TrackStudio, a Mac app built around this model. The longer guide, including the failure cases and a scene checklist, is here: https://trackstudio.xyz/blog/per-app-trackpad-scenes