AWS S3 is the industry standard for object storage. Cloudflare R2 eliminates egress fees entirely. RcloneView connects to both — here is how to choose.

AWS S3 established the object storage category and remains the most widely adopted service with 11 nines of durability, comprehensive lifecycle management, and deep integration with the AWS ecosystem. Cloudflare R2 launched as a direct competitor with a radical pricing advantage: zero egress fees. For RcloneView users managing data across multiple providers, understanding the trade-offs between S3 and R2 helps optimize both cost and functionality.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Pricing Comparison​

Storage Costs​

R2 is 35% cheaper than S3 Standard for active storage. However, S3's tiered storage classes (Infrequent Access, Glacier, Deep Archive) offer significantly lower prices for data that is rarely accessed. If your data has mixed access patterns, S3's lifecycle policies can automatically transition objects to cheaper tiers over time — a capability R2 does not offer.

Egress Costs​

This is R2's headline advantage. AWS S3 charges $0.09/GB for data transferred out to the internet (with lower rates for higher volumes and free transfer to CloudFront). Cloudflare R2 charges $0.00 for egress — all data retrieval is free.

For a 10 TB monthly egress workload, the difference is stark: roughly $900/month on S3 vs. $0 on R2. For storage-heavy, low-egress workloads, the difference is smaller and S3's ecosystem advantages may outweigh the egress savings.

API Operations​

R2 offers generous free tiers for API operations and is slightly cheaper per operation beyond the free tier. For workloads with high API call volumes (millions of small object operations), the free tiers on R2 provide meaningful savings.

Feature Comparison​

Storage Classes and Lifecycle​

AWS S3 offers six storage classes (Standard, Intelligent-Tiering, Standard-IA, One Zone-IA, Glacier Instant Retrieval, Glacier Flexible Retrieval, Glacier Deep Archive) with lifecycle policies that automatically transition objects based on age or access patterns.

Cloudflare R2 offers a single storage class with an Infrequent Access tier. There are no Glacier-equivalent cold storage options and limited lifecycle management.

For archival workloads, S3's Glacier Deep Archive at $0.00099/GB/month is unmatched.

Durability and Availability​

Both services provide high durability. AWS S3 quotes 99.999999999% (11 nines) durability. Cloudflare does not publish a specific durability number for R2 but states it is designed for high durability across multiple availability zones.

S3 Standard provides 99.99% availability. R2 does not publish a specific SLA but benefits from Cloudflare's global network.

Ecosystem Integration​

AWS S3 integrates with the entire AWS ecosystem — Lambda, CloudFront, Athena, EMR, SageMaker, CloudTrail, and hundreds of other services. IAM policies, bucket policies, and VPC endpoints provide fine-grained access control.

Cloudflare R2 integrates with Cloudflare Workers (edge compute), Cloudflare CDN, and the Cloudflare dashboard. The integration is tighter and simpler but narrower in scope.

S3 API Compatibility​

Both services support the S3 API. R2 implements the most commonly used S3 operations (GET, PUT, DELETE, multipart upload, list objects) but does not support every S3 feature — notably, S3 Select, S3 Object Lambda, and some advanced bucket configurations are not available on R2.

RcloneView connects to both using the same S3-compatible remote type, so switching between them in RcloneView is a matter of changing the endpoint and credentials.

Using Both with RcloneView​

RcloneView's multi-cloud approach means you do not have to choose one or the other. A common strategy is to use S3 for archival data (leveraging Glacier tiers) and R2 for frequently accessed data (eliminating egress fees). RcloneView can sync, copy, or migrate between them with a few clicks in the two-pane explorer.

Set up both as S3-compatible remotes in the Remote Manager, and RcloneView handles the rest — compare bucket contents, run migrations, or schedule ongoing replication jobs.

When to Choose Each Provider​

Choose AWS S3 when:

• You need lifecycle policies and Glacier cold storage tiers.
• Your workload integrates with other AWS services.
• You require advanced features like S3 Select, Object Lambda, or Inventory.
• Data egress is minimal relative to storage volume.
• You need the published 11 nines durability SLA.

Choose Cloudflare R2 when:

• Data egress is a significant portion of your costs.
• You serve content through Cloudflare's CDN network.
• Your application uses Cloudflare Workers for edge compute.
• You want simple, predictable pricing without egress surprises.
• Your data does not require cold storage tiering.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add AWS S3 and Cloudflare R2 as S3-compatible remotes in the Remote Manager.
3. Browse both side by side in the two-pane explorer.
4. Migrate, sync, or replicate data between them based on your cost and access requirements.

AWS S3 remains the gold standard for object storage with its ecosystem depth and archival tiers. Cloudflare R2 disrupts the pricing model by eliminating egress fees. RcloneView lets you leverage both — or switch between them — without vendor lock-in.

Related Guides:

• Add AWS S3 and S3-Compatible
• Compare Folder Contents
• Create Sync Jobs

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Energy and utility companies generate vast amounts of operational data — from SCADA telemetry to field inspection photos. RcloneView helps manage, back up, and sync this data across cloud providers and on-premises storage.

The energy sector produces data at every level of operation: smart meter readings from millions of endpoints, SCADA system logs from substations, drone inspection footage of transmission lines, GIS mapping data for pipeline routes, and regulatory compliance records that must be retained for decades. This data lives across disparate systems — on-premises servers at generation facilities, cloud storage for corporate offices, and field devices that upload via mobile connections.

RcloneView provides a unified interface to manage this data across cloud providers, on-premises NAS devices, and S3-compatible object storage — enabling backup, replication, and archival workflows that span the organization.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Data Challenges in Energy and Utilities​

Energy companies face unique data management challenges:

• Volume: A single wind farm's SCADA system can generate gigabytes of telemetry data daily. Smart meter deployments produce terabytes annually.
• Retention requirements: NERC CIP standards require certain records to be retained for 3-6 years. Environmental compliance data may need to be kept for 30+ years.
• Geographic distribution: Assets are spread across remote locations — offshore platforms, rural substations, pipeline corridors — each with varying network connectivity.
• Security: Critical infrastructure data requires protection against both cyber threats and physical disasters. NERC CIP mandates specific cybersecurity controls for bulk electric system data.
• Multi-vendor environments: Different divisions may use different cloud providers based on their specific needs (Azure for corporate IT, AWS for analytics, on-premises for OT systems).

SCADA and Operational Data Backup​

SCADA historian databases accumulate operational data that is critical for both real-time operations and regulatory compliance. Backing up this data to cloud storage provides geographic redundancy and protects against on-site disasters.

RcloneView can sync SCADA data exports from an on-premises NAS or file server to AWS S3, Azure Blob, or Backblaze B2. Schedule nightly backup jobs that capture the day's historian exports and replicate them to cloud storage. For cost optimization, configure lifecycle policies on S3 to transition older data to Glacier tiers automatically — recent data stays in Standard for quick access, while historical data moves to Glacier Deep Archive at a fraction of the cost.

Field Inspection and Drone Footage​

Utility companies conduct regular inspections of transmission lines, pipelines, wind turbines, and solar installations. Modern inspections use drones that capture thousands of high-resolution photos and LiDAR scans per flight. This footage needs to be uploaded from field laptops to centralized storage for analysis.

RcloneView simplifies this workflow. Field technicians connect to the corporate cloud (Google Drive, OneDrive, or S3) from their laptops and upload inspection footage directly. RcloneView's bandwidth throttling prevents uploads from consuming the field site's limited connectivity. For sites with intermittent connections, RcloneView resumes interrupted transfers automatically.

Compliance and Regulatory Records​

NERC CIP, FERC, EPA, and state-level regulators require energy companies to maintain extensive records. These records must be stored securely, backed up independently, and available for audit on demand.

RcloneView's encrypted backup capabilities protect compliance records at rest. Use a crypt remote to encrypt files before uploading them to cloud storage. Pair this with S3 Object Lock or Backblaze B2 file lock for immutable storage — files cannot be modified or deleted during the retention period, satisfying WORM (Write Once Read Many) compliance requirements.

The job history panel provides an audit trail of every backup operation — when it ran, how many files were transferred, and whether any errors occurred. This log supports compliance audits by demonstrating that backup procedures are being followed.

Multi-Site Data Consolidation​

Energy companies operate across dozens or hundreds of sites, each with its own local storage. Consolidating data from these sites into a central cloud repository enables enterprise-wide analytics, reporting, and disaster recovery.

RcloneView supports this by connecting to storage at each site (via SFTP, SMB, or WebDAV) and syncing to a central cloud destination. Configure a separate remote for each site and create sync jobs that pull data into a unified bucket or container. The two-pane explorer makes it easy to verify that data from all sites is arriving correctly.

GIS and Mapping Data​

Geographic Information System (GIS) data — pipeline maps, transmission line routes, substation layouts, and environmental survey data — consists of large shapefiles, geodatabases, and raster images. This data is essential for operations, planning, and regulatory submissions.

RcloneView can sync GIS data between on-premises GIS workstations and cloud storage, providing backup and enabling collaboration between distributed teams. Mount a cloud-stored GIS repository as a local drive so that GIS applications can access the data directly without downloading entire datasets.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add remotes for your cloud storage (S3, Azure, or B2) and on-premises storage (SFTP, SMB, NAS).
3. Configure automated backup jobs for SCADA exports and compliance records.
4. Set up upload workflows for field inspection data with bandwidth controls.

Energy and utility companies manage some of the most critical and heavily regulated data in any industry. RcloneView provides the multi-cloud file management, automated backups, and encryption capabilities needed to protect this data while meeting compliance requirements.

Related Guides:

• Add AWS S3 and S3-Compatible
• Create Sync Jobs
• Job Scheduling
• Mount Cloud Storage as a Local Drive

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Freelancers juggle multiple clients, each with their own cloud platform. RcloneView unifies Google Drive, Dropbox, OneDrive, and more into a single interface — no more switching between apps.

Freelancers and independent contractors face a unique file management challenge: every client uses a different cloud platform. One client shares files through Google Drive, another uses Dropbox, a third sends deliverables via OneDrive, and your own backups live on a personal cloud or external drive. Without a unified tool, you spend time switching between apps, manually downloading and re-uploading files, and hoping nothing falls through the cracks.

RcloneView connects to all of these platforms from a single interface. Browse client folders, transfer deliverables, back up your work, and keep everything organized — regardless of which cloud each client uses.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

The Freelancer Cloud Problem​

A typical freelancer's cloud landscape looks something like this:

• Client A: Shares project briefs and assets via Google Drive
• Client B: Uses Dropbox for file exchange
• Client C: Works in Microsoft 365 with OneDrive and SharePoint
• Personal backup: Backblaze B2 or an external hard drive
• Portfolio/delivery: pCloud, MEGA, or another personal cloud

Managing five or more cloud accounts means five apps, five sets of credentials, and no unified view of your files. Searching for a file from a project six months ago means remembering which client used which platform. Backing up client work requires manual effort per platform.

Unified Multi-Cloud Access​

RcloneView's two-pane explorer lets you open any two cloud accounts side by side. Drag client files from Google Drive to your Backblaze B2 backup. Copy deliverables from your local workspace to the client's Dropbox folder. Compare your working copy against the client's latest uploads to check for new assets.

Add each client's cloud as a separate remote in the Remote Manager. Name them descriptively — "Client-A-GoogleDrive", "Client-B-Dropbox" — so you can find them instantly. All remotes are accessible from a single dropdown, eliminating the need to install each provider's desktop client.

Automated Backup of Client Work​

Losing client work is a career-ending event for a freelancer. A single accidental deletion or ransomware incident can destroy months of deliverables. RcloneView's scheduler automates backups to protect against this.

Set up a nightly sync job that copies your active project folders to a backup cloud (Backblaze B2 at $6/TB/month is popular among freelancers). RcloneView detects which files have changed since the last run and transfers only the deltas, keeping backup costs and bandwidth low.

For maximum protection, back up to two independent destinations — a cloud provider and an external drive. RcloneView can manage both backup targets from the same interface.

Client File Delivery​

When you need to deliver finished work to a client, RcloneView eliminates the download-reupload cycle. Open your workspace in one pane and the client's cloud in the other. Copy the deliverables directly — cloud to cloud — without the files ever touching your local storage (beyond the transfer buffer).

For large deliverables (video projects, design files, datasets), this saves significant time compared to downloading to your machine and re-uploading. RcloneView's real-time monitoring shows transfer progress so you can confirm delivery before notifying the client.

