Skip to main content
konst
February 1, 2021

"On Scroll" for prototyping

  • February 1, 2021
  • 361 replies
  • 78978 views
  1. I want to make a prototype where something changes when user scrolls content.

  2. I want to keyboard collapse when user starts scrolling content, but it’s impossible to do with drag action. Or it feels unnatural

  3. Or am I missing a way to do it with existing tools?

361 replies

taibaaslam
New Member
September 19, 2025

Figma’s prototyping is strong, but it still lacks on-scroll triggers—a core interaction for modern websites and apps. Scroll-based effects like fade-ins, sticky headers, and parallax are now standard in digital design, and not having them makes prototypes feel incomplete.

This gap is even more critical now that Figma Sites exist. If we want to design and deploy sites directly in Figma, we shouldn’t be limited in how we represent real-world interactions. Without on-scroll triggers, many designers are forced to rely on workarounds or move to other tools, breaking the workflow.

Adding native on-scroll triggers would allow more realistic prototypes, stronger collaboration with developers, and truly end-to-end design within Figma.

ChiSenires
Active Member
November 21, 2025

Just adding a +1 for on scroll triggers as I’m working on a prototype that needs this experience to exist so we could simulate some behavior for an element.

Chi
VirginiaPP
New Member
December 2, 2025

WE NEED ‘ON SCROLL’ TRIGGER PLEASE PLEASE PLEASE

j2j2j2
New Member
December 9, 2025

I need this feature. pleaseeee  🙏🏻

Mark Garcia
New Member
December 10, 2025

let’s not let this thread die down. please include this basic feature instead of ‘upgrading’ any AI or UI related stuff. 🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏

Shree Ransubhe
New Member
December 11, 2025

+1 for feature demand. 

Leo4411
New Member
December 11, 2025

Figma doesn’t support real “On Scroll” triggers yet, so the keyboard can’t auto-collapse when the user scrolls. Drag workarounds exist, but they feel unnatural because they don’t react to actual scrolling.
We’ll need to wait for native scroll-based interactions similar to how people wait for better tools like bug identification features.

Antoine Ghioni
New Member
June 3, 2026

Honest question: why on earth are they refusing to add this? surely there must be a specific reason because they must be aware that it’s very missing and asked a lot??!

antoineghioni.com
Armin_Rouhanian
Active Member
June 3, 2026

Honest question: why on earth are they refusing to add this? surely there must be a specific reason because they must be aware that it’s very missing and asked a lot??!

Hey there, I believe that current updates on Figma make & Figma AI stopped them implementing this one. prototyping might be useless if you can directly have a working code (yet not clean enough to be deployed in production) that you can test all of this. why should we set all prototype triggers one by one by ourselves?

I voted for this feature myself long ago. But today, I think there might be better options sooner than we expect.

Armin The Riverman
Antoine Ghioni
New Member
June 5, 2026

Honest question: why on earth are they refusing to add this? surely there must be a specific reason because they must be aware that it’s very missing and asked a lot??!

Hey there, I believe that current updates on Figma make & Figma AI stopped them implementing this one. prototyping might be useless if you can directly have a working code (yet not clean enough to be deployed in production) that you can test all of this. why should we set all prototype triggers one by one by ourselves?

I voted for this feature myself long ago. But today, I think there might be better options sooner than we expect.


Yeah, that totally makes sense. Bit of a hot topic, especially for me as both a senior art director and graphic design teacher who is very much against any gen AI related tools. So I hope Figma don’t end up going that route like you described because I still consider the intrinsic value in doing everything yourself, manually (which is and should be the point of what we do), especially in the formative years of younger designers and students where understanding what they do, how they do it and why they do it is a must.

But I’m not naive either and I realize that there’s very little chance they end up implementing such feature, no matter how much it’s been requested and expected, in this day and age of having everything going through the “AI lens”.

antoineghioni.com