Where Does Keymapp Keep Its Runtime Files?
Keymapp ZSA keyboard runtime socket paths on Linux and macOS.
Last updated
Keymapp exposes a runtime API socket rather than a settings file. Flashing tools talk to it locally. The socket path shifts per platform and install source.
Windows uses a TCP port instead of a socket file. Firmware binaries stay wherever the user saved them through the picker. Back up those files deliberately since no folder collects them.
Where Keymapp stores this, by platform
~/.config/.keymapp/keymapp.sock
Runtime API socket, not a settings store. Overridable via KEYMAPP_SOCKET env var. Firmware files are user picked with no fixed dir. Windows uses a TCP port instead.
~/Library/Application Support/.keymapp/keymapp.sock
Same socket semantics under Application Support. App Store builds sandbox under Containers with the same tail path.
Frequently asked questions
How do I use a custom socket path?
Point KEYMAPP_SOCKET at a custom path before launching both sides. The default differs per install source. Logs naming the socket path reveal which location the running build expects.
Where are firmware downloads kept?
There is no fixed dir. Firmware files are picked through a Browse dialog each time. Only the runtime socket sits at a stable path. Treat downloads as user managed.
Notice an outdated path? Let us know.