Protecting Client Data with Encryption​

Client work often includes confidential information — financial data, unreleased products, proprietary content. RcloneView's crypt remote encrypts files before they leave your machine. Even if your backup cloud is compromised, the encrypted files are unreadable without your encryption key.

Set up a crypt remote that wraps your backup destination. Files are encrypted on upload and decrypted transparently on access. The encryption is client-side — no cloud provider ever sees your unencrypted data.

Archiving Completed Projects​

When a project ends, you need to archive the files in a way that is cost-effective and retrievable. Transfer the project folder from your active workspace to a cold storage tier — AWS S3 Glacier, Backblaze B2, or Wasabi. Tag the archive with the client name and project date for easy retrieval later.

RcloneView's storage analysis helps you identify large files consuming expensive storage space. Move them to cheaper tiers and free up your active storage for current projects.

Managing Multiple Accounts Per Provider​

Some freelancers have multiple Google Drive accounts — one personal, one for a client's Google Workspace. RcloneView supports adding multiple remotes for the same provider, each with different credentials. Name them distinctly and switch between them without logging in and out.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add each client's cloud account and your personal backup destination as remotes.
3. Set up nightly backup jobs for your active project folders.
4. Use the two-pane explorer for cross-cloud file delivery and management.

Freelancers cannot afford to lose client files or waste time juggling multiple cloud apps. RcloneView consolidates everything into one interface with automated backups and direct cloud-to-cloud transfers.

Related Guides:

• Add Remote via Browse-based Log-in(OAuth)
• Create Sync Jobs
• Job Scheduling

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Publishing and print media companies handle thousands of manuscripts, design files, and print-ready assets. RcloneView centralizes these files across cloud platforms and automates the backups that protect years of editorial work.

The publishing industry runs on files — manuscripts in Word and PDF, book covers and illustrations in PSD and AI, page layouts in InDesign, and print-ready output in high-resolution PDF/X. These files flow between authors, editors, designers, proofreaders, and print production teams, often using different cloud platforms at each stage. A manuscript might start in Google Docs, move to Dropbox for editorial review, then land on an internal server for layout and production.

RcloneView connects all these platforms into a single interface, enabling publishing teams to manage their complex file workflows without manual downloading and re-uploading at every stage.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Publishing Workflow Challenges​

Publishing companies face several file management pain points:

• Large file sizes: A single book's design files (cover art, interior layout, illustrations) can total several gigabytes. Multi-volume series or art books can reach tens of gigabytes.
• Version control: Manuscripts go through dozens of revisions. Losing track of which version is current — or losing an earlier version that needs to be referenced — causes costly delays.
• Multi-platform teams: Authors use Google Docs, editors prefer Dropbox, designers work from local drives, and production sends files to print vendors via FTP. No single platform covers everyone.
• Long-term archival: Published works must be archived indefinitely. Backlist titles from decades ago may need reprinting, requiring access to original design files.
• Seasonal peaks: Publishing schedules create seasonal surges — fall catalog production, end-of-year releases — when file management demands spike.

Editorial Pipeline Management​

The editorial pipeline moves manuscripts through distinct stages: submission, developmental editing, copyediting, proofreading, and production. At each stage, different team members need access, and files often change platforms.

RcloneView's two-pane explorer bridges these platforms. An editor can pull the latest manuscript from an author's Google Drive, compare it against the previous version in the company's Dropbox, and push the approved version to the production team's OneDrive — all from one interface. The compare feature highlights files that differ between locations, making it easy to spot which manuscripts have been updated.

Design Asset Synchronization​

Design teams work with files that are too large for most cloud sync clients to handle gracefully. A single InDesign package for a 300-page book — including linked images, fonts, and the layout file — can exceed 10 GB. Syncing these packages between the designer's workstation, a review server, and cloud backup requires a tool that handles large files reliably.

RcloneView's multi-threaded transfers and resumable uploads ensure that large design packages transfer completely, even on imperfect connections. If a transfer is interrupted, RcloneView picks up where it left off rather than restarting from scratch.

For designers who need to access files stored in the cloud without downloading entire packages, RcloneView's mount feature maps a cloud folder as a local drive. This lets InDesign, Photoshop, and Illustrator open cloud-hosted files directly — useful for reviewing layouts without a full download.

Print Production File Delivery​

Print-ready files need to reach production vendors — printers, binderies, and distributors — reliably and on schedule. Many vendors still accept files via FTP or SFTP. Others use cloud storage drops on Google Drive or Dropbox.

RcloneView connects to FTP, SFTP, Google Drive, Dropbox, and S3 from the same interface. Drag print-ready PDFs from your internal storage to the vendor's FTP server, or copy them to a shared Dropbox folder. RcloneView's real-time monitoring confirms that files were delivered completely, and the job history provides a record of every delivery for production tracking.

Backlist and Long-Term Archival​

Published titles remain in a publisher's catalog indefinitely. Reprint requests, new editions, translations, and rights sales all require access to original files — sometimes decades after initial publication. Storing these archives on expensive active storage is wasteful; losing them is unacceptable.

RcloneView enables cost-effective archival by syncing completed project folders to cold storage tiers. Transfer finished books to AWS S3 Glacier Deep Archive ($0.00099/GB/month) or Backblaze B2. Organize archives by title, series, or imprint for easy retrieval. When a reprint request comes in, pull the specific title's files back to active storage through RcloneView.

Automated Backups for Active Projects​

Active projects need daily backups. A corrupted InDesign file or an accidentally overwritten manuscript can set production back by weeks. RcloneView's scheduler automates nightly backups of active project folders to a separate cloud provider.

Configure a sync job from the production team's primary storage (OneDrive, Google Drive, or a NAS) to a backup destination (Backblaze B2, Wasabi, or AWS S3). RcloneView's delta detection ensures only changed files are transferred each night, keeping backup windows short and costs low.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add remotes for each platform in your editorial pipeline (Google Drive, Dropbox, OneDrive, FTP, S3).
3. Set up automated nightly backups for active production projects.
4. Create an archival workflow for completed titles using cold storage tiers.

Publishing companies build their catalogs over decades. RcloneView ensures that every manuscript, design file, and print-ready asset is backed up, accessible, and organized across whatever cloud platforms your team uses.

Related Guides:

• Add Remote via Browse-based Log-in(OAuth)
• Browse and Manage Remote Storage
• Create Sync Jobs
• Mount Cloud Storage as a Local Drive

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Different cloud providers and operating systems handle filenames differently. Unicode characters, special symbols, and encoding mismatches cause sync failures — here is how to diagnose and fix them in RcloneView.

A file named résumé_2026.pdf on Google Drive might fail to sync to OneDrive for Business. A folder with Japanese characters on a local NAS might not transfer to S3. A filename containing #, %, or : might work on Dropbox but get rejected by SharePoint. These encoding and character compatibility issues are among the most frustrating cloud sync problems because they silently skip files or produce errors that are difficult to interpret.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Common Symptoms​

• "Invalid filename" or "Unsupported character" errors: The destination provider rejects filenames containing characters it does not support.
• Files silently skipped during sync: Transfer completes "successfully" but some files are missing on the destination. These files typically have problematic characters in their names.
• Garbled filenames on destination: Files arrive but their names contain %xx escape sequences, replacement characters (?), or mojibake (incorrect character rendering).
• "Path too long" errors: Encoded filenames become longer than the destination's path length limit (e.g., 400 characters for SharePoint, 1024 for S3).
• Duplicate files with similar names: Two files that look identical (e.g., café with composed vs. decomposed Unicode) are treated as different files.

Understanding the Problem​

Provider Character Restrictions​

Each cloud provider has different rules about allowed filename characters:

When syncing from a permissive provider (Google Drive, S3) to a restrictive one (OneDrive Business, SharePoint), files with restricted characters will fail unless encoded.

Unicode Normalization​

Unicode provides multiple ways to represent the same character. For example, é can be:

• NFC (composed): A single code point U+00E9
• NFD (decomposed): Two code points U+0065 + U+0301

macOS typically uses NFD, while Windows and Linux use NFC. Google Drive preserves the original encoding, while OneDrive normalizes to NFC. This means a file created on macOS and uploaded to Google Drive might not match the same file on OneDrive during comparison — even though the filename looks identical to humans.

Fix 1: Enable Automatic Character Encoding​

RcloneView (through rclone) automatically encodes restricted characters when transferring between providers. By default, each remote type has an encoding preset that handles its specific restrictions. For example, when copying to OneDrive, characters like ", *, and : are automatically replaced with Unicode equivalents that look similar but are allowed.

If you are seeing encoding errors despite this, verify that the encoding is not disabled. In the remote configuration, check that the encoding parameter is set to its default (do not set it to None). You can view and modify this in RcloneView's Remote Manager.

Fix 2: Handle Unicode Normalization​

If you are syncing between macOS-origin files and Windows-based cloud providers, Unicode normalization differences can cause false positives during comparison (files appear different when they are not) or duplicate files on the destination.

Use the --no-unicode-normalization flag in RcloneView's custom flags if you want to preserve the exact byte sequence of filenames. Alternatively, most cloud providers normalize filenames server-side, and rclone's default behavior handles this correctly for the most common cases.

For persistent issues, the --fix-case flag can help when case sensitivity differences between providers cause problems (e.g., S3 is case-sensitive; Windows local filesystem is not).

Fix 3: Rename Problematic Files​

For a small number of files with problematic characters, the simplest fix is to rename them on the source. Use RcloneView's explorer to identify files with special characters and rename them directly. Common characters to avoid across all providers:

• # % & { } \ < > * ? / $ ! ' " : @ + \`` \| =
• Leading or trailing spaces and periods
• Windows reserved names (CON, PRN, AUX, NUL, COM1-9, LPT1-9)

Fix 4: Use Filter Rules to Skip Problematic Files​

If you cannot rename files (e.g., they are on a shared drive you do not control), use filter rules to exclude files with specific character patterns from the sync. This is a workaround rather than a fix, but it prevents the sync from failing or stalling on problematic files.

In RcloneView's job configuration, add filter rules like:

• --exclude "**/*#*" to skip files containing #
• --exclude "**/*%*" to skip files containing %

Review the sync logs afterward to identify which files were skipped and handle them manually if needed.

Fix 5: Check Path Length Limits​

When filenames are encoded, they become longer (each restricted character is replaced with a multi-byte Unicode sequence). If the source path is already near the destination's limit, encoding pushes it over.

SharePoint has a 400-character path limit. Windows has a 260-character limit by default (configurable). S3 has a 1024-character key limit.

If you encounter path-too-long errors, shorten folder names in the source hierarchy or flatten deeply nested structures. RcloneView's explorer shows the full path, making it easy to identify deeply nested files.

Preventing Future Issues​

• Standardize filenames before upload: Avoid special characters in filenames from the start. Stick to alphanumeric characters, hyphens, underscores, and periods.
• Test with dry run: Before large syncs between providers with different character rules, use RcloneView's dry run mode to identify potential encoding issues without transferring data.
• Review sync logs: After each sync, check the job history for warnings about skipped or renamed files. Address these proactively before they accumulate.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Verify that your remote configurations use default encoding settings.
3. Use dry run to identify encoding issues before committing to a transfer.
4. Rename or filter problematic files as needed.

Encoding and Unicode issues are subtle but common when syncing across providers. RcloneView's automatic encoding handles the majority of cases, and the troubleshooting steps above resolve the rest.

Related Guides:

• Browse and Manage Remote Storage
• Create Sync Jobs
• Job History

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

S3 multipart uploads split large files into chunks for parallel transfer and resumability, but failures during the process can leave incomplete uploads, waste storage, and block transfers — here is how to fix them in RcloneView.

Amazon S3 and S3-compatible providers (Wasabi, Backblaze B2 S3, Cloudflare R2, MinIO, DigitalOcean Spaces) require multipart uploads for files larger than 5 GB and recommend them for files over 100 MB. The file is split into parts (default 5 MB to 5 GB each), uploaded in parallel, and assembled server-side. When this process fails partway through — due to network interruptions, timeouts, or misconfigured part sizes — the result is an incomplete upload that consumes storage but produces no usable object.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Common Symptoms​

