Custom Build

Rclone UI works with any rclone binary, which includes custom builds and community forks.

You might want to use a custom build for a number of reasons:

• Additional backends: Some forks add support for providers not yet available in the official rclone release (e.g. RealDebrid, enhanced S3 metadata).
• Experimental features: Try out new functionality before it lands upstream.
• Bug fixes: A fork may ship a patch for an issue that hasn't been merged yet.
• Custom patches: You may have your own modifications to rclone that you want to use.

The process is straightforward, you just need to replace (or alias) the rclone binary that Rclone UI uses with your custom one.

macOS

Rclone UI looks for rclone on your PATH. You can either rename your custom binary to rclone and place it in a directory on your PATH, or create a shell alias.

Option 1 — Replace the binary

# Move your custom binary into a directory on your PATH
mv /path/to/custom-rclone /usr/local/bin/rclone
chmod +x /usr/local/bin/rclone

Option 2 — Shell alias

Add this to your ~/.zshrc (or ~/.bashrc):

alias rclone="/path/to/custom-rclone"

Then reload your shell:

source ~/.zshrc

Option 3 — Symlink

ln -sf /path/to/custom-rclone /usr/local/bin/rclone

Windows

Option 1 — Replace the binary

Locate where rclone.exe is installed (commonly C:\Program Files\rclone\ or wherever you extracted it) and replace it with your custom build:

1. Rename your custom binary to rclone.exe.
2. Copy it to the directory where rclone is installed, replacing the existing file.

Option 2 — Update your PATH

1. Place your custom rclone.exe in a folder of your choice (e.g. C:\Tools\custom-rclone\).
2. Open Settings > System > About > Advanced system settings > Environment Variables.
3. Edit the Path variable and add your custom folder above the default rclone entry so it takes priority.

Linux

The process is the same as macOS — Rclone UI finds rclone via your PATH.

Option 1 — Replace the binary

sudo mv /path/to/custom-rclone /usr/local/bin/rclone
sudo chmod +x /usr/local/bin/rclone

Option 2 — Shell alias

Add this to your ~/.bashrc (or ~/.zshrc):

alias rclone="/path/to/custom-rclone"

Then reload:

source ~/.bashrc

Option 3 — Symlink

sudo ln -sf /path/to/custom-rclone /usr/local/bin/rclone

Verify it works

After swapping the binary, confirm Rclone UI picks up the right version:

rclone version

You should see the version string from your custom build. Then open Rclone UI — it will use whichever rclone binary is resolved on your PATH.

Community custom builds

Here are some notable custom rclone builds you may want to check out: