Where Does keyd Store Config on Linux?
keyd reads key remaps from /etc/keyd conf files on Linux, applied by reloading the service.
Last updated
keyd keeps system wide remaps in /etc/keyd as default.conf plus one file per application or device overlay. The daemon applies them at the evdev layer, so consoles and Wayland agree. USB quirks and virtual keyboards run through the same layer, so one reload covers every seat.
Edit as root, check syntax, then reload the keyd service. That folder versions well in system dotfiles. Per user tweaks belong in app configs instead of the system daemon.
Where keyd stores this, by platform
/etc/keyd
default.conf plus app specific overlays. Root owned. Reload the keyd unit after edits and test in a clean terminal.
Frequently asked questions
How do I apply keyd changes?
Save the conf files and reload or restart the keyd service. Test each layer before stacking more. A syntax slip can eat the whole keyboard until fixed.
Where do per app remaps go in keyd?
As overlay sections in /etc/keyd files or separate conf files in the same dir. Keep one file per app for readable diffs.
Notice an outdated path? Let us know.