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.

Hi again,

Regarding sites and particularly how frames work. I have a ‘products page’ with three options on it. I have made a component which is basically the three options and each reveals a different product on click. Each product image is a variant in the component set.

I set this up and can only then set each variant main frame as ‘Absolute’ which includes constraints. The child I dragged from the master into my actual web page is set as ‘Relative’ which is what I want, however when I press one of the options this then screws up the layout because its now gone to an ‘Absolute’ variant. Its so messy to work with the way its implemented right now, and I feel like I’m fighting with it.

My colleague suggested ‘simplifying’ the design however I disagreed and said the reason I wanted to implement the design (basically a carousel) was simplifying the design for the end user.

I don’t think we should have to wrestle with the design and layout options for standard design elements such as carousels when other available free software have such a low learning curve.

I’m happy to be corrected, but I don’t think its me doing anything wrong. Sites doesn’t function how you’d expect. I’m at the point where I will need to start the project again in a different system because I cant hand it over the way it is at the moment.

Also, look at this:-

Then when I preview or publish:-

Hi again,

Regarding sites and particularly how frames work. I have a ‘products page’ with three options on it. I have made a component which is basically the three options and each reveals a different product on click. Each product image is a variant in the component set.

I set this up and can only then set each variant main frame as ‘Absolute’ which includes constraints. The child I dragged from the master into my actual web page is set as ‘Relative’ which is what I want, however when I press one of the options this then screws up the layout because its now gone to an ‘Absolute’ variant. Its so messy to work with the way its implemented right now, and I feel like I’m fighting with it.

My colleague suggested ‘simplifying’ the design however I disagreed and said the reason I wanted to implement the design (basically a carousel) was simplifying the design for the end user.

I don’t think we should have to wrestle with the design and layout options for standard design elements such as carousels when other available free software have such a low learning curve.

I’m happy to be corrected, but I don’t think its me doing anything wrong. Sites doesn’t function how you’d expect. I’m at the point where I will need to start the project again in a different system because I cant hand it over the way it is at the moment.

Also, look at this:-

 

Then when I preview or publish:-

 

​
@Adam14  I think I have a solve for your absolute/relative issue. Add auto-layout to your component set frame (dashed purple line). You can then set the child elements to relative positioning. Similar to how in Figma Design, I’d do the same if I want to be able to have a component width/height set to fill.

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.

​@Adam14 Did you try adding two actions to the interaction? (e.g. Scroll to Features Section + Change to Focused/Active state).
 

Or, you could try variables and assigning them to instances. Then update the variable on click to change active/inactive states: https://help.figma.com/hc/en-us/articles/14506587589399-Use-variables-in-prototypes#h_01H91B3F52J1JADAAZ0WVH3SB6

​@Bryce_Driesenga  Thanks so much. Adding the auto layout to the component set worked a treat mate, cheers.

Also adding an additional action to the nav bar worked as well. Seems so obvious now haha, but thankyou. I do have tendency to overthink things sometimes.

​@Adam14 Glad to hear it! No worries at all, I had to think about it a bit before I realized, ha

I’ve been loving Figma Sites, but from someone who would love to eventually replace any additional tools to publish their own website, here are a few things I’d love to see:

• Breakpoints can be improved
  • Breakpoints, to me, are done initially upon website setup and applied to all subsequent pages. What’s been bothering me is that I have to go in and redefine the breakpoints per new page i’m creating. My workaround for this has been to create a ‘template’ page that has all the grids and breakpoints defined, then duplicating that to build out the new page.
  • I constantly test for responsiveness, and I would love for Figma to automatically add ‘min’ and ‘max’ widths to each breakpoint while doing so. For example:
    • Mobile breakpoint - 1-479 / Tablet breakpoint: 480-768
    • Unless my min/max widths are properly set, the breakpoint value is changed when I resize the tablet frame to test for responsiveness. So when I increase the size of my tablet frame to 768, mobile is increase to 1-767px. This makes sense if the frame itself is what defines the breakpoint values, but I think it could be handled better.
  • Text styles on the larger, primary breakpoint (typically desktop) default to the smallest breakpoint style (mobile), as opposed to the default text style it’s meant to fall-back to. For example:
    • I have a 64px heading defined in a text style, but I want to create a smaller version of this for mobile (1-479px). I’d create the breakpoint, override the size to 32px, then apply it to all the frames. On the desktop frame, instead of applying the 64px heading, it applies it as if it were a mobile breakpoint, making the heading 32px.
• Published sites are extremely laggy.
  •  I’ve gotten a couple of interactions applied to frames, but there isn’t anything on the page that should warrant the site to load at ~5fps. 
• Nested pages
• More interaction options, in general
• Adding percentages, viewport widths, and viewport heights as measurements would be extraordinary.
  • I currently use another ‘visual code’ website builder that supports this, and I find myself wanting that to be supported in Figma. Min/max widths can only go so far, especially if the only unit defined is pixels.

Overall, I’ve been loving Figma Sites, and considering this is the first launched iteration of the product I’m super excited to see how it improves overtime. Thanks for the consideration, and please let me know if there’s a more appropriate forum for me to raise these points!

Figma Sites – What We Heard and What’s Next
 

Thank you for sharing

Hi everyone! Thank you for joining the conversation and sharing your experiences with Figma Sites following our Config 2025 announcements. Your posts — from first impressions to deep technical insights — help us understand where Figma Sites is landing well and where we need to refine the experience.

