Please can we add this? I've spent days worth of time recreating stuff when this "feature" could have made it possible within seconds. Making component variations is an EXTREMELY common use case.

Not being able to duplicate components without it being an instance is severely affecting the user experience and workflow negatively

Anyone could explain it in simple words?

Let’s assume a scenario where the Main Component needs a variation that still retains the “one-to-many” quality of children inheriting properties but doesn’t affect any existing child components. To create a new parent component hierarchy, an instanced component must be ungrouped and rebuilt from scratch. Ungrouping components will also lose all the states and transition properties set up in Prototype mode. Here’s a workaround:

Clone an instance of the component for each state in the component.
Set each instance’s state to a different state.
Go through and ungroup each component instance.
Start making desired tweaks and changes to each component instance.
Recreate the new Main Component.

Copied from "https://www.toptal.com/designers/ui/adobe-xd-components-tutorial"

What does it mean by " making a component local to the file and rename ".

This should've been part of the initial release seeing how much time you already save when using components. Having to recreate a component (not to mention its states) is a waste of time when you could easily "set instance as new master component" or "create master component from this instance" when working with components...

This needs to be added ASAP!

It's confusing as to why this isn't a feature. In fact it's frustrating. I need to create a component with multiple states, that behaves the exact same way as another component, except the state images are different. Rather than Right Click > Duplicate, and letting me swap out the image. I have to recreate the entire component.

If you're reading this you're saying "no you don't, just copy it to a new file, make local, make edits, copy back to original file." @Ini Nya-Etok

Well that no longer works, as they've switched to published libraries. When you copy a component you get the red link icon, and there's no option to make it local anymore.

I know as professionals, we try to keep things cordial here, but this is ridiculous, the amount of time wasted, because they can't add a simple feature we've been complaining about for ages. I mean come on!

Thank you @Ini Nya-Etok

This helped a lot.

I tried Ini Nya-Etok's workaround and it works. Thanks!

What is going on here? I am SOOOOO tired of making new component -> stack, padding, fill color, states upon states all over again again and again.

1 component done -> Dublicate and change what needs to be changed. voila!

Once this feature hits I will have to redo + 100 components from scratch, again :/

Hi Laurel

Tried Vlad's workaround and I think you may have missed a step? Try this:

1. Copy main
2. Paste in new file
3. Make local in new file
4. Right click component in new file and select "Edit main component"
5. Rename Main in new file
6. Copy Main component from new file
7. Paste the copied component in original file (appears as an instance)
8. Right click the pasted instance and select "Edit main component"
9. Make Main component local in original file

And voila!

Hope this helps in the meantime. But PLEASE guys create a simple duplicate component function, this is such an avoidable workaround.

Desperately need this.
Tried Vlad's workaround but I am skeptical, because the component still says "Instance." Shouldn't it be a main component now since it's unlinked from the previous? Where is this one's "Main?" -- If I paste it in a new document, it is then linked to this instance which I had made Local. So this Instance is acting like a Main for its future instances. The actual MAIN is my original.

This is SO confusing. I'm still concerned that something will get overridden at some point.

disappointed again. Really need to recreate the same appearence component from zero because I cannot transform into main component again.

Hi,

+10000 votes for this feature.
Everything on the asset panel should be duplicatable and mergeable.

This is sorely needed. I think it would be super easy to implement too. Just add a new menu item when you right-click on an instance that converts it to a new main component.

I can’t tell you how many times I’ve had to create new components from scratch that were very similar to other components I had already created. I did not know about the work-around, so that helps a ton, but this is an easy, much-needed feature.

I thought I was working on 5 Main components. And after making all my edits, realized they were all "Instance" not "Main" because I'd saved the document under a new name. So now none of my component changes rippled through the document! If I ungroup the components, I will lose my hover states.

So YES. We need the capability to change an Instance of a component to either override the main, or be a new component, with all states inherited.

Thanks Vlad, this is a great workaround! Especially for complex components with many states.

For others who'll try Vlad's way: After pasting back and making local you need to also click Edit main component (because the pasted one is an Instance).

A quick workaround for duplicating components with a lot of similarities:

Copy/paste component in another file, then make local to that file and rename.
Then copy/paste back the new renamed component to your file and make it local again.

This seems to me, to be faster than rebuilding the component from scratch.
Cheers

This is very much needed for building any complex design.
Thanks

Please implement!

It's been way too long without this...