Use inverse of Boolean variable to show/hide layer

This just force me to create unnecessary component versions.

I don’t understand such a basic thing isnot offered but we have an AI tool integrated to add images...

I just encountered this (after only a short while with the product).  Yes, Visibility of a layer should allow the specification of an expression.  So, ‘Item Selected’ variable can be referenced as ‘Item Selected’, ‘!(Item Selection)’, or any number of other more complex expressions.  Please add this functionality soon so that we don’t have to duplicate all booleans and define (and set) a negated value alongside every boolean.

+1

Please add this, it would save a lot of effort and reduce confusion from redundant variables.

+100

There is so much bloat and unnecessary complexity in both if/else logic and creating variants to achieve this.

A hack I use is to set a conditional instead of connection lines and then use true/false statements in there

It’s insane that it wasn’t designed like this to begin with.

This is how variables work and are used in programming languages, and by Figma’s own UI – e.g. I toggle the visibility button on a layer to false, I expect it to hide, and I expect the Figma UI to update the visibility icon to display the closed eye – having two variables for this state in web development would be absurd, and is just as absurd in a design context. 

I am learning Figma variables at the moment and this was my reaction when I saw how they are currently setup: 

It is very hard to defend the current design logic if I were to say to a designer I work with that ‘Figma is easy’.

I still have hope for this feature.

+1 to this. Conditional logic would clean up my components. The necessity for `isVisible` and `isHidden` vars doubles the lift for designers.

+1000 would be so useful

+1 

pretty please! 🙏

A simple use case for example on a product card:

I just want to use one boolean (e.g. IsSoldOut)
When it’s true, I want to hide the CTA, BUT show the “sold out message”. 

At this moment, the possible workorounds:

A) create ShowSoldOutMessage and HideCTA boolean (Not optimal, as it does not reflect the component real behavior - as both cannot be true or false at the same time)
B) create separate component which holds the CTA and sold out message (NOT optimal as 1) it creates maintenance overhead 2) in case layers are in different sections / containers - it just won’t work)

Thanks! :)

I really need this.
(Real example: I have a block that I would like to HIDE when a variable is set to TRUE. Currently it’s only possible to show an element when a variable is set to TRUE)

+1

+1

Bring it to reality!

+1!
 

1. Expressions MUST be available for usage as a variable value
2. Expressions SHOULD be available as element property value. Could be achieved with help of the first item.

+1 

Very important.

+1 

Also need this...

+1

Still need this as of 2026...

+1 Still need this. Being able to set a variable value to an expression would suffice.