Common questions about Version History usually focus on storage usage, restore impact, and long-term retention; this FAQ covers 3 frequent questions.
FAQ
Does version history use storage space?
- Yes. Historical versions use cloud storage space.
- Larger files can take up more space across saved versions.
- You can delete versions you no longer need to free up space.
Will restoring a version replace my current content?
- Yes. After you restore a version, the file returns to the content state of that selected version.
- Your current content is replaced.
- If you still need the current edits, back up important content before restoring.
Can I keep historical versions for long-term use?
- Yes. You can manage important historical versions for longer-term reference.
- Rename important versions so they are easier to identify later.
- You can also use Save As to keep a historical version as a separate file for archiving.
Glossary
| Term | Definition |
|---|---|
| Version History | A record of earlier file states saved at different points in time. |
| Restore This Version | An action that rolls the current file back to the selected historical version. |
| Save As | An action that saves a historical version as a separate file instead of directly replacing the current file. |
| Version Notes | Information shown with a version record to help identify the background or changes for that version. |