Spectrum is now read-only. Learn more about the decision in our official announcement.


Figma is the first collaborative UI design tool built in the browser. Join our growing community and kick off a conversation!


Components turning into frames

July 3, 2018 at 3:51pm
The Figma community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

Components turning into frames

July 3, 2018 at 3:51pm (Edited 3 years ago)
Hi Everyone,
here is my issue: I have a global component. When I copy paste it to create an instance everything is fine. But when I try to copy paste the instance of the global component, it turns into a frame :/
Please let me know if i'm making a mistake or missing some kind of trick!
Show previous messages

July 23, 2018 at 4:49pm
can this be related with using the "Figma Desktop App beta testing"?
This is a known bug that we have logged and are working on a fix. We're hoping to get to this soon. Thanks for all of the reports. :)

August 6, 2018 at 12:17pm
Any update? ETA? Anything? This is seriously impacting our workflow, not in a positive way.
Hey Denis, unfortunately this is quite a complicated issue. We're working through some possible interim solutions, but overall this fix will take some time. With that being said it is something we're actively working on.

August 16, 2018 at 8:05pm

August 17, 2018 at 10:23am
I'm not sure whether I have the latest version or not (the linked document does not say which version it is related to and both Figma and Figma Beta are saying that I have the most up to date version), but the issue is still present.

August 28, 2018 at 6:44pm
Any updates?

August 29, 2018 at 4:12am
As mentioned right above that comment, it wasn't.

September 6, 2018 at 5:50am
Will this ever get fixed?

September 6, 2018 at 1:10pm
its been working fine for me!
Ahh I totally get how frustrating it is. It really gets in the way. I wonder why you're still having the issue after the update
Hmm I spoke too soon. Complicated components are still falling apart in some random cases

November 6, 2018 at 4:45am
Just wanted to pitch in that this bug still exists today.

November 21, 2018 at 4:27pm
Still exists today this is really crucial an easily breaks design systems. Since dragging a component with alt + mouse will duplicate it properly this should also be the case when copying something with cmd+c+v. Please :begging: this has to be fixed soon :)
I've also reported it via various channels, to various people, but I eventually gave up. I was always referred back to the release note that is saying it has been fixed, even though it wasn't. Shame really :)

November 22, 2018 at 6:13pm
This is also screwing up my design system right now. Please please fix this.

November 23, 2018 at 1:24am
I'm having this issue as well. It is hard to move forward on designs when you know the components aren't going to be created. I have 2 choices 1)stop designing now, or 2)redo everything later.
Is there a work around in the meantime?
the only workaround is not to copy / paste components (in a design tool 😅) and rather you have to drag the symbol from the side panel every time 😔
I guess the main difficulty is at Figma's "restore master component". When a component is turned into frame, user may not be able to restore it from instance?
Not really, or I might have a problem understanding what you mean exactly 🤔 The problem is in the various topic discussing this issue, people are looking into edge cases (like cutting a symbol, not just copying etc). But the problem is, that it does not work in the very basic flow. You have a component which has a component inside it. This is stored in a library. If you use the parent component in another file, and you try to copy the nested component from it, it automatically gets turned into a frame. It is very easy to replicate.

December 13, 2018 at 9:15pm
I'm still having this problem. Nested instances are still turning into frames or getting disconnected when I detach instance of parent component. Is team aware of this still being a problem?
Show more messages