How to start and use the rclone Web GUI step by step

If you've been struggling with the command line to manage your cloud storage, discovering how to launch rclone's web GUI could be a game-changer. Rclone is a true Swiss Army knife for cloud storage, but until you get the hang of its graphical interface, it can be a bit intimidating. Here, you'll see, step by step and in great detail, how to go from scratch to controlling your remotes from your browser without any unnecessary complications.

Throughout this guide, I'll explain how to install rclone on different systems , how to create remotes (Google Drive, OneDrive, S3, etc.), how to activate the official Web GUI, how to use third-party graphical interfaces, and, as a bonus, how to mount drives, automate backups, and optimize performance. Everything is explained in Spanish (Spain), with real-world examples of use on Linux, Windows, macOS, and even OpenWrt.

What is rclone and why should you be interested in its web interface?

Rclone is an open-source tool for managing files across more than 70 cloud storage services from a single interface, typically the terminal. It supports Google Drive, OneDrive, Dropbox, Amazon S3, Backblaze B2, Cloudflare R2, pCloud, Proton Drive, MEGA, and many more, and runs on Linux, Windows, macOS, and even routers running OpenWrt.

It's often described as a "Swiss Army knife for the cloud" because it extends the concept of rsync to the world of cloud services: you can copy, synchronize, mount drives, encrypt data, serve files via HTTP, WebDAV, or FTP, and automate backups. All of this is done using a fairly consistent syntax across providers.

The less user-friendly aspect is that, by default, everything is managed from the command line . For many users, this presents a significant barrier. Precisely for this reason, since version 1.49, rclone has offered an official web interface (rclone Web GUI), and there are third-party graphical applications that make daily use much more convenient.

In addition to web access, rclone allows you to mount your cloud storage as if it were a local disk , which is ideal if you want to work from your file explorer (Nemo, Nautilus, Explorer, Finder…) without having to manually copy and paste files.

Supported cloud services and usage types

One of rclone's greatest strengths is its extensive multi-cloud support . Instead of forcing you to learn a different app for each provider, you configure it once and then add "remotes" for each account or service.

For the average user, the most common options are connecting Google Drive, Google Photos, Microsoft OneDrive, Dropbox, Box, MEGA, pCloud, or Proton Drive . All of these options are supported, each with its own specific features, including both personal and business accounts.

At a professional level, rclone shines when working with object-based storage such as Amazon S3, Google Cloud Storage, Microsoft Azure Blob Storage, Backblaze B2, Cloudflare R2, or Wasabi. Many companies use it for backups, archiving, cross-region synchronization, or data migrations between providers.

You can also talk to rclone in terms of standard protocols : SFTP/FTP, WebDAV (for example with Nextcloud or ownCloud), SMB/CIFS (Windows shared folders) or even HTTP to download from web servers, so you centralize management without depending on specific clients.

Unlike rsync, rclone is designed specifically for the cloud: It understands remote APIs and OAuth authentication.bandwidth limits, caches, etc. And with options like --multi-thread-streams It can achieve transfer speeds higher than rsync on fast networks.

Install rclone on Windows, Linux, and macOS

Before starting the Web GUI, you need to have rclone installed and updated . The tool evolves quickly, so it's best to use a modern version (the Web GUI documentation requires at least version 1.49, but ideally you should use the latest stable version).

On Windows, a very convenient way is to download the official ZIP file (for example) rclone-v1.71.0-windows-amd64.zip (for 64-bit), extract it and place rclone.exe in a folder like C:\rclone\If you add that path to the environment variable PathYou can run rclone from any directory in the command prompt or PowerShell.

Another even simpler alternative is to use Winget or ChocolateyWith Winget, something like this is enough. winget install Rclone.RcloneAnd with Chocolatey you can make choco install rclone and even add WinFSP to take advantage of the drive mounting feature. To uninstall, the same managers provide the option with a similar command.

