Where Is the Rclone Config File?
Rclone config file on every OS, the override order, and the commands that reveal the live path.
Last updated
Rclone keeps remotes in rclone.conf: %APPDATA%\rclone on new Windows setups, ~/.config/rclone on Mac and Linux ($XDG_CONFIG_HOME respected, legacy ~/.rclone.conf still read). That file holds every remote with its tokens, so guard it like a password vault.
Explicit always wins: RCLONE_CONFIG and --config beat every default, and an rclone.conf next to the executable forces portable mode (even an empty one flips the switch). Priority runs exe dir, then AppData on Windows, then XDG, then legacy. Verify any confusion with rclone config file.
Where Rclone stores this, by platform
%APPDATA%\rclone\rclone.conf
Default for new configs when APPDATA is set. Portable mode when rclone.conf sits next to rclone.exe. Overrides: RCLONE_CONFIG env var, --config flag. Verify with rclone config file.
~/.config/rclone/rclone.conf
Same as Linux ($XDG_CONFIG_HOME respected). Same override order: exe dir, XDG, ~/.config, legacy ~/.rclone.conf, with env and flag on top.
~/.config/rclone/rclone.conf
Default for new files on Unix ($XDG_CONFIG_HOME respected). Legacy ~/.rclone.conf still read if present. Same env, flag and portable overrides as other OSes.
Frequently asked questions
Which rclone config file is actually active?
Run rclone config file. It prints the live path after applying the full priority chain, which settles every exe dir versus AppData versus XDG argument instantly.
How do I run portable Rclone from a USB stick?
Place an rclone.conf next to rclone.exe on the stick. Its presence alone forces portable mode, so remotes travel with the drive and nothing touches the host profile.
Notice an outdated path? Let us know.