InputConfig guide and documentation

Each page owns its subject outright, which keeps you from reading the same paragraph twice. Bindings holds the complete reference for what a control can send, so MIDI only covers what is genuinely MIDI specific and presets covers organizing and generating presets rather than the bindings inside them. Setup owns the path to a controller that works the first time; troubleshooting owns anything that used to work and stopped. Where two pages both touch a subject, one carries the explanation and the other links to it.

InputConfig sits between an input device and macOS and rewrites what the device sends. A button press comes out as a keystroke, a stick comes out as cursor movement or as scrolling, a trigger comes out as a mouse button, a knob comes out as the system volume. The device on the input side can be a game controller, a MIDI keyboard or pad box, your own Mac keyboard, mouse, or trackpad, or on some Macs a knock on the case. The output side can be keys and clicks, mouse motion, scrolling, a typed phrase, a macro, MIDI sent out to a DAW, a system function such as Mission Control or dictation, or a Siri Shortcut. No drivers are involved at any point.

It runs on macOS 14 or later and asks for one permission, Accessibility, because typing and moving the pointer on your behalf is not something macOS lets an app do quietly. It is free, with no paid tier and nothing locked; the optional tip jar unlocks nothing. The source is public under the MIT license, and the app has no network access at all, so what it reads cannot leave your Mac. If you want the longer version with screenshots, read the InputConfig overview, or see the rest of the free Mac software we publish.

InputConfig ships with 25 built-in help guides, and the welcome screen it opens on is where most people find them. They are written as tasks and as symptoms rather than as a feature list, so the titles read Connecting a Controller, Using 8BitDo Controllers, and Emergency Stop: Getting Out of a Preset. Version 1.4 added a search field across all 25, so you can type a controller name, an option name, or a symptom instead of scrolling the list. If what you want is that first screen walked through to a working preset, that is the setup page.

Three ways into it

Open Help Guide

The button on the welcome screen. It opens the whole library in a window of its own, grouped by subject and searchable. This is where the per-controller guides live, including the dedicated guide for the PlayStation Access Controller.

The Help menu

InputConfig Help, on Command and the question mark key, opens that same library from anywhere in the app without going back to the welcome screen. Quick Start Tour sits directly under it.

Quick Start Guide

A guided walkthrough that highlights each part of the window in turn, started from the welcome screen or from the Help menu. It is the shorter route to a first working preset if you would rather be shown than read.

The grid of feature cards filling the rest of the welcome screen is not part of that library, which is worth knowing before you go looking there for a guide. Each card opens a short animated demo of the feature instead, ending in a button that jumps straight to a matching example preset.

The About button opens the About tab in Settings, which shows the running version and build and the changelog inside the app. If you are checking whether an update fixed something, that is the shortest path to the answer.

What these pages add

The in-app guides are the quick reference. These pages go further where the extra room helps. Setup gathers per-controller quirks that are spread across several separate guides into one order of operations. Troubleshooting is indexed by the words you would type into a search box rather than by the feature at fault. The release notes link each 1.4 change to the page that explains it, which a plain list of changes cannot do. And a few subjects, including the Accessibility permission and the Smart Preset Maker, have no in-app guide of their own at all.