I can't modify a component's instance the way I'd like to

Hey hey ​@Carmelo_ 👋 Thanks for including the video. That makes this easier to dig into.

One thing worth checking first: in the Layers panel, do the wick and body inside your candlestick component each show a diamond icon (meaning they're their own separate components nested inside the candlestick), or are they plain rectangles/lines sitting directly in it? (a not zoomed-in screenshot showing your expanded left hand toolbar is helpful)

If they're nested components, that would explain what you're seeing — instances can only override certain properties, and size/structure changes can't be pushed onto a component that's nested inside another component. You'd need to make those edits on the main sub-component instead of the outer instance. More detail here: Swap components and instances.

If they're plain layers already, let us know and we'll look at the auto layout/sizing setup on the main component instead. Either way, happy to help! — Jaycee

No, the wicks and body of the candlestick component does not show any diamond icon in the layers panel. ​@Jaycee Lewis 

Hi ​@Carmelo_ 👋 Thanks for the additional screenshots. This is the expected Figma behavior, not a bug.

Instances only support overriding a specific set of properties — text, fill/stroke, effects, layout guides, nested instance swaps, export settings, and layer name. Resizing or repositioning a shape layer (like your candle's body or wick) isn't on that list, so those fields stay locked on instances even though they're fully editable on the main component. More here: Apply changes to instances — Supported properties.

If every candle needs an independently different body/wick size, components + instances aren't the right tool for that — plain grouped shapes (not linked as instances) will give you more flexibility. 

Resources: Groups versus frames (adjacent to your request but useful)

I hope this helps. I missed something or you still have questions, please let me know! — Jaycee

Thank you so much, ​@Jaycee Lewis, for clarifying this for me.

The problem is that my Figma project is choppy and freezes very often.

I discussed this with another Figma expert, and he told me that the main reason for this bug/freeze is that the deck is built from a large number of separate assets, with each candlestick added as its own asset across many slides.

That’s the most likely reason it feels slow: performance here depends less on memory but more on how many individual objects and images the file has to load and render at once, which is why memory usage might appear low even though the file is still struggling.

The more unique assets there are, the more work it takes to open and navigate the deck.

That’s why he advised me to turn the candlestick into a single reusable component, then place instances of it on each slide instead of using separate assets. Because every instance points back to a single component, the file has far less to load and render, and it makes editing easier as well.

I’m currently using plain grouped shapes (not linked as instances), but this causes my project to lag and freeze because there are many slides and many candles.

I’ve attached a video of the bug/freeze to this post.

I’d love to hear from you if you have a solution to suggest! :)

Hey ​@Carmelo_ 👋 I created a support ticket t get the freezing/lagging issue looked at. The ID is 2058494 and the subject line is File freezing and lag with many grouped shapes across slides. Please check your email inbox (and spam folder) for the support email. there are a few requests there that support will need so they can take a look at your file. Thanks for all the details so far. — Jaycee