• Upload stalls or hangs: The transfer appears to stop midway through a large file. RcloneView's monitoring shows no progress for an extended period.
• "EntityTooSmall" error: Parts smaller than the minimum size (5 MB for most S3 providers) were uploaded. This typically happens when the chunk size configuration is too small relative to the file size.
• "EntityTooLarge" error: A single part exceeds the maximum allowed size (5 GB).
• "InvalidPart" or "InvalidPartOrder": Parts were uploaded out of order or a part was corrupted during transfer. The server rejects the completion request.
• Storage usage grows but files do not appear: Incomplete multipart uploads consume storage. The parts exist on the server but the final object is never assembled.

Fix 1: Adjust Chunk Size​

The most common cause of multipart failures is an incorrect chunk size relative to the file size. S3 allows a maximum of 10,000 parts per upload. If your chunk size is too small for a large file, the upload exceeds the part limit and fails.

Example: A 500 GB file with the default 5 MB chunk size would require 100,000 parts — far exceeding the 10,000-part limit.

In RcloneView, adjust the chunk size when configuring your S3 remote or in the job's advanced options. A good rule of thumb: set chunk size to at least file_size / 10,000. For a 500 GB file, use at least 50 MB chunks. For most workloads, 64 MB to 128 MB chunks provide a good balance between parallelism and reliability.

You can set this with the --s3-chunk-size flag in RcloneView's custom flags field.

Fix 2: Increase Upload Timeout​

Large parts over slow connections can exceed the default timeout. If your connection is slower than 10 Mbps, a 128 MB chunk could take over 100 seconds to upload — close to default timeout limits.

Increase the timeout with the --timeout flag. For example, --timeout 300s gives each part up to 5 minutes to complete. You can also reduce the chunk size to make individual parts faster to transfer.

Fix 3: Reduce Transfer Concurrency​

Uploading too many parts simultaneously can overwhelm your network connection or the S3 endpoint. If you see frequent timeouts or connection resets during multipart uploads, reduce the number of concurrent transfers.

In RcloneView's job configuration, lower the transfers count from the default (4) to 2 or even 1 for very large files. You can also use --s3-upload-concurrency to control how many parts of a single file are uploaded in parallel (default is 4).

Fix 4: Clean Up Orphaned Multipart Uploads​

Failed multipart uploads leave orphaned parts on the server that consume storage and incur costs. These parts are not visible as objects — you will not see them when browsing the bucket in RcloneView or the AWS console.

To clean up orphaned uploads:

• AWS S3: Configure a lifecycle rule on the bucket to automatically abort incomplete multipart uploads after a specified number of days (e.g., 7 days). This is done in the AWS console under the bucket's Management tab.
• Using rclone: Run rclone cleanup remote:bucket from RcloneView's built-in terminal. This aborts all pending multipart uploads on the specified bucket.
• S3-compatible providers: Most providers support the same lifecycle rules or cleanup commands, but check your provider's documentation for specifics.

Fix 5: Enable Retry on Failure​

Network interruptions during multipart uploads can cause individual parts to fail. RcloneView retries failed operations automatically (default 3 retries with exponential backoff). If you experience frequent transient failures, increase the retry count with --retries 5 or --retries 10 in the custom flags.

For very unreliable connections, also set --low-level-retries 10 to retry individual HTTP requests before counting them as a failed operation.

Fix 6: Use Server-Side Copy When Possible​

If you are copying between two S3-compatible buckets on the same provider, server-side copy avoids multipart upload issues entirely — the data moves within the provider's network without passing through your machine. RcloneView uses server-side copy automatically when both source and destination are on the same S3 provider.

For cross-provider transfers (e.g., AWS S3 to Cloudflare R2), data must pass through your machine and multipart uploads apply on the destination side.

Preventing Future Failures​

• Set chunk size proactively: Before uploading files larger than 1 GB, calculate the required chunk size (file_size / 10,000) and set it in the custom flags.
• Enable lifecycle cleanup: Always configure a lifecycle rule to abort incomplete multipart uploads. This prevents orphaned parts from accumulating.
• Monitor transfers: Use RcloneView's real-time monitoring to catch stalled uploads early. Pausing and resuming a stalled transfer often resolves transient issues.
• Test with dry run: For critical uploads, use RcloneView's dry run mode to verify the transfer plan before committing.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Configure your S3 remote with an appropriate chunk size for your largest files.
3. Set lifecycle rules on your buckets to auto-clean orphaned uploads.
4. Monitor transfers in real time and adjust concurrency as needed.

Multipart upload failures are the most common issue when working with large files on S3. Proper chunk size configuration, timeout settings, and orphaned upload cleanup resolve the vast majority of cases.

Related Guides:

• Add AWS S3 and S3-Compatible
• Real-time Transfer Monitoring
• Create Sync Jobs

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

SSL/TLS certificate errors prevent RcloneView from establishing secure connections to cloud providers. These errors range from expired certificates to corporate proxy interception — here is how to diagnose and resolve them.

Every connection RcloneView makes to a cloud provider uses HTTPS with TLS encryption. The TLS handshake verifies the server's identity through its SSL certificate. When this verification fails, RcloneView cannot connect — no browsing, no transfers, no sync. Certificate errors are especially common in corporate environments with SSL-inspecting proxies, when connecting to self-hosted storage (MinIO, Nextcloud, Seafile), or when system time is incorrect.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Common Error Messages​

• "x509: certificate signed by unknown authority": The server's certificate was issued by a Certificate Authority (CA) that your system does not trust. Common with self-hosted storage and corporate proxies.
• "x509: certificate has expired or is not yet valid": The certificate's validity period does not match the current system time. Either the certificate is genuinely expired or your system clock is wrong.
• "x509: certificate is valid for X, not Y": The certificate's Common Name or Subject Alternative Names do not match the hostname you are connecting to. This happens when the endpoint URL does not match the certificate.
• "tls: failed to verify certificate": A generic TLS verification failure. Check the full error message for specifics.
• "remote TLS connection closed unexpectedly": The TLS handshake was interrupted, often by a firewall or proxy.

Fix 1: Check System Clock​

The simplest and most commonly overlooked cause: your system clock is wrong. TLS certificates have a validity window (Not Before / Not After). If your clock is outside this window, every certificate appears invalid.

On Windows, check Settings > Time & Language > Date & Time and ensure "Set time automatically" is enabled. On Linux, run timedatectl and verify the time is correct. On macOS, check System Preferences > Date & Time.

A system clock that is off by even a few hours can trigger certificate errors, especially for certificates that were recently issued or are close to expiration.

Fix 2: Corporate Proxy / SSL Inspection​

Many corporate networks use an SSL-inspecting proxy that intercepts HTTPS connections, decrypts them for inspection, and re-encrypts them with the organization's own certificate. This effectively performs a man-in-the-middle operation that is trusted by company-managed machines (because the corporate CA is installed in the system trust store) but may not be trusted by rclone's embedded certificate bundle.

To fix this, you need to tell rclone to use your system's certificate store or provide the corporate CA certificate explicitly:

• Option A: Set the --ca-cert flag in RcloneView's custom flags to point to the corporate CA certificate file. For example: --ca-cert /path/to/corporate-ca.pem.
• Option B: On Linux, ensure the corporate CA certificate is installed in the system trust store (/etc/ssl/certs/ on Debian/Ubuntu, /etc/pki/tls/certs/ on RHEL/CentOS). Run update-ca-certificates after adding the certificate.
• Option C: On Windows, if the corporate CA is installed in the Windows certificate store, rclone may not use it by default (it uses its own Go TLS implementation). Export the corporate CA from the Windows certificate store as a PEM file and use --ca-cert.

Contact your IT department to obtain the corporate CA certificate if you do not have it.

Fix 3: Self-Signed Certificates (Self-Hosted Storage)​

When connecting to self-hosted storage like MinIO, Nextcloud via WebDAV, or a private SFTP server with a self-signed TLS certificate, rclone will reject the connection because the certificate is not issued by a trusted CA.

You have two options:

• Recommended: Add your self-signed certificate to the system trust store or use --ca-cert to point to the certificate file. This maintains TLS verification while trusting your specific certificate.
• Not recommended but sometimes necessary: Use --no-check-certificate in the custom flags. This disables certificate verification entirely, making the connection vulnerable to man-in-the-middle attacks. Only use this for testing on trusted networks, never in production.

For MinIO specifically, consider generating a proper certificate using Let's Encrypt (free) instead of using a self-signed certificate.

Fix 4: Expired Server Certificate​

If the cloud provider's certificate has genuinely expired, there is nothing you can do on the client side — the provider needs to renew it. This is rare for major providers (AWS, Google, Microsoft, Dropbox) but can happen with smaller providers or self-hosted solutions.

Verify by checking the certificate in a web browser: navigate to the provider's URL and click the lock icon to view certificate details. If the certificate is expired, contact the provider. For self-hosted storage, renew the certificate using your CA or Let's Encrypt.

Fix 5: Hostname Mismatch​

Certificate hostname mismatches occur when the URL you are connecting to does not match the certificate's Common Name or Subject Alternative Names. This is common when:

• You connect to an S3-compatible endpoint using an IP address instead of the hostname.
• The endpoint URL has a typo or uses a different subdomain than the certificate covers.
• You are accessing a service through a load balancer or reverse proxy that presents a different certificate.

Fix by using the exact hostname that the certificate was issued for. Check the remote configuration in RcloneView's Remote Manager and verify the endpoint URL matches the certificate's hostnames.

Fix 6: Update rclone and RcloneView​

Older versions of rclone may use an outdated certificate bundle that does not include newer Certificate Authorities. Update to the latest version of RcloneView, which includes an updated rclone binary with current CA certificates.

Diagnosing Certificate Issues​

When a certificate error occurs, gather details using RcloneView's built-in terminal:

1. Run rclone lsd remote: with --verbose to see the full error message including certificate details.
2. Use openssl s_client -connect endpoint:443 (if available) to inspect the server's certificate chain.
3. Check the certificate's issuer, expiration date, and Subject Alternative Names to identify the specific problem.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. If you encounter certificate errors, check your system clock first.
3. For corporate environments, obtain and configure the corporate CA certificate.
4. For self-hosted storage, add the self-signed certificate to your trust store.

SSL/TLS certificate errors are always resolvable — the fix depends on whether the issue is your system clock, a corporate proxy, a self-signed certificate, or an expired server certificate. Identifying the root cause from the error message is the key to a quick resolution.

Related Guides:

• Add AWS S3 and S3-Compatible
• Add WebDAV
• Browse and Manage Remote Storage

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Power users know that keyboard shortcuts can cut file management time in half. RcloneView's shortcut system gives you fast access to navigation, selection, transfers, and job management without reaching for the mouse.

RcloneView's two-pane explorer is designed for efficient file operations across cloud providers. While the GUI is fully navigable with mouse clicks, learning the keyboard shortcuts transforms your workflow — especially when managing thousands of files across multiple remotes. This guide covers the essential shortcuts and workflow tips that experienced RcloneView users rely on daily.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Navigation Shortcuts​

Efficient navigation is the foundation of fast file management. These shortcuts let you move between panes, switch remotes, and navigate folder trees without clicking:

Pane Management​

• Tab: Switch focus between the left and right panes. This is the most-used shortcut in RcloneView — it lets you alternate between source and destination without moving your hands from the keyboard.
• Enter: Open the selected folder or file. For folders, this navigates into them. For files, this triggers the default action.
• Backspace / Alt+Up: Navigate up one directory level in the current pane.

File Selection​

• Ctrl+A: Select all files in the current pane. Useful for bulk operations like copying an entire folder's contents.
• Shift+Click: Select a range of files between the last selected file and the clicked file.
• Ctrl+Click: Toggle selection of individual files without deselecting others. Build up a multi-file selection across non-contiguous items.

File Operation Shortcuts​

Once you have files selected, these shortcuts execute operations quickly:

• Ctrl+C: Copy selected files to clipboard (for paste to the other pane).
• Ctrl+X: Cut selected files (move operation).
• Ctrl+V: Paste files from clipboard to the current pane's location.
• Delete / Del: Delete selected files on the remote. RcloneView prompts for confirmation before deletion.
• F2: Rename the selected file or folder.
• Ctrl+Shift+N: Create a new folder in the current pane's location.

Comparison and Sync Shortcuts​

RcloneView's compare and sync features have their own shortcuts:

• Compare button / shortcut: Launch a folder comparison between the left and right panes. The comparison highlights files unique to each side, files that differ, and identical files.
• Sync shortcuts: Initiate sync from left to right or right to left directly from the toolbar or keyboard.

