How to restore a previous version in Figma on Mac: file history steps for 2026

Check the version history in Figma first

Figma keeps a history of your file as you work. Start there. Open the file in the Figma desktop app and look for version history in the File menu. Menu labels can change between app updates. If the wording differs, use the search box in the Help menu. Figma's help center lists the current steps.

Read the list before you click anything. Each entry has a time and, often, a name. Open the entry closest to the moment before the mistake. Look at the page or frame you care about, not only the timestamp. A version can look right at the top and still be wrong further down the page.

Restoring is the step that needs care. A restore can change what the file looks like now. If you made good changes after that version, they can disappear from the main file. Save a copy of the file under a new name first. Then restore, and compare the two if anything looks off.

How long each Figma plan keeps old versions

The retention window matters more than anything else on this page. Figma's plans table says Starter keeps 30 days of version history. It says Professional, Organization and Enterprise keep unlimited history. Those are the limits in the table at the research date, so check it again before you rely on them. Your plan belongs to your team or account owner. Ask them if you do not know which one you are on.

Count from the day of the mistake, not the day you spotted it. Say you changed a text style on a Monday and noticed the next Friday. You are still inside a 30-day window on Starter. If you noticed a month or more later, the version may already be gone. The clock keeps running while you look for the problem.

These figures come from consumer surveys, not design teams, so treat them as a sense of scale. Backblaze's 2024 survey of US computer owners found that 74% had accidentally deleted important data at some point. Only 15% felt absolutely certain their most important files were securely backed up. Handy Recovery's 2025 survey reported that 70.7% of respondents had lost data at least once.

Mac File menu and Time Machine fallbacks

Sometimes Figma's history is not enough. The mistake may sit in a file that is already outside the window. Or the file you need is a local document in another app. Mac document apps have their own path. Apple describes it for apps that support document versions. Apple does not name those apps, so test the path in each one before you need it.

Apple's document version path

1. Open the document, then choose File > Revert To > Browse All Versions.
2. Click the tick marks on the timeline to find the version you want.
3. Click Restore to make that version the current one.
4. Or hold Option and click Restore a Copy to save that version as a new document.

Apple's guide says Mac document apps save a version every hour. They also save more often when you make many changes. They save again when you open, save, duplicate, lock, rename or revert a document. That is why a change from a few minutes ago may not have its own saved version yet. Do not rely on automatic saves alone for big moves.

Time Machine as the wider safety net

Time Machine covers the whole Mac, not one app. Apple's guide says to open the item's folder, then use Spotlight to open Time Machine. Move back through the backups with the arrows. Select the item and click Restore. Restored items return to their original location, so check the folder afterward.

Time Machine has one hard rule. The backup disk must be connected and turned on before you start. Apple's page on restoring from a backup says so. Apply the same rule when you restore a single file. A backup that never ran cannot help you. Check the date on the backup you open.

Why good designers still lose the version they need

Most of these mistakes are slips, not bad habits. Taproot summarizes Reason's skill-based error model, which sorts everyday errors into slips and lapses. A slip is when the action goes wrong even though you meant to do the right thing. A lapse is when you forget the step you meant to take. Careful people make both kinds.

The model ties slips to interruption and habit. A Slack message lands in the middle of a drag. You nudge a layer you meant to leave alone. Familiar tasks run on autopilot, so the wrong click slides past. The restore you need is often the one you made while distracted.

Deletion is common. In Handy Recovery's survey, accidental deletion made up about 34% of data-loss cases. Hardware failure made up about 30%. Those are shares respondents reported, not a root-cause study. Read them as a rough guide to which risks to plan for.

A worked example: fixing one broken component

Here is a realistic case. You are on a Starter file. On Tuesday morning you edit a shared button component. A few instances change in ways you did not plan. You do not notice until Thursday, when a developer asks why the button looks grey. You open version history. Tuesday morning sits inside the 30-day window, so the version should still be there.

Work through it in order. Open the list and find the version from just before your edit. Preview it and check the button. Then choose between two moves. You can restore the whole file. That also rolls back the Wednesday layout work you wanted to keep. Or you can bring back only the component, if the version view lets you copy from it. The second move is slower but safer.

The common mistake is restoring too fast. People roll back the whole file to fix one button, then lose a day of layout work. Before any restore, list what changed after the version you picked. A short list in a text note keeps you honest about what you are giving up.

Edge cases that catch people out

• Starter files keep 30 days of Figma version history. Older mistakes may be gone with no warning.
• Deleted items are a separate problem. Apple says deleted iCloud Drive files stay in Recently Deleted on iCloud.com for 30 days. Files removed for good cannot be recovered.
• Dropbox sets the window by plan. Basic, Plus and Family get 30 days. Business gets 180 days. Business Plus, Advanced and Enterprise get 365 days.
• Google Docs does not state how far back version history goes. Merged revisions can hide a version. You need edit permission to browse history.
• Time Machine only holds what was on your Mac's backup disk. Cloud-only files need the cloud app's own history.
• Restoring the wrong copy can cause a second mess. Read the file name and the timestamp before you click.

Mistakes people make when they try to restore

Restoring without comparing is the first trap. You pick a version that is missing a fix you made later. Compare the two before you commit, even if it takes a few minutes. The short check saves the longer repair.

Expecting the Mac File menu to work in Figma is the second. Figma is a cloud app, and its rules come from its plan. Apple's path belongs to document apps that support versions. Apple does not list them, so do not assume a match.

Waiting too long to look is the third. The window keeps running, and each day of waiting moves you closer to the cutoff. Check history the same day you spot trouble. A same-day look costs less than a search at the end of the window.

Trusting one spot check is the last trap. After a restore, look at the parts that depend on the file. Check prototype links, variables and components that other pages use. A file can look fine on the page you see and still be broken somewhere else.

Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. Ask where version history is, and Lazur draws a circle and a label around it. Ask how to restore, and Lazur guides you one click at a time, waiting for each click.

Lazur does not click buttons or edit your file for you. It is not a plugin or add-in for Figma. You still choose the version and press Restore yourself. The split is clear, and it helps to keep it in mind.

Lazur also helps with the routine around a restore. Hold fn to dictate a change log at the cursor, in any app. Ask Lazur to draft a short note to your team. Ask it to research how another tool keeps versions. Research runs in Lazur's own Chrome tabs through the Lazur for Chrome extension, then comes back with a summary and a report.

Privacy comes first. Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. If the file holds client data under an agreement, follow your employer's rules before you share the screen with any assistant.

You can download Lazur for Mac and read the plan details on the pricing page. Start with the check that matters most, which is the version window on your own plan.

Build the habit so you restore less often

The best restore is the one you never need. Start with a copy before any big change. Name the copy with the date and a short reason. Keep the backup disk connected so Time Machine can run. Each step takes little time when you do it on purpose.

Keep the routine small. Pick a few checks you will do each week and stick to them. Set a reminder in Apple Reminders for each check. You can also ask Lazur to set it by voice, which can be quicker than opening the app mid-task.

Next steps for designers on a Mac

If you want the wider Figma routine, read Figma for designers on Mac. If a restore revealed a variable problem, read Figma variables not updating on Mac. For a single frame you want to keep as a file, see how to export a frame as PNG in Figma.