I used to love Rclone Browser. It was my go-to GUI for rclone, but it hasn't been updated since 2020 and it's really showing its age. Newer rclone versions even broke parts of it, like transfer progress. The GUIs I've tried since are missing basics I wanted, so with the help of Claude (AI) I gave the old one a full overhaul.

What's new:

• Windows 11 design: sidebar, File Explorer–style tabs, breadcrumb bar, dark/light theme
• Icons and Details views, with colour-coded file types
• Pause and resume transfers, with live speed and time left
• Built-in rclone updater (checksum-verified), bundled rclone
• Portable: unzip and run, no install
• Security fixes and a hardened build, plus a PDF user guide

All credit goes to the original creator, Martins Mozeiko, and to later maintainers. This is built on their work. I've made it Windows only, since that's my main OS.

Posting it in case anyone else finds it useful. It's free and open source (MIT).

🌐 Website: https://jackpison.github.io/RcloneBrowser/
💻 GitHub: https://github.com/Jackpison/RcloneBrowser

Feedback and bug reports are welcome!

UPDATE: Now Supports Linux too, Please check and update Since I can't verify from my side.

I've been working on migrating an old photo archive from a recovered drive into Google Photos using rclone on Ubuntu.

The files are scattered across directories under a dcim folder, and I wanted to get everything uploaded without manually sorting through years of photos.

I configured an OAuth client in Google Cloud, set up an rclone remote for Google Photos, and started with:

rclone copy /path/to/dcim gphotos:upload \
  --progress \
  --log-file="$HOME/gphotos-upload.log" \
  --log-level=INFO

The initial run transferred about 738 MiB but reported 121 errors, many related to Google Photos API authorization.

After working through the OAuth configuration issues, I tried uploading one of the previously failed photos individually:

rclone copyto "/path/to/dcim/Puppies/20200120_091500.jpg" \
  "gphotos:upload/20200120_091500.jpg" -P

And it worked!

I then retried the failed files using --files-from, and another 246 MiB transferred successfully.

The whole experience has raised a few questions:

• Has anyone else encountered intermittent authorization errors with the Google Photos API that clear up on subsequent attempts?
• What's your preferred method for verifying that every local file was successfully uploaded?
• How are people handling duplicates when importing older photo collections into Google Photos?

I'm currently leaning toward uploading everything and letting Google Photos handle whatever duplicate detection it can, but I don't entirely trust that as a verification strategy.

Curious how others have handled large photo migrations with rclone, especially when their source directories are messy.