Version History
Version history gives you a timeline of saved snapshots of your script. You can save versions at key milestones, compare how the script has changed, and restore any previous state if you need to go back.
Saving a version
- Open the Versions tab in the right panel.
- Click Save Version.
- Give it a descriptive name, like "First Draft", "After Notes Session", or "Network Draft", and click Save. (If you leave the name blank, it's named "Version" plus today's date.)
That's it. The current state of the script is saved as a named snapshot.
Working with a version
Click any saved version in the list to select it. Each version shows when it was saved and, where available, its scene and word counts. Selecting it reveals its actions: Restore, Compare and, for most versions, Delete.
Restoring a version
If you want to go back to an earlier state of the script, select that version and click Restore. Premiere.Studio replaces the current script with the saved version straight away, and brings back the outline saved with it, if it has one.
Restoring doesn't save your current draft first. If you might want it back, save a version of it before you restore.
Versions saved for you
Premiere.Studio also saves a version automatically before some big changes. Importing a script over the open one always saves your current draft first, and won't replace anything if it can't. Generating a full script over an existing draft tries to save one too, so save a named version first if you need to be sure. You'll see these in the version list alongside your named versions.
Comparing versions
Select a version and click Compare to see how the current script differs from it, with additions in green and removals in red. This is useful for understanding what was added, removed, or rewritten during a particular stage of development.
Practical advice
- Name your versions clearly. A name like "Post-table read rewrite" is much more useful than "Draft 2" six months from now.
- Save often at key moments. Versions are lightweight. There's no cost to saving frequently.
- Use versions as milestones. They make it easy to track the evolution of your script across the entire development process.