# Images are not publishing

**URL:** <https://forums.realmacsoftware.com/t/images-are-not-publishing/51535>\
**Category:** Elements\
**Created:** [October 5, 2025, 1:57pm UTC](https://forums.realmacsoftware.com/t/images-are-not-publishing/51535 "2025-10-05T13:57:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeeep](https://avatars.discourse-cdn.com/v4/letter/j/b5ac83/32.png) [@jeeep](https://forums.realmacsoftware.com/u/jeeep)\
**Post date:** [October 5, 2025, 1:57pm UTC](https://forums.realmacsoftware.com/t/images-are-not-publishing/51535/1 "2025-10-05T13:57:14Z")

</div>

RapidWeaver Elements 1.3.5 (23877)

I have RapidWeaver Elements version 1.3.4. (23877) and after creating a new page, some images are not published. After Re-publishing All Files, images that were previously published disappeared. After investigating, I found that images that have Sizing - Custom set are not published. I have File Size set to 400.

---

<div class="post-metadata">

**Author:** ![Pegasus](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/pegasus/32/25035_2.png) [@Pegasus](https://forums.realmacsoftware.com/u/Pegasus)\
**Post date:** [October 5, 2025, 2:38pm UTC](https://forums.realmacsoftware.com/t/images-are-not-publishing/51535/2 "2025-10-05T14:38:40Z")

</div>

hey,

take a look in this thread:

> [@Image Component Sizing Issue](https://forums.realmacsoftware.com/t/image-component-sizing-issue/51166):
>
> @Dan I think I’ve found a new bug in the image component. When I set the “sizing” in the image component to custom, the images are no longer displayed — both in the preview and after publishing. See screenshots. This must have been introduced in one of the recent updates, since it worked before. I noticed this issue across several of my projects and had to set all “sizing” options back to original.

> [@Image Component Sizing Issue](https://forums.realmacsoftware.com/t/image-component-sizing-issue/51166/4):
>
> Ah yeah, resizing is not going to work on .webp (as we don’t support it, yet), that’s the issue!
