LinuxWindows

Where Does Deskflow Store Its Config?

Deskflow saves GUI settings to Deskflow.conf under XDG config on Linux. Windows uses the registry; macOS uses Library.

Last updated

Deskflow resolves settings per OS. Linux reads ~/.config/Deskflow/Deskflow.conf (XDG-aware, /etc/Deskflow fallback), creating it on first run. macOS uses ~/Library/Deskflow/Deskflow.conf. Windows prefers the install dir settings folder, else the HKCU registry key, spilling other files to ProgramData. The conf path anchors everything else the app writes.

Server screen arrangements can also live in hand-written text configs for CLI runs, separate from the GUI file. That split confuses migrators: GUI moves need Deskflow.conf, headless moves need the text file. Deskflow now upstreams the whole Synergy/Input Leap/Barrier family tree, so old configs under those names stay orphaned rather than imported.

Where Deskflow stores this, by platform

Linux
~/.config/Deskflow/Deskflow.conf

Screens, links, protocol choice. XDG-aware with /etc fallback. GUI generates it; CLI server runs use separate hand-written text configs. Historic Synergy/Barrier files never auto-import.

Windows
HKCU\Software\Deskflow\Deskflow (registry)

Same GUI settings role. Windows falls back to HKCU registry plus ProgramData spillover. Service mode needs non-portable layout; install-dir settings disable it.

Frequently asked questions

how do i migrate deskflow to a new computer

Copy Deskflow.conf (plus any hand-written server text configs) to the same OS path on the new machine. Screen layouts reference hostnames, so keep names stable or re-link clients after the move.

how do i reset deskflow settings

Delete Deskflow.conf (or reset via the GUI wiki steps) with the app closed. A fresh file generates on next start. Legacy Synergy/Barrier/Input Leap configs live under their own names and never interfere.

Notice an outdated path? Let us know.