Mt. Sync is a native GNOME desktop application that puts the full power of rclone behind a polished GTK4 interface. Whether you're mounting a remote drive, scheduling nightly syncs, or browsing files across a dozen cloud providers — Mt. Sync handles it quietly in the background while you get on with your work.

Works With Everything rclone Supports.

 

GitHub - gavindi/MtSync: A Gnome frontend to rclone to (auto)mount and sync your data

A Gnome frontend to rclone to (auto)mount and sync your data - gavindi/MtSync

GitHub - gavindi/MtSync: A Gnome frontend to rclone to (auto)mount and sync your data

rclone connects to over 40 storage providers. Mt. Sync gives all of them a native desktop home.

Cloud storage — Google Drive, Dropbox, Backblaze B2, MEGA, Box, Amazon S3, Google Cloud Storage, Proton Drive, Wasabi, Cloudflare R2, DigitalOcean Spaces, Hetzner, and more.

Self-hosted & network — SFTP, SMB/CIFS, WebDAV, FTP, OpenStack Swift, and others.

Local & encrypted — Local filesystem access and encrypted remote overlays via rclone crypt.

Each provider is shown with its own icon — Google Drive looks like Google Drive, Dropbox looks like Dropbox. Light and dark variants switch automatically with your desktop theme.
Mount. Browse. Sync. All in One Place.
Mount Network Storage as a Local Drive

Mount any remote as a local filesystem with a single click. Mt. Sync passes your VFS cache mode preference (off, minimal, writes, or full) directly to rclone so performance matches your workflow. Mounted drives appear as active jobs and can be unmounted just as easily. Mount jobs can be configured to start automatically when the daemon launches.
Dual-Pane File Browser

A side-by-side browser lets you navigate two locations simultaneously — any combination of local disk and remote storage. Sortable columns, MIME-type icons, breadcrumb navigation, back history, and per-pane hidden file toggles make it feel like a native file manager. A status bar shows file and folder counts with total size. The swap button exchanges the two panes with a single click.
Compare Before You Commit

Before transferring anything, hit Compare to see exactly what differs between the two panes. Mt. Sync runs rclone check across both locations and presents the results as a structured, paginated list grouped by subdirectory. Each row shows the filename, size, and modified date on the side where the file exists — nothing on the side where it doesn't. Status glyphs make the picture instantly readable: → exists only in source, ← exists only in destination, ≠ present on both sides but different, = identical. Click any column header to sort — files stay grouped with their directory so the structure of your storage is always clear.

Four toggle buttons in the centre of the action bar let you filter the results by status — hide source-only files, destination-only files, differing files, or errors individually. Toggle any combination to focus on exactly what you care about. Directory headers disappear automatically when all their files are filtered out.

Select one or more rows and act on them directly from the action bar — no need to leave the dialog:

Copy → — copy selected files from source to destination
← Copy — copy selected files from destination to source
Delete (source side) — remove selected files from the source remote
Delete (destination side) — remove selected files from the destination remote

After any action the comparison reruns automatically so the list always reflects the current state. A Cancel button lets you abort a long-running scan at any time.
Copy, Move & Sync

Copy or move selected files between any two locations — local or remote, same provider or different. Sync entire directories with rclone's fast delta transfers. Bi-directional sync (rclone bisync) keeps two locations in agreement without overwriting newer files. File include-filter patterns let you narrow transfers to exactly the files you want.
Scheduled Jobs

Set any job to run on a cron schedule. The built-in schedule editor takes five familiar fields (minute, hour, day, month, weekday) and shows a plain-English summary of when the job will next run. Jobs re-arm automatically after each completion. If a scheduled instance is still running when the next trigger fires, it is skipped safely — no pile-ups.