Share Your Thoughts

It’s been mentioned before but the work flow we use for branches is by a custom task ID. Being able to just search that task ID in the search bar and it show the branch would make it so much easier for everyone in our team including devs to locate branches etc. Is there any plans to make these branches searchable in global search?

When I press Command + T, it opens a new file window where I can create, search, or select a recent file. I usually use this to open my existing files. I used to use this process to open my existing file.If there were a keyboard shortcut to directly focus on the search bar, it would make it much easier for me to quickly open an existing file without using the mouse. 

Hello Figma Team,I’m a frequent user of the Figma app on macOS, and I’d like to share a small usability suggestion that could help prevent accidental interruptions during work.When using the app, I often press Command + A to select all elements. However, because Command + Q is very close on the keyboard, it’s easy to accidentally trigger it. When that happens, the app quits immediately and the current window closes, which interrupts the workflow.It would be very helpful if the macOS app could include an optional confirmation dialog before quitting (for example, “Are you sure you want to quit Figma?”), similar to what some other applications implement. This could help prevent accidental closures caused by nearby keyboard shortcuts.Thank you for building such a great tool and for continually improving the product experience. I hope this small suggestion might be helpful for the team to consider.Best regard,Bowen

Dear Figma Team,I love that you have already implemented slide nesting in Figma Slides:Meaning there isn’t only 1 level of hierarchy of slides listed in the lefthand sidebar, but I can actually nest slides to be “secondary” to a main slide, then while selecting the main slide I can choose to collapse or expand the list of nested slides underneath it.I have always appreciated Apple Keynote for having up to 5 nesting layers.I always use this feature to be able to go through a high-level presentation and then dig deeper on individual slide’s topics / subtopics during the conversation following the presentation.Seeing that you already implemented nesting, all of the controls to actually nest a slide (drag and drop), expand and collapse a parent slide, I wonder why you limited this feature to 1 nestling level: a main level and one nested level underneath.I would greatly appreciate if you could remove this constraint alltogether or up the number of allowed nesting levels to 5 as Apple Keynot

SummaryFigma’s text UI supports OpenType alternates for editable text through its typography controls. However, this capability is not exposed in the Plugin API.The Plugin API currently appears to expose only read access through openTypeFeatures and getRangeOpenTypeFeatures.There does not appear to be a way for plugins to apply OpenType features or alternates to a text range.Because of this limitation, plugins cannot implement typography workflows that apply alternate glyphs while keeping text editable. Key DistinctionsIt is important to note that this request focuses specifically on Discrete OpenType Features (e.g., salt, ss01, swsh, onum) rather than Font Variations (Variable Font axes like Weight or Slant). While Figma already provides some control over variable axes, the ability to toggle specific glyph substitutions via API is missing. ExampleImagine the word: babelSuppose the active font provides several alternate forms for the letter “b”.A user may want to select only the first

It is imperative that Figma address the issue of editable text in PDF exports. Clients, legal teams, accessibility—all need editable/scannable live text. Please!

Hi! Turning off “snap to pixel grid” in a Figma Design file no longer changes snapping behavior when dragging frames around. Whether this feature is turned on or off, a dragged frame still snaps to each pixel, no matter how zoomed-in. Note that some other objects (e.g., vector objects) still respect this setting. It’s just an issue with frames, components, and component instances. Note that If I group the frame, I then can drag the group to any sub-pixel location. I’ve restarted my machine, restarted Figma, checked for updates, reloaded tabs, tried it in other design files. Tried it in the client, in Chrome, and in Safari. Same problem. Can anyone else replicate this?

Hi everyone!Wouldn’t be useful to have the ability of creating instance clones that mirror the state of the original instance?Reading this closed topic () I found out there are other people interested in this idea, where changes you make on your instance (text, spacing, size, etc.) are automatically replicated to your instance clone. So the structure would be: master component > instance > instance clone. It would be even better to have the ability to override the clone, so certain features get automatically updated while others, the overridden ones, remain the same. 

Recently I unpleasantly discovered that anyone with view access to my file could duplicate it to their drafts. When trying to prevent this privacy and intellectual property leak, I discovered a way to block this by adjusting my sharing settings and unchecking the option:However, soon after my developers realised that they could now not export icons.  It seems like a way to control the posibility to fully copy a design file should be independent from the capability from exporting content to non-editable formats. Unfortunately, I cannot find a way to do so. I currently have to choose what to jeaopardize, our design's intellectual property or developers work.Please let me know how to keep my designs files safe from duplication without impacting production. Thank you.

Sometimes I want one boolean component property to both show something, and hide something else. It would be cool to be able to not only assign a boolean property to layer visibility, but also to indicate that it should show the layer if the property is false. Example scenario: Imagine a situation where I’m designing favourites section on the app’s sidebar. I want a sidebar to be a component. Now when favourites is empty, I want to show an empty state with a CTA instead of the CTA. And I want to add a toggle that both hides an empty state, and shows a list of favorite items.

