Skip to main content
Question

File Memory and Preferred Values instance swapping

  • February 21, 2025
  • 2 replies
  • 36 views

Tom deBruyn

TL;DR I want to know if anyone has explored using “Preferred Values” instance swapping as opposed to large Component Sets as a way to improve memory performance in both the Library and downstream project Figma Files.

I have a Library file with very complex components for charts in the UI. The components allow other designers to deeply configure a chart, and every aspect has nested variants for controls to be used in downstream project files. 

Each chart has many nested instances for controlling aspects such as the axis labels, number of columns and rows, the marks, count of series to be presented, and the legend, and the state of the data.

A single nested instance could contain hundreds of variants, as many as 5 tiers deep.  For example, a Trend Line instance can be configured with Variants for line style, which series it is, how many columns are in the data field, and the type of data.

This instance is set within a chart with other sibling instances, and higher tier interaction patterns beyond the base chart configuration.


These components are powerful design tools, but they consume huge amounts of file memory.  I’ve seen conversations about boolean properties vs. variants for memory but no one has mentioned preferred values instance swapping as another method.. 

Would using preferred values for configuration options use less memory than having nested instances that are part of huge component sets?  My thinking is that since “Each instance pulls all variants into the file memory for offline editing,” breaking a component set into smaller component sets and grouping them in a collection of “Preferred Values” might help the file perform better, at the sacrifice of some offline mode restrictions.

Wirkkarl
  • New Participant
  • May 14, 2025
Tom deBruyn wrote:

TL;DR I want to know if anyone has explored using “Preferred Values” instance swapping as opposed to large Component Sets as a way to improve memory performance in both the Library and downstream project Figma Files.

I have a Library file with very complex components for charts in the UI. The components allow other designers to deeply configure a chart, and every aspect has nested variants for controls to be used in downstream project files. 

Each chart has many nested instances for controlling aspects such as the axis labels, number of columns and rows, the marks, count of series to be presented, and the legend, and the state of the data.

A single nested instance could contain hundreds of variants, as many as 5 tiers deep.  For example, a Trend Line instance can be configured with Variants for line style, which series it is, how many columns are in the data field, and the type of data.

This instance is set within a chart with other sibling instances, and higher tier interaction patterns beyond the base chart configuration.


These components are powerful design tools, but they consume huge amounts of file memory.  I’ve seen conversations about boolean properties vs. variants for memory but no one has mentioned preferred values instance swapping as another method.. 

Would using preferred values for configuration options use less memory than having nested instances that are part of huge component sets?  My thinking is that since “Each instance pulls all variants into the file memory for offline editing,” breaking a component set into smaller component sets and grouping them in a collection of “Preferred Values” might help the file perform better, at the sacrifice of some offline mode restrictions.

It sounds like you're working with very complex Figma components that could definitely benefit from performance optimizations, especially with nested variants that can get heavy. Using "Preferred Values" instance swapping could be a smart move to reduce memory usage, as it allows for more efficient management of those nested components. Similar to how Phonexa optimizes business workflows, streamlining complex systems is key to improving efficiency. In the case of Figma, reducing the number of deep nested instances and swapping out for preferred values could help make your designs more memory-efficient, just as Phonexa's tools help businesses optimize customer interactions and data management for better performance.


Wirkkarl
  • New Participant
  • June 10, 2025
Tom deBruyn wrote:

TL;DR I want to know if anyone has explored using “Preferred Values” instance swapping as opposed to large Component Sets as a way to improve memory performance in both the Library and downstream project Figma Files.

I have a Library file with very complex components for charts in the UI. The components allow other designers to deeply configure a chart, and every aspect has nested variants for controls to be used in downstream project files. 

Each chart has many nested instances for controlling aspects such as the axis labels, number of columns and rows, the marks, count of series to be presented, and the legend, and the state of the data.

A single nested instance could contain hundreds of variants, as many as 5 tiers deep.  For example, a Trend Line instance can be configured with Variants for line style, which series it is, how many columns are in the data field, and the type of data.

This instance is set within a chart with other sibling instances, and higher tier interaction patterns beyond the base chart configuration.


These components are powerful design tools, but they consume huge amounts of file memory.  I’ve seen conversations about boolean properties vs. variants for memory but no one has mentioned preferred values instance swapping as another method.. 

Would using preferred values for configuration options use less memory than having nested instances that are part of huge component sets?  My thinking is that since “Each instance pulls all variants into the file memory for offline editing,” breaking a component set into smaller component sets and grouping them in a collection of “Preferred Values” might help the file perform better, at the sacrifice of some offline mode restrictions.

Hi everyone,

I’m exploring ways to improve memory performance in both Library and downstream Figma files. I have a complex Library file with deeply nested chart components, each with hundreds of variants up to 5 tiers deep. These nested instances control many aspects like axis labels, number of columns, legend, data states, etc.

These powerful components consume a lot of file memory. I’ve read discussions about boolean properties vs. variants, but haven’t seen much about using Preferred Values instance swapping as a strategy.

Would using preferred values for configuration options reduce memory usage compared to large nested instances in big component sets? My thought is that since each instance loads all variants into file memory for offline editing, breaking large component sets into smaller sets grouped by preferred values could improve performance—though it might limit some offline capabilities.

Has anyone tried this approach or have insights to share?

Thanks!
 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings