Webflow interactions not working on the published site
When Webflow interactions work in preview but not live, a script error from custom code is often stopping Webflow’s interactions runtime, or the trigger never fires on that device, such as a hover trigger on a phone. The risky part is that elements with an initial state of hidden or opacity 0 stay invisible when that happens. Check the live Console for errors, confirm which breakpoints each interaction runs on, and give important content a visible fallback.
What you'll see
Animations play in the Designer preview but nothing moves on the published site, or sections stay blank on phones. Scroll animations get stuck halfway, and text or images that should fade in never appear, leaving gaps visitors read as missing content.
Why it happens
1. The trigger never fires on that device
Hover triggers have no real equivalent on touch screens, and scroll triggers depend on layout that changes at smaller breakpoints. If the element starts hidden, it stays hidden when its trigger does not happen.
2. Custom code stops the runtime
An error in custom code in Site settings, Page settings or an Embed can stop Webflow’s interactions script, along with any GSAP-based effects that rely on it.
3. The interaction is limited to certain breakpoints
Interactions can be set to run only on some devices. An animation turned off for phones leaves the element in whatever state it started in.
4. Reduced motion settings
Visitors who turn on “reduce motion” in their operating system may get different behaviour if the site respects that preference, which can look like a bug if content depends on movement to appear.
How to fix it
- Publish, open the live site, and check DevTools > Console for errors. Temporarily remove custom code embeds that throw errors and republish to see whether interactions return.
- Select the animated element, open the Interactions panel and check the trigger settings to see which breakpoints the interaction runs on.
- Replace hover triggers with click or scroll-into-view triggers at Tablet and below.
- Avoid starting important text or images at opacity 0 or display none; if you must, make sure the trigger is reliable on every device or set a visible state for smaller breakpoints.
- For scroll animations that stick, check the trigger offsets at each breakpoint, since shorter or taller sections change where the animation starts.
- Test on a real iPhone and Android phone, scrolling at normal speed.
How to check it's fixed
- Scroll through each page on a phone and confirm all content becomes visible with no blank sections.
- Reload with the console open and confirm no errors appear.
- Turn on Reduce Motion in the phone’s accessibility settings and scroll again; every section should still be readable, even if nothing animates.
What a QAlaunch scan shows for this
- Phone and desktop screenshots where the visual review can spot blank sections or content that never appeared.
- Console errors from custom code that stop interactions.
- Layout shift while the page loads and animates.
- The scan can tell that content is missing from a screenshot, but it cannot judge whether an animation looks the way you designed it.
See exactly what a full report contains in the sample report.
Frequently asked questions
Why do interactions work in the Designer but not live?
The Designer preview does not run custom code, while the live site does. An error there can stop the interactions script on the published page only.
Do hover interactions work on phones?
Not reliably. Touch screens do not hover; iOS and Android may fire a hover effect on the first tap and then a click on the second, which feels broken. Use click or scroll triggers on tablet and phone breakpoints instead.
Is content hidden by interactions bad for SEO?
Search engines can usually read text in the page even when it starts hidden. The bigger risk is people seeing an empty section and leaving, so give important content a visible fallback.
Rather have a QA engineer test it by hand?
If this is a site you're launching or handing to a client, I'll go through it by hand, including the Webflow-specific issues a scan can't reach, like logged-in flows.
- Up to 10 key pages tested by hand, not a scan
- Every flow a customer uses: forms, sign-up, checkout, booking
- Real mobile and desktop browsers
- A written report in plain language, with screenshots
- A 15-minute call to walk you through it
- 10 years of professional QA experience
Tell me about your site and I'll reply personally, usually the same day.
No payment now. I'll confirm scope and price first.
Related fixes
More for Webflow: all Webflow fixes
Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.
Sources: Webflow community: GSAP scroll interaction not working live · Webflow Help: intro to interactions