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

hello. I am an engineer developing a design system at a company called Karrot (daangn.com) in Korea. I went to SF this time and saw Config, and I have high expectations for the new features.

For accessibility, I will move on because many people have already raised issues above, and Figma needs to upgrade the Interaction tab.

1. Motion Variables

It's great to be able to set custom beziers and custom springs, but we need the ability to manage these custom values at the team level.

It would be nice to be able to create and apply Variables to values like Duration, Bezier, etc.

I've been thinking about this before, but with Figma Sites, I feel like it's even more important.

2. Need the ability to manage Custom Bezier, Custom Spring

It's nice to be able to apply custom transitions for each element.

But that's about it. It doesn't seem to be possible to copy or clone custom transitions yet. I would like to be able to create custom transitions like Smooth Reveal and Expressive Reveal and share them as a team.

I'm very excited about the CMS, Figma Make, and other features that have yet to be released.

Thank you.

Recently while I was about to publish my website, I saw that one of the errors suggested that I must remove auto scroll to particular section within a webpage because it is not supported in Figma Sites. This feature is a must because usually users want to create one pager website.

figma sites are made frankly poorly, as is the figma forum, which apparently no one reads.

the division of files into specific sites and specific designs is unclear why it was invented at all, synchronization between layouts in different files is unclear how it works, and if there is no synchronization, what's the point of your layouts in figma sites files? Why do you always make a lame horse?

you turn on figma sites, wait six months for a cms update, turn on the cms update, wait six months for a figma make update. What is the point of such updates? to create a design in the current update, knowing that in six months this site will need to be changed to another, because the interaction structure will have already changed? and projects are not done quickly, complex projects take a lot of time, not in order to spend the same amount of time changing the structure in six months.

the projects that you presented last year are still in beta. You have an extremely strange and, in my opinion, completely opaque approach to your updates. The layout has been broken since last year, and you don't fix anything.

A lot of services doesn't mean a lot of good services. Try to do one thing well, so that updates come out on the day of the announcement, and not broken after half a year

I have finally had the opportunity to experiment with the Figma Sites. I am particularly interested in some of its features, such as:

1.  Loading a custom template to initiate a project
2.  Implementing breakpoints for specific responsive behaviors

However, my ultimate objective is not to directly create public websites, but rather to generate mockups that can be seamlessly integrated into our framework. Is there any possibility that I will be able to access features like a template library or genuine breakpoints within the default Figma interface?

I’ll agree with others who have wondered WHY embeds seem to have internal padding? If I use the same code to embed a video on Webflow or Framer it’s perfect - fits my layouts exactly as you’d expect. But in Sites it places the video with padding, making the video smaller than other images etc., completely throwing off the design intent. 

How it should line up:

Yet smaller when published:

Also, like Framer and Webflow, we very much need a preview of our embed in the editor. Impossible to design correctly without it. 

When you set the scroll behaviour of a frame to overflow: horizontal, or overflow: vertical, this only works when ‘clip content’ is switched on. I think this is how the overflow property works in CSS, but it might help to have a warning

I’ve run into 2 issues so far.

1. Overlay interactions copied over from ‘design’ don’t seem to work properly. ‘Sites’ sees the interaction, but it doesn’t actually work. In my example, clicking a button to open and overlay a frame.

   

    

2. A common font I am using ‘Montserrat’ doesn’t show properly when previewed.

I’m super excited about Figma sites and plan to use it extensively. I’ve been doing some testing and have found a few issues I hope that are fixed. The new effects of noise and texture don’t seem to work when previewed and blend modes don’t always work for some reason. Excited for the full release.

Just a suggestion: You may consider adding REAL value to your CORE product (e.g. better prototyping), instead of a range of half-bakes solutions for hobbyists that will never come to full fruition. You are becoming Adobe...

Hi, 

Figma sites sounds like a framer killer, but it’s pretty useless until we get viewport and % sizing.

Keep up the good work guys.