Skip to main content
Equinusocio
Jun 22, 2023 8:10 AM UTC

Add way to change opacity for color variables alias, fills, strokes, etc

When aliasing a color variable to another (img 1), or using it directly on an element (img 2), we should be able to override the opacity without the need to create a variable for each transparency variation:

Cant override opacity in the alias:

CleanShot 2023-06-22 at 10.09.00

Example 2

Cant override the fill opacity:

159 replies

Spela_Bricman
New Member
Jul 8, 2026 12:40 PM UTC

+1 we need this as well

recepkutuk
New Participant
Jul 29, 2026 1:03 AM UTC

I just noticed that it’s “technically” possible. It’s of no use to us at the moment but still possible. Here’s how to reproduce:

  1. Assign a color variable to an element.

     

  2. Add glass effect. Then you will notice the color variable has opacity of 20% now.

     

  3. Remove the glass effect. Color variable still has opacity.

     

djv
Figmate
Community Support
Aug 13, 2026 9:45 PM UTC

Hey All, thanks for your patience here and for keeping this thread going! 
 

To be transparent about where this stands, this request has been passed to the Variables team, and it's come up through multiple channels beyond this thread. While the team has been clear internally that they think this should exist,the holdup has been engineering capacity and some real design questions about how an alpha-modified alias should behave consistently across the product and translate cleanly to code, which is what @jjcm was digging into earlier in this thread.
 

I don’t have an exact timeline to share, but what I can tell you is that it's actively being worked on rather than parked. I'll come back to this thread with an update when there's something concrete to share. In the meantime, thanks to @Variables Plus and @Ebuka.I for sharing plugin approaches, and to everyone who's documented their token setups here that detail is genuinely what gets used when the team scopes this!

Tiziano
Active Member
Aug 30, 2026 10:03 AM UTC

Found this: so it is implemented then?

 

 

Kerry_Johnson
Active Member
Aug 31, 2026 6:14 PM UTC

Found this: so it is implemented then?

 

 

Hmm mine doesn’t show that, maybe you got selected for testing!

Kerry_Johnson
Active Member
Aug 31, 2026 8:45 PM UTC

I see it now, too!

Kerry_Johnson
Active Member
Sep 1, 2026 1:51 PM UTC

Nice work!  It, however, doesn’t seem to take into account appearance?  I know I can probably just freely type this into the opacity segment today but I didn’t want to change that just yet as the codified components rely on that opacity token currently.


Root:

 


Ext. collection:​​



Notice it’s “blind” to any branding until unlinking.  It also works if I set brand appearance directly onto the component, but removing it again (Cmd + Z) returns it to the broken state.

 

 

Edit: It fixed itself after flipping through branding color appearances in an ancestor layer to “refresh” the stale value I guess.  Leaving this here anyway in case it’s isolated to this new feature.
 

recepkutuk
New Participant
Sep 4, 2026 12:37 PM UTC

Thanks for the update but with all due respect, I don’t think this solution is the right approach. It’s definitely a step forward but we still need it in the properties panel. Please don’t call it a day and mark this topic “solved”. I’m prepared to die defending this hill.

 

Maria Rita Fiannacca
New Member
Oct 21, 2026 10:02 AM UTC

I still can’t find a straightforward solution to this.
Even simpler tools like Adobe XD were able to achieve opacity without breaking the link to colour assets.