Designers · problem and fix
Figma smart animate not working on Mac: causes and fixes for designers in 2026
If Figma Smart Animate is not working, the transition either fails to match layers or the file is too heavy to play smoothly. Figma falls back to a dissolve in the first case and stutters in the second. This guide shows how to tell which one you have, then fixes each one without buying anything.
The short answer
- Smart Animate matches layers by name and by position in the frame hierarchy. If names or nesting differ, the layer dissolves instead.
- Drop shadows, inner shadows, overlays and shape-to-shape morphs are not supported, so they will not animate as you expect.
- Stutter comes from heavy files. Figma sets a memory limit of about 2 GB per browser tab, and the desktop app uses the same limit.
- Check the Prototype tab first, then layer names, then file weight. Split large files before you try hacks.
What smart animate transitions that fail or stutter costs you
Your own time, measured in minutes
No survey or study in this research measured the time lost to Smart Animate problems. What you can measure is your own time. Write down the minutes a failed preview costs you for one week, including rebuilt layers and reloads. Your own log is more useful than any average.
The hourly value of your time
The BLS puts the median pay for graphic designers at $62,960 per year, or $30.27 per hour, in May 2025. Treat that as a rough rate, not a promise for your job. As illustrative arithmetic, one hour a week lost for 52 weeks comes to about $1,574 a year at that rate. This is a calculation, not a measured loss.
Client review rounds
A transition that dissolves when it should slide can look broken to a client. The next message often asks for changes you did not plan. No source here measures how often that happens. Run a short check before every review, so a broken transition does not become the topic of the meeting.
Interrupted flow
NN/g says a response within 0.1 second feels instantaneous. It also says 1 second is about the limit for a user's flow of thought to stay uninterrupted. A preview that stalls for seconds breaks that flow. The research here does not measure burnout from tool problems, so read this as a usability point, not a health claim.
Why it happens
Layer names do not match
Smart Animate matches layers by name and by position in the frame hierarchy, according to Figma's help page. If Title in the first frame is Title Text in the second, the layer has no match. Figma then brings the new layer in with a dissolve. The failure is silent, so nothing warns you.
Nesting differs between frames
Matching also depends on where a layer sits in the hierarchy. A card inside a group in one frame and loose on the canvas in the next can break the match, even when the names look right. A Figma staff member made the same point about hierarchy in a community thread.
Drop and inner shadows
Figma's help page says it does not support Smart Animate for layers with drop shadow or inner shadow. A layer with one of these effects may not animate as expected, even when its name and position match. Shadows are common on cards and buttons, so this failure shows up on many screens.
Overlays and shape morphs
Overlay actions are unsupported because Figma treats an overlay as a new frame. Moving between shapes is also unsupported. Both cases look like a broken transition when they are simply outside what Smart Animate does. Check the action type before you change layer names.
Components and variants pile up
Figma's memory guide says components and variants add weight to a file. Many separate variants of one button can push the file toward its memory limit. The guide recommends component properties to cut the count. A heavy file can stutter, and that stutter looks like a bad transition.
One giant file for the whole product
Figma's memory guide suggests splitting large files, for example one file per page. A single file that holds every flow, version and asset is hard to keep under the limit. Each browser tab gets about 2 GB for that file. The bigger the file, the less room the preview has to run smoothly.
Memory pressure on the Mac
Figma runs on browser technology, so the desktop app shares the browser memory limit. A third-party blog says the Helper (Renderer) process draws the canvas and holds most of Figma's RAM on a Mac. Other apps and tabs compete for the same memory. The preview is often the first place you notice it. web.dev says to keep 60 frames per second when animating, and lower rates cause stutters users notice.
How to fix it
These work with or without any app.
Match layer names exactly
Select the layer in each frame, double-click its name in the Layers panel, and type the same name. Watch for small differences such as Title and Title Text. Give each frame a unique name too, which a Figma staff member suggested in a community thread. Preview after each pair you fix.
Fix the nesting
Move the matching layer into the same group in both frames, or ungroup both. Keep the hierarchy the same from frame to frame. Preview one transition at a time, so you know which change helped.
Test without shadows on matching layers
Drop and inner shadows are unsupported for Smart Animate. Remove the shadow on a test copy and see whether the layer animates. If it does, decide how to keep the look without breaking the transition, and test that version before you change the production file.
Use the matching checkbox with care
Smart animate matching layers changes how fixed layers that do not match behave. Turn it on only for screens that need it, and watch the fixed layers in the preview. Turn it off again if other layers start to dissolve.
Reduce components and variants
Replace near-copies of a component with one component that uses component properties. Figma's memory guide recommends this to reduce the count. Fewer variants means fewer objects for the canvas to draw, and that helps a heavy file.
Split the file
Move each page or flow into its own file, following the memory guide. Test the split on a copy so the original stays intact. Keep the prototype flow inside one file where the transition lives, so the connections still work.
Compress images and split complex SVGs
The memory guide suggests the Downsize plugin for compressing images, and it suggests importing complex SVGs in smaller parts. Check image sizes before you import them. If one SVG makes the canvas lag, bring it in pieces and preview after each piece.
Quit, reopen and clear the cache
Quit with ⌘Q, wait a few seconds, and reopen the app. Close browser tabs you do not need. Turn off multiplayer cursors, layout guides and effects while you preview. Figma's checklist says to clear the desktop app cache too, but check its help center for the Mac steps first.
Check your browser and WebGL
Use the latest stable Chrome, Firefox or Safari. Confirm that WebGL is enabled, because Figma's checklist asks for it. If a Chrome extension blocks WebGL, test in a clean profile or a window without extensions.
Test forum tweaks one at a time
Community tips such as turning off hardware acceleration on Mac are anecdotes. Change one setting, preview, and note the result. Undo the change if nothing improves. Figma's official checklist does not list this tip, so do not treat it as a known fix.
Two different failures, one complaint
When people say Smart Animate is not working, they usually mean one of two things. The transition does not move the layers the way they expected, or the preview stutters. Those problems have different causes, so figure out which one you have before you change anything. Trying every fix at once wastes time and hides the real cause.
2 GB
Figma memory limit per browser tab, which the desktop app also uses
Reduce memory usage in files (Figma Help Center)60 fps
Frame rate web.dev says to maintain whenever you are animating
Animations and performance (web.dev)$62,960
Median yearly pay for graphic designers in May 2025
Graphic Designers (BLS Occupational Outlook Handbook)1 second
NN/g limit for a user's flow of thought to stay uninterrupted
Response Times: The 3 Important Limits (Nielsen Norman Group)How to tell which problem you have
Start with a clean test. Open the prototype, select the frame where the transition starts, and click Present, the play button at the top right of the Figma window. Click the trigger twice and watch the motion. If layers slide and one or two dissolve, you have a naming or nesting problem. If the test file is smooth but the real one is choppy, you have a weight problem.
- Some layers slide and a few fade: check names and nesting in those layers.
- Every layer dissolves: the frames share no matching layers, or an unsupported property sits on a layer.
- Smooth on a small file, choppy on a large one: the file is probably too heavy for its memory limit.
- Choppy only when other apps are busy: your Mac or browser is short on memory.
A worked example: the card that dissolves
Say you have a frame called Home with a card layer named Title. The second frame, called Home 2, shows the same card, but its text layer says Title Text because you renamed it while editing. Smart Animate looks for Title in Home 2, does not find it, and fades the text in. The fix is one rename. Select the layer in Home 2, double-click its name in the Layers panel, and type Title. Preview again, and the text should slide with the card.
Frame names matter too. A Figma staff member wrote in a community thread that Smart Animate is reliant on layer name and hierarchy. That person suggested unique frame names, which worked in their test. The thread did not mark an accepted solution, so treat the tip as a check, not a guarantee.
Why shadows, overlays and morphs never animate
Figma's help page says it does not support Smart Animate for layers with drop shadow or inner shadow. A shadow can break an otherwise matching layer, so a card that looks identical in both frames may still dissolve. Test it on a copy. Remove the shadow in one frame, preview, and compare the motion. If the layer moves, the shadow was the reason.
Overlays are a separate case. Figma treats an overlay as a new frame, so Smart Animate does not apply the same way. Moving between shapes, such as a rectangle that should become a circle, is also unsupported. For those screens, pick a transition type the page supports, and accept that the result will not be a true morph.
One more trap sits in the matching checkbox. The help page says that if you check Smart animate matching layers alongside another transition, fixed layers that do not match get a dissolve. They do not follow the transition you picked. Turn the box on only for screens that need it.
Check the Prototype tab settings
- Select the frame that starts the transition, then open the Prototype tab in the right sidebar.
- Confirm that a connection runs from the trigger to the destination frame.
- In the Animation section, open the transition field and choose Smart animate.
- Decide whether you need Smart animate matching layers, and read the warning above before you turn it on.
- Click Present and test again. Reload the preview if it looks stale.
You need edit access to change these settings. A view-only link can show the prototype, but it cannot show your edits. If the settings look right and the file still misbehaves, ask the file owner to confirm your access level. Smart Animate is on all plans, so your plan is not the cause.
Why a heavy file stutters on Mac
Figma's memory article gives an active limit of about 2 GB per browser tab. The desktop app runs on browser technology, so the same limit applies to it. At 90%, Figma shows a red alert tile. At 100%, the file locks. A file near that limit can stutter, and the preview is often where you notice it first.
Figma's troubleshooting checklist lists warnings at 60%, 75% and 100%. That does not match the memory article, which lists 90% and 100%. Use the warnings your file actually shows, and check the Figma help center for the current numbers. Do not plan around a threshold you have not seen in your own file.
A Mac blog estimates that Figma's Helper (Renderer) process draws the canvas and holds most of the app's RAM. It says a simple file may use 300 to 500 MB there, and a complex file can pass 1 GB by itself. Treat those figures as one blog's estimates, not Figma data. They still explain why a large file slows down before you see a warning.
Read your memory numbers on a Mac
Figma shows memory data inside the app. Open Main menu > View > Memory usage, choose Manage memory, and turn on the toggle called Show memory in layers panel. The Layers panel then shows memory figures next to layers. Write down the three heaviest areas. Those are your first candidates to simplify or move to another file.
Check the Mac side with Activity Monitor. Press ⌘Space, type Activity Monitor, and press Return. Open the Memory tab and find Figma's processes. Apple's guide also describes an Energy pane that lists energy use by app and process. The Apple page did not show a GPU section, so check your macOS version for that detail.
- Quit Figma with ⌘Q when you finish, then reopen it the next day.
- Close tabs you do not need, because each browser tab has its own memory limit.
- Force quit a frozen app with ⌘⌥Esc, then reopen Figma and retest the transition.
- Turn off multiplayer cursors, layout guides and effects while you preview.
Symptom, cause and first check
| Symptom | Likely cause | First check |
|---|---|---|
| Layer dissolves instead of moving | Name or nesting differs | Compare layer names in both frames |
| Drop shadow never animates | Shadow effect is unsupported | Test a copy without the shadow |
| Overlay does not slide | Overlays are treated as new frames | Check the action type in the Prototype tab |
| Preview stutters on a big file | Memory is near the 2 GB limit | Main menu > View > Memory usage |
| Warning tile on the file | Memory warning at 90% or 100% | Split the file and retest |
Fixes that cost nothing
Figma's memory guide suggests several fixes that need no purchase. Simplify the frame structure first. Reduce components and variants by using component properties instead of many near-copies. Split large files into smaller ones, such as one file per page. Structure helps every time, so start there before you touch settings.
Test any split on a copy so the original stays intact. The memory guide also names the Downsize plugin for compressing images, and it suggests importing complex SVGs in smaller parts. Check image sizes before you import them. If one SVG makes the canvas lag, bring it in pieces and preview after each one.
Browser, app and cache steps
Figma's checklist says to close unused tabs and to force-quit and reopen the browser or desktop app. It also says to clear the desktop app cache. The checklist does not give Mac steps for the cache, so look up the current steps in Figma's help center before you clear anything. Save a copy of the file first.
Check the browser too. Figma recommends the latest stable Chrome, Firefox or Safari. It asks you to confirm that WebGL is enabled. The checklist notes that a Chrome extension can block WebGL, so test in a clean profile or a window without extensions to rule that out.
Forum tweaks to test last
Community threads suggest other fixes. Some say to turn off hardware acceleration on Mac, to work at 100% zoom, or to clip frames to the same size. These are anecdotes. Figma's official checklist does not list them, and the threads did not mark a verified solution. If you try one, change only one setting, preview, and write down the result.
Mistakes that waste the most time
- Editing the wrong copy. Duplicated frames keep the old names, so fix the frame you actually preview.
- Renaming one layer and forgetting the matching layer in the next frame.
- Judging a transition on a stale preview. Stop the preview, then start it again.
- Turning on Smart animate matching layers as a catch-all fix. It can make other layers dissolve.
- Rebuilding the whole prototype before checking names. Most failures need one rename.
When to send the file to Figma support
If the names match, the shadows are gone and the file sits under the memory limit, send a report. In the community thread, Figma support asked the poster for a file link and to share the file with the support team. Describe the frame names, the transition type and the exact step where the motion breaks. That detail saves a round of questions.
Where Lazur helps, and where it does not
Lazur is a voice assistant for the Mac. Hold ⌥⌘ (Option and Command) and ask about anything on screen, and Lazur answers out loud. Ask where the Prototype tab is, and Lazur draws a circle and a label around it. Ask how to set Smart animate, and Lazur guides you one click at a time, waiting for each click. It does not click for you, and it does not edit your file.
Lazur looks at your 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. Lazur is not a plugin or add-in for Figma, and it does not edit your file. Pro costs $18 a month, or $15 a month billed annually, with 150 AI actions. The 3-day trial starts when you first open the app, with no credit card.
Next steps once the transition moves
Once Smart Animate works in one flow, repeat the check on the other frames. Keep a copy of the working version. Then read the guide on how to create a prototype in Figma for the connection and transition steps in more detail. For desktop setup and memory habits, see Figma for designers on Mac.
A stubborn prototype usually improves in layers. Fix names first, then effects, then file weight. Write down each change and its result so you know which one helped. If nothing changes after the full routine, the problem may be file size or a bug, so send the report and move on.
Faster with Lazur
Where Lazur helps with smart animate transitions that fail or stutter
Hold ⌥ ⌘ and say what you want. Lazur sees your Figma window. Lazur draws a circle and a label around the button or menu you need.
- 1
Hold ⌥⌘ and talk
- 2
Lazur draws a circle and a label around the button or menu you need.
- 3
You stay in Figma. Nothing to copy into a chat window.
More things to say in Figma
- “Why did this layer dissolve instead of sliding?”
- “Where is the Smart animate option?”
- “Walk me through setting Smart animate on this connection.”
- “Write a note to the file owner about the card title layer.”
- “Find recent community threads about Smart Animate failing.”
Free for 3 days, then $18/month. Download for Mac
You say“Lazur, where is the Prototype tab?”
Lazur · points at itLazur draws a circle and a label around the Prototype tab in the right sidebar, so you can open it yourself.
What designers say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Why did this layer dissolve instead of sliding?”
Lazur answers out loud, based on what is visible on your screen, and points at the layer names it can see.
Explains what's on screen
“Where is the Smart animate option?”
Lazur draws a circle and a label around the transition field in the Animation section.
Points at it
“Walk me through setting Smart animate on this connection.”
Lazur guides you one click at a time and waits for each click. It does not click for you.
Walks you through it
“Write a note to the file owner about the card title layer.”
Hold fn and dictate the note into any text field. Your personal dictionary keeps layer names spelled the way you want.
Types what you say
“Find recent community threads about Smart Animate failing.”
Research runs in Lazur's own Chrome tabs and comes back with a summary and a report.
Researches in the background
A plan you can start this week
- Day 1
Reproduce the failure
Open the prototype, click Present, and record which layers dissolve. Note the frame names, the transition type and whether the file feels heavy. Do not change anything yet.
- Day 2
Match names and nesting
Compare the layer names and group structure in the two frames. Rename or regroup one pair at a time. Preview after each pair, so you know which change worked.
- Day 3
Check effects and settings
Remove drop and inner shadows on a test copy. Check the Prototype tab, the connection and the Smart animate setting. Keep the matching checkbox off unless a screen needs it.
- Day 4
Measure memory
Turn on Main menu > View > Memory usage, then check Activity Monitor for Figma processes. Write down the three heaviest areas of the file, and note the warning tile if one appears.
- Day 5
Split, clean up and report
Split the heaviest page into its own file, reduce variants, and quit and reopen the app. Preview the full flow once more. If the failure stays, send the file owner or Figma support a short report with frame names and steps.
Questions people ask
Why does Figma Smart Animate dissolve instead of moving?
Smart Animate matches layers by name and by position in the hierarchy. A layer with no match in the next frame fades in, so it dissolves. Compare the layer names and grouping in both frames first, then preview again.
Does Smart Animate work with drop shadows in Figma?
Figma's help page says it does not support Smart Animate for layers with drop shadow or inner shadow. Test a copy without the shadow to see whether the shadow is the cause. Do not expect the shadow itself to animate.
Why is my Figma prototype laggy on Mac?
Heavy files can stutter, because Figma sets a memory limit of about 2 GB per browser tab. The desktop app uses the same limit. Check memory usage, close tabs you do not need, split large files, and reduce components and variants.
Do I need edit access to fix Smart Animate?
Yes. Figma's help page says edit access to the file is required for Smart Animate. A view-only link can show the prototype but cannot show your changes. Ask the file owner for edit access if you need to change settings.
Is Smart Animate available on every Figma plan?
Figma's help page says Smart Animate is on all plans. If a transition still fails, your plan is not the cause, so check names, nesting, effects and file size instead.
What is the memory limit for Figma on Mac?
Figma's memory article gives about 2 GB per browser tab, and the desktop app runs on the same technology. Reaching 100% locks the file. Figma's troubleshooting checklist lists different warning levels, so check the current help center numbers.
Can Lazur fix Smart Animate for me?
No. Lazur answers questions about what is on your screen, points at controls and guides you one click at a time. It does not click or edit your file for you. You still make the changes yourself.
Should I turn off hardware acceleration to fix stutter?
It is a forum tip, not an official Figma fix, and Figma's checklist does not list it. Change one setting, test the preview, and undo the change if nothing improves.
Sources
- Smart animate layers between frames (Figma Help Center) · Figma · checked 2026-11-07
- Reduce memory usage in files (Figma Help Center) · Figma · checked 2026-11-07
- Troubleshooting checklist (Figma Help Center) · Figma · checked 2026-11-07
- Guide to the Figma desktop app (Figma Help Center) · Figma · checked 2026-11-07
- Smart Animation doesn't animate properly (Figma Community) · Figma Community (user forum with staff replies) · checked 2026-11-07
- Response Times: The 3 Important Limits (Nielsen Norman Group) · Nielsen Norman Group · checked 2026-11-07
- Animations and performance (web.dev) · Google (web.dev) · checked 2026-11-07
- Graphic Designers (BLS Occupational Outlook Handbook) · U.S. Bureau of Labor Statistics · checked 2026-11-07
- Figma on Mac: why Helper (Renderer) eats RAM (Shiny) · Shiny (third-party blog) · checked 2026-11-07
- Activity Monitor User Guide (Apple Support) · Apple · checked 2026-11-07
Fix smart animate transitions that fail or stutter with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.