Search and Filter​

• Ctrl+F: Open the search/filter bar in the current pane. Type a filename pattern to filter the visible files. This is invaluable in folders with hundreds of files — type a few characters to narrow the list instantly.
• Esc: Close the search/filter bar and restore the full file list.

Productivity Tips​

Tip 1: Use Named Remotes Descriptively​

Name your remotes by purpose rather than provider — "Client-A-Drive" instead of "Google-Drive-2". When you have 10+ remotes, descriptive names save time finding the right one in the dropdown.

Tip 2: Leverage the Two-Pane Layout​

Keep your most-used remote in the left pane and switch the right pane as needed. For example, always keep your backup destination (Backblaze B2, S3) in the left pane and load different source remotes in the right pane. This creates a consistent spatial model — "left is backup, right is source" — that becomes automatic.

Tip 3: Pin Frequently Used Paths​

If you repeatedly navigate to the same deeply nested folder, create a bookmark or alias remote that points directly to it. Instead of navigating remote:/projects/2026/client-a/deliverables/ every time, create an alias remote called "Client-A-Deliverables" that opens directly to that path.

Tip 4: Use Dry Run Before Sync​

Before running a sync job on production data, always preview with dry run. This shows exactly what will be transferred, deleted, or skipped — without actually making changes. Catch errors before they happen.

Tip 5: Batch Operations with Job Queue​

Instead of running transfers one at a time, queue multiple jobs. Set up a copy from Remote A to B, then a sync from C to D, and let them run sequentially. The job queue handles execution order while you move on to other work.

Tip 6: Monitor Without Interrupting​

Switch to the transfer monitoring view to check progress without stopping your navigation. RcloneView shows real-time transfer speeds, per-file progress, and estimated completion time. Pause or cancel individual transfers without affecting others in the queue.

Tip 7: Use Drag and Drop for Quick Transfers​

For one-off transfers, drag and drop is the fastest method. Select files in one pane and drag them to the other. This works across any two remotes — cloud to cloud, local to cloud, or cloud to local.

Tip 8: Review Job History Regularly​

The job history panel records every operation with statistics. Review it periodically to confirm that scheduled jobs are running successfully, check transfer speeds, and identify any errors. This habit catches problems early — before a failed backup becomes a missed backup.

Building Muscle Memory​

The fastest way to internalize shortcuts is to use them deliberately for one week. Each time you reach for the mouse to switch panes, stop and press Tab instead. Each time you right-click to copy, use Ctrl+C instead. After a week, the shortcuts become automatic and your file management speed increases noticeably.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Set up your remotes with descriptive names.
3. Practice the navigation shortcuts (Tab, Enter, Backspace) until they are automatic.
4. Use Ctrl+F to filter large folders instead of scrolling.
5. Leverage dry run, job queues, and history reviews for confident operations.

Keyboard shortcuts and workflow habits compound over time. A few seconds saved per operation adds up to hours saved per month when you manage files across multiple cloud providers daily.

Related Guides:

• Browse and Manage Remote Storage
• Drag & Drop files
• Compare Folder Contents
• Execute & Manage Jobs

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Sharing a cloud file usually means navigating to the provider's web interface, adjusting permissions, and copying a link. RcloneView's link feature generates shareable URLs directly from the file explorer — across any provider that supports it.

When you need to share a file stored in the cloud with someone who does not have access to your account, a public or pre-signed link is the standard solution. Google Drive creates shareable links, S3 generates pre-signed URLs, and Dropbox provides shared links — each through different interfaces with different workflows. RcloneView consolidates this into a single action: right-click a file, generate a link, and share 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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

How Public Links Work Across Providers​

Different cloud providers implement file sharing differently:

RcloneView uses rclone's link command under the hood, which generates the appropriate link type for each provider automatically. You do not need to know the provider-specific sharing mechanism — RcloneView handles it.

Generating a Link in RcloneView​

To generate a public link for a file:

1. Browse to the file in RcloneView's explorer.
2. Right-click the file and select the link/share option.
3. RcloneView generates the link and copies it to your clipboard (or displays it for manual copying).

For providers that support expiry (like S3 pre-signed URLs), you can specify the link duration using the --expire flag in custom options. For example, --expire 24h creates a link that expires in 24 hours.

Using the Link Command via Terminal​

For more control, use RcloneView's built-in terminal to run the link command directly:

rclone link remote:path/to/file.pdf

This outputs the public URL. For S3-compatible providers, add an expiry:

rclone link remote:bucket/file.pdf --expire 48h

The terminal approach is useful when generating links for multiple files or scripting link generation as part of a workflow.

Provider-Specific Behavior​

Google Drive​

When you generate a link for a Google Drive file, rclone changes the file's sharing settings to "anyone with the link can view." The link does not expire unless you manually revoke sharing. Be aware that this modifies the file's permissions — anyone with the URL can access the file.

For Google Workspace accounts, administrators may restrict link sharing to organization members only. In that case, the generated link will only work for people within your organization.

OneDrive and SharePoint​

OneDrive generates sharing links through the Microsoft Graph API. The link type depends on your organization's sharing policies — it may be anonymous (accessible to anyone) or restricted to organization members. Personal OneDrive accounts can create anonymous links.

AWS S3 and S3-Compatible​

S3 pre-signed URLs are the most secure option. The URL contains a cryptographic signature that grants temporary access to a specific object. The link expires after the specified duration (default varies, maximum 7 days for IAM user credentials). No changes are made to the object's permissions — the pre-signed URL itself carries the authorization.

This makes S3 pre-signed URLs ideal for sharing files temporarily: the link works for the specified duration and then becomes invalid, with no cleanup needed.

Dropbox​

Dropbox creates a shared link that provides read-only access to the file. The link does not expire by default on Dropbox Plus and Professional plans. On Dropbox Business, administrators can enforce expiry policies.

Use Cases​

Quick File Sharing​

Generate a link for a report, design file, or dataset stored in the cloud and send it via email, Slack, or chat. The recipient downloads the file without needing a cloud account or access to your storage.

Temporary Access for Clients​

For freelancers and agencies, S3 pre-signed URLs are ideal for client deliveries. Upload the deliverable to S3, generate a 7-day pre-signed URL, and send it to the client. After 7 days, the link expires automatically — no manual cleanup needed.

Public Content Distribution​

For files intended for broad distribution (documentation, releases, media kits), generate a permanent link from Google Drive or Dropbox and embed it on your website or documentation. RcloneView generates the link without navigating to the provider's web interface.

Security Considerations​

• Permanent links expose files indefinitely: Google Drive and Dropbox links do not expire by default. If you share a sensitive file, remember to revoke the link when access is no longer needed.
• Pre-signed URLs are time-limited but shareable: Anyone with the URL can access the file during the validity period. Do not share pre-signed URLs in public channels if the file is confidential.
• Link generation modifies permissions on some providers: Google Drive links change the file's sharing settings. This is visible to other users who have access to the file.
• Audit shared links periodically: Review and revoke old shared links, especially for sensitive files. RcloneView's explorer makes it easy to navigate to files and check their sharing status.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add your cloud remotes in the Remote Manager.
3. Browse to a file in the explorer and generate a public link.
4. For time-limited links, use S3 pre-signed URLs with the --expire flag.

Generating shareable links from RcloneView saves you from switching to each provider's web interface. Whether you need a quick share link, a temporary client delivery URL, or a permanent download link, RcloneView handles it from the file explorer.

Related Guides:

• Browse and Manage Remote Storage
• Add AWS S3 and S3-Compatible
• Add Remote via Browse-based Log-in(OAuth)

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Google Drive is the backbone of Google Workspace, but managing backups and cross-cloud transfers requires more than the native client — RcloneView delivers that control through a visual interface.

Google Drive serves over two billion users with 15 GB of free storage shared across Gmail, Drive, and Photos. Workspace plans scale to unlimited storage on Enterprise tiers. The native Google Drive desktop client syncs files to your local machine, but it cannot replicate data to AWS S3, OneDrive, or a NAS. RcloneView connects to Google Drive via the Drive API v3 and provides a complete file management interface — browse, sync, copy, move, and schedule backups across Google Drive and any other storage provider.

Whether you are a student protecting coursework, a photographer managing thousands of RAW files, or a Workspace administrator syncing Shared Drives to an independent backup target, RcloneView gives you capabilities that the native client does not offer.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Connecting Google Drive in RcloneView​

Adding Google Drive uses the standard OAuth 2.0 flow. Open the Remote Manager, select Google Drive, and click authorize. A browser window opens where you log in to your Google account and grant access. The token is stored securely in your local rclone configuration.

During setup you choose the scope of access — full drive access, read-only, or file-level access limited to files created by RcloneView. For most backup and sync workflows, full access is the right choice. You can also configure access to Shared Drives (formerly Team Drives) during this step, selecting a specific Shared Drive by ID or letting RcloneView list all available drives.

Google Drive enforces API quotas — 10,000 queries per 100 seconds per project by default. RcloneView handles 403 userRateLimitExceeded responses automatically with exponential backoff. For large-scale operations, you can register your own Google Cloud project and supply your own client ID to increase quota limits.

My Drive vs. Shared Drives​

Google Drive distinguishes between My Drive (personal storage tied to a user account) and Shared Drives (organization-owned storage where files belong to the team, not an individual). This distinction matters for sync and backup because Shared Drives have different ownership semantics, stricter file naming rules, and separate storage quotas.

RcloneView handles both transparently. You can open My Drive and a Shared Drive side by side in the two-pane explorer, compare folder contents, and sync between them. When syncing from My Drive to a Shared Drive, RcloneView automatically adjusts for Shared Drive limitations — files with unsupported characters are renamed, and shortcut files are resolved or skipped depending on your preference.

Syncing Google Drive with Other Cloud Providers​

RcloneView's two-pane explorer places Google Drive alongside any other remote. Sync your entire Drive to Backblaze B2 for affordable backup, copy a specific project folder to AWS S3 for archival, or move old files to Wasabi for cost-effective cold storage.

Google Drive uses MD5 checksums for file integrity verification. RcloneView natively supports MD5 comparison during sync, so only files that have actually changed are transferred. This saves both time and API quota. For Google Docs, Sheets, and Slides — which are stored as cloud-native formats without a fixed file size — RcloneView exports them to standard formats (docx, xlsx, pptx) during download and sync.

For large transfers, you can configure multi-threaded downloads and adjust chunk sizes. Google Drive supports resumable uploads for files over 5 MB, and RcloneView leverages this to recover from interruptions without restarting the entire file.

Scheduling Automated Google Drive Backups​

A single copy of your data on Google Drive is not a backup. Accidental deletions, account suspensions, and ransomware can all result in data loss. An independent backup to a separate provider adds a critical safety net.

RcloneView's scheduler automates this process. Configure a nightly sync job from Google Drive to AWS S3 or Backblaze B2, and RcloneView handles delta detection, transfer, and logging. The job history panel records every run with statistics — files transferred, files skipped, total bytes moved, and elapsed time.

For Workspace administrators, scheduled backups of Shared Drives ensure that team data is replicated independently of Google's infrastructure. Pair scheduled backups with encryption (using a crypt remote) for an additional layer of protection.

Comparing Folders and Verifying Data​

Before committing to a large sync, RcloneView's compare feature shows exactly what will change. Select two folders — one on Google Drive, one on another remote — and RcloneView highlights files that exist only on one side, files that differ in size or hash, and files that are identical.

This is especially valuable after a migration. Run a compare between your Google Drive source and the backup destination to confirm every file arrived intact. The visual diff makes it straightforward to spot gaps and resolve them before decommissioning the original.

Mounting Google Drive as a Local Drive​

RcloneView can mount Google Drive as a local drive letter on Windows or a mount point on macOS and Linux. This lets you access Drive files directly from any application — file managers, video editors, or command-line tools — without downloading them first.

Enable VFS caching for best performance. This stores recently accessed files locally so subsequent reads are instant. The cache size and expiration are configurable. Mounting is particularly useful for media workflows where you need to browse or preview Drive files without a full sync.

Monitoring Transfers in Real Time​

During large transfers, RcloneView provides a real-time monitoring dashboard showing transfer speed, progress per file, and overall completion percentage. You can pause, resume, or cancel individual transfers without affecting the rest of the queue. Bandwidth throttling prevents Google Drive transfers from saturating your network — set a limit during business hours and allow full speed overnight.

