Where Does Fork Store Settings and Repos?
Fork keeps its tabs, favorites, and preferences in per OS app data, while repositories stay where you cloned them.
Last updated
Fork stores interface state in app data folders managed by the OS: open tabs, repo favorites, custom commands, and theme choices. Git repos themselves never move into those folders. They stay in your dev directories.
That split makes migration easy. Copy the config tree with Fork closed and favorites reappear on the new machine. Git identity still comes from global .gitconfig, so set user name there rather than hunting inside Fork. Avatars and per repo init settings ride along in the same backup.
Where Fork stores this, by platform
%APPDATA%\Fork
Exact interior may vary by version, check Roaming Fork if this does not match. Explorer integration adds registry keys pointing at %LOCALAPPDATA% Fork Fork.exe. Repos stay in your own folders.
~/Library/Application Support/Fork
Same model as Windows. Global git user info resolves from ~/.gitconfig, which Fork reads for commit authorship. Copy the support folder whole for migration.
Frequently asked questions
How do I back up Fork favorites and custom commands?
Close Fork, copy the app data folder above to backup storage, and restore it on the new machine before launching. Repos need separate copies or fresh clones.
Where is git user name set for Fork commits?
In global ~/.gitconfig (or %USERPROFILE% .gitconfig on Windows). Fork surfaces empty identity fields when that file lacks entries, so set it once in any git client.
Notice an outdated path? Let us know.