Share Your Feedback

Your current plans do not include a standalone option for just Figma Sites. It is not necessary to buy a full seat plan just because someone wants to use Figma Sites, right? Let’s offer a variety of different plans to make it easier for customers to choose

In the new UI, the color options have been changed to buttons that you click on to open the color picker:I now need multiple clicks to get to a text field that I can edit or copy the value of. The old UI (still used for Selection colors) was much more accessible: I could even paste a non-hex value into the field and it would recognise it correctly!Can we please bring back the old input or an alternative/faster/easier way to quickly edit/copy color values?

Description:In this thread, let's delve into the intricacies of designing user-friendly marketplace applications using Figma. Whether you're focusing on e-commerce platforms, service-based marketplaces, or digital product exchanges, sharing insights on: User onboarding flows Product listing and discovery interfaces Secure payment and transaction screens User profile and review systems Responsive design considerations Integration of Figma plugins and UI kits This discussion aims to compile best practices, design patterns, and resources that can aid in creating efficient and engaging marketplace applications.

Since Figma Desktop has become noticeably slower and heavier in recent times, any accidental quit can be very annoying, especially with multiple files open. Restarting consumes a lot of power, even on a high-end machine like M4/24GB RAM MBA. This makes it particularly disruptive during meetings while screen sharing, as the app often freezes or lags when reopening, so that's why I find very welcoming to toggle such warning before try to close the app like Chrome/Brave.PT/BR to EN: "Warn before quit" 

I have been a UX designer for over 12 years, and in that time I have seen countless tools come and go. Very few truly stand out, but Motiff was one of them.Unfortunately, most people never really got to know Motiff, and as a result it struggled to gain enough traction to sustain its own design platform. That said, I was genuinely excited to learn that the team decided to bring back their powerful features in the form of a Figma plugin, essentially Motiff AI 2.0.Here is the concern. Figma typically approves plugins within 10 business days. Yet it has been over a month, and the Motiff plugin still has not been approved. I can’t help but wonder why. From what I can see, there are plenty of mediocre AI plugins already available, but the one tool that could truly raise the bar for design quality is being held back.I also found a post by the Motiff team in this forum where they shared an update. It even had a reply, but since then there has been complete silence. That makes this situation fe

ATLEAST LET US GO BACK TO PREVIOUS UI VERSIONS OF FIGMA. STOP TRYING TO REINVENT THE WHEEL EVERY MONTH AND CHANGING EVERYTHING

I’m trying to make a simple prototype of four screens for an web app. At first everything was more or less ok, but the last two days the AI is constantly hallucinating, making changes that are not requested to the point that my project is almost ruined. From the simple request to add additional column to a table the AI changed my layout, typography, etc. for absolutely no reason

I know you can put variables in gradients but are we going to see the option of adding gradient styles to Figma variables anytime soon? At the next Config maybe? 🙏🏻

  I use custom code (CSS and JS) in Figma to optimize my website’s UI, but the current input area is too short. Editing longer snippets requires constant scrolling and slows me down. It may better if the input fields ara resizable. 

I occasionally (once is too often) see the AI self-talk mention being unable to see what’s going on due to a “truncated file”. What does that mean. Eavesdropping on its “tinking” I get the impression there are times it can’t access all the code and hast to make blind changes. Is that what’s going in? (It can’t be, right?)

Search engines, AIs, and even co-workers have a very hard time understanding what I’m talking about when I say “figma make”. I can’t get much help with it online cuz search engines and AIs think I using “make” as  a verb.Please, Please rename it to Build, or construct or something!

It looks so much better in diagrams.All the colored lines look goofy. And if you change shape colors, they don’t change with them so it’s very difficult to manage.Clean gray lines solve everything. Win win.

When publishing components in a library - any components which have been excluded should be remembered and remain unchecked during each subsequent publish update.  this might be more intuitive than that contextual hide when published option - which effectively does the same thing in a more hidden way. Maybe that’s the feedback make unchecking effectively the same as hide when publishing - with an easier reversal option.Especially in the early stages of creating a design/component library there is a lot of publishing using the component, making tweaks and republishing - each time the user has to unselect certain components they do not want to show up, but need for whatever reason it’s a chore to constantly need to uncheck items each time.  Just make the system remember please.

Being able to create custom stickers to use in Figjam is a fantastic concept - I’ve created simplified components from the design system to allow BAs a simple drag and drop wireframe maker that worked brilliantly.But I cannot for the life of me figure out the rules that custom stickers use in Figjam - specifically why do custom stickers (and stickies) need to keep thier aspect ratio?  if i want a wider sticker or a taller sticker I should be able to do that - at the very least the sticker should follow the rules for scaling set by the originating design asset (no?) This applies to stickies as well - it’s 2025!  -[real/physical] stickies come in many different sizes now give us some versitility. I always hoped figjam would be a nice replacement for more traditional diagraming tools to create flows and maps - and while you can do these things - I feel it’s much slower and less intuitive. line routing is goofy, text wrapping is goofy, coloring and shading is extremely limited, etc.Sorry -

