Suggest a Feature

I publish complex files about video game UI.I see my files being used and notification bar doesn’t allow me to see all names or visit those people profiles (if there is one).Seeing real names and profiles would help me feel more real connection to those who use my files, and it will keep me motivated to create more of them.Clicking on notifications just navigates me to the file page, and there are none lists of likes, uses available.  Could we have lists of likes, uses of our Community files?Maybe like in Instagram or Behance 

Currently there is a different order in the dropdown for Grid columns/rows than the dropdown in Resizing. The muscle memory really hurts here.Resizing:  Grid: Please unify the dropdowns for them to both either be:Preferred:Fixed width Hug contents Fill containerorFill container Hug contents Fixed width

Hi TeamThis is must have feature in figma! With the power of AI, Uizard Wireframe empowers to digitize hand-drawn wireframes in seconds with the click of the button. It can transform designs in to clickable prototypes with ease.https://app.uizard.io/This video explains the feature -  

Hi there.I create a new thread because this one is closed: Like many, I do my resumé with Figma. And I’ve seen that the text exported PDFs have undesirable spaces inside the words.Example:Copy/paste this text and you get:“with 2 0 + years of e xperience”, which is wrong!! Of course, the MKitFPDF plug-in solves some problems but brings some others, without to say it’s not free.Did someone got a real fix for this?

Hi Figma team and community,This is related to a similar issue reported here:MCP rate limit not acknowledging subscription I'd like to suggest an improvement to the error messaging around API and MCP access for Dev seat users.Current situation:When a Dev seat user tries to access a Figma project via the API or MCP without having edit permission granted at the project level, they receive this error:> "You've reached the Figma MCP tool call limit for your View seat on the Professional plan. Upgrade your seat or plan for more tool calls."This is misleading in two ways:1. The user already has a Dev seat — not a View seat.2. Upgrading the plan is not the fix. The actual issue is that edit permission hasn't been granted for that specific project. There is

When using Auto Layout for an entire page flow, not everything is spaced equally. For example, imagine a page like: Toolbar Heading Paragraph Input Button To put all of these into a single Auto Layout and give equal spacing to all of it is not typically how it’d work (eg, Toolbar + Heading might be close together, but more spacing around above and below the Input). To use the benefits of Auto Layout, I wrap these objects into their own Auto Layout frames and then use the padding within these nested frames to create the spacing between elements. It’d be great to be able to apply margins to objects (like text frames or other frames) without having to first nest them into their own individual frames. This would be closer to how CSS typically works as text elements (h1, h2, p, …) don’t need to be nested in a div to have margin added to them.

I’m surprised that after three years, FigJam still doesn’t support vertical text alignment in shapes. This has been a longstanding request (as evidenced by this older forum thread), and it’s a must-have for creating clean and professional-looking diagrams. Being able to align text to the top, center, or bottom of a shape is a standard feature in most design and diagram tools, and its absence in FigJam makes it harder to organize content quickly and consistently. Please consider adding vertical text alignment options to improve productivity and the overall user experience in FigJam.

ProblemIn Figma, comments are not preserved when duplicating pages, frames, or sections. This creates a major gap in workflows where teams need to iterate on designs while maintaining a record of client feedback.This has been a long-standing request from the Figma community for years, and continues to be a significant pain point.Real-world use caseIn a typical client workflow, we:Collect feedback directly in Figma via comments Duplicate a page or create a new version to begin revisions Need to reference and resolve original feedback as changes are implementedCurrently, duplicating a page removes all comment threads, forcing teams to either:Manually recreate comments (time-consuming and error-prone), or Constantly reference a separate file/page, which breaks workflow efficiencyImpactThis is a huge pain point across our

It would be super useful if unselected annotations were omitted while a specific one is selected. As is, annotations can make the interface extremely cluttered depending on the level of specificity added and it's hard to identify which element each note refers to. Simplified example bellow.  

The provided palette for text color is not accessible. Most colors do provide sufficient contrast against the white canvas.  I understand the second row of colors would be useful when the text is placed on top of color/darker surfaces, but the colors on the first row should at least meet AA over the white background of the canvas. Otherwise one is forced to always pick a custom color if the background is white, or from the few that provide the most contrast.

Sometimes when too many tabs are open, their names are getting truncated and it would be quite difficult to jump from one tab to another. E.g. tracing a component back to design system to check master component and documentations before jumping back to working file, it would take some time to locate where the working file tab is. Suggesting a feature to incorporate a search bar (collapse if it’s not activated) or even just a keyboard shortcut to let user quickly scroll through and search among opened tabs. Something like command+tab in macOS or control+tab in Figma but with better visual and thumbnails.

So this boggles me. Why can’t I change (override) the opacity of a referenced color-variable, without having to detach it? To me a color and an opacity value are two different things. So if I want an opacity on my referenced color e.g. “Blue-950” I have to detach it and change the value to my liking, now it is not referenced to the variable collection anymore. A workaround is to add that “Blue-950” with the desired opacity in the variable collection and then reference that new “Blue-950-50-percent”. It is so annoying that you can’t change opacity on the fly without loosing reference!!!

Hi, We are using Devin in our Org widely and integration with Figma for Read and Write operations are unavailable at this moment, when can we expect Figma MCP for Devin? Thx 

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

Please can we get percentages for variables? We can use percentages manually, but we can’t create a percentage as a variable. This would speed up my design to dev process tenfold, and considering we can already use percentages in the design, why disallow it in variables?An example is I want store values for line height and letter spacing as percentages which behave responsively/dynamically, so when creating type variables I don’t have to do manual calculations, store 10+ letter spacing/line height values based on which font size they will be used with and hope I never change the font size variable in the future.

Hey folks! 👋 I was using Figma’s Swap Library feature recently and came across a little hiccup that I think could use some improvement. You know how it works: when you swap libraries, Figma tries to match styles between the old and new library based on the token names, right? But… when there’s a name change or a slight difference in naming conventions, it just says “None found,” and that’s it. 😅 You’re left with elements still tied to the old library, which can be a bit frustrating, especially when you’ve spent time updating your naming structure to make things more organized or meaningful. What’s the Ask? Can we get

I would love to be able to create one prototype across the pages in a file that resembles an actual website. This would be ideal for bigger projects and would be easier to maintain as well. We can connect the component libraries across all the pages anyways. A way to connect the prototype would be great in my opinion and that will give Figma a big leg up on other platforms. What do you guys think?

With "Text-wrap: balance" headlines could be made more readable and visually appealing.Here’s how it could look: 

Hello, it would be nice to have the option to insert floating components inside text (like Emojis). Use case would be for signs or infos in complex dashboards. Its a hustle to do this now manually and also set kind of boundingboxes to sync different heighs of text and component. Regards

Stamps currently display the name of the user who placed them, but not when they were added. It would be very useful to also show the date and time for each stamp. Our team uses stamps to mark completed items. Being able to see exactly when a stamp was placed would help us better understand progress over time, track when decisions were made, and improve async collaboration. Suggested improvement:Show the date and time together with the user name on hover. This would make stamps significantly more informative, especially for teams using FigJam for workflow tracking and status updates.

It would be great to be able to merge two variables into one, so anywhere where either variable is referenced, the references will now point to the single, merged variable.

When I write create long paragraphs with text tool on the Figma I get the unnecessary spaces on edges of the paragraph like below. But I think if there a hyphenation feature (like Adobe Photoshop) it could add dashes automatically on the texts and fix this issue.

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.