Browsing and Managing Files​

RcloneView's explorer offers capabilities that the Google Drive web interface does not — bulk operations across tens of thousands of files, drag-and-drop between any two cloud providers, and side-by-side folder comparison. You can rename, move, delete, and create folders directly on Google Drive through the explorer. Shared Drives, shortcuts, and nested folder structures are all navigable in the explorer panel.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Authorize your Google account via OAuth in the Remote Manager and select your Drive type (My Drive or Shared Drive).
3. Browse your Google Drive in the two-pane explorer and set up a sync or copy job to another provider.
4. Schedule a daily backup to keep a redundant copy on S3, B2, or another cloud.

Google Drive handles collaboration and document editing, but RcloneView ensures your data is backed up, portable, and accessible across every cloud you use.

Related Guides:

• Add Google Drive
• Browse and Manage Remote Storage
• Create Sync Jobs
• Mount Cloud Storage as a Local Drive

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

SharePoint Online powers document management across Microsoft 365, but syncing its content to external clouds or a NAS requires a purpose-built tool — RcloneView bridges that gap.

SharePoint Online is the document management backbone for millions of organizations using Microsoft 365. Each SharePoint site contains document libraries that store team files, project assets, and corporate records. While the native OneDrive sync client can sync SharePoint libraries to local machines, it provides no mechanism for replicating data to AWS S3, Google Drive, or external storage. RcloneView connects to SharePoint Online via the Microsoft Graph API and exposes document libraries as navigable remotes — browse, sync, copy, move, and schedule backups across SharePoint and any other provider.

Whether you need to back up a compliance-sensitive library to immutable S3 storage or migrate a departing team's SharePoint site to Google Workspace, RcloneView handles it through a visual interface.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Connecting SharePoint in RcloneView​

SharePoint remotes in RcloneView are configured through the OneDrive remote type. During OAuth authorization, select SharePoint site instead of OneDrive Personal or Business. RcloneView queries the Graph API for available sites and lets you pick the target site and document library.

Each document library appears as a separate navigable path. If your organization has dozens of SharePoint sites — Marketing, Engineering, Legal, HR — you can add each as a separate remote or switch between libraries within a single remote configuration.

SharePoint's API throttling follows the same patterns as OneDrive for Business — 429 responses with Retry-After headers. RcloneView respects these automatically, using exponential backoff to ensure large transfers complete without manual intervention.

Navigating SharePoint Document Libraries​

SharePoint document libraries can contain nested folder structures, metadata columns, and versioned files. RcloneView's explorer displays the folder tree and file listing in its familiar two-pane layout. You can browse deep folder hierarchies, select files across multiple folders, and perform bulk operations — copy, move, delete, or download.

SharePoint enforces filename restrictions that are stricter than many other providers. Characters like #, %, and * are disallowed, and path lengths are limited to 400 characters. When syncing from a less restrictive provider (like Google Drive or a local filesystem) to SharePoint, RcloneView automatically encodes or replaces restricted characters to prevent transfer failures.

Syncing SharePoint to Other Cloud Providers​

Organizations frequently need to replicate SharePoint data to external systems — a secondary cloud for disaster recovery, a NAS for local access, or a different cloud suite during a platform migration. RcloneView makes this straightforward.

Open your SharePoint library in one pane and the destination (AWS S3, Google Drive, Backblaze B2, a local path) in the other. RcloneView compares file lists using size and modification time, transferring only changed files. For initial migrations with thousands of files, multi-threaded transfers and configurable chunk sizes keep the process efficient.

SharePoint stores file hashes as QuickXorHash, the same algorithm used by OneDrive for Business. RcloneView supports QuickXorHash natively, enabling accurate delta detection without downloading file contents for comparison.

Scheduling Automated SharePoint Backups​

SharePoint's built-in retention policies and recycle bin provide some protection, but they operate within Microsoft's ecosystem. A ransomware attack that compromises your Microsoft 365 tenant can affect SharePoint data along with everything else. An independent backup to a separate provider is the strongest protection.

RcloneView's scheduler automates this. Configure a nightly sync job from a SharePoint document library to AWS S3 with versioning enabled, and RcloneView handles the rest. The job history panel logs every run with transfer statistics, making it easy to verify that backups are completing successfully.

For compliance-driven organizations, pairing scheduled SharePoint backups with S3 Object Lock or Backblaze B2's file lock feature creates an immutable archive that satisfies regulatory requirements for data retention.

Comparing Folders and Verifying Migrations​

After syncing or migrating a SharePoint library, use RcloneView's compare feature to verify completeness. Select the SharePoint source and the backup destination, and RcloneView highlights files that exist only on one side, files that differ, and files that are identical. This visual verification eliminates guesswork and ensures data integrity before decommissioning the original.

Mounting SharePoint as a Local Drive​

RcloneView can mount a SharePoint document library as a local drive letter (Windows) or mount point (macOS/Linux). This lets you access SharePoint files from any desktop application — CAD software, image editors, or analytics tools — without the overhead of the OneDrive sync client.

Enable VFS caching to store recently accessed files locally for fast repeated access. This is particularly useful for teams that need to work with SharePoint-hosted files in applications that do not support cloud storage natively.

Monitoring Transfers​

Large SharePoint migrations can involve hundreds of thousands of files. RcloneView's real-time monitoring dashboard shows transfer speed, per-file progress, and overall completion. You can pause, resume, or cancel transfers individually. Bandwidth limits prevent SharePoint transfers from consuming your entire network connection during business hours.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Authorize your Microsoft 365 account via OAuth and select the SharePoint site and document library.
3. Browse your SharePoint library in the two-pane explorer and set up a sync or copy job to another provider.
4. Schedule a daily backup to maintain an independent copy on S3, B2, or another cloud.

SharePoint handles document management within Microsoft 365, but RcloneView ensures your SharePoint data is backed up, portable, and accessible across every cloud you use.

Related Guides:

• Add Remote via Browse-based Log-in(OAuth)
• Browse and Manage Remote Storage
• Create Sync Jobs
• Job Scheduling

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Moving from Google Drive to AWS S3 gives you object-level control, lifecycle policies, and infrastructure-grade durability — RcloneView handles the transfer through a visual interface.

Google Drive excels at collaboration and document editing, but organizations that need fine-grained access control, programmatic integration, or long-term archival often outgrow it. AWS S3 offers 11 nines of durability, lifecycle transitions to Glacier for cold storage, and IAM-based access policies. Migrating from Google Drive to S3 can seem daunting — different authentication models, different file semantics, and potentially terabytes of data. RcloneView simplifies the process with a visual GUI that handles the complexity behind the scenes.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Why Migrate from Google Drive to AWS S3​

Google Drive stores files as objects with Google-specific metadata — MIME types, sharing permissions, and native document formats (Docs, Sheets, Slides). AWS S3 stores objects as raw bytes with user-defined metadata, offering greater flexibility for programmatic access. Common reasons for this migration include:

• Cost optimization: S3 Standard costs roughly $0.023/GB/month, and S3 Glacier Deep Archive drops to $0.00099/GB/month. For large datasets that are rarely accessed, S3 is significantly cheaper than Google Workspace storage plans.
• Infrastructure integration: Applications running on AWS can access S3 directly with IAM roles, eliminating the need for OAuth tokens and API quotas.
• Compliance: S3 supports Object Lock for WORM compliance, bucket policies for IP-based restrictions, and CloudTrail for audit logging.
• Lifecycle management: Automatically transition files from Standard to Infrequent Access to Glacier based on age, reducing costs without manual intervention.

Setting Up Both Remotes​

Google Drive Remote​

Open RcloneView's Remote Manager and add a Google Drive remote. Authorize via OAuth, selecting full access scope. If you need to migrate Shared Drives, select the target Shared Drive during setup. For large migrations, consider registering your own Google Cloud project client ID to increase API quota limits beyond the default 10,000 queries per 100 seconds.

AWS S3 Remote​

Add an S3 remote in the Remote Manager. Provide your AWS Access Key ID and Secret Access Key, select the target region, and specify the bucket name. If the bucket does not exist, you can create it from RcloneView or the AWS console. For the storage class, choose Standard for frequently accessed data or Standard-IA for archival migrations.

Planning the Migration​

Before transferring data, assess the scope:

1. Size audit: Use RcloneView's storage analysis to determine the total size of your Google Drive. This helps estimate S3 costs and transfer time.
2. Google Docs handling: Native Google documents (Docs, Sheets, Slides) have no file size on Drive. During migration, RcloneView exports them to standard formats (docx, xlsx, pptx). Decide whether you need these exports or can skip them.
3. Folder structure: Google Drive allows characters in filenames that S3 handles differently. RcloneView encodes special characters automatically, but review your folder structure for extremely deep nesting or very long path names.
4. Bandwidth: A 1 TB migration at 100 Mbps takes roughly 22 hours. Schedule migrations during off-peak hours or set bandwidth limits to avoid disrupting other operations.

Executing the Migration​

Open Google Drive in the left pane and S3 in the right pane. Navigate to the source folder on Drive and the target prefix on S3. You can copy the entire Drive or select specific folders.

RcloneView uses MD5 checksums from Google Drive and compares them against S3 ETags for files under 5 GB. For larger files uploaded as multipart, S3 ETags are not standard MD5 — RcloneView falls back to size and modification time comparison in these cases.

For the initial migration, use a copy job rather than sync to avoid any risk of deleting files on the destination. Once the initial transfer completes and you verify the data, you can switch to sync for ongoing replication.

Verifying the Migration​

After the transfer completes, use RcloneView's compare feature to verify that every file arrived. Select the Google Drive source and S3 destination and run a comparison. Files that match appear as identical; files that differ or are missing are highlighted.

For critical migrations, run a check operation that computes checksums on both sides and reports any discrepancies. This adds time but provides cryptographic verification of data integrity.

Post-Migration: Ongoing Sync or Cutover​

If you are running Google Drive and S3 in parallel during a transition period, schedule a daily sync job in RcloneView to keep S3 up to date with Drive changes. Once you are ready to cut over, disable the sync job and decommission the Google Drive storage.

For organizations moving from Google Workspace to an AWS-native stack, this migration is often one piece of a larger platform transition. RcloneView can handle the data movement while your team manages the application and workflow changes.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add Google Drive and AWS S3 remotes in the Remote Manager.
3. Run a storage audit to estimate migration size and cost.
4. Execute a copy job from Drive to S3 and verify with compare.
5. Optionally schedule ongoing sync until you are ready to cut over.

Google Drive handles collaboration, but AWS S3 delivers the durability, lifecycle management, and programmatic access that production workloads demand. RcloneView bridges the two with a straightforward migration path.

Related Guides:

• Add Google Drive
• Add AWS S3 and S3-Compatible
• Compare Folder Contents
• Job Scheduling

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Switching from OneDrive to Dropbox means moving files between two different ecosystems — RcloneView handles the transfer, metadata preservation, and verification through a visual interface.

OneDrive integrates deeply with Microsoft 365, while Dropbox focuses on file sync and collaboration with broad third-party app integration. Organizations switching productivity suites, teams moving to Dropbox for its superior smart sync or Paper features, or individuals who prefer Dropbox's file recovery capabilities all face the same challenge: transferring potentially years of data between platforms. RcloneView connects to both via their respective APIs and provides a straightforward migration path.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Why Migrate from OneDrive to Dropbox​

The decision typically involves one or more of these factors:

• Platform switch: Moving from Microsoft 365 to Google Workspace or a suite that does not include OneDrive, while preferring Dropbox for file storage.
• Smart Sync: Dropbox's smart sync (online-only files with local placeholders) has a longer track record and broader application compatibility than OneDrive's Files On-Demand.
• Third-party integrations: Dropbox connects with a wider range of creative and productivity tools through its API ecosystem.
• File recovery: Dropbox Business plans offer 180 days of version history, compared to OneDrive's 30-day limit on Personal plans.
• Cross-platform consistency: Dropbox provides a more uniform experience across Windows, macOS, and Linux.

Setting Up Both Remotes​

OneDrive Remote​

Open RcloneView's Remote Manager and add a Microsoft OneDrive remote. Authorize via OAuth, selecting OneDrive Personal or Business depending on your account type. For Business accounts, choose your personal drive or a SharePoint document library.

Dropbox Remote​

