Where Does HopToDesk Store Config?
HopToDesk reads per-device config plus api.json from its config dir. Linux uses ~/.config/HopToDesk; logs sit beside it.
Last updated
HopToDesk keeps per-device state in a config directory: device ID and password, api.json overrides for custom networks, mcp.json discovery tokens, and logs. Linux uses ~/.config/HopToDesk/config, Windows %APPDATA%\HopToDesk\config (C:\ProgramData variant for services), macOS its Application Support or Preferences equivalent.
Custom networks are file-driven. An api.json with rendezvous plus TURN entries redirects the client off the public network entirely, either as a local file or a hosted URL the app downloads. The on-premises story stays split though: signal and relay self-host while the dashboard remains a hosted service, so config covers connectivity, not the whole product.
Where HopToDesk stores this, by platform
~/.config/HopToDesk/config
Device id, api.json overrides, mcp.json tokens, logs. Custom networks via local api.json or hosted URL. Service installs use the ProgramData path variant.
%APPDATA%\HopToDesk\config
Same role on Windows. Per-user under Roaming; services and all-users setups use ProgramData. --import-config and --changeid flags script fleet moves.
Frequently asked questions
how do i migrate hoptodesk to a new computer
Copy the config dir (device id, api.json, mcp.json) to the same OS path on the new machine. IDs travel with the files, so the device keeps its identity. Logs stay behind; they never matter for restores.
how do i point hoptodesk at my own servers
Drop an api.json with rendezvous and turnservers into the config dir (or serve it over HTTPS and point Choose Network at the URL). The app reads it at startup and skips the hosted API. Service installs need the all-users path variant.
Notice an outdated path? Let us know.