Issues with Image Rotation in Component 349 When Exporting from Relume to Webflow

Raj · 2026-04-23T06:46:46.364Z

Hi everyone, I’m trying to use Component 349 and export the project to Webflow. It has four image-and-text sections where, as you scroll through the text, the image stays fixed and fades into the next one. It previews correctly in Relume, but once exported to Webflow, it only shows the fourth image. The images do not rotate as intended, it just stays stuck on the last one. Has anyone run into this before or know how to fix it? Attached video, thanks so much: https://www.relume.io/components/layout-349

10 comments

· Sorted by Oldest

Malka G.
·
·
Check in the preview not in the designer.
Matt J.
·
·
Raj Would you mind sending a read-only/sandbox link?
Matt J.
·
·
Raj just as an FYI - the component works fine for me in the webflow designer freshly dropped in - so its definitely something within your project. 99% of the time, the issue is that a parent div has overflow hidden applied. So I can help find that pretty quickly once I have a Webflow sandbox link. Here's how to provide the correct link: https://www.relume.io/resources/faqs/how-to-share-your-figma-webflow-projects-for-effective-support
Raj
·
·
Hey thank you so much for looking into this, here is the sandbox link: https://preview.webflow.com/preview/rajs-radical-site-6b3e91?utm_medium=preview_link&u[…]1&preview=ebca79fc42dcf9b0ee72e0c2067439a1&workflow=preview
Matt J.
·
·
Raj ah so the other reason this one breaks is that when you use the Relume Site Builder to position the images into this component, and then import into Webflow, it rewrites the classes which breaks the interaction.
Matt J.
·
·
so if you look at the first image element - that's what the class should be, and you'll see that it has a combo class of is-image1 - you'll want 3 more like that - is-image2 etc. And you'll have to reconnect the interactions. In this case, its probably a lot quicker to just drop in a fresh version of this component instead and then place the images again and then everything will work but I just wanted to explain why it broke.
Matt J.
·
·
Its something that I have brought up to the engineers - they intentionally did this - without realizing this ramification. The solution is definitely not an easy one, so its likely not to get fixed for awhile.
Raj
·
·
Thanks Matt, I'll try it right now to see if it works. So I'll just remove the "contain" and positioning and have it set to whatever the default component was. Thanks for looking into this, will give it a try now and let you know shortly.
Raj
·
·
Hey Matt, it seems to be working. Thank you so much for your help, I was stuck on this for a few hours yesterday. Have a great day!
Matt J.
·
·
Raj awesome! No worries

Malka G.
·
·
Check in the preview not in the designer.
Matt J.
·
·
Raj Would you mind sending a read-only/sandbox link?
Matt J.
·
·
Raj just as an FYI - the component works fine for me in the webflow designer freshly dropped in - so its definitely something within your project. 99% of the time, the issue is that a parent div has overflow hidden applied. So I can help find that pretty quickly once I have a Webflow sandbox link. Here's how to provide the correct link: https://www.relume.io/resources/faqs/how-to-share-your-figma-webflow-projects-for-effective-support
Raj
·
·
Hey thank you so much for looking into this, here is the sandbox link: https://preview.webflow.com/preview/rajs-radical-site-6b3e91?utm_medium=preview_link&u[…]1&preview=ebca79fc42dcf9b0ee72e0c2067439a1&workflow=preview
Matt J.
·
·
Raj ah so the other reason this one breaks is that when you use the Relume Site Builder to position the images into this component, and then import into Webflow, it rewrites the classes which breaks the interaction.
Matt J.
·
·
so if you look at the first image element - that's what the class should be, and you'll see that it has a combo class of is-image1 - you'll want 3 more like that - is-image2 etc. And you'll have to reconnect the interactions. In this case, its probably a lot quicker to just drop in a fresh version of this component instead and then place the images again and then everything will work but I just wanted to explain why it broke.
Matt J.
·
·
Its something that I have brought up to the engineers - they intentionally did this - without realizing this ramification. The solution is definitely not an easy one, so its likely not to get fixed for awhile.
Raj
·
·
Thanks Matt, I'll try it right now to see if it works. So I'll just remove the "contain" and positioning and have it set to whatever the default component was. Thanks for looking into this, will give it a try now and let you know shortly.
Raj
·
·
Hey Matt, it seems to be working. Thank you so much for your help, I was stuck on this for a few hours yesterday. Have a great day!
Matt J.
·
·
Raj awesome! No worries