Add a Dropbox remote. Authorize via OAuth — RcloneView opens a browser window for Dropbox login and permission grant. The token is stored in your local rclone configuration. Dropbox remotes provide access to your entire Dropbox, including team folders if you are on a Business plan.

Planning the Migration​

Before starting the transfer:

1. Filename compatibility: OneDrive for Business restricts characters like # and %, while Dropbox has its own restrictions (e.g., trailing spaces and periods). Files that exist on OneDrive may need renaming for Dropbox compatibility. RcloneView handles encoding automatically, but review your file structure for edge cases.
2. Size and structure: Use RcloneView's storage analysis to determine total data volume. A 500 GB migration at 50 Mbps takes roughly 22 hours.
3. Shared files and links: OneDrive sharing permissions and links do not transfer to Dropbox. Document any critical shared links before migrating so you can recreate them on Dropbox.
4. OneNote notebooks: OneNote files stored on OneDrive are not standard files — they require export before migration. Consider exporting them separately.

Executing the Migration​

Open OneDrive in the left pane and Dropbox in the right. Navigate to the source folder and target location. Use a copy job for the initial migration to preserve files on both sides until verification is complete.

RcloneView compares files using size and modification time. OneDrive uses QuickXorHash while Dropbox uses its own content hash — since these are incompatible, RcloneView relies on size and timestamp comparison for delta detection between these two providers. Files that match are skipped, and only new or changed files are transferred.

For large migrations, enable multi-threaded transfers and set an appropriate bandwidth limit to avoid saturating your connection. RcloneView's real-time monitoring shows transfer progress, speed, and estimated completion time.

Verifying the Migration​

After the transfer, use RcloneView's compare feature to verify completeness. Select the OneDrive source and Dropbox destination and run a comparison. Files that match appear as identical; missing or differing files are highlighted.

Pay attention to Google Docs-style files if you had any Office Online documents — these should have been converted to standard Office formats during the transfer. Verify that the converted files open correctly in Dropbox.

Post-Migration Steps​

1. Install the Dropbox desktop client and configure smart sync preferences.
2. Recreate any shared links or folder permissions on Dropbox.
3. Update application integrations that pointed to OneDrive paths.
4. Keep the OneDrive data for a transition period (30-60 days) before deleting it.
5. If running both in parallel, schedule a daily sync job in RcloneView to keep Dropbox current.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add OneDrive and Dropbox remotes in the Remote Manager.
3. Run a copy job from OneDrive to Dropbox.
4. Verify with the compare feature.
5. Complete post-migration steps and decommission OneDrive when ready.

OneDrive and Dropbox serve different ecosystems, but RcloneView ensures your data moves between them cleanly and completely.

Related Guides:

• Add Remote via Browse-based Log-in(OAuth)
• Compare Folder Contents
• Real-time Transfer Monitoring

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Both Wasabi and Cloudflare R2 are S3-compatible and marketed as low-cost alternatives to AWS S3, but their pricing models differ in important ways — RcloneView handles the migration between them with a visual interface.

Wasabi offers hot cloud storage at $6.99/TB/month with no egress fees, but enforces a 90-day minimum storage duration and a minimum monthly charge. Cloudflare R2 charges $0.015/GB/month (roughly $15.36/TB) with zero egress fees and no minimum storage duration. For workloads with frequent data retrieval or short-lived objects, R2 can be significantly cheaper. RcloneView connects to both as S3-compatible remotes and provides a straightforward migration path.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Why Migrate from Wasabi to Cloudflare R2​

Both providers eliminate egress fees, which is their main selling point over AWS S3. The decision to migrate typically comes down to:

• Minimum storage duration: Wasabi charges for at least 90 days of storage per object, even if you delete it sooner. R2 has no minimum, making it better for transient or frequently replaced data.
• CDN integration: R2 integrates natively with Cloudflare's CDN network, enabling instant public access to stored objects through a Cloudflare domain without additional configuration.
• Workers integration: If your application uses Cloudflare Workers, R2 provides zero-latency access from edge compute.
• Pricing at scale: For storage-heavy workloads, Wasabi's flat per-TB rate may be cheaper. For workloads with high API call volume, R2's pricing model (free for the first 10 million Class B requests per month) may win.

Setting Up Both Remotes​

Wasabi Remote​

Open RcloneView's Remote Manager and add an S3-compatible remote. Select Wasabi as the provider, enter your Wasabi Access Key and Secret Key, and specify the region endpoint (e.g., s3.us-east-1.wasabisys.com). Select the bucket you want to migrate.

Cloudflare R2 Remote​

Add another S3-compatible remote and select Cloudflare R2 as the provider. Enter your R2 Access Key ID and Secret Access Key (generated from the Cloudflare dashboard under R2 > Manage R2 API Tokens). The endpoint follows the format https://<account-id>.r2.cloudflarestorage.com. Create a target bucket in the Cloudflare dashboard or let RcloneView create one during setup.

Executing the Migration​

Open Wasabi in the left pane and R2 in the right pane. Navigate to the source bucket on Wasabi and the target bucket on R2.

Since both providers use the S3 API, metadata transfer is straightforward — content types, cache-control headers, and custom metadata carry over. RcloneView uses server-side metadata during the transfer, preserving object properties without additional configuration.

For the initial migration, use a copy job. RcloneView compares files using MD5 checksums (both Wasabi and R2 return standard MD5 ETags for non-multipart uploads) and transfers only new or changed files. Multi-threaded transfers with configurable concurrency keep the migration efficient — set transfers to 8-16 for large bucket migrations.

Be aware of Wasabi's minimum storage duration: if objects were uploaded recently (within the last 90 days), you will still be billed for the full 90 days on Wasabi even after deleting them. Plan your migration timeline accordingly — migrate first, verify, then delete from Wasabi after the 90-day window passes.

Verifying the Migration​

After the transfer, use RcloneView's compare feature to verify every object arrived on R2. Select the Wasabi source and R2 destination and run a folder comparison. Identical objects appear matched; missing or differing objects are highlighted for review.

For additional confidence, run a check operation that computes checksums on both sides. This verifies data integrity at the byte level.

Post-Migration Cleanup​

Once you have verified the migration:

1. Update application configurations to point to R2 endpoints instead of Wasabi.
2. Test application access to confirm everything works with R2.
3. Wait for the 90-day minimum storage period to pass on Wasabi before deleting objects, to avoid early deletion charges.
4. Delete the Wasabi bucket and deactivate Wasabi access keys.

If you need to run both providers in parallel during the transition, schedule a daily sync job in RcloneView to keep R2 updated with any new objects added to Wasabi.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Add Wasabi and Cloudflare R2 as S3-compatible remotes.
3. Run a copy job from Wasabi to R2.
4. Verify with compare and check operations.
5. Update application endpoints and clean up Wasabi after the retention period.

Both Wasabi and R2 are strong S3-compatible options, but when your workload profile changes, RcloneView makes the migration painless.

Related Guides:

• Add AWS S3 and S3-Compatible
• Compare Folder Contents
• Create Sync Jobs

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Not every sync job needs to transfer all files. RcloneView's time-based filters let you target only files modified within a specific window — sync today's changes, skip files older than 30 days, or back up only recent uploads.

Rclone's --min-age and --max-age flags are powerful tools for controlling which files participate in a sync, copy, or move operation based on their modification time. RcloneView exposes these options through its custom flags interface, enabling precise control over time-based file selection without touching the command line.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Understanding Min-Age and Max-Age​

The two flags work as time-based filters on file modification dates:

• --max-age: Only include files modified within the specified time window. A file modified 2 hours ago passes --max-age 24h. A file modified 3 days ago fails --max-age 24h and is skipped.
• --min-age: Only include files modified before the specified time window. A file modified 30 days ago passes --min-age 7d. A file modified yesterday fails --min-age 7d and is skipped.

Think of it this way:

• --max-age 24h = "files newer than 24 hours" (recently modified)
• --min-age 7d = "files older than 7 days" (not recently modified)

Time Format​

Both flags accept flexible time formats:

Duration values are relative to the current time when the job runs.

Use Case 1: Sync Only Today's Changes​

When you have a large cloud storage with terabytes of data but only want to sync files that changed today:

--max-age 24h

Add this to the custom flags field in RcloneView's job configuration. The sync job will only consider files modified in the last 24 hours, dramatically reducing the time spent listing and comparing files. This is useful for daily incremental backups where you know only a small percentage of files change each day.

Use Case 2: Archive Old Files​

Move files older than 90 days from active storage to cold storage:

--min-age 90d

Use this with a move operation (not sync) to transfer files older than 90 days from Google Drive to S3 Glacier. The files are removed from Google Drive after successful transfer, freeing up space on the active storage while preserving them in the archive.

Use Case 3: Time-Window Sync​

Combine both flags to target a specific time window. For example, sync files modified between 7 and 30 days ago:

--min-age 7d --max-age 30d

This is useful for staged archival workflows — files less than 7 days old stay on active storage, files between 7 and 30 days move to warm storage, and files older than 30 days move to cold storage.

Use Case 4: Skip Recently Modified Files​

During a migration, you might want to skip files that are actively being edited to avoid transferring incomplete work:

--min-age 1h

This ensures only files that have been stable for at least an hour are transferred. Files currently being edited or saved are left for the next sync run.

Use Case 5: Nightly Backup of Recent Work​

For a nightly backup job that captures only the day's work:

--max-age 25h

Using 25 hours (instead of 24) provides a 1-hour overlap with the previous day's backup, ensuring no files are missed due to timing differences between the backup schedule and file modification times.

Applying Time Filters in RcloneView​

In RcloneView's job configuration:

1. Open the sync or copy job settings.
2. Navigate to the advanced options or custom flags section.
3. Add --max-age 24h or --min-age 7d (or both) to the flags field.
4. Save the job and run it.

The flags apply to every file comparison during the job. Files that do not meet the time criteria are skipped entirely — they are not listed, compared, or transferred. This can significantly reduce job duration for large remote storages.

Combining with Other Filters​

Time-based filters work alongside other rclone filter options:

• With include/exclude: --max-age 24h --include "*.pdf" syncs only PDF files modified in the last 24 hours.
• With size filters: --max-age 7d --min-size 1M syncs only files larger than 1 MB modified in the last week.
• With directory filters: --max-age 24h --include "/projects/**" limits the scope to a specific directory.

This composability lets you build precise transfer rules without complex scripts.

Dry Run First​

Before running a time-filtered job on production data, use RcloneView's dry run mode to preview which files will be affected. Dry run lists the files that match your filter criteria without actually transferring them. This confirms that your --min-age and --max-age values select the right files before committing to the operation.

Common Pitfalls​

• Time zones: Modification times are compared in UTC. If your local time zone is significantly offset from UTC, adjust your duration values accordingly or use absolute date formats.
• Provider accuracy: Some cloud providers (notably Google Drive) report modification times with limited precision. A file modified "today" on Google Drive might have a timestamp that differs by several seconds from the actual modification time.
• Sync vs. Copy with min-age: Using --min-age with sync can be dangerous — sync deletes files on the destination that do not exist on the source. If --min-age filters out recent files from the source listing, sync may delete them on the destination. Use copy (not sync) when using --min-age to avoid unintended deletions.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Create a sync or copy job in the job manager.
3. Add --max-age or --min-age flags in the custom flags section.
4. Test with dry run to verify the file selection.
5. Schedule the job for automated time-based backups.

Time-based filters turn RcloneView into a precision tool for incremental backups, staged archival, and targeted sync operations. Use them to reduce transfer time, minimize bandwidth usage, and implement sophisticated data lifecycle workflows.

Related Guides:

• Create Sync Jobs
• Execute & Manage Jobs
• Job Scheduling

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Running RcloneView on an AWS EC2 instance gives you server-grade bandwidth for cloud transfers, 24/7 operation for scheduled jobs, and eliminates the need to route data through your local machine.

When migrating terabytes between cloud providers, your local internet connection becomes the bottleneck. An AWS EC2 instance with gigabit networking can transfer data between cloud services at speeds your home or office connection cannot match. Running RcloneView on EC2 also means transfers continue 24/7 without keeping a local machine running, and data moving between S3 and other AWS services stays within Amazon's network — often at no egress cost.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Why Run RcloneView on EC2​

