Suggest a Feature

style 

It is not obvious in the default view of an open document that the user needs to create a frame as a canvas to start a design. Suggestion to either have a visual tooltip pointing to the frame icon in the toolbar alt. a “create frame” button centered on the main area/window. 

I think it would be much easier to use annotations if they were highlighted when hovering or selecting an asset / frame / object that had one attached. Right now it’s a bit overwhelming trying to find the right line.  

It would be great to have the option of setting a max-width of a grid. Elements would stretch but always with a maximum value.

I’ve created this UI for Narrati through claude ai, I am not sure how to import this UI to figma, If there any figma AI which can convert screenshot into figma design, I want to shift this website to framer, thats why looking for a solution.Framer websites & figma is very same, if there any way to make screenshot to figma design, building framer websites become so easy.

It would be great to be able to use multiple individual variables for effects. For example, I have a blur and a drop shadow saved as two separate variables. I don’t always use them together, but sometimes I do. I would like to be able to use both together, without having to create a separate variable with the blur and drop shadow.  

In trying to meet users where they are working we need to place documentation within Figma files. This means we want documentation for various personas. In our case, we need to provide documentation for consumers of our library and assets, and documentation for those creating the assets. Feature to propose: A way to expand security trimming (similar way in which we can share teams/projects/files) so we can place documentation within our file for creators and hide it from consumers.

Need:I would like to optimise the publishing of the different libraries and ideally manage it from a central place.Use case:I have one asset libraryI have one style libraryI have one component libraryI have multiple files for different features - Figma being still too slow to allow me to manage a whole application in one file.Let’s say all the feature files need elements from the three above-mentioned library.Now I change a color in the style library and as of today what I would have to do would be the following: Go in each dependent library and update all the elements that use the color from the style library Publish the libraries Go in each file to update the components in some cases publish some files so that other files can have the latest update of componentsThis requires to open many files and this could be “easily” optimised if there was a feature that allowed to create a pipeline that we can run everytime we update a library.Or another solution, have a centralised place in whic

Our design token collection (variables) was accidentally deleted. Would be nice if there could be a restore action or trashcan concept for retrieving deleted collections. Perhaps archiving could be interesting as well.

I’m really liking the new sections in FigJam (which I used to have to make manually with shapes) but I’ve noticed that the normal grid dots don’t seem to show up within the sections which makes it tough to align items within them that are farther apart (in my case vertically stacked sections). Would it be possible to get these added back in? Or at least some way to use/create guides (similar to those in most photo/graphics editing software)?

Decades ago when prototyping interfaces I would just use HTML prototypes, which made tooltips super easy to prototype.  Decades later with Figma - which is an excellent design and prototyping tool don’t get me wrong - adding tooltips to one’s prototype, is incredibly painstaking.  It would be so much easier if Figma just added a field for each layer called “tooltip”, which, when hovered over in prototype mode, would display the tooltip after a number of milliseconds (which could be customized as a bonus feature).  This would make Figma prototypes tooltip-friendly in such an easy way.  And from a designer-developer handoff perspective,  it would be great if Figma prototypes had a toggle to enable text selection in the prototype. That way the developer would just run the prototype, get the tooltip in context, and copy its text. 

Nice work including Typography and Gradients as variables! But I feel like the ability to use a variable for opacity when defining a color palette is missing. Which means the size of my color palette is double what it should be as you have to define each opacity as a separate variable.

The “Approve all” button in the Admin Dashboard is way too easy to click by accident. First, in some conditions the “View history” button is in place of the “Approve all” button. E.g. during loading, or when you have no requests. This way, if I’m on the “your requests” tab and there are 0 requests, and I want to go to All requests history, I go to “all requests” and click “view history”, but by the time I move my mouse to the “view history” button and click there, it’s suddenly replaced by the “approve all” button, because there are some requests on the “all requests” tab, and the “approve all” button is rendered with a delay. Second, there’s no confirmation of this action, which is very strange considering its importance. Figma needs to move the “Approve all” button so it doesn’t appear in place of “View history”, and/or ask for confirmation after clicking it.

