Fix Cloud Sync Timestamp Mismatch Errors in RcloneView
Timestamp mismatches cause rclone to re-transfer files that have not changed, wasting bandwidth and time. This guide explains why they happen and how to configure RcloneView to handle them correctly.
When rclone syncs files between two locations, it compares modification timestamps to decide which files need updating. If the source and destination report different timestamps for the same file — even by a single second — rclone treats the file as changed and transfers it again. This leads to unnecessary transfers, inflated bandwidth costs, and sync jobs that never seem to complete cleanly. The problem is especially common when syncing between different cloud providers, or between local storage and cloud remotes that handle timestamps differently.

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.