We've read every reply in the thread and are sharing this summary with both our product and engineering teams to help shape what comes next.

What we heard

Here are the most common and impactful themes raised by the community here in Figma Forum:

1. Accessibility: Export Options & Integration Flexibility

A key request was the ability to export clean, semantic HTML/CSS or integrate Figma Sites with existing CMS tools. Many of you see Figma Sites as a powerful tool — if it can fit into their broader publishing and dev ecosystems.

“Are there plans to allow code export (HTML + CSS for publishing elsewhere, or to integrate into other CMS’s or existing codebases)? That would be the make-or-break feature for my use.” (2 likes)
 — Etienne_Despres

2. Accessibility: Structure, Interactions & Design

From nested pages to font fidelity, scroll-to-section behavior to video embeds, designers are eager to bring more interactivity and polish to Sites — especially when building client work or portfolios. Designers illustrated the importance of Figma being sensitive to the folks using this product and the opportunities to make it more accessible for all.

“Figma, at your scale, I would implore you to get this right and not ship products that will perpetuate continued creation of inaccessible digital products. Your average user may never notice these features, or how they could make things worse, not better, for accessibility. And even if they do notice them, some of them seem to actively make it more inaccessible.” (16 likes)
 — Emily Lawes

“Do y'all plan to get Figma Sites to the point where it can produce semantic HTML and provide a way to provide accessible names to icon buttons and images? ...]  I hope that as you iterate on this product you ensure the folks paying to use it are set up for success.” (16 likes)
 — shkeating

3. Rollout Access Clarity

Many of you were excited to try Sites but weren’t sure why the feature wasn’t available yet — especially those on paid plans. Questions about seat types, timing, and how to actually find Sites in the UI came up frequently.

“Just upgraded my account to try Figma Sites. Have a full seat on Pro. See no access to Figma Sites anywhere... any ideas?” (3 likes)
 — matt abrams

What we're doing with this feedback

We’ve shared your input directly with the teams working on Figma Sites and are actively tracking themes that surfaced most frequently, and — in a few cases, updates are already underway.

Here’s where some of that feedback stands now:

• Accessibility: A substantial portion of your feedback emphasized semantic HTML and assistive tech compatibility. We support tagging today, and are exploring how to improve semantic structure across blocks, including default behaviors that impact screen readers. Keep an eye on this Figma Sites article — Improve the accessibility of your site — we’ll continue updating it with fresh resources and guidance as they become available. More to come soon!
   
• Export & CMS Support: Code export  and CMS integrations are top-of-mind. While not available yet, these areas are being explored for future roadmap considerations — especially as more teams request publishing flexibility.
   
• Font Fidelity & Customization: Good news — custom fonts support is coming soon. We’ve heard your reports on Google Fonts and variable text rendering inconsistencies. These issues are under investigation, and we’re reviewing how font handling can better match your design file expectations.
   
• Nested Pages & URL Structure: This is a frequently requested improvement, and we’re gathering examples to explore solutions that support scalable site architecture. Most recently, we announced updates to apex domain support. Learn more here: Apex domains and custom subdomains in Figma Sites.
   
• Component Behavior & Breakpoints: Multiple users noted differences between Figma Design and Sites when it comes to variables, auto layout, and component states. We’re reviewing this feedback to smooth out those inconsistencies and make responsive behavior more predictable and performant. For more details and latest updates, keep an eye on this article: Create a responsive component that automatically adapts to each breakpoint.

We’ll continue to update release notes and relevant forum threads as improvements go live. Keep an eye out at: Figma product news & release notes.

What’s next — want to keep the conversation going?

Still have more to add? We’d love to hear more:

• Ask a question or get help in Ask the Community.
• Report a bug or friction point in Report a Problem.
• Drop in features and improvements in Suggest a Feature.
• Anything else? We want to hear from you in Share Your Feedback.

Again, we're deeply grateful for your thoughtful posts — from detailed bug reports to feature improvements. Your feedback helps ensure Figma Sites is accessible for everyone.

Hello!

We LOVE the idea of figma sites so far. Alongside Figma Make, this will allow our product and UX/UI teams to rely less on developers, which vastly improves time to market, and frees up dev resources for other tasks. Even with some features still missing, we are already planning to invest heavily into this.

As you mentioned, data integration already seems to be an important part of your roadmap. We used Figma Make together with around 2-3 prompts to integrate a public API endpoint, and rendered them into a Figma Site using around 3 prompts. Amazing!

Integrating external data this way allows for great custom components with custom data. However, the issue for us is that these custom components are not connected to our design system anymore.

So if you are planning to roll out CMS functionality, one idea would be to allow for integration of any kind of JSON based REST API – and connect the resulting data to existing Figma components. This allows the usage of dynamic data inside global Figma components, which can then be managed and updated in the design system.

Obviously, connecting any major large CMS like Wordpress or E-Commerce content like Shopify is also great feature that we would benefit from.

Keep up the great work!

Smart animate doesn’t work when ported from Design to Site when:

• Shape has a texture 
• Animation includes moving masked shapes

Figma Design. All transitions are smooth. Left to right:

1. Border radius
2. Texture size
3. Masked shape position
4. Border radius with static texture

Figma Site. Same order and animation.
Textures are not visible. Masked shape is not moving.

Bonus. Smart animate only switches between start and end state without transition/animation, even in Figma Design, when I add a shape with a Pattern fill. When adding the same component to Figma Site it doesn’t even show up in the preview.