How To Install Rclone on Debian 13

Managing files across cloud storage from a Linux server is painful without the right tool. You end up juggling browser uploads, proprietary clients, or brittle shell scripts that break at the worst possible time. Rclone solves that problem cleanly: it gives you a single, powerful command-line tool that connects to over 70 cloud storage providers from one unified interface.
This guide covers exactly how to install Rclone on Debian 13 step by step, using three different methods so you can pick the one that fits your setup. By the end, you will have a working Rclone installation on Debian 13 Trixie, a configured remote, and the knowledge to keep everything updated without relying on stale packages.
What Is Rclone and Why Run It on Debian 13?
Rclone is an open-source command-line program written in Go that manages files on cloud storage. Think of it as rsync, but for the cloud.
It supports providers including Google Drive, Amazon S3, Dropbox, OneDrive, Backblaze B2, Mega, SFTP, and many more. You can copy, sync, move, mount, encrypt, and check files across all of them using a consistent command syntax.
Debian 13 “Trixie” was released on August 9, 2025. It ships with Linux Kernel 6.12 LTS, APT 3.0 with the new Solver3 dependency resolver, and uses tmpfs by default on /tmp, which speeds up Rclone’s temporary file operations. It is a rock-solid base for any server running long-running sync workloads.
Prerequisites
Before you start, confirm the following:
- A running Debian 13 (Trixie) system, either desktop or server edition
- A user account with
sudoprivileges (not running as root directly) - An active internet connection
- Basic comfort working in a Linux terminal
curlinstalled, or willingness to install it (covered in Method 2)unzipinstalled, or willingness to install it (covered in Method 3)- Knowledge of which cloud storage provider you want to connect (Google Drive, S3, Dropbox, etc.)
Step 1: Update Your System Before Installing Rclone
Always update the package index before installing anything on Debian. Skipping this step is the most common reason installs fail due to dependency mismatches.
sudo apt update && sudo apt upgrade -y
The apt update command refreshes the local package cache so Debian knows what versions are available. The apt upgrade -y applies any pending system updates automatically. On Debian 13 with APT 3.0, this runs noticeably faster than on older releases.
Once the update completes, you are ready to choose your installation method.
Step 2: Choose Your Installation Method
There are three reliable ways to install Rclone on Debian 13. Each has specific use cases.
| Method | Best For | Version |
|---|---|---|
| APT (Debian repo) | Simplicity, managed upgrades | May be older |
| Official install script | Latest stable release, recommended | Always current |
| Manual binary download | Air-gapped servers, version pinning | Full control |
Pick the method that matches your environment. Most users should start with Method 2.
Method 1: Install Rclone via APT
This is the simplest approach. You install Rclone directly from Debian’s official package repository.
Step 2a: Run the Install Command
sudo apt install rclone -y
APT resolves all dependencies automatically and places the binary in /usr/bin/rclone.
Step 2b: Verify the Installation
rclone version
Expected output:
rclone v1.xx.x
- os/arch: linux/amd64
- go version: go1.xx.x
Important caveat: The version in Debian’s repository often lags several releases behind the official upstream. If you need the latest features or bug fixes, use Method 2 instead.
Method 2: Install Rclone via the Official Install Script (Recommended)
This method pulls the latest stable Rclone binary directly from rclone.org, verifies it cryptographically, and installs it in a single command. It is the recommended approach for most Debian 13 users following the Rclone on Debian 13 setup process.
Step 2a: Install curl If Needed
sudo apt install curl -y
Step 2b: Run the Official Rclone Install Script
sudo -v ; curl https://rclone.org/install.sh | sudo bash
Here is what each part of this command does:
sudo -vrefreshes your sudo credentials so the session does not time out mid-installcurl https://rclone.org/install.shfetches the official install script| sudo bashpipes the script directly to bash and runs it with root privileges
The script auto-detects your system architecture (amd64, arm64, etc.) and downloads the correct binary. It also skips the download if you already have the latest version installed, which makes it safe to re-run at any time.
Step 2c: Confirm the Installation
rclone version
Compare the version shown against the latest release listed at rclone.org/downloads. They should match.
Method 3: Install Rclone Manually via Binary Download
Use this method on servers without internet access post-setup, when you need to pin a specific version, or when you want full control over binary placement.
Step 2a: Install Required Tools
sudo apt install curl unzip -y
Step 2b: Download the Rclone Archive
Navigate to the rclone.org/downloads page and note the latest version number. Then run:
cd /tmp
curl -O https://downloads.rclone.org/rclone-current-linux-amd64.zip
The rclone-current-linux-amd64.zip URL always points to the latest stable release for 64-bit Linux, so you do not need to update the URL manually.
Step 2c: Extract the Archive
unzip rclone-current-linux-amd64.zip
cd rclone-*-linux-amd64
Step 2d: Copy the Binary and Set Permissions
sudo cp rclone /usr/bin/
sudo chown root:root /usr/bin/rclone
sudo chmod 755 /usr/bin/rclone
The chmod 755 ensures the binary is executable by all users while only being writable by root.
Step 2e: Install the Man Page (Recommended)
sudo mkdir -p /usr/local/share/man/man1
sudo cp rclone.1 /usr/local/share/man/man1/
sudo mandb
Installing the man page lets you run man rclone at any time for quick offline reference.
Step 2f: Verify the Installation
rclone version
Step 3: Configure Rclone on Debian 13
Installation alone does nothing useful. You need to configure at least one remote, which is Rclone’s term for a cloud storage connection. This section covers the full configure Rclone on Debian 13 process.
Start the Configuration Wizard
rclone config
The interactive wizard opens. You will see a menu with options like n for new remote, l to list existing remotes, and q to quit.
Create a New Remote
Type n and press Enter, then give the remote a short, memorable name:
name> gdrive
Rclone then presents a numbered list of supported storage providers. Type the number next to your chosen provider and press Enter.
Authenticate with Google Drive
For Google Drive, you can leave the client_id and client_secret fields blank to use Rclone’s default shared credentials. Press Enter to skip both.
For a headless server without a browser, Rclone will generate a URL. Open that URL on a desktop machine, authorize access, then paste the resulting token back into the terminal. This is the standard flow for server environments and it works reliably.
For Amazon S3, you will need your AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Enter them when prompted.
For Dropbox and OneDrive, Rclone uses a browser-based OAuth flow automatically.
Verify the Remote Works
rclone ls gdrive:
This lists files in the root of your configured remote. A successful output with your files confirms that authentication is working correctly. An empty output with no errors also means the connection is valid, just that your root directory is empty.
Step 4: Mount Cloud Storage as a Local Directory
One of Rclone’s most powerful features is mounting a cloud remote as a local directory using FUSE. This lets any application read and write to cloud storage as if it were a local folder.
Install FUSE 3
Debian 13 uses FUSE 3 (fuse3) by default. Install it if not already present:
sudo apt install fuse3 -y
Enable non-root users to mount FUSE filesystems by editing the FUSE config:
echo "user_allow_other" | sudo tee -a /etc/fuse.conf
Without this line, only root can perform FUSE mounts.
Mount a Remote as a Local Directory
mkdir -p ~/cloud/gdrive
rclone mount gdrive: ~/cloud/gdrive --daemon
The --daemon flag sends the mount process to the background so it keeps running after you close the terminal. You can now access your Google Drive files at ~/cloud/gdrive like any local folder.
Unmount the Directory
fusermount -u ~/cloud/gdrive
Step 5: Learn the Essential Rclone Commands
Once Rclone is configured, these are the commands you will use most often in day-to-day operations on a Linux server.
List files in a remote:
rclone ls gdrive:
Copy local files to cloud storage:
rclone copy /local/path gdrive:/backup
Sync a directory (one-way mirror):
rclone sync /local/path gdrive:/backup
Check for differences without transferring:
rclone check /local/path gdrive:/backup
Move files to cloud:
rclone move /local/path gdrive:/archive
Critical distinction: sync deletes files in the destination that no longer exist in the source. If you want to preserve both sides, always use copy instead. This catches many users off guard when they run sync for the first time.
Step 6: Keep Rclone Updated on Debian 13
Staying current matters. Newer Rclone releases fix bugs, improve transfer speeds, and add support for updated provider APIs. This Linux server tutorial covers three update strategies.
Using rclone selfupdate (Best for Script and Binary Installs)
Rclone includes a built-in selfupdate command available since version 1.55. It downloads the latest stable release, verifies it with a hash and cryptographic signature, and replaces the running binary automatically.
Check what version would be installed without downloading:
sudo rclone selfupdate --check
Apply the update:
sudo rclone selfupdate
Install the latest beta release:
sudo rclone selfupdate --beta
Revert to a previous version if needed:
sudo rclone selfupdate v1.67.0
Replace v1.67.0 with the version number printed when you ran the update.
Using APT (For APT-Based Installs)
sudo apt update && sudo apt upgrade rclone
This works but depends on Debian’s package release cycle, which typically lags behind upstream.
Automate Updates with a Cron Job
sudo crontab -e
Add this line to update Rclone every Sunday at 3 AM:
0 3 * * 0 /usr/bin/rclone selfupdate
Troubleshooting Common Rclone Issues on Debian 13
Even on a clean Debian 13 install, things can go wrong. Here are the most common problems and their fixes.
Problem: command not found: rclone
The binary is not in your $PATH. Run which rclone to check. If it returns nothing, reinstall using Method 2 or verify the binary is in /usr/bin/ or /usr/local/bin/.
Problem: unknown command "selfupdate"
Your installed Rclone version is older than 1.55. This happens when you installed via APT and got an outdated package. Reinstall using the official script (Method 2) to get a current version.
Problem: Mount fails with a FUSE error
Either fuse3 is not installed, or user_allow_other is missing from /etc/fuse.conf. Run sudo apt install fuse3 -y and check that /etc/fuse.conf contains user_allow_other.
Problem: OAuth authentication token expired
Cloud provider tokens expire periodically. Reconnect the remote with:
rclone config reconnect gdrive:
Problem: Slow transfer speeds
The default concurrency settings are conservative. Boost performance with:
rclone copy /local/path gdrive:/backup --transfers=16 --checkers=16
--transfers controls parallel file transfers, and --checkers controls parallel file comparison threads. Adjust both based on your server’s available CPU and bandwidth.
Congratulations! You have successfully installed Rclone. Thanks for using this tutorial for installing Rclone on your Debian 13 “Trixie” Linux system. For additional help or useful information, we recommend you check the official Rclone website.