Share Your Thoughts

When renaming multiple frames or artboards at once in Figma, the numbering order currently follows the layer list order (as shown in the Layers panel), not their visual order on the canvas. This often leads to unexpected numbering (e.g., instead of numbering from 1 to 10 in left-to-right order, the names are assigned based on layer stack order). Feature request:Add an option to batch rename frames/artboards using their spatial order on the canvas (e.g., left-to-right, then top-to-bottom), instead of relying only on the layer list order—just like some plugins.

 Welcome to Kidsomia, the ultimate kids play zone in Manikonda! Enjoy exciting indoor play areas, fun activities, and the best birthday party venue for kids. Book now!

We often encounter the challenge of working with icon sets that contain a large number of component variants. When searching for a specific icon, it’s extremely frustrating that there is no search functionality available. Additionally, the lack of a sort option makes it even harder to find what you’re looking for, as the icons are not organized alphabetically but by the date they were added. This often results in spending several minutes just to locate a single icon, which is very inefficient and time-consuming. We would really appreciate having both search and sort functionalities integrated within the variant section of the icon component — especially for large icon sets that are all stored under one master component.Cheers,J

For comments that have been resolved, can the user avatars in the comment panel not be set to gray? It's quite inauspicious, as it looks like the person has passed away.

Currently not a way to rename colors in Figma slides with the library feature. Is there a way to do this that I don’t know about? It would be tedious to re-add a color with the appropriate name because I would have to reassign all components to the newly named color.

The new Figma update is just fine. I appreciate they tried to make the UI a bit more graphic, but in doing so - I feel like the program runs slower and the layers panel isn’t anymore intuitive, but now just clunky. One of the features I loved the most - manually adjusting spacing between elements, seems to have disappeared from the workspace entirely. 

In grid features Canvas Stacking (Last to Top/First to top) is not working properly

I’d love to see support for automatically renaming layers to match the filename of an image that's placed or replaced in a design. Right now, Figma uses the image filename as a layer name inconsistently—mostly during the initial placement, and not when replacing an image. This leads to extra manual work and inconsistent layer naming, especially when working with many assets.It would be incredibly helpful if Figma could auto-update the layer name to reflect the actual filename of the image fill—ideally both on placement and when replacing an image.Thanks for considering this improvement!

Alt text and tooltips are incredibly important for accessibility. But to show a tooltip interaction in Figma, (afaik) you need to create a custom tooltip/find out as a component and then create a show/hide interaction on mouseover in the prototyping. I would like to request that Figma allows for users to add tooltips to page elements, so that this functions per a standard tooltip — showing where the cursor hovers on the element, and with the user only needing to add the text (no need to create and hide a a text panel).

課題：PaddingやMarginなどレイアウトを調整する際、つい全角で数字を入力してしまうことがあります。しかし、こういった場合、毎回変換キーを押して全角→半角に変換するか、最初から入力し直す必要があり、少し手間です。提案内容：数字を自動で半角に変換するオプション---Problem:When adjusting layout values like padding or margin, I often end up typing numbers in full-width (Japanese input). To fix this, I need to manually convert them to half-width or retype them, which is a bit inconvenient. Proposal:Add an option to automatically convert numbers to half-width.

I love the intuitive “Ready for Dev” switch to signal a handoff state, and the working mode it provides our engineering partners.Before this state, however, we also have a need to review, incorporate, and track content updates. Related, there is also a step that requires regulatory review and approval.It would be interesting to see additional modes that cater to our other partners, much like “Ready for Dev”. I realize our content and legal/compliance partners can comment directly, but would be great to have a dedicated space for them to enter and track changes, before we hand off to engineers.

I really like Figma’s effort to build a mass-production system with Buzz, but I still prefer the Table to Figma plugin for five main reasons: Direct connection to Google Sheets Build your spreadsheet in Google Sheets and link it straight to Table to Figma—no manual export/import required. Layer visibility toggles A Boolean column (TRUE / FALSE) lets you show or hide layers. One simple exemple : This is essential when you need to display a dollar sign before prices for the English market but hide it for the French market. Bulk updates through components Turn elements into components and push global changes without re-importing the spreadsheet every time. Images handled via URLs instead of in-cell uploads Embedding images directly makes the sheet heavy and unwieldy—especially when I have to deliver 200-plus variants. Table to Figma lets me reference images with URLs, keeping the file light and the workflow fast. Variants and layouts driven from the sheet With “Variant” or “Layout

