Learn how Playbook keeps every version of an asset together so you can review its history, compare versions side by side, and roll back to an earlier one.

Instead of a folder full of final_v3_FINAL files, Playbook keeps every iteration on the same asset. When you replace a file with a new version, the previous one is saved automatically as a revision, and the live asset is always the latest. That means one asset carries its whole history, and you can always look back or restore an earlier cut.

Add a new version

To add a version, open the asset's Version history panel and choose New version to upload the updated file (from your computer or from Playbook). Playbook snapshots the previous state (the file, its previews, title, and metadata) automatically, so nothing is lost and you do not create a duplicate.

See an asset's version history

Open the Version history panel to see every past version, newest first, with thumbnail peeks. This is the full change history for that asset in one place; the latest is marked Current.

Compare and restore an earlier version

Select a previous version to view it against the current one, so you can see exactly what changed. When you find the one you want, choose Restore this version to make it current. Restoring is non-destructive: the state before you restored is itself saved as a version, so you can always go Back to current or restore again.

Good to know

• Version history is on every plan. How far back you can restore depends on your plan: a 7-day window on Free and Pro, and unlimited on Team and up (older versions prompt an Upgrade to Team to restore).
• This is different from grouping, which stacks several different assets together. Version history keeps the history of one asset.