Skip to main content

Is there a technical problem with figma make recently?
i have been working in a project for the past month, i took a break for 4 days and continued working today and suddenly I can not create any new figma make objects on Figma sites anymore (using previously designed Figma Design components).

I thought first that my components are too complicated, i stripped down the design into a basic element, literally some text in few different variants, but after the element is created, and i give the first command, the figma make element is deleted on its own and return to the original design.

Any know technical issues or it is just my project getting too heavy?

Hey ​@Osama Aboelezz — welcome to Figma Forum, and thanks for sharing your experience with Figma Make so far. I’ll make sure your feedback reaches the right teams, as we’re always iterating based on designer and developer input.

I wanted to check if you are still running into this issue. Also, could you confirm which plan you’re on? If you’re on Starter, note that AI credits are limited. You can read more about how they work here: How AI credits work. Starter plan AI credit access is lower than paid plans and may change over time.

Regarding the issue of the element returning to the original design — are you receiving any error messages? If so, this guide may help clarify next steps: Troubleshoot AI tools in Figma.

Thanks again for your feedback — we appreciate your insights and want to make sure you get the most out of Make.


Hi ​@Tom Reem 

thanks for getting back to me. I am on Pro Plan.

The issue is mainly happening with Figma Sites, specially with integrating Figma Make objects. The code is very unstable and I am mainly facing 2 problems:

1- sometimes figma make (inside sites) is unable to create very simple elements. After creating the code, the code returns to the original design object automatically. My Workaround was I created the element in another Figma Sites project and pasted it afterwards in the original project. That worked, which suspects my doubts that Figma sites, being still beta, is still unstable and the file was just too big (maybe!). Tip: Projects between figma sites, from one site to another, does not have the library concept. I can copy an object from one project to another but that's it, when the original one gets updated there is no linkage anymore. But even worse I can not embed the element locally, I only get the message go to original object. That's something you can work on definitely!

2- the other project which does not have a work around unfortunately is how most “complex” figma make objects shows up a completely out of scale height when set to “hug”. The example shows an element, which behaves completely normal when published, but gets an unjustifiable height ( which keeps changing and increase exponentially with time). For reference this element height should be around 500px, but the frame is rendered at 4428. This number keeps increasing on its own till it reaches some six figure digits!. And as I said, most of the time, when published it behaves correctly, but the problem is you can not interact with the project anymore. Imagine working in a website which is 500,000px height! Any tip how to overcome this issue?


Hey ​@Osama Aboelezz — thanks for taking the time to try those resources and report back! I’m glad to hear you made some progress with your Figma Sites project with the pasting solution, but I definitely hear you on the areas that still need improvement.

The behavior you mentioned with the frame height is a bit puzzling. 🤔 Would you be willing to share the file with our Technical Quality team? This will help us get to the root cause. To do that, please fill out this secure form and include:

  • the link to this Forum post for context
  • a link to the file where this is happening
  • ‘can edit’ access granted to support-share@figma.com for the impacted file
  • a screen recording showing the issue in action.

Really appreciate you helping us troubleshoot, and let me know if anything else comes up!


Reply