Thanks for that @Hal_Lee , will test it 😉

This is what it says in their guidelines

Copy pasting variables across files

Variables can be used in prototypes.

Currently, if you copy and paste objects to different file, the prototype will continue to work as the variables transfer over. However, any unpublished variables applied to prototypes won’t be available for further use, like when creating Set variable actions, or switching an object’s number variable.

We are working on improving transferring variables across files. As a workaround, either recreate the variables in the destination file, or duplicate the original file.

If the original file is published to team libraries, copied and pasted variables will work as expected.

If you receive a notification that pasting unpublished variables across files won’t create new local variables yet, try publishing the source library and and enabling it in the destination file.

Hey everyone,

To give you an update, with the launch of some new Figma Prototyping updates, you can now copy and paste local variables: when copy and pasting an element with a local variable bound to it, Figma will create a collection with the new, copied variable so it can be used freely in the new file. You can learn in our Help Center article here. Hope this helps!

Hey @Celine_Figma nice that this feature is launched.

I am however wondering if it is possible to move variables from one library to another one.

Like you are able to move already published components to another library by cutting them out and pasting them in the new file. After publishing them inside the new file, all linked instances will remember their master and know it‘s been moved. Therefore no link will break.

I basically want to do the same thing with variables.

Will this be possible anytime soon-ish?

Hey Oliver, thanks for your feedback! To be transparent, it’s not on our immediate roadmap at the moment but, it’s definitely on our radar for improvement.

I’m happy to pass your feedback to the team to give them visibility, though I can’t guarantee an ETA for any improvements. Thank you!

Thanks for the update. Good to hear

You can add the variables to a library, then when you import the library the variables are also copied. I did this test just now and it worked well, including actualizations.

Thanks for your input @Luana_Sousa.

I am however thinking of the following issue.

A company creates a library including a lot of components, now Figma has a new feature and they create a lot of variables in the same file. Now they are scaling and even merging with another business unit and see the need for a foundation level and a dedicated token/variables library and even another variables library to add a semantic layer.

As it turns out, their current variables (that are heavily used already in their files) shall be moved to the foundations layer and the dedicated library, WITHOUT UNLINKING all the variables that are used in the tons of other files.

What could they do?

Oliver and i are barking up the same tree.

I desperately need to lift out an entire product’s components and variable information and move them to a dedicated library file while keeping everything linked. Obviously the components are easy with the tools given, and i can even copy variables over and re-link them pretty well to said components using some of the aforementioned plugins…

HOWEVER, all other variables break link (turn grey in the inspector) with any of these methods and i really feel stuck with no way forward short of manually combing through hundreds of frames and manually re-linking variables in non-component designs.

We very much need this as well. We have a bunch of variables in a library and want to split off a specific group of them to be in a different library as they are really used by different groups of people. Having them all together is causing complications but I haven’t found a good way to move them without breaking where they are in use already.

The issue at hand has not been solved. This thread shouldn’t be marked as “LAUNCHED”.

There has been a way to cut and paste (effectively, move) styles and components for a while… Now variables are a step back from this 😞

This has not been resolved. Copying and pasting elements does not also copy and paste local variables applied to the element from one file to another. @Celine_Figma This issue is becoming a big problem for our company to maintain and consolidate multiple files who use variables from multiple published libraries.

We need the ability to move local variables that have been published in Figma File A to Figma File B without any files who link to those variables to be de-linked or require any manual updating. At this time, there is NO WAY to move variables from one file to another.

Hi, new to the forum. Just seen this post and I’m having a very similar problem. I want to drag or copy and paste my variables from one collection to another. Anyone figured that out yet?

not solved but there is lip service being paid to knowing it’s an issue at least ¯_(ツ)_/¯

Just adding my support here. The ability to move variables in the same way as components and not break links is super helpful when it comes to maintaining a growing design system. Hope we can get this feature on the roadmap!

I’m unable to copy a text layer and keep the variables linked up?

Just wanna push this topic. Copy & paste of variables from one file to another would be great!

Having to rely on broken or paid plugins for such a feature is ridiculous after 1 year and going out of beta (when variables are still in alpha state)

Same applies to collections.

And if you do it, do it right. Make Figma track the vars/collections and offer to move them to a new file when you publish (like for styles and components).

It’s Figma. It will take them 5 years.

Can’t believe that there is no way to transfer variables between files. Components could be transferred, so do variables. This feature should be the very first thing to consider when the “variables” feature was discuss.

Every single source of truth should be able to transferred between files. Since the memory management problem of Figma file is a disaster.

¯_(ツ)_/¯

Thanks for your feedback. We hear you. I will share this with our internal team.

As of today, this is not always true. I just copied and pasted components associated with local variables and they were not added - unless I’ve somehow missed a special command to do that with. 😢

Hey Oliver, and others in the community! Thanks everyone for your feedback.

As you mentioned another feature request (to be able to move variables from one library to another one) I’ve gone ahead and switched this topic as a feature request and edit the title, so everyone can vote up for this idea.

(For visibility, our team is aware of this feature request, it’s in our radar though I can’t guarantee an ETA for any improvements.) Thank you!

Yes but this doesnt allow copying between collections or files

Hi,

My team is currently working on the design system for the entire organisation (consisting of several product teams working on different digital products). We have created primitive and semantic colour tokens in the local variables of our main Design system file. The rest of the organisation has no access to the local variables except the semantic colour tokens on the right panel when designing.

Some product teams require different themes in their products, while some do not. May I ask if there’s a way for product teams to have the variables which are in the main Design System file in their own local libraries as well?

Not just a copy and paste but the same set of local variables which are linked to the main Design System file, able to receive updates from the main file should there be any changes.

Thank you!