On Ubuntu or Debian-type systems, the recommended way is to use the official installation script running curl https://rclone.org/install.sh | sudo bashIf you prefer more control, you can download the package .deb of a specific version and install it with sudo dpkg -iIn case of dependency problems, sudo apt -f install usually solves it.

On macOS, the usual practice these days is to use Homebrew with brew install rcloneAlternatively, you can choose manual installation by downloading the macOS ZIP file, extracting it, and moving the binary to /usr/local/bin/ to add it to the PATH. On all systems, once installed, it's advisable to run rclone selfupdate every now and then to make sure you're keeping up to date.

Setting up remotes in rclone step by step

The heart of rclone is the “remote”That is, the configurations that represent each account or provider. All that information is normally stored in ~/.config/rclone/rclone.conf (on Linux and macOS) or in the user's configuration folder on Windows.

To create a new remote, the process almost always starts with rclone configWhen you run this command, rclone will tell you if you already have remotes created or if you need to create one with the option n) New remoteYou will need to choose a name (for example gdrive, onedrive, OpenCAYLE for an S3 type Ceph, etc.).

Then comes the moment to choose the storage typeRclone shows you a fairly long list with options like Google Drive, OneDrive, Dropbox, S3, SFTP, WebDAV, Ceph, etc. You select the number or type the corresponding identifier (for example) onedrive o drive (for Google Drive).

Depending on the supplier, rclone will ask you for a customer ID or with a Client SecretFor most users, simply leaving these fields blank and pressing Enter is sufficient, using the default values ​​included with rclone. Then you'll choose the scope (for example, option 1 for full access to Google Drive), and you'll usually accept empty values ​​in fields like root_folder_id o service_account_file.

In most cases you will say no to the Advanced configuration (option n In “Edit advanced config”), you will proceed to the authentication section. If the system has a browser, the easiest way is to use automatic configuration: rclone opens a tab, you log in to your account (Google, Microsoft, etc.), accept the permissions, and it automatically receives the token. If you are in an environment without a browser (for example, an SSH server), rclone will display a command. rclone authorize to launch on a machine with a browser, from where you will get a JSON token that you will paste back into the server.

Example configuration: Google Drive, OneDrive, and S3

To show you how everything fits together in practice, let's look at several real-world examples of configuring remotes using rclone's interactive wizard. Even if you later want to manage it from the Web GUI, this initial remote setup phase is usually done in the terminal.

In the case of OneDrive on Windows, open a command prompt (Windows key + R, type cmd or you use PowerShell) and run rclone configYou create a new remote, you give it a name (for example) onedriveNext, select OneDrive as your storage type, and leave the Client ID and Secret fields blank. Rclone will then ask for your region (usually "global"), offer to configure advanced options (reply no), and ask if you want to use auto-configuration. Answering yes will open your browser, log you in with your Microsoft account, and authorize access.

To Google DriveThe process is similar: in the list of storage types, choose the number corresponding to Drive (for example, 13 in some versions of the list), accept the default values ​​for Client ID and Secret, choose the scope (usually option 1 for full access), and leave blank. root_folder_id y service_account_fileAgain, you can use the automatic browser configuration or, if you're on a remote server without a GUI, copy the URL that rclone gives you, open it in a browser from another machine, log in, and paste the verification code into the terminal.

In more advanced environments, such as a Ceph-compatible S3 storageThe wizard will ask you for different information: provider (Ceph, Minio, Wasabi, etc.), whether you want it to read the credentials from environment variables or enter them manually, the access_key_id y secret_access_key You'll need the region (often a generic option without an explicit region) and the API endpoint (for example, a URL with port 443) provided by your provider. You can also choose the default ACL type (private, public, etc.) and leave the server-side encryption section blank if you're not using it.

When finished, rclone will show you a Remote configuration summaryIf everything is correct, confirm by selecting the option to keep that configuration and exit the wizard. q) Quit configFrom there, you can list remotes with rclone listremotes and check directories or files with commands like rclone lsd remoto: o rclone ls remoto:.

