Share Your Thoughts

Current: Site > Settings > General > Custom codeAdd section: Site > Settings > General > Non-page requests So I could addPairs of request and static content: robots.txt (and add static text content) some-verification-file-name.txt (and add static text content) sitemap.xml (and add static/dynamic content) Redirects request (and redirect url) This should cover a wide range or common scenarios. 

We’re using templates as an early way to handle branching in Figma Make. There’s a primary prototype that the team remixes and iterates from. As work progresses, we manually pull changes back together, and when a remix becomes the new source of truth, we promote it to the primary prototype and archive the old one.This process is very manual and hard to stay on top of. Having real branching and merging for Figma Make files, similar to what exists for design files, would be a game changer. Hoping something like this is on the radar and shipping soon. 🤞

Comments are not preserved when duplicating a page, frame, or section, which creates friction in revision workflows.Our team collects client feedback in comments, duplicates designs to begin revisions, and then loses the original comment threads. This forces us to manually recreate feedback or constantly reference an older version, which slows iteration, increases the risk of missed feedback, and adds overhead across projects.A helpful solution would be the ability to preserve comments on duplication, anchor comments to objects instead of canvas positions, or show comments from a previous iteration.This is a significant pain point for an organization of over 6,000 employees, where even small gaps in functionality can have a wide-reaching impact. PLEASE HELP!

