On this page
Quick steps
Undo from the menu
Open Main menu → Edit → Undo. If that works and ⌘Z or Ctrl+Z doesn't, the key is being sent to the wrong place or mapped to the wrong key.
Match the keyboard layout
Go to Main menu → Preferences → Keyboard layout and pick the layout your computer uses. On AZERTY and QWERTZ keyboards the Z key sits somewhere else, so a mismatch breaks undo first.
Click the canvas
If a plugin window, a text field in the sidebar or the browser's address bar has focus, the undo key goes there instead of to the file. Click an empty part of the canvas and try again.
Reload or switch apps
Reload the file, or open it in the browser if you use the desktop app (and the other way round). If undo works in one and not the other, the problem is local to that app.
Restore from version history
Click the file name, choose Show Version History, and preview earlier versions. Duplicate the one you need and copy the layers back, or restore it if the whole file should roll back.
Figma undo and redo shortcuts
| Action | Mac | Windows |
|---|---|---|
| Undo | Mac⌘Z | WindowsCtrlZ |
| Redo (not documented by Figma) | Mac⇧⌘Z | WindowsCtrlShiftZorCtrlY |
| Save a named version | Mac⌘⌥S | WindowsCtrlAltS |
| Actions menu (run a command by name) | Mac⌘K | WindowsCtrlK |
| Keyboard shortcuts panel | Mac⌃⇧? | WindowsCtrlShift? |
Figma's help center documents undo but not redo, so the redo keys above are the common ones rather than official ones. Open the shortcuts panel to see what your keyboard layout uses. Every other key that stops responding is covered in Figma shortcuts not working.
Why Figma undo skips steps or fails
A plugin made the change
Figma's plugin API doesn't add a plugin's actions to undo history one by one. Unless the developer adds checkpoints with figma.commitUndo(), everything a plugin did in one run comes back as a single undo step. One ⌘Z can remove a whole batch of renamed layers or generated content, or nothing seems to happen until you press it again. If a plugin misbehaved and undo won't clean it up, see Figma plugins not working.
Someone else changed it
In a shared file, your undo covers your own edits. Figma built multiplayer undo so that undoing and redoing never overwrites what other people did after you, which means ⌘Z won't bring back a frame a teammate deleted or moved. Find the version from before their change in version history and copy the layers across.
The keyboard layout is wrong
Figma maps shortcuts to a US QWERTY keyboard by default. Two forum threads about undo failing have about 19,500 and 12,900 views, and the fix Figma's community points to first is Main menu → Preferences → Keyboard layout. Figma shows a warning banner when the setting and your system layout disagree.
The browser or another window has the key
In the browser, ⌘Z goes to whatever has focus. A plugin's own window, the layer name you're editing, a sidebar input or a browser extension can take it before Figma does. Click the canvas, and if undo still fails in the browser only, try a private window with extensions off. For the desktop app, clearing the Figma cache is the standard reset.
Undo stops partway through a session
Some forum reports describe undo working, then stopping after a few minutes, with a restart fixing it only for a while. Nobody has posted a reliable cause. If this happens to you, save a named version with ⌘⌥S / Ctrl+Alt+S before any big change, and report it through Figma support with a screen recording.
Is there an undo history in Figma?
No. Figma doesn't show a list of undo steps, and it doesn't document how many steps it keeps or whether they survive a reload. People have asked for an undo history panel on the forum. Treat undo as short-term and version history as the record.
Version history opens from the file name menu with Show Version History. Figma saves an autosave checkpoint every 30 minutes, and the Starter plan shows 30 days of history while paid plans show all of it. Restoring a version replaces the current file, so save a named version of the current state first, or right-click the old version and choose Duplicate to open it as a separate file and copy only what you need.
How to undo Ready for dev in Figma
Marking a section, frame or component Ready for dev is a status, and you remove it from the same place. Click the Ready for dev label on the section, frame or component, then choose Remove status from the dropdown. You need a Full or Dev seat. Figma doesn't document whether ⌘Z reverts a status change, so use Remove status rather than relying on undo.
The green icon next to the page name disappears once nothing on that page is marked Ready for dev. On Organization and Enterprise plans, Dev Mode also keeps version history for each design marked Ready for dev, including any reason typed when a changed design's status is updated. More on statuses in the Figma Dev Mode guide.
Ranked listThe most useful Figma plugins for everyday work in 2026Frequently asked questions
How do I redo in Figma?
Redo is commonly Shift+Cmd+Z on Mac and Ctrl+Shift+Z or Ctrl+Y on Windows. Figma's help center doesn't document it, so check the shortcuts panel (Ctrl+Shift+?) for your layout.
How many times can you undo in Figma?
Figma doesn't publish a limit. Forum users report that undo runs out after a long session and doesn't survive closing the file, so save named versions for anything you might need to get back.
Can you undo someone else's changes in Figma?
Not with Cmd+Z or Ctrl+Z, which walks back your own edits. Open version history, duplicate a version from before their change, and copy the layers you need into the current file.
Why does Ctrl+Z not work inside a Figma plugin?
When the plugin's window has focus, the key goes to the plugin, and most plugins don't handle it. Click the canvas first. A plugin's changes to the file usually undo as one step.
More in Troubleshooting
- Figma plugins not working? How to fix itFigma plugins not loading, missing or greyed out? Check your seat and edit access, org approval, network blocks and cache. A step-by-step checklist that works.
- How to Fix "Can't Open File: WebGL Isn't Supported" in FigmaFix Figma's "WebGL isn't supported" error: turn on graphics acceleration, check WebGL, update to a supported browser, and fix Edge tracking prevention.
- Figma Not Working? Every Fix, in the Order to Try ThemFigma not loading, showing a blank white screen or crashing? Check Figma's status, your browser version, WebGL, the desktop cache and file memory, in order.
- How to Make Figma Less Laggy and FasterFigma slow or laggy? Each file gets 2GB of memory. Check the memory meter, find heavy layers, and cut hidden layers, variants, big images and extra pages.
- Figma shortcuts not working? How to fix themFigma shortcuts or Ctrl+Z not working? Figma assumes a US QWERTY keyboard. Set your real layout in Preferences, then check undo, redo and Show/Hide UI keys.
- How to Clear the Figma CacheClear the Figma desktop cache with Help > Troubleshooting > Reset Figma and Restart, or delete the cache folders on Mac or Windows. Plus the browser method.
- How to install Figma pluginsFigma plugins don't need installing: open one from the Community or run it inside a file. Steps for Figma Design, Dev Mode, FigJam, Slides, saving and admins.
- Figma plugin vs widget: what's the difference?A Figma plugin runs for one person and closes when done. A widget is an object on the canvas everyone can see and use. When to pick which, with examples.
- How to Generate All Component Variants in FigmaFigma shows only the variants you draw. Here's how to lay out every combination of variant, boolean and nested props as a matrix, by hand or with Instancer.
- Figma Keyboard Shortcuts: The Full Mac and Windows ListEvery Figma keyboard shortcut Figma documents, for Mac and Windows: tools, layers, auto layout, components, text, zoom, prototyping and panels, in one list.