Where Does croc Store Config and Received Files?
croc keeps no config or history: transfers use ephemeral codes through relays, and files land in the working directory.
Last updated
croc stores nothing locally. No config file, no history, no account. Transfer codes negotiate through public relays or a self-hosted one, then expire unused.
That statelessness is the whole backup story: there is none to make. Received files land in the invoking directory, which is the only placement control. Flags select relays per transfer when needed.
Where croc stores this, by platform
(no state; downloads land in working directory)
Stateless by design with no config file. Ephemeral codes expire after use. Received files save into the working directory.
(no state; downloads land in working directory)
Same relay model on Mac via Homebrew installs. Self-hosted relays configure server-side, not in the client. Nothing migrates.
(no state; downloads land in working directory)
Same behavior on Windows builds. Working directory decides placement. Codes never persist anywhere.
Frequently asked questions
How do I move croc to a new machine?
Nothing to move. Reinstall the binary anywhere and it works identically. Relay choice passes per-transfer with flags when defaults do not suit.
Where do received files go?
The directory where you ran receive. Croc saves into the working directory with no prompt for destination. Change directories first to control placement.
Notice an outdated path? Let us know.