Revisions & rollback

There is no save button in the Inwista editor — and no way to lose work. Every change you make is saved automatically, and each save becomes a revision: a complete snapshot of your project you can return to at any time. This guide explains how the revision history works and how to roll back safely.

Autosave: every change becomes a revision

As you edit — moving captions, restyling text, adding elements — Inwista saves automatically a few seconds after you pause. Each save is stored as a new revision with a timestamp, so your history reads like a diary of the project: not one undo trail that evaporates when you close the tab, but permanent snapshots that survive sessions, devices and teammates.

The Revisions panel

Open the history icon in the editor's left sidebar to see the full list, newest first. Each entry shows when it was saved — "Today at 2:31 PM", "Yesterday at 9:04 AM" — and the revision you're currently working on is highlighted.

Some entries carry a label. Original is the very first state, exactly as the transcription pipeline delivered it — it's always there, at the bottom of the list. Enhanced and Regenerated mark revisions created by those AI operations, so you can always tell what changed your project: you, or a tool.

Rolling back — and why it's always safe

Click any revision and the editor loads that snapshot into the timeline. Here's the important part: loading a revision changes nothing by itself. You're browsing, not overwriting — flip between revisions as much as you like to compare states.

The moment you make an edit on top of a loaded revision, autosave kicks in and creates a new revision from there. The newer revisions you "rolled back past" are not deleted — they stay in the list, still loadable. History in Inwista only ever grows; nothing you did is ever destroyed by a rollback.

Your safety net for AI operations

Because subtitle enhancement and re-transcription create labeled revisions automatically, you can run them without ceremony: if the result isn't what you hoped, open the Revisions panel and load the state from just before. This is the intended workflow — experiment first, judge afterwards, roll back if needed. The Original entry is the ultimate fallback: the untouched transcription is always one click away.

What a revision contains

A revision is a snapshot of your composition: captions and their timing, styling, animations, and every element on the timeline. Whatever revision is loaded when you export is what gets rendered — so you can even roll back to an earlier cut and export that version.

One naming collision worth clearing up: the cloud storage integrations also have a revisions folder — that one holds timestamped copies of delivered files in your Dropbox or Drive. The editor's revisions live inside Inwista and track your project state. Same word, two different safety nets.