Hi,

I appreciate this feature and I do use it for some while.

However, I would also expect to be able to save components from any file to the <library file>.
This would help me keep track of the created components and re-use them as I design more screens, in separate files.
Currently, I can't keep up with updating the <library file> as I work. I tried but it consumes a massive amount of time.
The extent to which I use this feature is by creating a <library file> that contains all the colours, fonts and a few basic components (inputs, selectors, buttons).

I really think this is a must-have for large projects where you use many XD files. You don't know before starting the work what components you'll have. As you create more and more screens in separate files, it gets more and more difficult to create the components in the file where the library is.

I've also added a new feature request for this here https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/45953599-add-master-components-to-a-library-from-any-file

UPDATE: I resolved this by making a change to any state in the main in source document, then updating in the non-library document. Now all states of the component are displaying the link icon, and are inheriting changes when made to the main component in the source document.

This feature is not available as of August 1, 2022.
Is there documentation on this?

When I select a state other than the one I saved to the library, the link icon disappears, and is no longer able to "Edit Main in Source Document".

Instead, the option is now "Edit Main Component", and the "Main Component" (not the linked component) is spawned onto the canvas of the file, rather than taking the user to the main component in the source document.

It took me a lot of digging around, but it looks like the functionality was released.

From what I can tell, you need to create your "design system" with components, etc and then publish the XD document to a Creative Cloud library - https://helpx.adobe.com/xd/help/whats-new/2021.html#component-cc

I found instructions on how to do this at https://helpx.adobe.com/xd/help/work-with-creative-cloud-libraries-xd.html#publish-share.

Hope it helps.

This component-state saving feature is not working in the latest version of XD.

Could an Adobe representative please confirm whether or not this feature is indeed "completed"? As others have stated, the ability to save components with multiple states into shareable libraries does not seem to be possible at this point.

@Elaine - I am on the latest XD and can confirm that component states are NOT being saved in the CC library component. Dragging the component into a new doc loses all states outside of default. Please advice

Hello
Can you confirm this as I am using 36.2.32.5 Cloud 4.5.1.1 and it doesnot work

Hello can you confirm this because I am on 36.2.32.5 and it does not work

How do you do this? If it has been added its not clear on how to do it

How do you do this? If it has been added its not clear on how to do it

I came here expecting to find out that I was mistaken, and that it actually was possible to save component states in a CC library. I even tried saving the master as a cloud file thinking maybe it would work if every part of the thing was on your servers, but no such luck. I am utterly amazed at how boneheaded this oversight is.

Look, I get it. You've only got so many developers, and you've got to focus on your primary goal of hobbling the local storage use of your software so that you can force everyone onto yet another cloud storage service. But you should know that Adobe XD is the primary reason that the company I work for pays for CC. They don't care that it gives me Premiere and Animate, and have questioned repeatedly why we ALL need Photoshop and Illustrator. We keep selling our bosses on your software by touting XD's power with a CC account. You keep up with stuff like this and we are going to start losing that fight.

Not being able to share buttons with their states is a major pain when dealing with large-scale projects. Having the ability to share it with CC libraries would improve XD a lot.

My Design Team is also waiting for this ...

I'm also waiting for this option - why is so huge difference between build-in components and CC library. It should be working the same way.

Is this something planned for a new update? It's been more than 3 months we are all waiting to be fixed. For now states can be used only in small projects.

I started use components option some time ago and see one thing that doesn't seem to work with CC Library. When I add component there and copy from library to another project it seems to see only default state.
It is quite surprising as updating components in the original file updates all changes in any instances within other files when I just copy/paste them between files. Why the same doesn't apply to the component added to library? Am I missing some sync option here?

We have a very complex design system within our company, and it is imperative for us to have the components stored with their associated states as well. Otherwise, the components states feature becomes redundant, isn't it?

At this point, I'm very annoyed with this issue, since it didn't cross my mind to check if the states will be added to the CC library as well. And now, I'm sitting here with a few hundred components that I cannot add to the CC library since they cannot be used anyhow.
I'm not even starting to talk about the time invested in "converting" all the components to have states — prior to the component states feature, we had created and used one component for each state.

@logan Exactly I share your pain.

Is this something planned for a new update in the near future?
It's essential for our work as a team.

I mean, component states are XDs biggest differentiator. How can you not A) support them in your own library system, and B) not make them function cleanly enough for users to tell the difference between limitations and bugs?