Features

The parts that make protection trustworthy.

Rove is built around inspectable state and reversible actions. Here is what it does — and where the boundaries are.

A local revision is committed before any cloud replication is attempted.

Saves stay protected without internet. Pending uploads resume when you reconnect.

Use Local only, Google Drive, or a synced folder you already trust.

Name and pin revisions you want to keep until you remove them yourself.

Both sides are preserved. Rove asks before it overwrites anything.

Preview what will change and create a pre-restore recovery point first.

Protection modes

Choose how often a checkpoint is made.

Checkpoints changed save data periodically and after game exit. A practical default for most smaller traditional save sets.

Capture after the tracked game closes. Useful when you want fewer checkpoints during a session.

Capture stable changes more frequently. Results depend on save size, disk speed, antivirus, and the game.

Keep control over when a checkpoint is created. Rove still preserves local revisions before remote replication.

Storage & safety

Use Rove as a local revision and restore tool without configuring any cloud destination.

Connect directly from the desktop app using user-authorized OAuth and the drive.file scope. No developer API keys are supplied by end users.

Choose a folder managed by OneDrive, Dropbox, Syncthing, or a similar tool. The provider handles its own replication.

When both sides changed, Rove preserves both versions and asks how to resolve the difference. It does not silently overwrite by default.

Review the proposed change, verify required data, and create a pre-restore Recovery Point before changing save files.

Pause globally or per game, inspect activity history, and use diagnostics when permissions, quotas, disk space, or file locks get in the way.