Suggest a Feature

Hi, I've been working on a prototype, and animating the chat bubbles turned out to be quite a tedious task. To create the animation, I had to duplicate multiple frames and apply individual delay animations to each chat bubble.I'm wondering, is there a way to apply a delay animation to a group of elements collectively and adjust the timing for each, similar to how you'd stagger animations when loading a collection of cards?With Figma's current capabilities, the only workaround seems to be creating multiple frames and manually adjusting the opacity and timing for each element to simulate delayed appearance which becomes repetitive and time-consuming when applied across multiple components.Would love to know if there’s a more efficient approach or if this is something the team is planning to improve in the future.

It would be really helpful to be able to use a variable to set a Type Style’s Letter Case (under the Type Settings meatball menu). It could be a String Variable, and the options would be “As entered”, “Uppercase”, “Lowercase”, “Title case”, and “Small caps”. I personally use modes to switch between different brands, and some brand styles require uppercase while others don’t allow it. This suggestion may be a small feature in the grand scheme, but I wonder if others would also find it useful.

I am using auto layout a lot in my projects and think it is awesome. However, there is one small issue that annoys me a lot. The default setting for canvas stacking is always “Last on top”, which is usually not what I want. For instance when switching state of a dropdown in a layout, the dropdown list will appear below the content that is underneath it (at least in my case where the list is using absolute position). With lots of nested auto layouts, things quickly become a mess if you forgot to change this when you created the auto layout. I would suggest either of these solutions: Change default to “First on top”. Make the default setting optional Remember the last used setting (like the animation properties work)

One of the properties, very basic in CSS, that I miss most often in Figma is “background-color” for text. Would be awesome if you’d consider adding this feature on your roadmap, especially that you aim to become a competition for webflow.

I’d like to suggest an improvement to Edit instance swap property.Currently, when swapping a nested component via instance swap property, it’s not possible to adjust the swapped component’s — such as size, state, variant properties, or other component properties.It would be very useful if, within Edit instance swap property 🙏

One thing that’s become frustrating is that it’s no longer possible to collapse just the left panel while keeping the right panel visible.In UI2: Ctrl+Shift+\ only hid the left sidebar. The collapse arrow on the left also only hid the left sidebar. Now in UI3: Both Ctrl+\ and Ctrl+Shift+\ collapse both left and right panels. The collapse arrow also hides both panels together. This makes workflows harder for users who want to maximize canvas space but still have quick access to the Inspector or Design panel on the right.Request:✅ Please restore the ability to independently collapse the left and right panels — both via shortcut and via the left collapse arrow.✅ Even a setting in Preferences to toggle between “unified collapse” and “independent collapse” would be great.

Just to bypass the disability of not allowing the glass effect to be applied to shapes, here is the workaround I found that does it half-way.The layer hierarchy is as follows:Group layer (Parent)|__ Group layer (Holds the ‘Frame’ where effect can be applied)      |__ Frame (The Layer with the Glass effect)|__ Vector Mask (The shape in question, used as a mask for the Group layer as you can’t get it by just masking the frame, doesn’t work like that)|__ Vector Layer (Used for the Stroke effect around the logo)This is really bad UX and I think should be allowed for shapes if it’s just a shader.

Hello Figma team,Feature Request: Exclude Specific Content from Frame ClippingWe propose introducing an option to selectively exclude certain elements from being clipped within a frame or component.Currently, when a frame has “Clip content” enabled, all child elements are uniformly clipped to the frame bounds. This limits design flexibility in cases where designers need specific elements (such as tooltips, floating labels, badges, or overlays) to visually extend beyond the frame while still preserving the frame’s structure, layout behavior, and constraints.Suggested Enhancement: Add a per-layer or per-component setting such as “Exclude from clipping”. When enabled, the selected element would visually overflow beyond the parent frame boundaries, even if Clip content is turned on. The parent frame should retain its clipping behavior for a

https://fonts.google.com/specimen/Zalando+Sans+Expanded?preview.text=Hello%20awesome%20people!%20Do%20you%20want%20Zalando%20to%20be%20added%20to%20Figma%20fonts%3F&query=zalando  

This seems like a very large design oversight in Figma Slides. The help article says that “Published changes only apply to new slide decks that are made with the template.” Doesn’t this defeat the entire purpose of having a custom template where you can edit a style and have it apply to your entire presentation, instead of needing to manually tweak a header style on every slide? I expected this to work the same way instances update in Figma Design when you make a change to the main component, but even after publishing changes to a custom template in Figma Slides, my existing slide deck that pulls from that template isn’t updating colors & text styles. The published template changes would only apply to brand new slide decks, which means I’d have to define the template first and

I'd love to be able to transform ONLY selected nodes. For example: rotation, resizing, etc. This can be quite hand sometimes when drawing and using shapes 

I find the thumbnail is slow to update and often doesn’t update for days (at all?). A work around has been to choose “Restore default thumbnail” and then “Set as thumbnail” on the desired frame. The thumbnail has become an important feature to me and I use it to convey information to my team. The inconsistent thumbnail updates are a little problematic. Suggested solution: an option in the right-click menu for the file to “Refresh thumbnail”.

