Skip to content
CloudMountCloudMount Docs

Version history

Some storage keeps the old content of a file each time it is overwritten. CloudMount lists those versions for a file and puts one back, so a file you overwrote by mistake can be brought back as it was.

Which drives have it

Section titled “Which drives have it”
  • Amazon S3 and compatible storage, on a bucket with versioning turned on. Turn it on in your provider’s console; it only keeps versions of changes made after that. Providers that don’t keep versions list none.
  • Backblaze B2, which keeps old versions unless a lifecycle rule in your account removes them.

Other drive types don’t show version history, including encrypted drives, aliases and combined drives on top of an S3 or B2 drive. Google Drive and OneDrive keep revisions too, but CloudMount can’t reach them yet.

Open a file’s history

Section titled “Open a file’s history”
  • Android: open the drive’s settings and tap Version history, then browse to the file.
  • Windows: right-click the file in the drive’s folder in File Explorer and choose CloudMount > Version history….

The list shows each old version with when it was saved and its size, newest first. The file’s current content isn’t in the list.

Restore or save a copy

Section titled “Restore or save a copy”
  • Restore puts the old version back in place of the file. The storage does this by copying the old version over the file, so the content it replaces becomes a version itself: nothing is deleted, and you can restore that one too. CloudMount asks first.
  • Save a copy puts the old version beside the file, named like report (version 2026-01-02 150405).pdf with the time that version was saved, and leaves the current file as it is.

A file with changes on this device that haven’t uploaded yet can’t be restored until they have, so the upload doesn’t land over the restored version. On Android that includes a file open in an app. On Windows, once restored, the file in the drive’s folder shows the restored content.

Things to know

Section titled “Things to know”
  • Suspended versioning. An S3 bucket whose versioning was turned off again still lists its old versions, but stops keeping new ones. CloudMount then doesn’t restore over the file, which would replace it for good; save a copy instead, or turn versioning back on.
  • Versions take space. Every version counts towards your storage until you or a lifecycle rule deletes it. CloudMount never deletes versions.
  • Deleted files aren’t listed: version history starts from a file that is there now. On Android, Trash can keep deleted files.
  • The free plan includes version history.