• Speed: EC2 instances in AWS data centers have multi-gigabit network connections. Transfers between S3 and external providers leverage this bandwidth instead of your local connection.
• Free S3 transfer: Data transfer between EC2 and S3 within the same region is free. For large S3-to-cloud migrations, running on EC2 eliminates the biggest cost — local egress.
• 24/7 operation: Scheduled jobs run continuously without keeping a desktop machine on. The EC2 instance handles nightly backups, weekly migrations, and ongoing sync jobs.
• Proximity to data: If your source data is in AWS (S3, EBS, EFS), running RcloneView on EC2 puts it next to the data for minimum latency.
• Team access: Multiple team members can access the same RcloneView instance remotely, sharing configurations and job histories.

Setting Up an EC2 Instance​

Instance Selection​

For most RcloneView workloads, a small to medium instance is sufficient:

• t3.medium (2 vCPU, 4 GB RAM): Suitable for light sync jobs and small migrations.
• m5.large (2 vCPU, 8 GB RAM): Better for concurrent transfers and large file operations.
• c5.xlarge (4 vCPU, 8 GB RAM): For heavy migration workloads with many parallel transfers.

Choose an instance in the same region as your S3 buckets to avoid cross-region transfer costs.

Operating System​

Launch the instance with Ubuntu Server LTS or Amazon Linux 2. Both support RcloneView without issues. Install a lightweight desktop environment for the GUI:

# Ubuntu
sudo apt update && sudo apt install -y xfce4 xrdp

# Amazon Linux 2
sudo yum install -y xrdp xfce

Enable and start the RDP service so you can connect to the GUI remotely.

Security Group Configuration​

Open the following ports in your EC2 security group:

• Port 3389 (RDP): For remote desktop access to the GUI. Restrict to your IP address.
• Port 22 (SSH): For terminal access. Restrict to your IP address.
• Port 53682 (optional): If you need to run OAuth flows from the EC2 instance, this is rclone's default OAuth callback port. Alternatively, use headless OAuth configuration.

Installing RcloneView on EC2​

SSH into the instance and download RcloneView:

1. Download the Linux AppImage or .deb package from rcloneview.com.
2. Make the AppImage executable: chmod +x RcloneView-*.AppImage
3. Connect via RDP and launch RcloneView from the desktop environment.

Headless OAuth for Cloud Providers​

EC2 instances typically do not have a local browser for OAuth flows. For providers that require OAuth (Google Drive, OneDrive, Dropbox), use headless authentication:

1. On your local machine, run rclone authorize "drive" (or the relevant provider) to complete the OAuth flow.
2. Copy the resulting token.
3. On the EC2 instance, paste the token into RcloneView's remote configuration.

Alternatively, configure RcloneView with an external rclone instance and set up the OAuth token through the RcloneView connection manager.

Configuring S3 Access​

For S3 access from EC2, use an IAM instance role instead of static access keys. Attach an IAM role with S3 permissions to the EC2 instance, and rclone will use the instance metadata service to obtain temporary credentials automatically. This is more secure than storing access keys on the instance.

In RcloneView's S3 remote configuration, leave the access key and secret key fields empty and set the environment auth to use the instance profile.

Running Large Migrations​

With EC2's bandwidth, large migrations that would take days on a home connection complete in hours:

• 1 TB Google Drive to S3: Approximately 2-4 hours at sustained speeds.
• 10 TB S3 to Backblaze B2: Approximately 1-2 days depending on B2 API throttling.
• Cross-region S3 replication: Near line-speed within AWS.

RcloneView's multi-threaded transfers take full advantage of EC2's network capacity. Set transfers to 16-32 and checkers to 16 for maximum throughput on larger instances.

Scheduling Server-Side Jobs​

RcloneView's built-in scheduler handles recurring jobs. Configure nightly backups from Google Drive to S3, weekly sync between S3 and Backblaze B2, or daily replication to a DR region. The EC2 instance runs these jobs regardless of whether you are connected via RDP.

Keep the EC2 instance running continuously for scheduled jobs, or use a start/stop schedule (via AWS Instance Scheduler or a Lambda function) to run the instance only during backup windows.

Cost Management​

EC2 costs vary by instance type and runtime:

• t3.medium on-demand: ~$0.042/hour ($30/month if running 24/7)
• Spot instances: Up to 90% cheaper for interruptible workloads like one-time migrations.
• Reserved instances: Lower hourly rate for long-running server-side sync setups.

For one-time migrations, use a spot instance — launch it, run the migration, verify, and terminate. For ongoing scheduled backups, a reserved t3.small or t3.medium is cost-effective.

Remember: S3 data transfer within the same region from EC2 is free. Data transfer out to the internet (e.g., to Backblaze B2 or Google Drive) incurs standard AWS egress charges.

Getting Started​

1. Launch an EC2 instance with Ubuntu or Amazon Linux and a desktop environment.
2. Download RcloneView from rcloneview.com and install on the instance.
3. Configure remotes using headless OAuth for cloud providers and IAM roles for S3.
4. Run migrations and schedule backup jobs leveraging EC2's bandwidth.
5. Terminate or stop the instance when not needed to control costs.

Running RcloneView on EC2 gives you the speed of AWS's data center network, the convenience of a GUI for managing transfers, and 24/7 operation for scheduled jobs — the ideal setup for large-scale cloud migrations and ongoing server-side sync.

Related Guides:

• Add AWS S3 and S3-Compatible
• Add OneDrive headless
• Headless Google Drive
• External rclone example

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

Linux Mint is one of the most popular desktop Linux distributions, but it lacks built-in cloud storage integration beyond basic Nemo file manager plugins — RcloneView fills that gap with full multi-cloud support.

Linux Mint ships with excellent desktop tools — Nemo file manager, Timeshift for system backups, and a polished Cinnamon (or MATE/Xfce) desktop. However, cloud storage integration is minimal. There is no native Google Drive, OneDrive, or Dropbox client from the system. While third-party solutions exist (Insync, rclone CLI, GNOME Online Accounts on MATE), none provide a comprehensive multi-cloud GUI. RcloneView runs natively on Linux Mint across all editions and connects to 70+ cloud providers.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Installation on Linux Mint​

Linux Mint is based on Ubuntu LTS, so installation follows the same process as Ubuntu/Debian systems.

Method 1: AppImage (Recommended)​

The AppImage is the simplest installation method and works across all Linux Mint editions (Cinnamon, MATE, Xfce):

1. Download the RcloneView AppImage from rcloneview.com.
2. Make it executable: right-click the file in Nemo, select Properties > Permissions, and check "Allow executing file as program". Or run chmod +x RcloneView-*.AppImage in the terminal.
3. Double-click to launch.

The AppImage bundles everything RcloneView needs, including an embedded rclone binary. No system packages are required.

Method 2: .deb Package​

Download the .deb package from the RcloneView website. Install it by double-clicking (which opens the package manager) or from the terminal:

sudo dpkg -i rcloneview_*.deb
sudo apt-get install -f

The .deb package integrates with the system — it adds RcloneView to the application menu and handles desktop file associations.

FUSE Setup for Mounting​

To mount cloud storage as local directories on Linux Mint, FUSE must be available. Most Mint installations include FUSE by default. Verify by running:

fusermount --version

If FUSE is not installed, add it:

sudo apt install fuse3

Ensure your user is in the fuse group:

sudo usermod -a -G fuse $USER

Log out and back in for the group change to take effect. After this, RcloneView can mount any cloud provider as a local directory that appears in Nemo alongside your local folders.

Adding Cloud Storage Remotes​

Launch RcloneView and open the Remote Manager. Add your cloud accounts:

• Google Drive: Select Google Drive, authorize via OAuth in your default browser (Firefox or Chromium on Mint).
• OneDrive: Select Microsoft OneDrive, authorize via OAuth.
• Dropbox: Select Dropbox, authorize via OAuth.
• S3-compatible: Enter your access key, secret key, and endpoint for AWS S3, Wasabi, Backblaze B2 S3, etc.

Each remote appears in the explorer dropdown. Linux Mint's default browser handles OAuth flows smoothly — no special configuration needed.

Browsing and Managing Cloud Files​

RcloneView's two-pane explorer complements Nemo for cloud operations. While Nemo handles local files excellently, RcloneView extends that capability to cloud storage. Browse Google Drive in one pane and your local home directory in the other. Drag and drop files between them, or between two different cloud providers.

For users familiar with Nemo's dual-pane mode (available via a Nemo extension), RcloneView's layout will feel natural. The difference is that RcloneView's panes can open any cloud provider, not just local and network paths.

Mounting Cloud Storage in Nemo​

Once mounted, cloud storage directories appear in Nemo just like any other folder. You can open files directly from mounted cloud storage in your Linux Mint applications — LibreOffice, GIMP, VLC, or any other app.

Mount your Google Drive to ~/GoogleDrive and it appears in Nemo's sidebar. Enable VFS caching for smooth performance — recently accessed files are cached locally, so repeated access is instant. Configure the cache size based on your available disk space.

Scheduling Backups with System Integration​

RcloneView's built-in scheduler handles recurring backup jobs. Configure a nightly sync from your home directory (or specific folders) to Google Drive, Backblaze B2, or any other cloud provider. RcloneView runs the scheduled jobs automatically.

For Linux Mint users who prefer system-level scheduling, you can also trigger rclone commands via cron or systemd timers using RcloneView's external rclone connection mode.

Autostart on Login​

To have RcloneView start automatically when you log in to Linux Mint:

1. Open Startup Applications from the system menu.
2. Click Add and enter the path to the RcloneView AppImage or the installed binary.
3. RcloneView will launch with your desktop session, ready for scheduled jobs and mounted drives.

Getting Started​

1. Download RcloneView from rcloneview.com — AppImage or .deb.
2. Install FUSE if you plan to mount cloud storage.
3. Add your cloud accounts in the Remote Manager.
4. Browse, sync, and back up your files from Linux Mint's desktop.

Linux Mint provides a polished desktop experience, and RcloneView adds the multi-cloud file management that the system lacks natively. Together, they give you complete control over local and cloud storage.

Related Guides:

• Add Google Drive
• Mount Cloud Storage as a Local Drive
• Job Scheduling

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

TerraMaster NAS devices offer affordable network storage, but their built-in cloud backup options are limited — RcloneView extends your TerraMaster with multi-cloud backup, sync, and file management through a visual GUI.

TerraMaster manufactures popular NAS devices running TOS (TerraMaster Operating System). While TOS includes basic cloud sync features for a few providers, it does not support the full range of cloud storage services that businesses and power users need. RcloneView connects to your TerraMaster NAS via SFTP or SMB and bridges it to 70+ cloud providers — enabling automated backups, cloud-to-NAS sync, and cross-cloud file management.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Why Add Cloud Backup to Your TerraMaster​

A NAS provides fast local storage and RAID redundancy, but it does not protect against:

• Site-level disasters: Fire, flood, theft, or power surges can destroy the NAS and all its drives simultaneously. RAID protects against drive failure, not site loss.
• Ransomware: If ransomware reaches your network, it can encrypt NAS shares. Cloud backups (especially to immutable storage) provide a recovery point.
• Hardware failure beyond RAID: Controller board failures, power supply damage, or firmware corruption can make the entire NAS inaccessible regardless of RAID level.

Cloud backup provides geographic redundancy that a local NAS cannot. RcloneView automates this backup while keeping your primary workflow on the fast local NAS.

Connecting RcloneView to Your TerraMaster​

RcloneView runs on your desktop or a separate machine (not on the TerraMaster itself) and connects to the NAS over the network. Two connection methods are available:

SFTP Connection​

Enable SSH on your TerraMaster (TOS Control Panel > Services > SSH). Then add an SFTP remote in RcloneView's Remote Manager:

• Host: Your TerraMaster's IP address (e.g., 192.168.1.100)
• Port: 22 (default SSH port)
• Username: Your TOS admin username
• Password or SSH key: Your TOS credentials

SFTP provides encrypted file transfers and is the recommended method for accessing NAS data from RcloneView.

SMB Connection​

If your TerraMaster shares are accessible via SMB (Windows file sharing), add an SMB remote in RcloneView. This uses the standard Windows network path format and is convenient if you already have SMB shares configured.

Backing Up NAS Data to Cloud Storage​

Once connected, set up a backup job from your TerraMaster to a cloud destination:

1. Open the TerraMaster SFTP remote in the left pane.
2. Open your cloud destination (AWS S3, Backblaze B2, Google Drive, Wasabi) in the right pane.
3. Navigate to the folders you want to back up on the NAS.
4. Create a sync job that copies NAS data to the cloud.

