Skip to main content
NeoLym
NeoLym
New Member
September 10, 2026
Question

Library publish does not propagate image assets referenced by overrides on nested instances

Hi,

Images inside a published library component fail to load in consuming files. We have narrowed down a consistent reproduction.

Steps to reproduce:
1. In a library file, create component A with an image fill applied directly to its own layer. Publish it. This works correctly everywhere.
2. Create an instance of A and replace the image in its slot (an image fill override on the instance).
3. Wrap that instance together with other layers into component B, and publish B as part of the same library.
4. In any consuming file, including a brand-new one, insert component B.

Result: the slot image does not load, and we get "An invalid image or thumbnail was removed."

Key observation: component A on its own always renders correctly, in every file. Only images that are referenced through an override on a nested instance fail to appear in consuming files. This suggests that assets living on a component's own layers are collected at publish time, while assets referenced only by an override on a nested instance are not.

Additional observation: repeatedly re-publishing the library restores images for some components while others remain broken, and the recovering subset differs each time. This indicates the image data does exist server-side and that propagation is partial and unreliable rather than absent.

Already tried, with no effect:
- Restarting the desktop app, and opening in a browser instead
- Replacing the images with freshly uploaded files from disk (new assets, not reused references)
- Duplicating the library file and publishing the duplicate
- Resetting instance overrides, swapping instances, re-inserting instances from the Assets panel 

We are unable to share the affected production file, but we can provide a minimal reproduction file built with placeholder images if that helps.

Question:
-Are image assets referenced by overrides on nested instances expected to propagate on library publish? If yes, this is a defect and we would like it filed.

This blocks our promotion template workflow, where slot-based image replacement is used on every campaign, so any guidance on a supported pattern would be appreciated. Thanks,

3 replies

Jaycee Lewis
Figmate
Jaycee Lewis
Figmate
September 10, 2026

Hey ​@NeoLym 👋 Thanks for taking the time to provide a detailed writeup. I have a few questions to help us troubleshoot things:

  • When you select the placeholder in the main component, does a slot property show up in the Properties section of the right sidebar?
  • After you replace the image in an instance, does the slot property show a [Modified] tag?
  • Is the image a fill on the slot layer itself, or on a layer placed inside the slot?

Thanks for the additional details! — Jaycee

NeoLym
NeoLymAuthor
New Member
September 11, 2026

Hi Jaycee, thanks for looking into this. Answers below.

1. Yes. When I select the placeholder in the main component, the slot property does appear in the Properties section of the right sidebar.

2. Yes. After replacing the image on the instance, the slot property shows the [Modified] tag.

3. To be precise, the image is not a fill applied to the slot layer itself, and it is not a fill applied to a layer that already exists in the main component. On the instance, I insert a new image layer into the slot and delete the layer that was originally there. So the slot content is replaced at the layer level, and the image belongs to a layer that exists only as part of the slot override.

That instance is then wrapped into another component, which is what gets published. If layers introduced purely through a slot override are not collected as part of the published component's assets, that would explain why the image reference arrives in consuming files without the image data.

Thanks!

Jaycee Lewis
Figmate
Jaycee Lewis
Figmate
September 11, 2026

Hey ​@NeoLym 🤩 Thanks for all your help so far. I opened a support ticket for this. The ID is 2126658 and the email subject line is Library publish — slot-based image overrides intermittently missing in consuming files. I added a few requests there to help support with your case. Please keep an eye on your email (and spam folder if necessary) for the email and any replies from our team. — Jaycee

    Terms & ConditionsAccessibility statement