Skip to main content
Justin_Stagge
October 3, 2023
Question

Prototype is slow but file is small

  • October 3, 2023
  • 26 replies
  • 3794 views

I have a prototype with a lot of connections but overall the file is small (11%).
Although the prototype lags, loads slowly, and triggers the ‘unable to load…’ browser notification.

  • There are no images within the file
  • Most animations are ‘smart animate’

This topic has been closed for replies.

26 replies

Vulning
June 2, 2024

Having the same issue, can confirm small file size of 4%.
For me it happens on normal vertical scroll aswell as when opening an overlay

Rob_Winters
New Participant
February 17, 2025

Also having the same issue with a small file (6%) memory usage.

My prototype is heavy on the tables which scroll both horizontally and vertically. It’s incredibly laggy and unusable for feasibility and usability tests. The only way I can get it to run smoothly is turning off the on hover interactions, which is not feasible, as we use hover states to expose functionality.

y_toku
Figmate
Community Support
February 18, 2025

Hi ​@Rob_Winters ,

 

Sorry to hear you're experiencing performance issues. Our team is actively investigating, so could you please reach out to us by filling out the form at the following URL: https://help.figma.com/hc/en-us/requests/new?ticket_form_id=29433525829271? 

 

Thanks for your patience.
Toku

 

 

InterfaceInsights
New Participant
February 18, 2025

It mostly happened when “Smart Animate” Animation applied in Prototyping. Change Prototype Interaction Animation from “Smart Animate” to “Instant” OR “Dissolve”.  Run the Prototype and It always works for me. 

February 18, 2025

  

Jean_the_Web_Machine
New Participant
July 14, 2025

I’ve run into performance issues due to the complexity of vector images—having multiple detailed vectors on a single frame didn’t affect the file size, but it significantly slowed down prototype rendering. In presentation mode, I couldn’t scroll smoothly up and down the screen.

I only discovered the cause after gradually removing elements from the frame and realized that my icons (which had complex vector paths) were the source of the lag.

Hope this helps!