Share Your Thoughts

This is tiny, but would help tremendously to be efficient with keyboard in Figma. Every time I’m changing icon size (or any other size) I use multiples of 4px. Here’s the process:Select {{element}} e.g. icon Press ‘k’ to activate scale tool Default active input is the multiples, but it’s harder to figure out what is the multiple of getting from 24 px to 20 px as opposed to writing 20 px in the input When you press tab it iterates over anchors and eventually get you to the top of the menu, so you have to use mouse to click above to either Width (W) or Height (H)   Proposed solution: Make the default active inp

Hi,I think it would greatly improve the starred pages in the sidebar if you could organize them in separate folders or categories. Now it is one long list that makes it difficult to easily find what you’re looking for.

Describe the problem you’re experiencing and how your idea helps solve this I like to work on my iPad Air with Apple Pencil. It’s great in Miro app. Lets me deal with comments or make small adjustments while away from the big screen. Now Figma is not very useful on mobile browsers. Most tools are disabled. One workaround is Figurative app but that is only marginally better and not developed for the last few months. Add as much context as possible (screenshots, Figma files, mockups, etc.) Ask questions to bring the community into the conversation (e.g. Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?, etc. Anyone tried this on Android tablets? Some funky workarounds like connecting keyboards or hacking browser settings? I guess it’s okay on Windows based tablets and convertibles, at least non ARM based ones. What about phones?

Enhancing Component Flexibility with Slots: A Real-World Scenario"We often find ourselves needing to edit content within a component instance without detaching it. While a 'change once, update everywhere' approach for simple variant states is great, we really need more flexibility within those instances."Understanding the Power of SlotsThe Slot feature introduces a powerful new component property acting as a designated placeholder within a master component. This allows components to achieve both rigorous standardization and dynamic flexibility. Designers can now freely swap, add, or remove content and structural elements inside a component instance, all without ever having to detach it.When combined with Auto Layout and other Component Properties, Slots make components significantly easier to manage and far cheaper to maintain. This approach is partic

Is anyone else running into a lot of memory issues since upgrading to UI3?  Seems the memory management is worse than it used to be.Getting memory limit errors on files that seems much too small to justify them. Had an issue where I could not merge a branch back into main due to running out of memory.  Even running the operation on a PC with 96 GB of ram (yes, ninety six) did not fix the problem (what? HOW?!) I just tried to disconnect a bunch of frames from their component masters (with a lot of nesting) and the operation failed.  First it asked if I wanted to reopen in recovery mode.  Then the interface just went away and left me with a blank window.I use a lot of nesting to make my mocks responsive, and I build everything from components so I can use properties to configure each one how I need.  My approach has always been hard on Figma and performance regularly ground to a halt, but this behavior feels new.  Is anyone else dealin

There is no easy way to collapse all text styles and groups in the variables window. Even adding Option/Alt click ability like you can for the Layers panel would be helpful.

I noticed a few posts about this but they were closed.In Settings > Billing, the ‘Payment details’ modal does not show a payment method, and I don’t know if I have one on file or not. What is shown here creates the assumption that there is not one on file.  I understand that the billing invoice will show the card brand and last four of the payment method, but in my case for example, on an annual plan, the last invoice was nearly a year ago and I’ve changed cards since then.I could just fill this out again(?), but I think the management of it could be improved.It should show the payment method on file, and include typical options seen on other sites that accept pa

HiI think it could be very practical if we could resize these panels. And that they would maintain that size individualy.It’s a bit annoying to scroll so much.Thank you  

HiI think it would improve productivity a lot if we could scale objects with the selecting tool and pressing CTRL while dragging handles.Thanks

Hi Figma team and community! 👋As a product designer who frequently works with complex layouts, I've really appreciated the flexibility of Auto Layout. However, I’ve noticed a few limitations with Grid Auto Layout that I believe could be improved to make the design workflow even smoother.Here are my suggestions: 1. Remember previous Grid settings when switching backWhen switching from grid auto layout to horizontal/vertical layout and then back to grid, it would be great if Figma could remember the previous settings (e.g., column/row count, spacing). This would save time and avoid repetitive reconfiguration. 2. Add “Fill”, “Fixed”, and “Hug” options to Grid Auto LayoutCurrently, these sizing options aren’t available in grid m

Example: Variables and modes created for different values at breakpoint sizes Components created with those variables applied In addition to number variables (spacing, widths, etc.), variables for nested property switches are applied per mode to accomplish changes that aren’t currently variable types (scales, font sizes, visibility, etc.) The goal is to allow for components to be responsive via automatic application of property values, whether top level or in nested components. This is primarily of interest to our team in Design mode but I think it would be useful in Prototype mode as well. That way if a component constructed with nested property variables is placed into an “iPad” mode frame, its nested properties also get set to the properties/variants that make the display correct for the iPad mode. Currently without this support, trying to convert components from supporting device sizes via variants to via variables turns into a

On the grid. Can you make the sizing dots available on all sides so don’t have to scroll to edit sizing. I know you guys looked it already, but if there’s a way to make adjustments based on the lines rather than the dots, it would be helpful! I’d also like to be able to set breakpoints on the grid boundaries with variables. This would really allow me to replace too many layers with grid and build tables with grids. Cant really do this now.

A productive feedback software fosters productive feedback culture! What I experienced in your Forum / Issue Tracker:✅ The forum guidelines recommend “Search before you post”. ❌ But the search function is currently very mediocre!Please make sure that one can least…Decide in which fields search shall match: Title, Body, Fulltext. (e.g. Github in:title) Highlight where the query matched in your the search results . To quickly grasp relevance. Filter by issue status: Open, Closed. You have that data per issue, make use of it! Screenshots of the current experience:

I don’t think this used to be a problem, but since the new update it’s now full of bugs and I really miss the old UI. The bottom menu is a waste of space, just put it back in the top and let us use the short cuts! I have a habit of creating components outside a frame and I noticed that recently, it’s super hard to select objects grouped by auto-layout! I’m forced to put the whole thing in a frame just to do this or it will drag out individual element eventhough they’re all inside an auto-layout! Another thing about ‘Shift + I” shortcut for inserting components is that it will always prioritize inserting inside an auto-layered object closest to my cursor rather than where my mouse key is pointing, EVERY SINGLE TIME.

Hi, I have been searching to disable the “Spell Check”. While the Online Guide explains it clearly where to find it, intuitively I wouldn’t expect it there.To me, Spell Checking is either a user-setting or a preference of the application, not specific to the document or whatever I’m currently editing. I would suggest either moving or adding the “spell check” to the user-settings dialogue or the application-preferences.Option AOption B Let me know what you think Regards Lukas

Every good forum usually has a “meta” category where to submit shortcomings/proposals on the forum software itself.Due to lack of this I will post my Meta suggestion into the closest available category, which is:  Share Your Thoughts → Share Your Feedback.But I recommend you to create such a category, which is a best practise.

This is an easy-to-implement suggestion, with a lot of value for devs. Please add { position: sticky; top: 20px; z-index: 10; } to the note type name in the documentation https://www.figma.com/developers/api#node-types. It gets really frustrating having to scroll up to find out to which node type that propriety refers.

Widgets are hard to use, allow them to either be stored in the UI on the left (or right) similar to how the HUD is customisable in Adobe suite. Or allow the plugins to ‘escape’ the figma software boundary while in use for space.Also - I just wanted to send quick feedback from the app but ended up on a bit of a hike, to here. is there a way to just very quickly submit feedback from within the app?

I am able to create a table using the grid auto-layout option. but I’m not able to reorder the columns or rows. It would be a great feature.

Need something like this plug-in  to be supported natively. Exports AVIF and allows default presets to be configured with preferred compression and scaling.

HiJust wanted to give a general UI Pro feedback.I work with design software for more than 20 years. I adapt very quickly to new options and I consider myself very selective with what I work with. Working with Adobe since the beginning, I added Figma to the toolset a couple of years ago.I have a mix of the best tools (for me) for my line of work: Illustrator, InDesign, Photoshop, After Effects, Bricks Builder, Audition, VS Code, Dreamweaver (stopped using it after nonsense updates) and Figma. I consider myself an advanced user in all of them.This is not to grab myself, it's just to accentuate the fact that I have a strong working instinct and experience with these kind of tools. What they all have in common is the fact that they are built for professionals: optimized for productivity and with a consistent and customizable UI. And that's also the fact they last for so long. Figma appea

Hi I’ve got a “big canvas” habit in Figjam mapping out new project ideas and working through problems.  It would be handy to be able to add fix navigation points in my canvas that I can jump between when talking to a new customer to share my ideas - currently having to do a lot of zooming in and out to find the right spot.Interest if this could be added to the roadmap or whether I’ve missed an existing feature?

I can’t figure out how to do this, looks like it might be supported. This keeps the feature from being more usable for me because I need to be able to hand-off some assets as some kind of editable vector image that clients can download and open up on their own programs for any needed touch ups.

When I select an element in a component or component set to add a boolean property, Figma displays a modal window showing the list of available properties. But boolean properties with long names are truncated without any option to disclose the full name.Please Figma should provide a resize capability or tooltip option for the modal to make it more accessible.  

Description:I would like the ability to create variables directly from a selected component in the canvas or assets panel.  Current Behavior:Currently, to create a variable that references a component, I must manually set it up in the Variables panel, which involves multiple steps and disconnects the workflow from the component itself. Proposed Solution:Enable a right-click option on any component (or an option in the top bar) to “Create Variable from Component.” This would automatically populate the variable name and link the component instance as the value. Benefits: Speeds up design system setup Improves discoverability and adoption of variables Enables more modular and scalable design tokens