Version control, in a DAM, means keeping every revision of an asset under a single record: one asset, with a history of the files it has been. When a retouched image replaces the original, the asset's identity, metadata, links, and permissions stay the same — only the current file changes, and the previous one remains reachable in the history.

This solves the most familiar failure in shared storage: hero_final_v3_FINAL_approved(2).jpg. Filename versioning multiplies files, and every copy is a chance for someone to use the wrong one. With real versioning, there is exactly one place the asset lives, and it is always current. Anything pointing at the asset — collections, share links, portal pages, systems consuming it over an API — automatically serves the newest version, which is how a corrected image updates everywhere at once instead of everywhere someone remembers.

History matters as much as currency. Being able to see when a version arrived, compare it with what it replaced, and roll back when a "fix" turns out to be a regression is routine maintenance in an active library. Version history also answers the retrospective question — "what did this asset look like when we shipped that campaign?" — that filenames never can.

In freedam, uploading a new file to an existing asset creates a new version while preserving the full history, and previous versions can be viewed and restored.

Related terms: Audit Trail, Duplicate Detection, Rendition