Am curious if there’s an easy way to exclude the second fallback parameter from any css custom properties displayed within the dev inspector? Our dev team will not utilize the fallback values, and is hoping to sync these variables 1:1 with the css custom properties defined within the codebase. We’re aware we can manually edit the variable and exclude the second parameter, but would love if there were a way to make this the default behavior.i.e. we would prefer color: var(--primary-100) over color: var(--primary-100, #f3f3f3) as a default if possible.

I work for 4 different companies with unique Figma accounts. All the projects I am currently working on are open, which is about 20 tabs. Switching between profiles for these different companies makes my workflow SO slow. Is there a way Figma would consider adding the ability to switch profiles in the open file so I don't have to close everything and start fresh, losing time and often forgetting what I was doing in the first place?  Thank you! 

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

I'm building a responsive alert banner and trying to achieve a behavior similar to fit-content in CSS. Here's what I need: The banner container stretches to 100% width, Inside, there's a button and a text label, The text should stay on one line and hug its content until it reaches the limit of the container, Once it can't fit anymore, it should wrap onto multiple lines (essentially behave like fill). Think of it as:"hug content until there's no space left → then behave like fill".This should happen dynamically, depending on the container width,so no fixed max width.Is th

The title just about summarizes my issue. Developers until recently had access to ruler measurements and annotations with their Dev Mode seats. Recently, these tools were stripped from them. I don’t understand why only designers can measure distances or leave annotations, so long as they are not editing files, why should Devs be unable to annotate or inspect files using the tools Figma designed for Devs to inspect files?Good design practice in Figma often requires us to build things differently than they would be built with actual HTML/CSS. with Autolayout in mind, it’s better to determine the space between objects rather than apply padding to the top of Divs as many devs would do. However, when a dev wants to measure the total space between elements, they should be able to use rulers to make the measurement THEY need and not the one Figma decided they should have. Why were these tools stripped from Developers? We’re already on an Organization plan, paying quite a lot

I have been working with Slot for a while, introduced it in our component library too.Here are a couple of observations:The magenta outline feels too prominent and interferes with design and understanding of space, padding, etc. I would have preferred a subtle affordance that slot exists.While selecting things on canvas, earlier entire frames, components would easily get selected but with slots in those components, when I drag and select, selection happens randomly, sometimes, only slot layers are getting selected instead of entire frame or component which is not what I expect. And, it just messes it up. Cmd+X / Undo doesn’t work properly if I delete something from slotted component. There is not an easy way to return to previous state.

When copying vector-text content from FigJam into Figma Slides, the pasted elements cannot be scaled properly, which breaks layout, readability, and the overall structure :(This creates friction in the workflow between ideation and presentation, I had to recreate a lot of content manually instead of reusing it. Unexpected I have to say.Enabling proportional scaling for grouped vector (strokes!) and text elements would make it much easier to move seamlessly between tools and maintain consistency across collaborative work. Thanks in advance :) 

Hey Figma team and community!Now that Figma Sites CMS is in public beta, I'd love to see one feature added  scheduled publishing.Right now you can publish content immediately, but for things like blog posts, product launches, or event pages, it would be super useful to set a date and time for content to go live automatically.This is a pretty standard CMS feature and would make Figma Sites much more viable for real production websites.Anyone else feel this would be a valuable addition?

Feedback 1: since Figma Desktop App version 126.1.2 text styles picker always shows libraries of styles in collapsed state. It’s super annoying, since search doesn’t work until you un-collapse it.Feedback 2: please fix up/down arrow behavior on styles. Example: the text span has style “Body/Emphasized” → I press arrow up expecting it to switch to “Body/Emphasized” → instead Figma selects “Headline/Regular” (the style that just happened to be below the search box). I papercut myself on this multiple times every day for the past couple of months now, at least.Figma’s a great product, I love it, but bugs like these are a big let down for me. I believe basic features like text styles should be dogfooded more to remain best in class. 

I have successfully rasterized last Friday. But two days later, which is now Jan 13 2026, the Rasterize selection disappeared in object menu. I can only find it by searching Actions… Is there anyone can help me look into it, thank you so much!i use macbook pro 15-inch, 2018, Vetura 13

When adding or editing a comment you are currently able to use the following key combinations:[Shift]+[Enter] to go to next line [Ctrl]+[Enter] to go to next line [Enter] to post the commentI’d like to see the function of [Ctrl]+[Enter] and [Enter] switched. This would in line with a lot of other programs and also with adding/editing text in Figma. So, for the adding/editing a comment I’d love to have the following key combinations:[Shift]+[Enter] to go to next line [Enter] to go to next line [Ctrl]+[Enter] to post the comment

Thanks for the update — really excited to see Sites CMS finally launching 👏It’s a great start, and we’re already experimenting with it.There are a few key CMS capabilities we still feel are critical for real-world usage:Video support in CMS fields We currently can’t embed or bind video content (e.g. hosted video URLs) from CMS fields into modules. This is essential for modern marketing pages, case studies, and content-driven sites. Grid / layout control for CMS lists CMS lists don’t currently support true grid layouts. This makes it very difficult to build responsive, multi-column layouts (especially across breakpoints), and limits design flexibility compared to typical front-end grid systems. CMS item status / workflow We really need basic content states such as: Draft Unpublished Published This is critical for real con

Every time I switch back to Draw the tools color resets to white. Am I missing something? A product that really understands designers perhaps 🤔?Jokes apart, it feels “rude” to forget the colors I so carefully picked just a couple clicks previously.

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

I am trying to export an entire figma make prototype to figma designs. It seems crazy to have to do this screen by screen when there is so much embedded functionality (modals, tabs etc). Is there plan to do this in the future? Or am I missing something 😅 Thank you!

When marking a comment as resolved, we are now automatically moved to the next one. I’m wondering if or how we can disable this behaviour?My work flow being to go from screen to screen of user flows, and not comments to comments, this is very disrupting as it can bring me anywhere in the file, and I need to find and navigate back to where I was. I understand this might be useful for reviewers that only goes through questions left by other people, but this probably not most users, so it would be useful to have the ability to disable this feature.

Would love to request a feature that supports connecting Figma directly to our binary store (Artifactory) for all package retrievals! Will make it easier to connect our design system!

My team wants to be able to use Figma pages as historical records of certain releases. The problem is we either have to detach all components, or create a separate file so updates in our libraries don’t affect what we’ve historically released. It would be nice to be able to “lock” certain pages as a part of the current Dev mode lock, to be able to store a historical preview of what is in production. (They don’t want screenshots because they want to still be able to enter prototype mode. Any suggestions you have on others way to do this would be appreciated!

I’d like to share feedback regarding the implementation of AI credit limits in Figmake. As a designer managing multiple complex projects, I believe credit restrictions would greatly undermine Figmake’s usefulness in real-world design and prototyping workflows.  1. Most AI usage is for fixing bad or incomplete output, not luxury use.  In practice, a large percentage of AI prompts in Figmake are iterative—used to correct layout issues, rebuild misinterpreted elements, or align behaviors with visual intent. Each refinement quickly consumes credits even though the output quality depends on that iteration. Penalizing iteration limits the model’s ability to produce accurate prototypes, especially when the AI output is imperfect through no fault of the user, making credit usage really unfair and frustrating.2. Predictability becomes impossible, discouraging adoption.  With a credit cap that no one knows how to predict and calculate ahead of time, I can’t plan how

These are new and improved color formats that replace hex and rgb. They will soon become the standard in web browsers. They open up more colors than are currently possible. The Expanding Gamut of Color on the Web | CSS-Tricks - CSS-Tricks

I would like to provide feedback on  support experience.I wanted to pay for Figma but both payment methods were declined. I was told that problem is with my bank and I need to contact them or use another card, thats all we are closing you case.I contacted my bank which confirmed there are no declines or restrictions on their side.I tried another card but I cant pay in euros from ukrainian card according to Figma restrictions and I cant change currency in invoice according to Figma restictions again!I contacted support once more and all I get was the same “contact your bank or use another card” without any real investigation of the issue.This has been time-consuming and frustrating.Could this case please be escalated to someone from billing or a support manager who can properly review it? Because it looks like you dont need your customers to pay you.

Since Figma does not support going back to previous views, it is quite frustrating to switch between pages. Would you ever allow the same file to be opened in another tab, but not in a new app window? This would become very handy to switch between pages in the same file.