Hasher Remote — Add Checksums to Storage That Lacks Them in RcloneView
The Hasher virtual remote adds hashing on top of an existing remote, so integrity checks still work where the storage has no checksums.
Some storage backends cannot supply file hashes, which weakens comparisons and verification after a transfer. RcloneView supports rclone's Hasher virtual remote, a wrapper that layers hashing over a remote you already have. This guide covers when it helps and how to use it.
Manage & Sync All Clouds in One Place
RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.
- One-click jobs: Copy · Sync · Compare
- Schedulers & history for reliable automation
- Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
Free core features. Plus automations available.
What the Hasher Remote Does
Virtual remotes wrap an existing remote to add behavior. Alias shortens paths, Crypt encrypts, and Hasher adds hashing for integrity checks. If a backend does not expose checksums, comparisons fall back to size and modification time, which can miss content that changed without altering either.
By wrapping that backend in a Hasher remote, you give it a hash capability so checksum-based comparison has something to work with. It is a good fit for archives and backups where correctness matters more than speed.
Create a Hasher Remote
Open the Remote tab and choose New Remote, then select the Hasher type. Point it at the underlying remote and folder that you want to wrap, and give it a name you will recognize, such as archive-hashed. Once saved, it appears in the explorer like any other remote.
Use the wrapped remote wherever you would use the original: browsing, copying, or as a sync source or destination. Keep in mind that hashes are tied to the wrapper, so consistently use the Hasher remote for the data you want verified.
Use It with Sync and Compare
In a sync job's Advanced Settings, turn on Enable checksum so files are compared by hash plus size. Combined with a Hasher remote, this gives more trustworthy results than size and time alone.
Run a Dry Run first to preview what will be copied or deleted, then execute. RcloneView mounts AND syncs 90+ providers from one window, on Windows, macOS, and Linux, so the same verification approach works across your clouds.
Review Results in Job History
After a run, open Job History to confirm status, files transferred, and total size. If a job reports errors, the Log tab shows details.
Getting Started
- Download RcloneView from rcloneview.com.
- Add the remote that lacks checksums, if you have not already.
- Create a Hasher remote that wraps it from Remote > New Remote.
- Build a sync job with Enable checksum on, and run a Dry Run first.
Stronger verification means you find silent differences before they matter.
Related Guides:
- Virtual Remotes — Combine, Union, and Alias with RcloneView
- Fix Cloud Sync Checksum Mismatch with RcloneView
- Fix Cloud Backup Verification Failures with RcloneView
Supported Cloud Providers