I’m working with Figma Sites and its built-in CMS, and I’d like to suggest a feature that would significantly improve the developer experience when using code layers / React components.Feature requestProvide an official React hook (or similar API) to access CMS data from code, for example:const teams = useCollection('teams');orconst { data, loading, error } = useCollection('teams');Why this would be valuable Many developers want to build custom React components (carousels, filters, tabs, animations) that rely on CMS data. Today, CMS data is accessible only through visual bindings, not programmatically. A hook like useCollection would: Bridge the gap between design-driven CMS and code-driven components Reduce the need for manual exp

When a comment is marked resolved, it just shows the filled checkmark icon. It doesn’t say who resolved it and when it was marked as resolved.Contrast this to Google Docs, etc., which shows this information.I already saw:View who resolved a comment and when • 2 years ago • 4 replies See who has resolved or reopened comments • 10 months ago • 0 repliesProblem still stands.We should also be able to see who reopened a previously resolved comment, and when.

Background: I am a developer, and I use Figma exclusively in Dev Mode via the web interface. I don’t have (nor do I want) any edit access to the designs I’m implementing. That’s for the designers. When the Measure tool appeared (the ruler icon on the upper left toolbar), I latched onto it very quickly. It greatly improved my speed of accurately implementing a design. There are certainly other ways to measure things in Figma, but they are all transient. The best part of the new tool was that I could quickly measure many different things and have all the measurements persist so that I could then just refer to them during development. It was a simple yet well-conceived tool.

hi Figma, i need your magic. I require both a maximum and minimum character limit for the text property. This will allow me to establish clear guidelines for UX writers, ensuring that their content fits within the designated character limits and maintains a tidy design and layout.

Hello, I would like to know if it’s possible to select several words in a text layer, for example to put them all in bold or a different color from the rest, but all at once. Like in Word or Google Doc, I believe the shortcut is ctrl + select the desired words or part of words. It would be useful if it also worked across multiple text layers. I tried all the shortcuts I could think of but nothing seems to work… Selecting words one by one and apply the wanted properties every time feels soooo tedious. Maybe its not a popular request but that would be so useful. Thanks !

My suggestions is to allow users to include annotations and / or measurements  when they export images. Seems that we can’t currently do thisThe user benefits –allows users to share images with annotations and measurements when creating images to be shared wither wider stakeholders and creating documentation for other platforms. If we can’t export annotations and measurements, then for those instances requiring annotations in an export as an image, users won’t use the annotations feature, and revert to creating “Notes” manuallyHope this makes sense

Hi there! For design systems, because components can contain other components, it might be a good idea to allow designers to set an “inherit from child” or passthrough option that allows the size to be set by the child component. Right now I think everything is enforced by the parent level, and it can break things (reminds me of my childhood lol .. just kidding - kind of?). Bottom-up works better than top-down in any case :) (see New Scientist, “Why complex systems do better without us”). --And a lot of life is learning to let go lolI have a feeling this may have been reported as a bug in the past, and it may be a technical limitation of HTML itself. It may be worth considering for a future version of HTML/CSS if that’s the case. I notice the “hug” feature already inherits from child in its own way, but

… not fake elements that look like links. The reason why is because someone posted a link to a Figma file inside a Figma comment, and when I tried to open it in a new tab (making sure I’m holding Cmd in macOS, same as Ctrl in Windows), it just opened in the same tab as the Figma file I’m currently viewing. It’s also impossible to right-click the link and get a link-related context menu. It’s not possible to easily copy the link too. Right now what we get is a regular browser context menu. Worst parts are: The draft comment I wrote was completely lost because of this navigation. There was no warning, and it wasn’t saved to be restored later. The back button doesn’t work. It doesn’t take me back to where I was. It just reloads the linked page, and then the back button is fully disabled. I had to go find the previous location myself manually. PS: On that note: Please also reduce the label of long links to be truncated with ellips

It would be great if dev could export without rounded corners applied and or have some export flexibilities

I use Figma for Mac, and often need to copy+paste the link designer shares on slack.

Hi Figma Team,First, I want to say that I am really enjoying the new AI capabilities in 2026. However, I’ve identified a workflow friction point regarding the export process that I believe could be significantly improved.Below is a proposal for a "Batch Copy" feature to enhance the design-to-canvas workflow:The Problem (Current Experience): Currently, when generating a multi-page web application using Figma’s AI tools, I am required to copy each generated page individually to move them onto my main canvas. This becomes a repetitive and time-consuming task when dealing with complex user flows (e.g., Home → Product → Cart → Checkout).The Solution (Suggested Enhancement): I propose adding a "Copy Entire Flow to Canvas" button. Function: This would allow users to transfer all generated screens/pages of a web application to the Figma canvas in a single action.

When working in teams on Figma projects, especially on larger or long-term products, it becomes difficult to manage changes, ownership, and reviews in a structured way.Right now, multiple designers can work on the same file, but it’s not always clear who changed what, or how those changes should be reviewed before becoming part of the main design. This often forces design leads to manually compare versions or rely on informal processes outside of Figma.It would be very helpful to have a Git-like workflow built into Figma, tailored for design teams. For example: The ability to create branches from a main file and work on specific features or sections Clear visibility into who worked on which frames or components and when A pull request–style flow where a designer can submit their changes for review A review step where a lead or manager can comment, request changes, and approve

If I’m already logged into Figma on my computer, can I just display a QR Code and Deep link my Figma app to that account so I can quickly preview my design? I’m not expecting it to know what project I’m in but that would be AMAZING if it could but I would settle with just logging in for me.