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 9, 2018 at 3:01am
Hey there Jude. I'm not able to reproduce this at the moment. Could you provide some more info?

July 9, 2018 at 2:37pm
Thanks for checking in. I realized that it was because I was copy and pasting nested components hoping they would appear as component instances outside their parent component. I am assuming this is a limitation in Figma
Oh interesting. Yeah this may either be a bug or a limitation. I'll have to check with the team later today on this. Thanks.
It would be awesome if its just a resolvable bug. Thanks for looking into it!
Yeah. It is a Figma limitation

July 10, 2018 at 6:41am
Really? I thought it was working before 🤔
this bug happens sometimes. if you copy by dragging the instance it won't happen
Last time I reported this to Figma (copying an component instance nested in another component instance), and it would copy it as a frame), they said this was a known bug. But that was a month ago.
P.S. This is really irritating when maintaining a design system. It's so intuitive/handy to grab and copy any component/subcomponent from the screens you're working from, buy alas, you'll inadvertently ruin the design systems... The worst thing you often won't notice it immediatelly. At some points you'll just notice you have 50% frames where there should have been components.
and you swear you’re not trying to copy it to a different project?
As long as it is in the same project it’s usually safe from this even if the instance component has lost its master it is still a component generally.
It consistently doesn't work.
If you're copy-pasting child instances from the parent master component, it works. If you're copy-pasting child-instances from the parent component instance, it pastes frames...
...In the same project, building the simplest example starting with the blank document. Anyway, I've already sent an example to Figma support.
P.S. This doesn't mean Figma isn't 99.9% awesome. :)
Sorry! I misread your post! Haha. Guessing this is by design... but who knows! :) <3

July 11, 2018 at 2:01pm
Yup that's how I discovered the issue. I was copy pasting components /nest components from my design system and was shocked when I looked at the sidebar and saw a bunch of frames. Hoping for a fix :)

July 12, 2018 at 12:41pm
This bug got worse as of today. Before, I was able to copy components across files (which share the same team library), and the components would persist. But now, everything gets turned into frames.

July 17, 2018 at 3:35pm
Any feedback on this? Im continuing to experience this today. Sometimes I copy paste a component multiple times and it stays a component, and then for a while it randomly pastes as a frame

July 18, 2018 at 3:17pm
Not any more feedback, but we do have this logged.

July 19, 2018 at 8:28am
I'm not sure it is related to this. But there is more hiccups going on when copying components. For example -> (It wouldn't copy the component for the first couple of tries so bear with it when watching the video)

July 23, 2018 at 8:14am
this is still a problem, and it probably needs to be upped in priority :( Basically styles are being disconnected all the time, and components as well.
For example, if you copy a component, from another component (basically if you copy a nested component), it gets pasted as a component, but if you copy this component from a standard frame, it gets pasted as a frame.
2 also, there are cases when copying components across different files gets stripped of their styling. I've just noticed that half of my screens have detached styling.
I understand, that Figma is gaining in popularity, features are requested all the time, and the community is very vocal, but since we have no control over what version of Figma we use, you need to double down on ensuring that features that might delete hours or maybe days of work are properly tested. Because there is no point of using styles, if they get randomly detached.
I am certain I am experiencing this issue in some way or another:

July 23, 2018 at 4:37pm
I'm experiencing this as well, if I copy a Frame (e.g. screen desktop frame) that has a bunch of components to another file, all the components turn into frames. My team library is also shared.
but sometimes some components survive, it's definitely a bug
can this be related with using the "Figma Desktop App beta testing"?
Show more messages