[Config 2025] Figma Sites is here — let’s hear what you think! 💻

So Figma Designs previously exported to Webflow to make it a seamless process from autolayout in Figma to then full design and animation in Webflow. Is that integration going away? Or will Figma Sites allow export to Webflow still but make that faster? Where do all the integrations play with Sites vs Design, seems weird to have it as a separate ecosystem? I want to play with Sites, but based on all of this forum info, seems like a waste of time until Google fonts, spacing and accessibility is rolled out properly? 

I love the new sites feature but not having the ability to create any dropdowns, popups and overlays is whats really stopping me from using it.. workarounds don’t work well or easy and for now the prototying feature works better. I’d love to see this come into sites as creating live demos of feature before deveopment would be game changing!

Thanks to everyone for sharing feedback and questions about Figma Sites — a few clear themes have emerged, and I want to highlight and reflect on them here. Some of these echo earlier patterns, and others dig deeper. We don’t have timelines to share yet, but your input is already helping inform what we prioritize next.

With that, here’s what I’m seeing come up from the folks in the forum here:

1. There is a need for more accessibility features. We currently support accessibility tagging in the design panel and are continuing to make improvements so that websites are optimized for screenreaders. Learn more about how you can make your Figma Site accessible.
    
2. Typography and font support matter deeply. Without consistency between the design file and the published site designers and engineers are running into friction they weren’t expecting. People want creative control and accuracy across breakpoints.
    
3. Component and variable behavior could be more consistent between Design and Sites. For people trying to reuse established design systems and patterns, this disconnect results in manual rework.
    
4. Responsive behavior and breakpoints would improve with more flexibility. Folks with custom grid settings or tightly controlled responsive layouts are running into conflicts, layout bugs, or unclear behavior when switching between views. Others noted that without true fluid/responsive behavior this version feels a bit rigid.
    
5. Embeds, video playback, and scroll behavior are areas for continued improvement. These little things add up quickly when building interactive pages.
    
6. Animations and transitions: powerful, but could be more scalable. One person put it perfectly: “Custom, but individual.” They want to scale design motion without reinventing it each time.

Thank you again for taking the time to reflect here. It helps us better understand what’s resonating, what’s missing, and how we can support your workflows.

I’m trying to recreate an effect I’ve prototyped in Figma Design and having no luck. To achieve it, I basically animate a mask in from the left, pause, then slide out to the right.

In Sites, I’ve tried adding a reveal interaction to the mask (also tried the layers inside the mask) having it slide in from the left, then slide out to the right. It never seems to actually animate and I either don’t see the text at all or I just see the text static. Is it not possible to use interactions on masks?
 

Is Figma Sites going to be available for Education plan? It would truly be a game changer!
 

It would be important for us to be able to make website links private. We want to be able to publish, but not have it open to just anyone.

Any news on Figma Sites going public with the suggested feedback ​@Tom Reem ?

I’m desperately waiting for these and CMS features to use in production 🙏🏻

Really enjoying playing with Figma Sites so far 🎉

Some things I’ve been struggling with:

1. This is a problem in Figma Design too, but I’d really love to be able to set a consistent link style (and behavior) across a file without needing to hack it together via a component. 
2. I’d like to have some containers using interesting shapes, not just rectangles, but add auto-layout automatically converts them into flat rectangles. (This one’s probably more of an edge case/specific need, so I understand if this is a long ways out, if ever.)

The rest have been covered in previous feedback roundups.

One last request: I’d love to publish my sites to the community! Any chance this will be coming soon?

I love it, but the whole thing is just a hot mess right now. Currently I’m investigating more than 10 issues that prevent me from creating a rather simple website. Not even mentioning some deeper, much more complex issue with how the whole thing is coded on the back.

I’ve found a few issues with Sites. I know its in Beta. However I find it odd that no one caught what I caught before release so perhaps its user error. I will lay out my issues below:-

Buttons - I pulled buttons from my design system into my new design in Sites. The buttons are setup with various states - default, hover, focussed etc. I then had the buttons link to another page on the site. This doesn’t work. The states work fine, however I have to spam the button multiple time to get it to take me to the referenced page.

This is also the case for the Nav bar I created as a component, though it does appear to work slightly better. One thing I did with this is to have the link on the nav bar take me to the correct page, on that page I set it as the ‘focussed’ state so that it was highlighted. This seems to work fine. However I cant find a way to have the button set up as ‘Scroll to’ but then highlight once the destination of the scroll is reached.

I then click features to scroll down:- 

This button for example:-

This is prototyped to take me to the @products’ page, but I have to spam it to get it to work. The first few clicks cycle through the states I gave it before it decides to go anywhere. It does work like this in Figma Design. They just seem to work. Do I need a different approach here?

I also have some other buttons for a carousel with a default state and one ‘pressed’ state. Once I made the carousel it wouldn’t work until I removed the ‘pressed’ interaction from the child component.

I hope someone can help.