Skip to main content
Question

Component Layers Being Removed by Figma?

  • July 29, 2026
  • 1 reply
  • 18 views

ipotter-smith Relias

I have a component (Select Field) that is appearing correctly in the library, however when designers at my org bring it over into their files via the asset panel, it shows up without the actual field- just the title and supporting text. When inspecting the layers, the field layers are not present in the component.

Beyond that, when a user pastes in the component directly from the library file, Figma prompts them with an update that incorrectly removes the layers again.

Does anyone know what is happening? I have never seen this one before and have no idea how to go about fixing it.

1 reply

Tom Reem
Figmate
  • Figmate
  • July 29, 2026

Hey ​@ipotter-smith Relias — welcome to Figma Forum, and thanks for calling this out. Happy to help dig into this.

To narrow it down and try to reproduce it on my end, a few questions:

  • How are your designers bringing the Select Field component in (e.g. dragging from the Assets panel, or copy/pasting from the library file)? Does one method behave differently from the other?
  • When you publish an update to the component from the library file, do the layers come through correctly in the consuming file?
  • Is this happening in the Figma Desktop App, the browser, or both? If the app, can you and your team confirm you're on the latest version (126.7.10 or later)?
  • Is there any additional error/notification associated with the update prompt you're seeing before the layers are removed?

While you're gathering that, here are couple of things are worth trying, since this does sound similar to some other reports I’ve seen:

  1. If you’re up for it — in the library file, make a small change to the Select Field and its nested components, then publish. In the affected file, open the library updates modal (the book icon) and accept updates — and let it finish fully before closing the file. For more on this, have a look here: Review and accept library updates.
  2. If accepting the update still strips the layers, the instance in that file is likely the problem rather than the library. Try deleting the existing instances, reloading the file, then inserting a fresh copy from the Assets panel. For steps on this, check out this article: Create and insert component instances.

If it's still happening after that or, if you’d like to have a team member take a deeper dive, the fastest path is for us to look directly at a file where it's occurring. Keep me posted on how it’s going and I can open a ticket to share the file securely.