Figma version history restore: retention limits and named-version persistence on the Starter plan

Our team relies on Figma's built-in version history as the rollback mechanism for design files. Restoring an earlier version is non-destructive — it copies the old state to the top of the history as a new version — so the rollback itself can be undone. That part of the behavior is well documented and works as expected.

The unresolved constraint is retention. Figma's free Starter plan has been documented to keep roughly 30 days of version history per file, while paid plans retain full history. We use named versions ("Save a version") as labeled checkpoints before major redesigns, and we need to know whether those checkpoints survive past the retention window on Starter-plan files, or whether only paid plans guarantee long-term persistence. Assume current Figma plan tiers as of late 2026; specifics may have changed and should be verified against the Help Center.

There is also a permission boundary to confirm: restoring and saving versions appear to require edit access, while view-only collaborators can browse history but not change the file's current state.

• Are named versions exempt from the Starter plan's ~30-day history retention, or do they expire with the rest?
• Is edit access on the file strictly required to restore a version, or does any team-level permission override this?
• Does restoring a file version affect published team-library components in any way, or are file rollback and library publishing fully independent?