Version History

How versioning works

Uploading a replacement saves the previous file in version history. AI tool results can appear separately as AI Derivatives. Use "Use as version" when you want a derivative to replace the current file. Editing metadata does not create a new file version.

Viewing version history

Open an asset and choose "History" in the details sidebar. The version timeline shows earlier files with dates and available notes. AI Derivatives appear in a separate list.

Uploading a new version

To replace an asset with an updated file, open it and click "Upload new version". Drag in the new file or browse to select it. The new file takes over as the current version. The previous file is saved as a version you can restore later.

The new version inherits all tags, metadata, and collection memberships from the previous version. You do not need to re-tag or re-organize anything.

Restoring a previous version

Open a previous version’s actions menu and choose "Restore". Studio makes it the current file and archives the file it replaces. For a connected Sirv file, this can also replace the file at its Sirv path. Check where the current file is used before restoring.

If an AI result needs work, compare it with the Studio original before choosing another result or running the tool with different settings.

Side-by-side comparison

Open a previous version’s actions menu and choose "Compare with current" to compare it with the current image. AI derivatives have a separate "Compare with original" action.

Version details

Each version entry shows the file size, dimensions, format, and how it was created. You will see labels like "Uploaded", "Background removal", or "Upscale 2x" so you know exactly what happened at each step.

Storage and retention

Previous file versions use storage. You can permanently delete an archived version from its actions menu when you no longer need it. The current file is managed separately from archived versions.