RcloneView's delta detection ensures only files that have changed since the last backup are transferred. For a NAS with terabytes of data, the initial backup may take days, but subsequent daily backups transfer only the day's changes — typically completing in minutes.

Choosing a Cloud Backup Destination​

For NAS backup, cost-effective storage with no egress fees is ideal:

• Backblaze B2: $6/TB/month, free egress through Cloudflare partnership. Simple pricing, good for straightforward backups.
• Wasabi: $6.99/TB/month, no egress fees. 90-day minimum storage duration applies.
• AWS S3 Glacier Deep Archive: $0.99/TB/month for archival data. Retrieval takes hours and incurs per-GB retrieval fees, but storage costs are the lowest available.
• Google Drive: Convenient if your team already uses Google Workspace. Storage costs are higher but integration is seamless.

For most TerraMaster users, Backblaze B2 offers the best balance of cost, simplicity, and retrieval speed.

Scheduling Automated Backups​

Configure RcloneView's scheduler to run NAS backups automatically:

• Daily incremental: Sync changed files from the NAS to cloud every night. Minimal bandwidth usage after the initial seed.
• Weekly full verification: Run a compare operation weekly to verify that all NAS files match the cloud backup. This catches any discrepancies from interrupted transfers or silent data corruption.

Set bandwidth limits to prevent backup traffic from consuming your network during business hours. Schedule backups for overnight or off-peak hours.

Syncing Cloud Data to Your TerraMaster​

The reverse workflow is also useful: pull cloud data to your NAS for local access. If your team collaborates on Google Drive but needs fast local access to project files, sync the relevant Drive folders to your TerraMaster. Edit files locally at NAS speeds, and RcloneView syncs changes back to the cloud on schedule.

This hybrid approach gives you the collaboration benefits of cloud storage with the performance of local NAS access.

Encrypting NAS Backups​

For sensitive data, use RcloneView's crypt remote to encrypt files before they leave your network. The encryption happens on your desktop machine (where RcloneView runs) before uploading to the cloud. Even if the cloud provider is compromised, your NAS backup data remains unreadable.

Monitoring and Verification​

RcloneView's job history logs every backup run with statistics: files transferred, files skipped, total bytes, elapsed time, and any errors. Review the history regularly to confirm backups are completing successfully. Use the compare feature periodically to verify that the cloud backup matches the NAS contents.

Getting Started​

1. Download RcloneView from rcloneview.com.
2. Enable SSH on your TerraMaster and add it as an SFTP remote in RcloneView.
3. Add a cloud destination (B2, S3, Google Drive, or Wasabi).
4. Create and schedule a daily backup job from NAS to cloud.
5. Verify backups periodically with the compare feature.

Your TerraMaster NAS handles local storage and sharing. RcloneView adds the cloud backup layer that protects your data against site-level disasters, ransomware, and hardware failure beyond RAID.

Related Guides:

• Browse and Manage Remote Storage
• Create Sync Jobs
• Job Scheduling
• Job History

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

AzCopy is Microsoft's CLI tool for Azure Blob and Azure Files transfers. RcloneView is a multi-cloud GUI that supports Azure alongside 70+ other providers. Here is how they compare.

AzCopy is purpose-built for moving data into, out of, and between Azure storage accounts. It handles Azure Blob Storage, Azure Files, and Azure Data Lake Storage Gen2 with tight integration into Azure Active Directory and SAS token authentication. RcloneView takes a different approach — it connects to Azure as one of many supported providers and manages transfers through a visual interface. The right choice depends on whether your workflow is Azure-only or multi-cloud.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Provider Support​

AzCopy supports Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2, and Amazon S3 (as a source for copying to Azure). It does not support Google Drive, Dropbox, OneDrive, Backblaze B2, or any other non-Azure provider as a destination.

RcloneView supports 70+ providers including Azure Blob Storage, Azure Files, Google Drive, OneDrive, Dropbox, AWS S3, Backblaze B2, Cloudflare R2, SFTP, WebDAV, and many more. If you manage data across multiple cloud providers, RcloneView eliminates the need for multiple transfer tools.

Interface​

AzCopy is a command-line tool. Every operation requires constructing a command with flags, SAS tokens or Azure AD credentials, and source/destination URLs. There is no GUI — you work entirely in a terminal.

RcloneView provides a visual two-pane file explorer. Browse Azure Blob containers alongside Google Drive, drag and drop files between providers, and configure sync jobs through dialog boxes. The GUI makes it accessible to users who are not comfortable with CLI operations, while a built-in terminal is available for advanced users who want direct rclone command access.

Authentication​

AzCopy supports Azure Active Directory (OAuth 2.0), SAS tokens, and service principals. It integrates with az login and supports managed identities on Azure VMs. For Azure-to-Azure transfers, it can use server-side copy with no data passing through your machine.

RcloneView supports SAS tokens and account keys for Azure Blob and Azure Files. For Azure AD authentication, you configure the credentials in the remote setup. While RcloneView does not integrate with az login directly, it stores credentials securely in the rclone configuration file with optional encryption.

Transfer Performance​

AzCopy is optimized for Azure transfers. It supports parallel operations, automatic retry, and server-side copy between Azure accounts (data moves within Azure's network without touching your machine). For Azure-to-Azure migrations, this is significantly faster than any tool that routes data through a local machine.

RcloneView routes data through your machine for all transfers, including Azure-to-Azure. However, it offers multi-threaded transfers, configurable chunk sizes, bandwidth limits, and resumable uploads. For transfers between Azure and non-Azure providers, performance is comparable. For Azure-to-Azure transfers, AzCopy's server-side copy has a clear advantage.

Sync and Scheduling​

AzCopy supports azcopy sync with delete detection based on last-modified timestamps. Scheduling requires external tools like cron or Windows Task Scheduler.

RcloneView provides sync, copy, and move operations with built-in scheduling. Configure a recurring job with a visual scheduler — no external tools needed. The job history panel logs every run with detailed statistics.

Monitoring​

AzCopy outputs progress to the terminal and writes log files. You can check job status with azcopy jobs list and azcopy jobs show.

RcloneView provides a real-time monitoring dashboard with per-file progress, transfer speed graphs, and overall completion percentage. You can pause, resume, or cancel individual transfers from the GUI.

Feature Comparison Table​

When to Choose Each Tool​

Choose AzCopy when:

• Your workflow is Azure-only (Azure Blob ↔ Azure Blob).
• You need server-side copy between Azure accounts for maximum speed.
• You require Azure AD/managed identity authentication on Azure VMs.
• You are scripting transfers in CI/CD pipelines that only touch Azure.

Choose RcloneView when:

• You manage data across Azure and other providers (Google Drive, S3, Dropbox, etc.).
• You prefer a GUI over command-line operations.
• You need built-in scheduling, monitoring, and job history.
• You want to mount Azure storage as a local drive.
• You need client-side encryption with crypt remotes.

Getting Started with RcloneView​

1. Download RcloneView from rcloneview.com.
2. Add your Azure Blob or Azure Files remote in the Remote Manager.
3. Browse your Azure containers alongside other cloud providers in the two-pane explorer.
4. Set up sync jobs with built-in scheduling and monitoring.

AzCopy excels at Azure-to-Azure transfers with server-side copy and Azure AD integration. RcloneView provides a broader multi-cloud solution with a visual interface, built-in scheduling, and support for 70+ providers. For teams managing data beyond Azure, RcloneView eliminates the need for multiple specialized tools.

Related Guides:

• Add AWS S3 and S3-Compatible
• Browse and Manage Remote Storage
• Create Sync Jobs

Supported Cloud Providers

View All Providers →

Connect Your Clouds →

S3 Browser is a Windows GUI for managing Amazon S3 and S3-compatible storage. RcloneView is a cross-platform multi-cloud GUI supporting S3 alongside 70+ other providers. Here is how they compare.

S3 Browser is a dedicated Windows application for browsing, managing, and transferring files to Amazon S3 and S3-compatible services like Wasabi, Backblaze B2, and MinIO. RcloneView connects to S3 as one of many supported backends and extends its capabilities to Google Drive, OneDrive, Dropbox, SFTP, and dozens of other providers — all through a visual two-pane explorer that runs on Windows, macOS, and Linux.

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

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Provider Support​

S3 Browser supports Amazon S3 and S3-compatible services (Wasabi, Backblaze B2 S3, MinIO, DigitalOcean Spaces, Cloudflare R2, etc.). It does not support Google Drive, OneDrive, Dropbox, SFTP, WebDAV, or any non-S3 provider.

RcloneView supports 70+ providers including all S3-compatible services, Google Drive, OneDrive, Dropbox, MEGA, Box, Backblaze B2 (native and S3), SFTP, WebDAV, FTP, Azure Blob, Google Cloud Storage, and many more. For S3-only workflows, both tools work well. For multi-cloud environments, RcloneView eliminates the need for separate tools per provider.

Platform Support​

S3 Browser runs on Windows only.

RcloneView runs on Windows, macOS, and Linux. For teams with mixed operating systems or administrators who manage cloud storage from a Linux server, RcloneView provides cross-platform consistency.

Interface and Navigation​

Both tools provide a file browser interface for navigating buckets and objects. S3 Browser uses a single-pane explorer with a tree view sidebar. RcloneView uses a two-pane explorer where you can open two different remotes (or two different buckets) side by side.

The two-pane layout is particularly useful for S3 workflows like comparing bucket contents, copying between buckets in different regions, or transferring files between S3 and Google Drive. RcloneView also includes a built-in terminal for running rclone commands directly when needed.

S3-Specific Features​

S3 Browser provides deep S3 integration: bucket policy editor, CORS configuration, lifecycle rule management, server-side encryption settings, access control list editing, and pre-signed URL generation. These are valuable for S3 administrators who need to manage bucket configurations.

RcloneView focuses on file operations: browse, copy, sync, move, delete, compare, and mount. It does not expose bucket-level configuration settings like lifecycle rules or CORS. For S3 administration tasks, you would use the AWS console or CLI alongside RcloneView.

Sync and Scheduling​

S3 Browser offers folder sync in its Pro version (paid). The free version supports manual file transfers only.

RcloneView provides sync, copy, and move operations with built-in job scheduling. Configure a recurring sync job with cron-style scheduling, bandwidth limits, and filter rules — all through the GUI. Job history tracks every run with transfer statistics.

Encryption​

S3 Browser supports S3 server-side encryption (SSE-S3, SSE-KMS, SSE-C). Client-side encryption is not available.

RcloneView supports S3 server-side encryption and adds client-side encryption through rclone's crypt remote. With crypt, files are encrypted on your machine before upload — even the provider cannot read your data. This works with S3 and every other supported provider.

Mounting and Local Access​

S3 Browser does not support mounting S3 buckets as local drives.

RcloneView can mount any S3 bucket (or any other remote) as a local drive letter on Windows or mount point on macOS/Linux. This enables applications that do not support S3 natively to access bucket contents as if they were local files.

Feature Comparison Table​

When to Choose Each Tool​

Choose S3 Browser when:

• You work exclusively with S3 and S3-compatible providers on Windows.
• You need bucket-level administration features (policies, CORS, lifecycle rules).
• You want a lightweight tool specifically for S3 file browsing and management.

Choose RcloneView when:

• You manage data across S3 and other providers (Google Drive, OneDrive, SFTP, etc.).
• You need cross-platform support (macOS, Linux, or Windows).
• You want built-in scheduling, monitoring, and job history.
• You need to mount S3 buckets as local drives.
• You want client-side encryption with crypt remotes.

Getting Started with RcloneView​

1. Download RcloneView from rcloneview.com.
2. Add your S3 or S3-compatible remote in the Remote Manager.
3. Browse buckets alongside other cloud providers in the two-pane explorer.
4. Set up sync jobs, mount buckets, or configure encrypted backups.

S3 Browser is a solid choice for Windows users who only need S3 file management with bucket administration features. RcloneView provides a broader solution with multi-cloud support, cross-platform compatibility, built-in scheduling, and encryption — making it the better choice for teams managing data beyond S3.

Related Guides:

• Add AWS S3 and S3-Compatible
• Browse and Manage Remote Storage
• Mount Cloud Storage as a Local Drive

Supported Cloud Providers

View All Providers →

Connect Your Clouds →