Create a single logic for working with components from different sets, without the need to separately create one logic for some components, another for instances, a third for masters - options, they all allow you to do the same thing, only in different ways, which VERY OFTEN confuses beginners, it still confuses me, and it is very inconvenient, because it confuses the user in the structure of relationships between setsfor example, you allow changing components in instances through the ability to change a component through the swap panel of the instance, preset for all components, and also allow you to create a PROPERTY from such a component for another componentSimplify the logic, allow working with all components as properties, and in the properties create the ability to switch between properties for the component, and the instance swap property (properties of components from other sets), so you do not have to create an instance swap property in the master component instance every tim

Currently, you are able to use the ctrl+B command on a text style to apply the bold font weight to a desired string of text without breaking the text style. However, if you want to apply other font weights like light, medium, semibold, or black, you must either create a entirely new text style (which can add up quite quickly) or detach the text style and manually change the weight. A way to apply various font weights without breaking the style (in the same vein as applying different styling like bold, underline, and italic) would be extremely helpful in increasing a design system’s adoption and flexibility.

Right now objects can only animate “on click” or “after previous step”In Keynote, you can have object animations build in with other objects, and have a delay before the animations happen. This allows for some really clean build in animations and more control. Would be awesome to have in here as I’m trying to migrate away from Keynote to vertically integrate into Figma.

The other day my internet went out and I was frustrated to discover I couldn’t work on a design in Figma because by default it saves everything to the cloud. Please allows us to select an option where files are either saved locally instead of online or a copy is saved locally. It makes sense to have it in the cloud for the browser based app, but not for the desktop one.

Relatively uselessPlease either change or add the ability to see the actual date and time a document was created/modified instead of these relative values.

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. 

Hi. I see that macOS Figma App has iproj files for multi language but these files seems to be unused to allow user to change language ! Contents → Frameworks → Electron Framework framework → Versions → A → Ressources → fr.iproj Also the only proposed alternative is to use chrome browser and it extension gg translate , but this one can be intrusive ! I use only safari .

Hello, Figma team!I was hoping if we could add a feature in the asset library where in details panel we could zoom in on what we were seeing.Like you can see in the attached screenshot. It is very difficult to see the email. We are creating a component library for our team so that they can use these emails in any project but because it is so small people are having a really hard time looking at the email.Can we please do add a zooming feature here. With respect,Ayush MaanFigma pro user

Hi thereI think it would be a great timesaver if it were possible to choose which libraries are automatically added to new files within a project. At the moment I am constantly removing the default libraries and having to search & add the ones I want to each new file created. Being able to control this at a project level will reduce a lot of friction and repetitive admin, and is in line with the concept of keeping files as light as possible.Thanks team Figma for all your hard work on an awesome product!

At our company, we regularly share our Figma designs with clients for feedback. We also use annotations (comments/notes) to leave technical or developer-specific instructions. Ideally, we’d like those annotations to only be visible to developers (in Dev Mode), not to clients viewing the design.However, we’ve noticed that these annotations also show up in the regular design view — meaning our clients can see all those notes too, which isn’t ideal.Are we missing a setting or best practice here? Is there a way to completely hide these developer annotations from client view (not just manually hide them per user)? We’re hoping for a more foolproof way to restrict access to those notes.Thanks in advance!

Hey, can anyone explain the reason, why it is not possible to add dev resource in branches? It seems to be only available in the master, which feels weird. More context: In our case working with branches means the work that is reviewed before a merge must be complete so adding the correct dev resources is very likely part of review processes but the way its currently provided is for unknown reasons prohibited. Is that a technical limitation? Why is this the case? The fix would just be to add the plus button while working in branches, someone must have actively removed it to be unavailable in branches?

UI3 erased my muscle memory on where to go to adjust a layer’s position and layout properties. They now appear at different positions depending on what type of element I’ve selected. E.g. a component with a lot of properties will cause the position and layout sections to be completely scrolled off the bottom of the panel. This adds up to cumulative slow downs and increased cognitive load while adjusting these parameters across many layers quickly. And there is no good way to restore this muscle memory because the panels are always in a different position. Would love to see these moved back to the top or a way to reorder the panels via settings or something… Thanks!