I rely sometimes on Figma to help with microcopy and I can see the AI features have been helpful to accelerate my writing, is there a way to inject, update my writing guidelines and tone of voice into the modal so it gets the overall gist of how we want to write

Hello Figma Team, We’ve been excited about the launch of Figma Sites and have been testing it as a potential solution for our company’s website.  The experience so far has been great so far but as we dig deeper, we’ve run into a few areas that seem limited today. We completely understand this is to be expected while in beta. But we’d like to get some clarity on a few critical items:  General Availability: When is Figma Sites expected to move out of beta and into full release? Site Structure: At the moment, subfolder structures (e.g., website.com/feature/subfeature) aren’t supported. Is this planned, and if so, is there an expected timeline? Redirects: It seems redirects are also not supported. Will redirect functionality (including handling of trailing slash versions) be added, and when? Are there any recommended interim solutions? 404 Page: We also couldn’t find a way to create a custom 404 page. Is that capability available yet, or is it still on the roadmap? Cookies & Tracking:

With any large organization users when accepting invitations to Figma are not mindful what they type as their name.  When someone simply uses Initials or a First name it makes it difficult to reconcile users or know what users are doing.  Please update the Administrator functionality to allow changes to the persons name.     

I spent a month building this project.200 users already rely on it.And then—one update.One privacy pop-up.One broken publish button.Everything stopped.I tried what everyone else tried.Rollback to an old version?Sure—it works. But why should I accept that?Policies updated.Privacy terms rewritten.And suddenly, they own everything while I own… nothing.Imagine this: your designs, your infrastructure, your users…all trapped inside a system that won’t even handle an error gracefully.No proper documentation.No accessibility.No GitHub support.No real answers.We deserve better.Better error handling.Better transparency.Better respect for creators.Because right now?We’re building their platform.And they’re taking everything from ours. [Moved from “Figma Make down?” to “Share Your Feedback” by a moderator on 27-Aug-2025.]

You’d observe that when ypure on any website and you navigate between pages, the browser loads the page. The cue you’d see is either the ring loader or in my case, Dia browser, a line strip shpws under the address bar…For my published Figmasite page, nothing happens and so when i navigate to another page, it doesnt seem like something is happening

For many reason, (1) Grid still no CSS autofit/autofill functionality, (2) requirement assets be on the same page in order for prototyping to work, etc., there are still occasions where you need to nest an instance in a component in order to achieve intended behavior. Unfortunately this also explodes layer count andreduces efficiency. Is there any chance you all can (address the underlying, more flexibility with prototyping, please add autofit/autofill on grid asap) make it where the instance can become a component and still hold its relationship while being a different kind of component itself?

 My original command: “Move the subject to the left so that there is more background on the right side of the image.”. Figma AI not only did the command but also decided to give me a facial feature updateSo… My facial feature was changed by Figma AI, even though the command was not containing anything regarding editing the subject. I find it problematic, because my ethnicity is changed & without consent.

こんにちは、FigmaSitesの登場により、マークアップや実装を伴わないクイックなページ公開機能は私達のプロダクトを加速させる重要なエンジンの一つとなっています。数々のページをローンチしてきましたが、いずれもXにてURLをシェアした際、OG情報が取得できていない事がわかりました。その原因は、FigmaSitesのページはJSによってレンダリングされており、Xの投稿時にはリンク先のHTMLだけを参照しJSは実行しないことによって、OG情報を取得できていないのだと推察しています。タイトルやOG情報などはJSでレンダリングせず静的にHTMLに記述することによってさらにこの製品はパワーを発揮できるはずです。ご検討のほどおねがいします。

Current: right click project “Settings” Click name type in new name Desired:right click project “Rename Project” type in new nameAlso, if you try to add special characters, the error message spits you back out on the Settings screen, whereas it should just keep you on the Rename form

​​​​​The button for this was so easy to find always in the bottom left of the screen. First the icon recently changed to what looked like a notebook, then it kept moving around and now disappearing all together. It’s now completely gone, and after minutes of searching the closest thing I found was the Templates and tools section, but it is broken as the search function always returns the same set of results shown in the screenshot.

Why does a perfectly functioning thing constantly have to get changed, confusing the users?  

The brand I work for has multiple branches with their own colors, each color containing 8 different hues. I created a color style for each color and use them when creating designs. Sometimes I need to play around with the colors to find the correct hue, but this can be very frustrating due to the fact that when I click ‘Fill → Library → select my color’ the menu immidiatly closes. If I have to do that 8 times to find the right hue + circle back to the best options that means I have to click at least 18 times. But if the menu would stay open I could do it within 9 clicks. This might not seem like much at a glance, but when you have over 25 shapes/text blocks on a page that need color that means I have to do 450 clicks instead of 225. I can see how the menu staying open is not helpful in everybody's usercase, but having a toggle somewhere where I can choose whether I want this menu to stay after a selection would be very helpful and save me a lot of clicks. TLDR; When selecting a pre-set