// Learn

Auto-versioning explained: stop renaming files _v3_FINAL_v2

·6 min read·versioning · workflow

Why filename-based versioning collapses on any active project, and how automatic versioning by filename fixes it without forcing designers to change how they save files.

In this guide

  1. The _v3_FINAL_v2 problem (why every designer has been here)
  2. Why generic cloud storage version history is not enough
  3. How filename-based auto-versioning works
  4. What happens when the same file is re-uploaded
  5. Rolling back to a previous version
  6. When versioning should be manual instead
This article is part of the SaveITT design-workflow guides. The full article is being written — the outline below shows what it will cover. When the body lands, it will sit here in normal prose paragraphs, with H2 section headings derived from the outline. For now this paragraph plus the outline gives crawlers enough structure to begin indexing the URL.
Related to this guide
See every SaveITT feature that supports this workflow →

Keep reading

How to organize design files across multiple clients
A practical structure for managing 5-20 active client projects without files going missing between Dropbox, Drive, and the local desktop.
Client approval workflows that don't live in email
Why "approved via reply-all email" loses tracks of which version got the green light, and how to move approval into a single URL with a clear paper trail.
Try SaveITT free

3 projects, 5 GB, no credit card.

Start free →