How to start the official rclone Web GUI

Since version 1.49, rclone has offered an official web interface for managing remotes, browsing files, viewing logs, and launching operations without using the terminal. It's still somewhat experimental, but it works surprisingly well and is constantly adding more features.

The key command to start it is rclone rcd --rc-web-guiWhen run in a terminal, rclone starts "remote control daemon" (rcd) mode, checks if the GUI package is downloaded, and if not, downloads it automatically. It then starts an HTTP server linked by default to localhost Using a self-generated username and password, it serves the web interface through that same port and opens your browser with a login token to enter without having to enter credentials.

While the Web GUI is in use, it's crucial that rclone continues running in that terminal . If you close the window or stop the process, the interface will become unresponsive. The logs will show incoming requests and status messages for operations you launch from the web interface.

If you want the interface to stay updated, you can add the option --rc-web-gui-update so that it checks for new versions of the GUI package on startup. And if at any point the interface breaks (for example, after a failed update), you have --rc-web-gui-force-update to force the download of the latest available version.

By default, rclone automatically opens the browser, but if you're on a server without a graphical environment or simply don't want it to, you can disable that behavior with --rc-web-gui-no-open-browser and then access it manually from another computer by entering the corresponding address and port in the browser.

Use the Web GUI locally, remotely, and behind a proxy

The basic setup assumes that rclone and the browser are running on the same machine , typically your desktop or laptop. However, you can also separate the rcd daemon and the browser to manage rclone from another machine, which is very useful on servers, VPSs, or routers.

In advanced usage, the flag --rc-web-gui It's actually a shortcut that involves several things: downloading the Web GUI package if it's missing, verifying that authentication is in place, setting up a user (by default something like "gui") and a random password, and activating --rc-serve to serve the static interface files and unite everything under the same RC API address and port.

If you want to expose the Web GUI to the outside world, it is recommended to do so with SSL and proper authenticationFor example, you can specify that it listens on port 443, or use a file htpasswd This allows you to control usernames and passwords, and provide an SSL certificate and key. This kind of setup lets you have a publicly accessible interface with a reasonable level of security, provided you choose strong credentials.

Another interesting possibility is to place the Web GUI behind a reverse proxy (like Nginx or Apache) on a specific path, for example /rcloneTo do this, you can use the flag --rc-baseurlwhich tells the interface where it's located within the site's URL, and combine it with --rc-htpasswd Or, if you prefer to keep it simple, with --rc-user y --rc-pass to set up a single username and password.

In any case, it's best to avoid exposing your web GUI to the internet without any protection, as this would leave you with a backdoor granting unrestricted access to your remote servers. Ideally, you should restrict access by IP address, use a VPN , or at least ensure that the RC server only listens on internal addresses when you don't need to expose it to the outside world.

Special example: starting rclone Web GUI in OpenWrt

On routers running OpenWrt, it's quite common to use rclone to set up Google Drive or other services on your home network. Some firmwares integrate rclone into the LuCI interface, but the initial configuration is usually done via the terminal before you can use the graphical interface.

A typical flow would be entering the OpenWrt web interface, go to Services > Terminal and open a session. From there, you launch rclone config To create a remote from Google Drive or another service, follow the classic steps: choose the storage type, accept the default Client ID and Secret, select the appropriate scope, leave the root folder and service account file fields empty, and answer that you do not want to edit the advanced settings.

Since routers typically don't have a web browser, when rclone asks you for Use auto config you will answer n It will then display a URL. Copy and paste that address into a browser on your computer, log in with your Google account, and once permissions are granted, the browser will return a code that you will need to paste into the router's terminal to complete the authentication.

