VFS Cache — Boost Mount Performance for Cloud Drives in RcloneView

March 21, 2026 · 4 min read

Senior Engineer

Mounted cloud drives feel slow by default—VFS caching in RcloneView trades disk space for speed, letting you work at local drive speeds.

When you mount a cloud drive (Google Drive, Dropbox, AWS S3) through RcloneView, every file access hits the network. This works but feels sluggish—opening a document takes a second or two, listing folders stalls, and reading files feels bottlenecked. VFS cache solves this by caching frequently accessed files locally.

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.

What Is VFS Cache?

VFS (Virtual File System) cache stores recently accessed files and folder metadata on your local disk. When you open a file from a mounted cloud drive, RcloneView checks the cache first—instant access if it's there, network fetch if it's not. As you work, the cache grows; older entries are evicted to make room.

This simple strategy removes the network latency from common operations.

VFS Cache Modes

RcloneView supports three cache modes, each balancing speed vs. disk usage:

Mode 1: Off (No Cache)

Every access hits the network. Safest for dynamic files, slowest for repeated access. Use this only if disk space is critical or cache conflicts matter.

Mode 2: Minimal Cache

Caches file metadata (names, sizes) and recently opened files. Fast for folder navigation and repeated reads. Uses minimal disk—typically under 1 GB for most workflows.

RcloneView remote explorer and mount interface

Best for: Document editing, photo browsing, regular file access on limited-disk machines.

Mode 3: Writes Cache

Like minimal, but also caches write operations. Files you've just modified stay local before background sync. Dramatically speeds up workflows with frequent writes.

Best for: Content creation, video editing, bulk file operations—high volume changes before cloud sync.

Mode 4: Full Cache

Aggressive caching—all accessed files cached permanently until manually cleared. Fastest for repeated access, largest disk footprint. Requires manual cache management.

Best for: Archived data, read-heavy workflows, machines with plenty of disk space.

Configuring VFS Cache in RcloneView

RcloneView cloud-to-cloud transfer configuration

Open RcloneView and navigate to a mount configuration:

Select your cloud remote (e.g., Google Drive)
Go to Advanced Settings → VFS Cache
Choose cache mode: Minimal, Writes, or Full
Set cache directory (default: /tmp/rcloneview-cache on Linux, %TEMP%\rcloneview-cache on Windows)
Configure cache size limit (e.g., 10 GB)—RcloneView auto-evicts old files when exceeded
Enable cache backend if using local SSD for extra speed

Apply and remount—performance instantly improves.

Cache Directory Best Practices

Place cache on fast storage: SSD preferred over HDD
Separate from system: Use a dedicated partition to avoid filling your OS drive
Monitor disk usage: Check cache size regularly; increase limit if evictions are frequent
Clean periodically: Clear old caches if you stop using a remote (safe—cache rebuilds)

Real-World Performance Gains

RcloneView monitoring and performance tracking

With no cache, opening a 50 MB folder listing takes 2-3 seconds. With minimal cache, it's instant on the second access. Writing to a mounted drive? With writes cache enabled, you see local disk speeds (milliseconds) instead of network latency (seconds).

Trade-off: Requires 5-50 GB disk space depending on your workflow. For most users, this is worthwhile.