This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Sites. Our team will be actively reading and sharing relevant takeaways with the product team.
What we’d love to hear from you:
What aspects are you most excited about — and why?
Where do you still have questions or want more clarity?
A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand.
Keep feedback focused on Figma Sites — this helps everyone follow along.
Page 1 / 3
Such a great feature. I'm looking forward to publishing my portfolio and other projects in Figma. Thank you for this work!
When will this be rolled out? So far I don't see anything about it in either the normal app or the beta app and I have a paid seat :(
just upgraded my account to try Figma Sites. have a full seat on Pro. See no access to figma sites anywhere...any ideas?
Been playing with the new grid auto layout, loving it so far.
The other two announcements I was excited to try out were Sites and Make. Sites is nowhere to be found, and Make just says AI unavailable - which obviously makes it unusable.
So, what’s the deal with these? Is there a release date for Sites? Is Make just down temporarily?
I’m on the Pro plan and I’m trying to find Figma Sites and it’s no where to be found? Is this something that will take multiple days to fully roll out?
I have a pro plan full seat but see no option for sites in browser or desktop app
Hi everyone — love seeing the excitement around Figma Sites! It's rolling out now and will be available to everyone on a paid plan by end of day. Appreciate your patience — keep an eye out.
Quick heads-up:
If you want to use every available feature in Figma Sites, like the AI tools, you will need a Full seat.
Figma Sites is currently not available on the Starter plan and a limited experience will be launched soon.
Once fully rolled out, you'll be able to create a new Sites file by heading to the Figma browser and hitting the "Create" button in the top right.
Looks promising. 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.
Cool so far! Would be great to have nested pages and folders for organization and URLs.
does the educator plan provide access for figma site?
How can I add a custom domain? I have already looked on the help page. According to them, it should have its own Domains tab. Unfortunately I don't have it.
Google Font Space Grotesk doesn't work
which is strange because other fonts works
Oh of course only my favorites ones don’t work Outfit, Lexend, Jost fonts
Also tested in figma offical template
Will Figma Sites be accessible for Educational/Student accounts as well, or will I need to pay for it?
Some Google Fonts just aren’t working on a public site. Also Cyrillic symbols are not displayed correctly, while it looks good in an edit mode.
How can I add a custom domain? I have already looked on the help page. According to them, it should have its own Domains tab. Unfortunately I don't have it.
You have to publish your site with a Figma default subdomain. After that domains settings will appear.
It looks promising, still a lot to add in functionality to make me switch from Framer, but I’m sure that will come. My biggest concern is that this will become a new half-supported initiative like too many things are in the last couple of years at Figma. But let’s wait and see.
A big worry-flag for me, without knowing more around the tool (so I can be totally wrong), is the fact that in the demo’s I saw people use it in a “Copy and paste your designs from Figma into Sites”, which… totally defeats the point of having everything in 1 tool.
Being able to make a design dynamic according to data would make it possible to combine precision and ease of modification for visuals like charts in Figma Slides, where it really counts.
Seems like the font sizes are not correctly loading in the public link. Not even in the original template previews: https://plugin-value-scrum.figma.site/
The heading font is getting the lowest viewport’s font size (mobile) by default.
Looks promising. 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.
Many businesses, mine included, will need more information on the hosting structure before it’s allowed to be utilized to host a page or site. Is there any deeper documentation regarding this?
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? In the demo site it was just a pile of divs.
I get as an authoring tool it is not your responsibility to ensure every single aspect of accessibility of each and every site (I work on an enterprise design system and it is the same for us, some things we can control, others we can't and is based on how it is used) but we do have to make sure authoring tools empower creators to follow accessibility guidelines, and we especially need to make sure we don't make it impossible to ship accessible code, which is what Figma Sites is currently doing. I highly recommend checking out the Authoring Tool Accessibility Guidelines, published by the W3C: https://www.w3.org/WAI/standards-guidelines/atag/ for some evaluation criteria for Figma Sites as an accessible authoring tool.
I was excited for this when it was initially mentioned, but if the sites are going to be only be divs, it is essentially impossible to release accessible websites with it. Meaning most businesses globally can't use it without risking litigation or having their product pulled from the market. I hope that as you iterate on this product you ensure the folks paying to use it are set up for success.
I have done a very short review of your accessibility functionality whilst creating a sample website and I have found the following issues:
Accessibility settings are hidden by default - you have to manually add them to each layer. Why can’t we make these settings already visible?
No high-level view of applied tags - you have to click into every single layer to check.
Everything defaults to a <div>. Why can’t we utilise the purpose of some of the Blocks to add some basic semantics?
The last character in a text layer gets its own <span>? This affects screen readers. See attached output of VoiceOver. VoiceOver output reading a CTA as the full span without the last character
Redundant use of
<a role="link" tabindex="0">
I have also seen examples of a <div> element with a href?
Links open in new tabs by default, but there’s no clear way to notify users (unless you override aria-label).
aria-label is added everywhere, sometimes duplicating visible content or mislabeled as “alt text.” This could cause WCAG 2.5.3: Label in Name failures. Also, now I have tested this more, if you apply a tag to something like a heading, the usage of aria-label duplicating the intenral <div> actyually makes the heading completely inaccessible to VoiceOver, where it doesn’t read the content of the heading due to the ‘grouped’ element inside it with aria-label. So applying accessibility tags can actually make it worse for users.
Default content blocks aren’t accessibility-ready - e.g., poor reading order in card layouts where images are above their heading - means screen readers will here a related image before the heading - have we considered keyboard and reading focus order?
No functionality possible like skip links.
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.
Loving it so far. We need a hide/show header on scroll interaction though. The scroll transform interaction does not really work like it does in framer.
Yet again, a new tool has been launched without proper accessibility features. This situation is particularly concerning because even a junior developer could create a more effective solution using semantic HTML instead of relying on numerous <div> elements.
Emily provided a brief analysis that highlights the main issues. However, I believe it would be ideal to conduct audits in accordance with the Authoring Tool Accessibility Guidelines (ATAG) to establish the key criteria from design to code.
I have done a very short review of your accessibility functionality whilst creating a sample website and I have found the following issues:
Accessibility settings are hidden by default - you have to manually add them to each layer. Why can’t we make these settings already visible?
No high-level view of applied tags - you have to click into every single layer to check.
Everything defaults to a <div>. Why can’t we utilise the purpose of some of the Blocks to add some basic semantics?
The last character in a text layer gets its own <span>? This affects screen readers. See attached output of VoiceOver. VoiceOver output reading a CTA as the full span without the last character
Redundant use of
<a role="link" tabindex="0">
I have also seen examples of a <div> element with a href?
Links open in new tabs by default, but there’s no clear way to notify users (unless you override aria-label).
aria-label is added everywhere, sometimes duplicating visible content or mislabeled as “alt text.” This could cause WCAG 2.5.3: Label in Name failures. Also, now I have tested this more, if you apply a tag to something like a heading, the usage of aria-label duplicating the intenral <div> actyually makes the heading completely inaccessible to VoiceOver, where it doesn’t read the content of the heading due to the ‘grouped’ element inside it with aria-label. So applying accessibility tags can actually make it worse for users.
Default content blocks aren’t accessibility-ready - e.g., poor reading order in card layouts where images are above their heading - means screen readers will here a related image before the heading - have we considered keyboard and reading focus order?
No functionality possible like skip links.
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.
Couldn’t preview anything. The screen still loading and nothing happens. Tried even to run some of the templates without success. Am I doing something wrong?
Last year the CTO of Figma stated at Config the following quote.
“The other hard part about converting designs to code is the fact that most engineers - atleast engineering leaders….. they don't want more code. ...I'll be honest with you, we have enough code. We need less code. We need faster code in certain places. We need code that we can all reason about again, and stuff like that. And so we're not that excited about a bunch of AI writing a bunch of new code that a lot of engineers don't understand. We want to reuse the code that we're already building to replace some of the older code we have. We want that code to automatically.
You know, take advantage of all the accessibility work we're doing, you know, all the responsive layouts and things like that. And so I also think there's a place for these new technologies to help us better utilize the code we have. And I think in order to do that, engineers have to build a reason about how it's utilizing it and have some control and influence over what it's utilizing. And so, you know, code connect, I think even absent AI is already very useful, but you can see it as a sort of built in block in terms of.”
As someone with a vision disability who designs in Figma, I hope accessibility is more than a checkbox for you. Fixing the generated code is a real chance to lead by example and create truly inclusive experiences—for everyone.
I love it! I think it’s a very natural extension for Figma.
I am curious to know about pricing. What happens after 2026? The free period is good but before I migrate, it’s typically good to know what the pricing would be in the future so clients aren’t locked in.
Is it SEO-friendly yet or will that be a fast-follow? I find it tough to set H1, H2 tags etc.
