Suggest a Feature

These are new and improved color formats that replace hex and rgb. They will soon become the standard in web browsers. They open up more colors than are currently possible. The Expanding Gamut of Color on the Web | CSS-Tricks - CSS-Tricks

Reopening this topic as it was the closest topic I found on this was closed a while ago.I’m wondering how the community is going around not having this feature in Project folders? I agree that having that level of organization in Projects helps a lot to keep clear paths to past work without the need to Archiving. Any recomendations on how you address this while Figma doesn’t have this feature available more than welcome! And happy to provide more insight if the ask isn’t clear. 

I know this has been requested a handful of times but want to riase again. I would love to see the ability to add sub folders within project files. I work for a large organisation in which we have multiple teams and products. I work within the website team which has a whole bunch of delivery squads within in. We use the current project folders for each of our squads. The enables us to keep all the squads under one website team within the organisation structure. Having sub folders would be super beneficial.

It would be great if there was a way for Figma to retain the crop settings on images of the same/similar dimensions so that we don’t have to re-crop each time we swap images in Figma Slides (and any other Figma program). This is especially helpful for showcasing product mockups, where we may want to frame more tightly around a logo and avoid resetting the crop every tie we change it out. See below for examples -- when dropping in a new photo that has the same dimensions as the original photo, it keeps the “Crop” settings applied in the fill panel, however it behaves more like “Fill” as it reverts the fill dimensions back to the width or height constraint of the frame. It would be great if replacing image fills functioned more like InDesign, where it maintains the proportions of the image inside the frame rather than of the frame itself.   

Can you guys make the file management system a little more packed up. For example, A folder for personal Files, another for for templates and Favorite is already there… it will be so much helpful for some of designers who had a lots of personal practiced project… Thank you…

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.

Hello! I use Figma for large projects and really, really don’t want folders within folders. Straight to 3-4 levels Can you add such functionality?

Figma is a powerful design tool that allows designers to create and collaborate on projects seamlessly. However, as the number of projects grows, organizing your workspace can become a daunting task. Finding specific projects can be difficult, especially if your workspace is cluttered and disorganized. Fortunately, Figma provides users with the ability to create folders and subfolders to keep their projects organized and easily accessible. One of the most useful features of Figma is the ‘Drafts’ section, which allows you to save incomplete or unfinished projects. This feature is especially handy when you need to work on multiple projects simultaneously, but don’t want to clutter your workspace with unfinished designs. The ‘Drafts’ section gives you the ability to save your progress, so you can come back to it later. To add a folder to your Drafts section, follow these easy steps: Click on the ‘Drafts’ section located on the left-hand side of your Figma dashboard. Click on the ‘Create

Please answer the questions as soon as possible. Any approximate date to next release.

Figma make has been super useful! I like that you can click elements and there are basic things you can edit, such as font, size, spacing, etc. It would be even better to take it further by allowing basic editing right in the file, without having to go as far as creating it into a design file.For example, I wanted to delete some text elements. Or change some text, move a couple things around. These simple things are a lot faster to just do yourself, than ask AI to do little things and wait. Then you might not even like it and want to change it back! Sincerely, I’m impatient and also like getting my design hands dirty.

It would be helpful if pressing the ESC key could cancel an ongoing drag operation when a user accidentally clicks and starts dragging the wrong object.Currently, the only way to undo this action is to use Ctrl+Z, which adds an unnecessary step. Allowing ESC to immediately cancel the drag operation and restore the object's original position would make the workflow faster and more intuitive.This behavior is common in many other software applications, so users are already familiar with it. Implementing it would improve usability and help prevent accidental changes.

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

I use percentages in a project for the letter spacing. I can’t use variables to achieve this value. It always defaults to pixels.

ProblemWhen a layer has constraints set to Bottom (MAX), the constraint only takes effect when the parent is resized. If you manually change the layer's height in the properties panel, the top-left origin is used — the layer grows downward, and the bottom edge shifts.This creates an asymmetry with the Left/Top (MIN) constraint. A layer pinned to the left at x=0 naturally stays in place when you change its width — x=0 doesn't need to move. But a layer pinned to the bottom at y=720 (in a 1080px parent) does need y to recalculate when height changes, and currently it doesn't.Expected behaviorWhen I set a layer's constraint to Bottom, changing its height should keep the bottom edge fixed and grow upward (y = parentHeight - newHeight). The same logic should apply to Right for width changes.Current workaroundThe only way to achieve this today is to wrap the layer in an auto-layout frame with a spacer above it. This adds unnecessary complexity to the layer tree for what should be a single-pro

Would be awesome to support a Webp file when exporting images like Sketch. (without using any plug-ins)

First and foremost, thank you to the Figma team for introducing animation features it has truly been a game-changer for digital design workflows. As we integrate these tools further into our UI/UX design process, a few key areas in animation management and export fidelity require refinement: Enhanced Animation Layering Control: Improved control over animation layering logic would significantly streamline creating intricate micro-interactions and layered dynamic components. SVG Animation Export Issue (Glass Effects): When exporting icon styles or components with glassmorphism effects (such as background blurs, multi-layered fills, or stroke effects) to animated SVG format, the effect rendering breaks or disappears in the exported file. A fix ensuring background blurs and layer effects are preserved in animated SVG output is essential. Native / Enhanced Lottie Export with Effect Support: Native, full-fidelity Lottie export capabilities—supporting advanced layer effects (shadows, blur

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v

Hi, I’m not sure if this is new since the May update, but I wonder why “empty” (all elements hidden) Auto Layout Frames keep the size of the last hidden child (and I do not mean last in the list, but the last element to have been toggled out of view by the user), making them not-0px high even with nothing in them. See here a file with a Frame with three hidden rectangle: the Frame keeps the size of the last child rectangle to have been hidden. When adding a 0-px Frame to the AL frame, and toggling this 0-px Frame off last, the container goes 0-px. In my opinion, empty AL Frames should have a height of 0. What do you think?

Far too often do I find myself having to change a component or other auto-layout layer between Hug and Fill Frame, and then double click and change its child, ad nauseum. This is very common in tables, where specific cases occur in which a cell component needs to be adjusted a certain way, and I would need to change from fill to hug, for example.It would be an enormous time saver to be able to cascade the sizing option down to all children in a single click. 

I often duplicate existing mocks to work on feature updates. Deleting previous annotations one by one is extremely tedious. It would be helpful if the tool could recognize when a frame has been duplicated and then allow bulk clearing of annotations.

When reusing Auto Layout across different frames or components, there is no way to copy and paste only the Auto Layout settings. Users have to manually recreate spacing, padding, alignment, and other layout properties, or use Paste Properties, which also applies changes they may not want. SuggestionIntroduce a dedicated Paste Auto Layout action that copies only Auto Layout properties. When pasting, a small dialog could let users choose which settings to apply, such as Direction, Spacing, Padding, Alignment, Wrap, and Clip content. This would make it much faster to reuse layouts while avoiding unwanted changes to fills, effects, typography, or other design properties.Addition!This could also work to fills, strokes, effects. ExampleRight click an Auto Layout → Copy Auto Layout → Paste Auto Layout on another frame. A dialog appears where users can select exactly which Auto Layout properties to apply before pasting.  

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. 

Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%). Interestingly …You can use a variable for letter-spacing ( which accepts a number variable - but reads it as a percentage) - the challenge remains that line heights by default are absolute not percentages - even though you can input a percentage. Percentages allow greater flexibility and less calculations Word around would be to allow formula in a variable e.g. =[variable] * 1.5 Or figuring out a way for the line height to be toggle between absolu