Where Does Input Leap Store Its Config?
Input Leap reads screen layout from a user config (~/.config/InputLeap) or a system fallback, in Barrier file format.
Last updated
Input Leap inherits the Barrier config format: screens with aliases, links between edges, and options. The server reads the first file it finds, preferring your user config over the system one.
SSL certificates sit next to the config in an SSL subdirectory. The profile directory flag (--profile-dir) moves both at once, which is the clean way to test a second layout without touching the live one.
Where Input Leap stores this, by platform
%LocalAppData%\Input Leap\InputLeap.sgc
Screens, links and options in Barrier format plus an SSL subfolder beside it. System fallback at C:\ProgramData\Input Leap\InputLeap.sgc. Server listens on port 24800 by default.
~/.config/InputLeap/
Default user config per the man page (~/.config/InputLeap/input-leap.conf). GUI-saved files use InputLeap.conf in the same folder; system fallback at /etc/input-leap.conf. Override with --config.
Frequently asked questions
How do I configure Input Leap without the GUI?
Write the screens, links and aliases sections by hand (the repo ships example files) and pass it with input-leaps --config <path>. The GUI writes the same format, so either path converges.
Where are the Input Leap TLS certificates?
It lives beside the config in an SSL subfolder of the same user directory. New fingerprints need one manual accept per client; after that the files just sit there.
Notice an outdated path? Let us know.