Could you please stop it? I don’t know how many times this happened to me as a multi user/multi team user I couldn’t find my files at the same place I left them and having heart attacks almost. Whatever your strategy on updates, it is really very shitty for the users-at least in my experience. I spent two hours just now to understand what you did with the navigation and why I can not see my project folders as I organized them before. At least keep our starred projects on the left side so we could find some things easily, maybe? 😮‍💨 You assume all designers have lots of free time to explore your new ways of navigation each time you update it and organize their files/organization structures accordingly? Most of us are regular working class people, just trying to fit some work-hours in our busy calendars and you are turning it to a big hustle for us just to find and open an existing file🤦🏻‍♀️ Stop using your time to adding new AI features maybe and put some real time to design and bui

It would be better to keep the comments in Figma history. Sometimes we resolved the comments and would like to recheck again what comments we solved. Sometimes I incidentally click resolve button and would like to see the comments again. At that time it would be great if we can see the comments in version history. 

English is difficult for me and I struggle with it. Hope to support Chinese language as soon as possible，please，please，please，please，please，please~

As already mentioned here:🔗 https://forum.figma.com/archive-21/make-figma-free-for-open-source-projects-21667It would be awesome to have an open source plan with more features — like unlimited public design files or access to some of the technical features from the Professional plan. ✨Maybe a good compromise could be a discounted plan — like $10/month — that includes variables by API and similar tools. 💡For open source developers working in their free time, the $20/month Professional plan is already quite a stretch — and $90/month for the Organization plan is simply out of reach. 😵‍💫All of this is just for public design files anyway — which helps promote Figma itself. 📢For private projects, I totally understand the need for stricter pricing. 🔒

Please, it’s time to reduce friction between designers and developers talking about responsive designs. Each website/application is different and requires a different amount of breakpoints, so using just desktop, tablet and mobile isn’t enough. Integrated support for breakpoints would be a breakthrough and would make a lot of developers happy.

Hi all,I’ve been building bar graphs and came across a suggestion for you.Have you thought about adding a percentage option in an auto layout?For example I have a bar graph with one bar entirely filled (300px = 100%) and other bars in incremental steps (30px = 10% increments) However, when I try to make this responsive and change the height from 300px to 400px, the incremental steps remain at 30px of a now 400px bar, so they are no longer increments of 10%.

Hi Figma team!I noticed Make supports importing only library components from Figma Design. Would be great to import a frame from a file for prototyping. My team’s design process is typically to start with a high fidelity screen which uses a mix of our design system and custom components. We want to link this source frame into Make so that we can get a functioning prototype for cross-functional team discussions. Is this feature being considered? Are there any recommended workarounds in the meanwhile?  Look forward to hearing from you!Best,Shaziya

It would be fantasitc to have an option where the presentation notes are somehow incorporated into a PDF, perhaps the slide on the top half and the presentation notes on the bottom half. This is great for 1) sharing the presentation as knowledge to other non-tech savvy stakeholders in a PDF format and for 2) printing out and practicing the presentation on paper if there’s an IRL component to it as well.

Recent effects like noise, texture, or progressive blur are not scalable. Since the sliders are limited to 100, scaling a shape linked to these effects will result in a different visual appearance, as the effects do not scale with the shape.

It would be incredibly helpful to see where a component instance is used across all files, not just within the current file. Designers working with shared libraries often hesitate to edit or remove a component because they don’t know which other files rely on it.A built-in Figma feature that shows which files and pages a component is used in would boost confidence in making changes and improve design system maintainability.

Although the new version of the color filler can clearly see more configurations, you can't directly fill in the HEX value. You must open the filler and select the HEX mode to fill it in. It is not in line with an excellent interactive design experience. I hope it will be modified in the next version. In addition, each major version change of figma will lead to a lot of additional learning costs. I hope the product manager can reflect on it. Finally, thank the team for providing such a useful tool.

Hello Figma Team, First of all, thank you for your continuous efforts in improving Figma. I would like to provide feedback regarding the slide feature (using frames as slides for presentations or documentation).Currently, there is no option to set custom aspect ratios (e.g., 16:9) or manually adjust slide frame sizes, which creates limitations when designing and sharing content across different environments. In particular, as mobile-first content consumption increases, there is growing demand for vertical slide formats (e.g., 9:16).However, the current slide feature seems to be optimized for horizontal layouts, making it difficult to work with vertical slides without unwanted whitespace or layout distortion. Additionally:  There’s no way to freely set the aspect ratio or size of individual slide frames. The display output for slides is fixed, which often causes layout inconsistencies in real-world presentation or documentation use cases.  If the slide feature allowed custom frame rat

When using Figma web on an iPad, it is possible to unintentionally move content and accidentally ruin a design because an item can be selected and moved in a single gesture. Many iPad apps including your own Figjam app solve this by requiring a tap and release gesture on an object to select it before allowing it be manipulated. Given that a single finger drag on a blank area currently invokes the selection box, please consider making this the default behavior until something has been explicitly selected. Or make it so a single finger pans the canvas like Figjam and create parity between the two.