UI UX is mainly focus with the User’s Interaction and Designs, various basics that most of the UI and UX designers need to know to measure the interest of the customer, business processes, and product reach. UI is the activity of teams to collect requirements from the customer or organization, and UX is the complete front-end process, as per the interaction with the user and requirements gathered by the UI team. UI UX Designs can be practiced at [url=https://www.fitaacademy.in/]FITA Academy[/url] with intensive and exclusive programsAlso check: [url=https://www.fitaacademy.in/ui-ux-designer-course-in-coimbatore/] UI UX Designer Course in Coimbatore[/url] | [url=https://www.fitaacademy.in/ui-ux-design-course-in-tiruppur/] UI UX Designer Course in Tirupur[/url]  

I use figma for a lot of subtracting and a bit more complex workflows, i would love to use figma’s tool more but working with pages that lag each time i make a change, cause of figma using only a few gb of RAM (I have 32) and only a single core is really annoying. Currently i use figma to design for game interfaces games and changing softwares is really not an options for me so adding this would definitely help a lot.

Why can’t you underline text styles? I get you could just have text underlined in your design system, but it would be nice to simply add an underline to text while you’re designing as well.

Every time I paste the copied YouTube link where the YouTube video is supposed to start at a specific timestamp it starts from the beginning. When I paste the link into the browser the video starts in the correct spot. Has anyone else experienced this and found a way to get the link to start at the proper timestamp?Figma Desktop App version 125.5.6MacOS 15.5

Feature request: Make variables accessible via floating modal optionally.I’m building a personal portfolio and I don’t have a design system or library. I have also not designed several mockups beforehand, so I’m designing inside Sites. For a very small project like this, it’s not unreasonable. However, I’m finding it incredibly difficult to use variables in the same way as I have been doing so in Figma Design. Previously, I could eyedropper colours from my designs and seamlessly create variables because these could be managed from a floating modal. Changes made to my variables could be seen updating live in my designs because the modal could be moved around and did not completely obscure my design. In Sites, I need to constantly be switching between my file and the variables view, this for each variable I want to add and each time I want to make any modification to my variables.I understand that features are different from one Figma product to the next, but if a feature exists across 2

Add the ability to activate prototype effects when a user scrolls to specific vertical positions.For example: Trigger an effect automatically when reaching a certain Y position (e.g., 1836px). Trigger an effect between two Y positions, starting at one point and stopping at another (e.g., start at 1836px, stop at 1936px). This feature would make Figma Prototyping far more powerful, enabling precise scroll-driven interactions and animations across designs.

So the conclusion of today's update is that it is not easy to use and is prone to component explosion. It is only used in specific scenarios and is not as comfortable as using large components and instances. If we add slot content for switching in the future, there may be many gameplay options. Moreover, it is interesting to convert slots into components without using them. However, the problem now is that if I create a slot, about 3-5 components will be generated, which will explode later on

Hi Team,Super excited about slots. I was at the Figma Sydney event yesterday, loved hearing Zoe talk about the process. I’ve been trialling it out today. I notice that we have started putting slots into some of our DS components, particularly helpful for the the input field component, which is roughly 44 px high.I notice that if I have an instance of an input field into my design and try and use the slot in the leading icon spot, if my browser or window is zoomed out too far, I notice that the pink ring shows up but the tiny plus in the middle to add the component. I have to zoom in in order to see the plus icon and then interact with slots, because I notice that the area around or the pink field itself is not directly interactable.  Loving it otherwise!

I have created some slots for columns in my table component and I cannot duplicate them from the parent component instance. Sometimes it works and sometimes it doesn't. To solve this, I have to add a duplicate using the + button, and then they can be duplicated without any problems.

Is there a way to reset the prototype with an interaction without forcing the user to press R to reset? I’d rather continue the flow and just reset some key components and variables rather than take them out of the flow and start the whole thing again. Resetting variables is OK, but there are a few components (an add to trolley one for example) I need to reset back to its original state but I don’t see a way to do this.

My suggestion for Figma is to add a “slot” functionality to components. This would allow designers to create more flexible and customizable components, by adding empty slots or placeholders within a component. Users could then insert their own content or elements into these slots, without having to ungroup or modify the component itself. This functionality would save time and increase efficiency for designers, while also promoting a more consistent design system across a project or organization. I believe this feature would greatly enhance the flexibility and usability of Figma’s component system, and would be a valuable addition to the platform.

Request for a new feature of dividing flows into sections and the ability to show/hide flows in prototype view’s left sidebar. When flows are added in a section flows in each section can be shown/hidden in prototype view.

Feature Request: Native Lottie (.json) File Support in Figma PrototypesSummary:Please consider adding native support for Lottie .json files within Figma prototypes, allowing designers to preview and interact with lightweight animations directly in the canvas and prototype mode.Why This Matters:Lottie animations are widely used across mobile and web platforms due to their small file size and rich visual capabilities. Currently, Figma only allows Lottie integration via plugins like LottieFiles, which limits functionality to static previews (GIF/SVG) or external exports. This creates friction in the design-to-development workflow and reduces fidelity in prototype presentations.Benefits of Native Support:Real-time playback of .json animations in prototypes. Improved design accuracy and stakeholder communication. Seamless handoff to developers using Lottie in production. Competitive parity with tools like Adobe XD and Framer.Suggested Implementation Ideas:Add a native Lottie layer type or c

Hello. I’m creating a design sandbox with some instructions for designers. I want to use images as instructions and I want those images to link to another page in the file. Is it doable? I tried doing it with prototype settings but that only works when file is viewed as prototype and that’s not what I need. Thanks

HelloFor years, Figma has been the gold standard for interface design. It’s fast, collaborative, and somehow manages to make design feel fun again. But even with all its brilliance, there’s always been one small—but incredibly frustrating—gap in its system.Figma doesn’t have subpages.And honestly, that’s wild.The chaos of one giant pageIf you’ve ever worked on a complex design system or a product with multiple flows, you know exactly what I’m talking about. You open a Figma file, and suddenly you’re staring at 200 artboards, 50 prototypes, and a sea of arrows that look like someone spilled spaghetti on your screen.Sure, you can organize things into pages. But those pages quickly become their own mess. Before you know it, you’ve got 25 of them—each representing some combination of “v2,” “final_final,” and “do_not_touch.” Not to mention the pages for design system tokens, experiments, and archived explorations.It’s not that Figma’s organization tools are bad—they’re just flat. And that’s