File versions and history
Found this helpful? Share it:
Found this helpful? Share it:
Overwrite a file by accident? Drive keeps previous versions of your text files and documents, so you can look back and roll one forward 🕐
Each time a text file or document is saved over, idapt keeps the content that was there before as a version. Every edit an agent, a synced computer, or you make adds to the file's history automatically, with nothing to switch on.
Images, video, audio, archives, and other binaries are not versioned, because keeping full copies of large media would fill your storage fast.
Smaller text files keep more history than larger ones, and very large files keep none:
File | Previous versions kept |
|---|---|
Text or code under 100 KB | 10 |
Text or code under 1 MB | 5 |
Text or code under 10 MB | 3 |
PDF or office document under 10 MB | 3 |
Anything 10 MB or larger, and all media and binaries | None |
idapt keeps a numbered history of a file's previous saves. You can list those versions, read an earlier one, and restore any of them to roll the file back to it.
Restoring replaces the current content, and it saves the current state as a new version first, so a rollback is itself reversible and you can always roll forward again.
Version history and rollback are available through the idapt API and your agents, so you can ask an agent to show a file's history or put an earlier version back. See the API reference.
Each file carries a limit on how many versions it keeps, and you can raise it to hold more history or lower it to save space. Media and binary files stay unversioned whatever the limit.
Versions count toward your Drive storage, and so do trashed files until they are purged. If storage is tight, lower a file's version count and clear space from Trash. See Drive: files and folders for your storage limits.
Related articles
Was this helpful?