When finished, rclone will ask for confirmation to create the remote, and when you accept, you can exit the wizard with the option qThen, from the OpenWrt interface, in sections such as NAS > RcloneIt is common to have boxes for run rclone as daemon, save and apply changes, and even options to open the React Web UI (rclone's web interface) directly from the panel.

Many of these panels will show you an address for the rclone daemon (for example http://192.168.1.1:5572), that you will have to copy and paste into the WebUI when opened in the browser. Some systems use default credentials such as username and password “admin”, which you could later change to something more secure.

Other graphical interfaces for rclone

While the official Web GUI is very useful, there are also third-party graphical applications that connect to rclone and further simplify its use. These are a good option if you don't want to rely on a browser or if you prefer a classic desktop app.

One of the best-known is Rclone UI , a modern interface that works on Windows, macOS, and Linux. It offers drag-and-drop file browsing, a scheduler for regular backups, background task management, and visual progress bars, which greatly simplifies large data migrations.

Another long-standing option is RcloneBrowser , an open-source project that has been in development for years. It's especially convenient on Linux because it's usually distributed as an AppImage, so you can download it, mark it as executable, and launch it without complex installations. It's ideal if you're looking for something lightweight for file lists, occasional downloads, and simple operations.

These alternative GUIs don't replace the base rclone configuration, but they do make it easier to navigate the cloud, launch backups, and review logs , all with less risk of messing things up with a misspelled command in the console.

Basic usage: listing, copying, synchronizing, and mounting drives

While the web interface and GUIs are very helpful, knowing the basic rclone commands will be useful even for understanding what the web GUI itself is doing behind the scenes. The most basic functions are listing the contents of your remotes and copying files.

To list files by size on a remote, you use commands like rclone ls remoto:While rclone lsd remoto: It only shows you directories and rclone tree remoto: It offers a tree view. If you want to inspect a specific folder, simply add it after the colon, for example rclone ls onedrive:Documents.

Regarding copies, rclone copy It allows you to copy in a single direction without deleting anything at the destination. You can copy from local to cloud, from cloud to local, or directly between clouds. Options such as --progress o -P They show progress in real time; --dry-run It allows you to see what the command would do without touching anything, and --transfers=N Adjust the number of parallel transfers (default 4) to speed up or slow down the operation as needed.

The command sync It makes the destination identical to the origin, erasing anything extra. It's very powerful but also destructive, so it's normal to try it first with --dry-run And, if you handle sensitive data, consider using copy instead of syncFor bidirectional synchronization (source and destination update each other) there is bisyncalthough it is still considered experimental functionality.

One of the star functions is rclone mountwhich allows you to mount a remote location as if it were a local drive or folder. In Windows, for example, you can mount a remote OneDrive as drive X: with rclone mount onedrive: X: --vfs-cache-mode fullIn Linux or macOS, you would create a directory like ~/OneDrive and you would assemble it with rclone mount onedrive: ~/OneDrive --vfs-cache-mode full --daemon. Parameter --vfs-cache-mode controls cache behavior: from no cache to full modewhich is usually the recommended option for working on documents.

Real-world examples: legacy systems, crontab, and token renewal

Rclone shines especially on older or less powerful machines where official cloud clients have long since ceased providing support. For example, 32-bit laptops running lightweight Linux distributions like Linux Mint 19.3 Tricia are still perfectly adequate for office tasks, but they need seamless access to Google Drive without relying on a browser or resource-intensive applications.

In these cases, the solution usually involves configuring rclone with Google Drive, creating a folder in the /home (for example drivetrabajo) and mount the cloud on top of it at system startup. This way, you can open the file manager (Nemo, in the case of Linux Mint) and work on your documents as if they were on a local disk, while rclone handles synchronizing changes with the cloud on the fly.

To automate assembly at startup, it is very common to use crontabEditing the user's cron table with crontab -eYou can add a line that runs rclone mount at startup, sometimes with a small delay, using /bin/sleep 30 This allows time for the device to connect to Wi-Fi before mounting the unit. This prevents assembly errors when the network takes a few seconds to become available.

One detail that many people overlook is that the Google Drive tokens They are not permanent. In some scenarios, after about 200 days they become invalid and rclone can no longer authenticate the account. The most direct way to fix this is to remove the affected remote from rclone config (option d) Delete remote) and recreate it exactly the same way, repeating the authentication flow in the browser. Alternatively, you can use the command rclone config reconnect remoto: to renew tokens without discarding the entire configuration.

The rclone configuration is saved in the file rclone.conf inside the hidden folder .config/rclone from the user, which even allows you to back up that configuration or move it between machines if you want to replicate your remotes on several computers without redoing the entire wizard.

Automated backups and cloud migrations

Beyond its interactive use, rclone is well-suited for automating recurring tasks such as backups, archiving, and synchronizing large volumes of data between cloud providers. While the web GUI can help you configure and launch tasks, in many cases you'll want to rely on the operating system's built-in scheduling tools.

In Windows, for example, you can create a task in the Task Scheduler to execute rclone.exe with arguments of the type sync C:\ImportantData onedrive:backup --log-file=C:\rclone\backup.log every night at a specific time. The task configuration is saved in XML and allows you to adjust triggers, conditions, and execution parameters without having to write lengthy scripts.

In Linux, it's practically a classic to use cron To launch rclone, edit the crontab with crontab -e and you add a line like 0 2 * * * /usr/bin/rclone sync /home/user/documents gdrive:backup --log-file=/var/log/rclone-backup.log so that at 2 a.m. your documents folder is synchronized with a "backup" folder in Google Drive.

To mass migrations between cloud services (for example, moving everything from Google Drive to OneDrive) it is common to adjust parameters such as --transfers, --checkers and fragment sizes (--drive-chunk-size, --onedrive-chunk-size) to maximize the available bandwidth. Combined with a --log-file You can check if there have been any errors, retries, or files that were not copied.

If you're also concerned about confidentiality, rclone includes a remote type called crypt that acts as an encryption layer on top of another remote. By configuring it, you can upload your data to the cloud already encrypted, transparently: rclone takes care of encrypting filenames, content, and, if you want, directory names as well, without the provider having any easy way to see what you're storing.

Performance, troubleshooting, and security

When you start pushing rclone to its limits with large volumes, issues like performance, authentication errors, and memory consumption arise . The Web GUI can give you a visual idea of ​​what's happening, but it's helpful to know a few key settings.

For very large files, it is often advisable to increase the size of the fragments that rclone sends to the provider (for example with --drive-chunk-size=256M in Google Drive) and use more simultaneous transfers, provided your connection and machine support it. Otherwise, if you handle millions of small files, options like --fast-list, --transfers tall and more --checkers They can improve the performance of listings and comparisons.

When authentication fails, messages like “failed to make oauth client” usually appear. Most commonly, the token has expired or that something has changed in the provider's configuration. Commands like rclone config reconnect remoto: Or, ultimately, deleting and recreating the remote usually solves it.

In resource-constrained environments, such as small VPSs or routers, you may also encounter problems with the memoryIn this case, lowering parameters such as --buffer-size, play with --use-mmap Reducing the number of parallel transfers can help prevent rclone from consuming all the RAM.

From a security standpoint, in addition to the aforementioned remote crypt, rclone allows encrypt your own configuration file using a password, so if someone gets hold of your rclone.conf It should not allow access to your tokens and keys. It's also a good idea to follow the principle of least privilege: grant only read permissions if you don't need to write, restrict access to specific folders, and rotate API keys periodically.

Ultimately, having a web GUI, a good remote configuration, and some backup automation gives you a very powerful ecosystem where you control all your cloud storage from a single point . Whether you're working from a modern PC, reviving a 32-bit laptop, or using an OpenWrt router, rclone and its web interface let you take your files anywhere without relying on proprietary clients or countless different applications.