Figma Version History

Version history keeps a timeline of your file. Mistakes become easy to undo, and old ideas stay within reach. Every serious Figma user relies on it to protect hours of work.

The Idea in Plain Words

Imagine a notebook that photographs every page at regular intervals. Spilled coffee on today's page costs nothing. You open yesterday's photo and copy what you need. Version history works the same way for designs.

Automatic Versions

Figma saves changes constantly and groups edits into automatic versions after periods of activity. Each version shows a date, a time, and the name of the editor.

Version History
-------------------------------------------
Today
  4:30 PM    Auto-saved   Priya
  2:10 PM    Auto-saved   Priya
Yesterday
  6:45 PM    Auto-saved   Sam
  11:20 AM   Named: "Client review draft"

Free plans keep a limited window of history. Paid plans keep versions longer.

Open Version History

  1. Click the file name at the top of the canvas.
  2. Choose Show version history.
  3. Browse the list in the right panel.

The shortcut is Ctrl + Alt + H (Cmd + Option + H).

Preview an Old Version

Click any version to view the file as it looked at that moment. The canvas switches to read-only mode, so nothing changes by accident. Pan and zoom to inspect details.

Restore a Version

Click the three-dot menu beside a version and choose Restore this version. The file returns to that state. Newer work remains in history, so restoring never destroys the timeline.

Timeline

Mon ───── Tue ───── Wed ───── Thu
 v1        v2        v3        v4 (current)
                      ↑
               Restore v3

Create Named Versions

Named versions mark important moments. Press Ctrl + Alt + S (Cmd + Option + S), or use Add to version history from the menu. Type a title and a short description.

Weak names              Strong names
---------------------   --------------------------------
Version 7               Approved by client - May 12
Latest                  Before navigation redesign
New one                 Handoff to developers

Moments to Name a Version

  • Before a risky redesign.
  • After client approval.
  • At the moment of developer handoff.
  • At the end of each work week.

Branching in Brief

Larger plans offer branching. A branch copies the file so a designer can explore changes safely. The team reviews the branch and merges it into the main file once everyone agrees. Think of a branch as a side road that rejoins the main highway.

Main file ──●────────●────────●──── (stable)
             \              /
Branch        ●──●──●──●───●        (experiment, then merge)

Recover a Deleted Layer

  1. Open version history.
  2. Find a version from before the deletion.
  3. Preview the version and copy the missing layer.
  4. Return to the current file and paste.

This method saves work without rolling back everything else.

Common Mistakes

  • Relying on automatic versions alone and never naming milestones.
  • Restoring a full version when copying one layer would do.
  • Ignoring history limits on a free plan and expecting old versions to remain.

Practice Task: Time Travel in Your File

Open any practice file and save a named version called Starting Point. Change the colors of three layers and delete one shape. Open version history, preview Starting Point, and copy the deleted shape. Return to the current file and paste it back. Finish by restoring the named version to see the whole file return. The drill builds the confidence to experiment freely.

Save name → Make changes → Preview old version → Copy or restore